Discuss the 4.3.22 release

[loukingjr]

On restart of VM, this Network Share listed as Disconnected Network Drive. All folders and files show for it. IF try to disconnect , not found.

sounds like the exact same problem socratis and I described.

[ChipMcK]

Well, USB Stick/Flash drives still work.

On restart of VM, this Network Share listed as Disconnected Network Drive. All folders and files show for it. IF try to disconnect , not found.

sounds like the exact same problem socratis and I described.

Auto-Mount is not "normal" usage for mine, thereby obscuring the problem.
Down-grade or Not ???? <sigh>

[loukingjr]

I just rolled back the GAs to 4.3.20 for all Windows guests < Windows 10 and everything is fine.

[ChipMcK]

Downgraded to 4.3.20 and in Windows under Network:VBoxSvr can not browser to the Shared Folders, stops at VBoxSvr.

[Eddie500]

Hello. I do not know if im in the correct forum, but this is the first for me and i would like some help installing vistual box. thanks

[loukingjr]

Hello. I do not know if im in the correct forum, but this is the first for me and i would like some help installing vistual box. thanks

No, you are not in the right section and how to install VirtualBox is covered in the user manual.

At least include some info such as what computer you are using, have you tried installing it, did you have a problem installing it, etc..

[Marebul]

Hi there,

4.3.22 is another disaster for me. Apologize for creating an useless topic (see here) but this time, I can't start any VM and I'm getting this message :

Thanks for the help and for getting VBox back to the stability

[pit]

- Shared folders is seriously broken across all Windows guests.
- My shared folder is setup as: read-only, not auto-mount, permanent.
- In the guest, you could go to Explorer, Network, and browse to \\VBoxSvr\SharedFolder.
- This fails with GAs 4.3.22 (\\VBoxSrv is empty), it works fine if you downgrade to 4.3.20 (even in place).
- Guests that it fails: 2000, XP, 7, 8.1, 10 (b9841 and b9926), pretty much every Win guest.

I confirm - have the same problem, only downgrade fix the issue

[fat cat]

I had a similar problem with adding Transient network folders to the Virtual Box 4.3.22, as discussed above. After a downgrade to 4.3.20 and the execution of the corresponding Guest Additions, I again had access to the Transient folder in the \\VBOXSVR\ network folder of my virtualized Windows 7, 32 bit. My host system ist Kubuntu 14.04.

[mpack]

Could all those having problems with GA features (such as shared folders), please make clear whether the problem is only with the latest GAs, or does it happen even with older versions of the GAs on 4.3.22 host software?

[loukingjr]

Could all those having problems with GA features (such as shared folders), please make clear whether the problem is only with the latest GAs, or does it happen even with older versions of the GAs on 4.3.22 host software?

Rolling back to the 4.3.20 GAs fixed shared folders for me while keeping the 4.3.22 host software. Shared folders never actually "broke". They just say "Disconnected Network Drive" and \\vboxsvr is empty. But the files in the shared folder are still there and accessible on the E: drive (on mine).

[Biite]

Hi there,

Anyone's got problems with PXE-booting VM's? After the upgrade to 4.3.22 from 4.3.20 my VM's fail to PXE boot.
I've got an HP Eliteboot 8560p with an Intel 82579 LM Gbit adapter running on Windows 8.1. Returning to 4.3.20 re-enables the functionality.

Tried different kinds of guest configs, e.g. Windows 2012 64-bit/Linux Ubuntu 64 bit/Linux RedHat 64 bit/Linux Redhat 32 bit, but it does not seem to make any difference.

Regards,
Biite

[mpack]

I have upgraded today and virtual machine does not start. I have opened ticket: 13827 .
What to do since I really need to have access to this virtual machine? Thanks.

@SamH: your host only has 2 CPU cores, so assigning 2 cores to the VM is probably not the best idea you've had. Threads are not cores - if they were then nobody would be paying a premium for cores.

[mpack]

@Marebul: You would probably be better off posting in the "Errors related to security" discussion in the "Windows Hosts" forum - and nothing much will happen anyway unless you provide the VBoxStartup.log file as the error message indicates.

[quickbooks]

Please take a look at this https://www.virtualbox.org/ticket/13653

Guess we are stuck forever with 4.3.14!

Also affects CentOS 7 host.


Note: if I use 4.3.14 host, and if the W7 guest has 4.3.20 Guest Additions I don't see the glitches.
So it is most likely a regression in the host code after the 4.3.14 release.