Installing 5.2 Extension pack disables the VB Shared Folders

[Don Hughes]

After upgrading to VB 5.2, all guests lost access to their shared folders (
VBOXSVR\)defined under VB Machine Settings. The shares are correctly defined and were working immediately prior to installing the VB 5.2 Extension Pack.

64 Bit Linux host various Windows clients.

[Socratis]

Can you please explain to me why you skipped all the instructions in the ticket opening page? And you went straight for the ticket? Without even changing a single option? I don't know what your host is, what your guest is. I don't see a log. And all options are "Other". Even the VirtualBox version in the ticket is 5.1.30, when you talk about 5.2.0!!!

Please fill in some information if you want some help. BTW, it's usually better and faster, if issues like this one (configuration, question) get first addressed in the ​VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Please be sure to mention that you came from the bug tracker and include the ticket number.

[Xbase++]

have report the same here https://www.virtualbox.org/ticket/17192 and got same (copy/paste) Answer ...

and YES, i have try many before report it e.g. create new Profile with new Network Card / NAT etc.

AMD FX-8350, Gigabyte 990-XA-UD3, 16 GB RAM Host : Windows 10 16299.19, 64bit Guest : Windows Inside 10.17017.1000 32bit

[Socratis]

@Xbase++
This is my standard answer no. 37, for all the people that think that opening a ticket will get faster results. It doesn't. Usually if you go to the forums you will get a faster response, plus a lot more eyes to look at your issue. If it has been established that a lot of people are getting the same behavior, then we direct people to open a proper ticket with logs and support diagnostics so that the developers can focus on the true nature of the bug. You didn't even bother to post a VBox.log. That's because you didn't even read the instructions, did you?

So, please, by all means, keep the discussion here, without any diagnostics or logs. You seem to understand what's working better.

[Don Hughes]

I apologize for getting the version wrong. I first upgraded to 5.1.30 and was testing that before I noticed that there was a 5.2.0 version which I then installed and forgot to make the change to the version. I tried to modify the ticket, but was unable to. Clicking on the version or modify links just takes me to the search screen; and the only choice under Modify Ticket at the bottom of the screen is "leave as new". Previously I have been asked to NOT fill in too many of the other fields since I am running a limited environment, and support is better able to judge if it affects just my type of hosts etc. or includes others; but I did mention in the body that I am running Linux hosts and Windows clients. I could not decide on the correct choice between guest additions and shared folder, so I left it as other. I spent some time searching for other similar tickets but all of the ones that I found either had been closed or were for versions several releases back. Again, in the past, I have been asked to open a new ticket instead of re-opening an old one for a different version because although the description may be similar it is likely a different problem. The log took a bit longer because it was on the shared folder that is no longer working.

I fail to see how this can be a "configuration, question", when these are systems that have been in operation for over 5 years and were working correctly right up until I installed the 5.2.0 Extension Pack.

And I was not "trying to get faster results". This defect is more than a minor annoyance - like the new device driver error messages that now pop up on launching a VM - this broke several running applications. I wanted to give a heads up to other users where this might be catastrophic.

Based on the just added notice: "Update: The Guest Additions image with the 5.2.0 release fails to work with recent Linux guest kernels.", I am not the only one with issues with the 5.2.0 Extension Pack. Although the notice says it is for Linux guests, it also solved this problem with the Shared Folders between a Linux host and Windows guest.