Shared folders doesn't work with Win2003 x64 and WinXP x64 -> fixed in SVN/2.1.4

Did you also try a "net use s: \\vboxsrv\SharedFolder?" in the command line? Does your user in the VM have admin rights or is it a restricted user?

Please try to install the Guest Additions again, this time with the parameter "/l" (enables debug logging). You'll find the logs ("install.log" and install_ui.log) in the installation directory (usually under C:\Program Files\Sun\...).

I have the same behaviour on 2.0. After updating vbox to 2.0.2 and it's guest additions shared folders work again.

Host: WinXP x64 SP2, guest: WinXP SP3.

Replying to pentagonik:

Did you also try a "net use s: \\vboxsrv\SharedFolder?" in the command line? Does your user in the VM have admin rights or is it a restricted user?

This did not work too. Then every start of windows explorer freezes.

Please try to install the Guest Additions again, this time with the parameter "/l" (enables debug logging). You'll find the logs ("install.log" and install_ui.log) in the installation directory (usually under C:\Program Files\Sun\...).

The logs I have added. I hope it helps.
I work always as a local admin (host&guest).

I'm experiencing the same on Linux x64 host with XP x64 guest...

I'm having the exact same problem with a 64-bit Gentoo as host system and Windows XP x64 SP2 (US) as guest.

If I try to add the shared folders by browsing then explorer just hangs as soon as I select the share itself. If I add the network drive by specifying the path directly without trying to browse the share then it actually maps the drive. But as soon as ANY access to the drive and share is done explorer hangs again. And with "any" access I mean it's even enough to just open "My Computer" which tries to list all your drives, tries to access the network drive and will end up hanging while displaying a blank page.

This problem has been fixed for me with the installation of Vitualbox 2.0.4. Shared folders work fine again in the same virtual machine that had problems before.

It looks like I spoke too soon on this matter (or rather the ticket was closed too soon without waiting for confirmation from other people that had the problem.

I have since used all versions of VirtualBox (now at version 2.1.0) and while access to shared folders works *sometimes*, it usually only works for a single session (at most). This means that I must not leave the shared folder connected at system reboot, because on the next restart it will be inaccessible with the symptoms mentioned above.

Right now I tried 2.1.0 again with the latest VirtualBox Guest Additions and the problem was back right away when I connected the shared folder.

Unfortunately this issue is far from being fixed. :|

Replying to Loibisch:

It looks like I spoke too soon on this matter (or rather the ticket was closed too soon without waiting for confirmation from other people that had the problem. I have since used all versions of VirtualBox (now at version 2.1.0) and while access to shared folders works *sometimes*, it usually only works for a single session (at most). This means that I must not leave the shared folder connected at system reboot, because on the next restart it will be inaccessible with the symptoms mentioned above. Right now I tried 2.1.0 again with the latest VirtualBox Guest Additions and the problem was back right away when I connected the shared folder. Unfortunately this issue is far from being fixed. :|

I have exactly the same problem. Connecting shared folders works for one session only. If I leave the shared folders to connect after reboot, then after rebooting, accessing them in any way (ie. just opening "My Computer") freezes the guest OS and leaves the host CPU working at 100%.

Host OS: Ubuntu Intrepid (32bit) Guest OS: Windows XP (32bit)

It happens on two different machines, one is AMD Turion 64 X2 laptop, the other is AMD Athlon X2 6000, both with AMD-V enabled.

http://www.virtualbox.org/ticket/2764 This seems to be the same problem. The attached VBoxSF.sys solved the problem for me.

HOST = Windows XP 32 bit SP3

GUEST= Windows XP 64 SP1

VBox 2.1.0, latest aditions

========== same problem, works in command prompt

========== exporer, My Computer and IE all hang.

Please retest with 2.1.2. A similar issue has been fixed there. Do not forget to update the guest additions.

Still same problem with 2.1.2 and 2.1.2 guest additions Host: Ubuntu x86_64 Guest: WinXP 64

In command prompt, everything seems to work: net use, changing to the drive, dir, even copying a file and even opening a .doc file by just typing its name at the command prompt.

But explorer, my compuyter, and opening file dialogs (e.g. in Office) all hang

pdumon, please attach the VBox.log file for a VM run where you've got the hang.

I have still the same Problem with Win2003x64eng and VirtualBox 2.1.2 (VBox_Win2003_x64_002.log)

Win2003x64eng with VB 2.1.2

Host:

Win Vista SP1 x32 Italian

Guest:

Win XP SP2 x64 English - no Win Updates at the time

every access to shared folders hangs explorer process, and any other process trying access them.

When we should expect stable support of shared folders in x64 guests? I think it's a major issue..

UPDATE FROM PREVIOUS POST:

1. I forgot to mention my VBox version, it's 2.1.2 2. Only some Explorer Shell APIs hangs when invoked, programs like total commander works fine, you can copy, launch and whatever you want on shared folders. And text based commands works fine too (net use, cd, copy, etc.)

VBoxSF.sys shared folders guest driver for 64 bit Windows guests and VirtualBox 2.1.2

Please try the attached VBoxSF.sys driver. Copy it to the guest \Windows\system32\drivers directory (make a backup copy of existing VBoxSF.sys). The new driver contains a fix for 64 bit guests.

Thanks.
For me it works with Win2003 x64 eng guest on WinXP x64 eng host.
WinXP x64 eng guest not yet tested.
VirtualBox v2.1.2

Ticket #3154 has been marked as a duplicate of this one.

Confirmed working for WinXP x64 guest on Ubuntu 8.10 x64 Guest Thanks!

Thanks for testing. The fix will be included in the next VBox version.

log after trying new vboxsf.sys in Win7