Page 1 of 1

Shared folders locking up guest

Posted: 25. Mar 2019, 23:19
by OtherPhilC
Running 6.0.4 r128413 on 64 bit Win7 Ultimate on Intel Core i5-2500.
Guest is Win7 Ultimate 32 bit.

There are 3 shared folder settings:
(Share, host path, access, auto mount, guest drive)
Share1, Q:\, Full, Yes, Q:\
Share2, L:\VBoxdhares, Full, Yes, V:\
Share3, L:\A Folder Label, Read-only, Yes, S:\

When attempting to copy S:\some path\somefile.exe to a local folder using Windows Explorer, it would consistently lock the system, requiring a forced shutdown.
Then, noting these drives are set up using standard net use commands, I tried using an administrator command prompt window:
NET USE S:\
This results in four lines of output:
Local name s:
Remote name \\VBoxSvr\Share3
Resource type disk
The command competed successfully

Except, that is it. The command DOES NOT complete. (There is no prompt and the window cannot be closed.)
I finally had to resort to dragging from a host Explorer window and dropping on the guest desktop to import the file to the guest.

As I write this, I am beginning to wonder if this feature has an issue with long file names containing spaces. (Share3 has a different actual path than shown above, but the folder name does contain spaces.)

Re: Shared folders locking up guest

Posted: 26. Mar 2019, 03:12
by OtherPhilC
I remembered that, per recommendation of the SSD manufacturer, I had recently disabled 8.3 names on the host using the DOS command:

fsutil behavior set disable8dot3 1

On a pure hunch I just used the same command on the guest and rebooted it to force remounting of the shared folders.

This appears to have solved the problem! The NET USE command now does actually complete.

Windows is a very strange beast.

Re: Shared folders locking up guest

Posted: 26. Mar 2019, 17:33
by OtherPhilC
My fix doesn't quite work. Windows Explorer still freezes the guest system when opened to a folder shared with the host. I will file a bug report.

Re: Shared folders locking up guest

Posted: 26. Mar 2019, 18:05
by andyp73
OtherPhilC wrote:I will file a bug report.
Before you start raising bug reports and tickets, can you zip the VBox.log file from the guest in question and post it here. There may be something in it that jumps out.

-Andy.