Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Vista Business & VMware Tools - Explorer.exe crashes on shared folders

0 views
Skip to first unread message

Chuck Chopp

unread,
Nov 24, 2006, 2:10:12 PM11/24/06
to
I'm running the RTM build of Windows Vista Business, installed into a guest
VM under VMware v5.5.3 on a WinXP Pro SP2 host. I have shared folders
enabled for this VM. If I connect a drive letter as follows:

NET USE Z: \\.host

And I then start an instance of explorer.exe, followed by navigating to
"Computer" [a.k.a. My Computer], I get message from Vista indicating that
explorer.exe encountered a problem and had to be stopped. This only happens
when the explorer attempts to browser into the default namespace such that
it needs to enumerate the drive letter that is connected to "\\.host" for
access to shared folders.

If I disconnect the network drive, then explorer.exe behaves normally w/o
any crashes.


--
Chuck Chopp

ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com

RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651

Do not send me unsolicited commercial email.

moconnell

unread,
Nov 28, 2006, 7:30:00 AM11/28/06
to
Chuck Chopp wrote:
> I'm running the RTM build of Windows Vista Business, installed into a
> guest VM under VMware v5.5.3 on a WinXP Pro SP2 host. I have shared
> folders enabled for this VM. If I connect a drive letter as follows:
>
> NET USE Z: \\.host
>
> And I then start an instance of explorer.exe, followed by navigating to
> "Computer" [a.k.a. My Computer], I get message from Vista indicating
> that explorer.exe encountered a problem and had to be stopped. This
> only happens when the explorer attempts to browser into the default
> namespace such that it needs to enumerate the drive letter that is
> connected to "\\.host" for access to shared folders.
>
> If I disconnect the network drive, then explorer.exe behaves normally
> w/o any crashes.
>
>
I've had the same issue:
http://www.vmware.com/community/thread.jspa?threadID=61625
No solution but for a work around you can use cmd prompt to navigate
through to the mapped location. I guess that exoplorer invokes some guff
that causes this to happen...
would live to know a solution as it's stopping me do some vital tests..
MOC
0 new messages