virtualbox.org

All the same conditions described here: viewtopic.php?f=7&t=79857 up to the end. I reinstalled guest additions and the drives do show up but they hang. I can click around here in there in the mapped drive but eventually it hangs. Where it's causing the biggest issue is opening a lot of files, for example, a Visual Studio project that is located on the share. This hangs and prevents projects from fully loading.

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

Log attached, thanks.
Edit.. re-attaching. Last one got truncated.

It's not clear to me why the log date is ten days old with Sep 17 2016.

Couple of things.

You are using the Arch distro version of VBox and not totally supported here. It may be something that is being changed from the original source because I can transfer GB's of data and hundreds of files with no issue.

Also I totally hate automount. Bad things happen for me when I use it, mostly permission issues. I would use the standard mount and make it persistent in the guest instead.

Finally is the W-10 guest the released version or the one they update all the time? I don't really do Windows but have read that it may be an issue with guest additions on the "ring" type.

Additional info in case it's helpful... The mapping is done via bat file specified in the group policy so they can be shared under all users with 'runas':
Local Group Policy Editor -> Computer Configuration -> Windows Settings -> Scripts (Startup/Shutdown) -> Startup

An example line in the .bat file:

Try what I posted and see if it helps. If not we need to move you to Windows guests because I really believe that is going to be your issue. W-10 is just too much of a moving target for the DEVs to keep up with on a timely basis.

Thanks Perryg, it looks like removing the automount did the trick. I can finally access a full solution without the hangups.

It's w-10 enterprise and the update was forced without a prompt. I use it daily for development and right after the update it just went south on me. The vbox arch package wasn't updated during the time frame so I'm guessing it's something in the w-10 client update.

Anyway, I'm good to go, thanks again!

Posting this update for those that may have googled their way here with similiar issues.

Removing the automount did help but not completely. There were still many of the same issues discovered when trying to do day-to-day work. The only way to get back was to rollback the win-10 update.

Thanks for replying back on your findings. I will move this to Windows guest now.