#15932 closed defect (duplicate)
BrokenSharedFolder
| Reported by: | jim.rather | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.6 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
I am using CentOS7 as the host and Windows 10 as the guest. I have a shared folder on the host that is mounted by the guest. After a random period of time, Explorer or anything accessing this shared folder becomes "Not responding" within Win10. I get the Win10 "waiting" ring. Unfortunately, I never get an error message within Windows 10 or in the log files of CentOS7. To troubleshoot it, I tried to safe shutdown and/or reboot the Win10 guest, but it will not successfully shutdown. It must be hard booted in order to resolve.
When I try to "modify" the Shared folder settings on the host, I get an error that says "Broken Shared Folder". I do not know how to provide any more information like debug information or logs but would be willing to provide any details if instructed how.
Change History (4)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
I am experiencing the exact same problem. It started with a Windows 8.1 guest on a Windows 10 host. I created a new Windows 10 Guest, thinking my 8.1 guest was corrupt, and today I started experiencing the same problem on the new Windows 10 guest.
I didn't have the problem immediately after creating the new VM, and the Windows 8.1 VM ran fine for over a year (and several days on the latest VBox stable build). I suspect that this may be related to a recent Windows update.
I have not been able to narrow it down to a particular file or file type, however I have had it fail both copying files to the host and from the host.
follow-up: 4 comment:3 by , 8 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Most likely a duplicate of #15662. Please check the latest 5.1.x Guest Additions from the test builds page.
comment:4 by , 8 years ago
Replying to frank:
Most likely a duplicate of #15662. Please check the latest 5.1.x Guest Additions from the test builds page.
Thanks... I will give it a shot!


Sorry, I am using 5.1.6 with latest Guest Additions installed. I also believe this issue started with the Win10 anniversary update. I do not recall it happening with Win10 prior to this update but it has happened fairly consistently recently even through multiple updates of Virtualbox (5.1.x, etc.).