Upgraded to 5.0.14 and can no longer browse???

[bobmct]

Been using Virtual Box for many moons quite successfully. Today I upgraded to the latest version and now I cannot browse files when I try to define shared folders. Kind of stops me in my tracks when trying to connect an ISO for a new VM.

I tried to search for a similar issue without success. Hopefully someone reading this will have a solution.
Any suggestions/ideas greatly appreciated.

Thanks

[socratis]

I cannot browse files when I try to define shared folders. Kind of stops me in my tracks when trying to connect an ISO for a new VM.

The two issues are not related. Would you mind explaining in FULL detail what your problem is? "I cannot browse files" is too generic. We need details; host, guest, OS of both, etc., etc. Please read the following: Minimum information needed for assistance. As far as the "VBox.log.zip" goes, here's what you do:
- Start the VM.
- Record the error message. EXACTLY. Post a screenshot if you have to.
- Shut down the VM (if it hasn't aborted by itself).
- Right-click on the VM in the VirtualBox Manager.
- Select "Show Log..."
- Save it, ZIP it and attach it in your response.

[Just2Evil]

I found with Fedora that I had to add the vboxsf group to the list of groups the non-root user had access to.

Also found I had issues with the host-only adapter when upgrading to 5.0.14 and that I had to do a uninstall and reinstall 5.0.14 for the host-only adapter to function.

[jakke]

I've had big issues with networking after the 5.0.14 upgrade as well... hope a patch comes out ASAP. This is ridiculous that this has been approved to go live.
I had to adjust my network adapter on all of my virtual machines, going from my normal Windows network drivers to some unknown Qualcom drivers