VMware Communities: Message List - 2.0.5: Upgrade breaks network disk mapping

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Wed, 04 Nov 2009 21:18:32 GMT

Sadly, our installer guys don't seem to comprehend testing all scenarios or even code inspection.

This installer bug has been fixed in the Fusion 3.0 releases though, and I personally tested it myself, 32 and 64 bit VMs both.

However, did you try the workaround for the installer nonsense? That is, uninstall the VMware Tools using the control panel Add or Remove Programs, reboot VM, do your upgrade to Fusion 2.0.5 and
then install the VMware tools, reboot the VM.

This should then get your network drive mappings working. If you did the above and the drive letter access still fails for some reason, then you are hitting a different bug.

Thanks.
Steve

Re: 2.0.5: Upgrade breaks network disk mapping

jptxs — Wed, 04 Nov 2009 20:04:29 GMT

etung and/or steve goddard,

Has there been any official word on PR 422610? Is there some way to
track that via the web? I really hope to upgrade to 10.6 soon and I'm
afraid that Fusion support in version 2.0.4, which I'm running to avoid
this issue, is not going to be there.

Any advice?

Re: 2.0.5: Upgrade breaks network disk mapping

jptxs — Mon, 14 Sep 2009 20:28:02 GMT

Steve,

I have simply downgraded since there was nothing in 2.0.5 I needed. The only concern I have right now is finding out when (if?) this issue will be addressed in 2.0.5 and also getting an answer about Snow Leopard support for 2.0.4 so that I can upgrade my OS even if this issue is not yet resolved. I asked that on another thread (http://communities.vmware.com/message/1346570#1346570).

Thanks for any insight.

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Mon, 14 Sep 2009 19:24:20 GMT

Hi there,
Sorry been on vacation for a couple of weeks.

Not any progress that I can see from the installer group. I will ping them and see if they have looked at this or plan too in the short term.
Sorry for delays in this. I don't think there are any ways to view this as it is in an internal database.

Does the uninstall followed by a install of the tools get around this for you?
If so, you can always repeat that process when you want to go to the newest version if you have not heard that the upgrade issue has been addressed.
Steve

Re: 2.0.5: Upgrade breaks network disk mapping

jptxs — Wed, 26 Aug 2009 00:28:04 GMT

etung and/or steve goddard,

Has there been any official word on PR 422610? Is there some way to track that via the web? I really hope to upgrade to 10.6 soon and I'm afraid that Fusion support in version 2.0.4, which I'm running to avoid this issue, is not going to be there.

Any advice?

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Fri, 17 Jul 2009 16:57:27 GMT

The uninstall and then install gets around an installer issue for upgrading.
That got the drive letter mappings to work at all.
That is totally different from this second issue which even when
the drive mappings do work and are present, the explorer dialog
does not show them in this instance.
Does that help make a distinction between the two issues?
Follow the installer workaround above and you should be fine using drives to
the shared folders.

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

jptxs — Thu, 16 Jul 2009 13:50:02 GMT

above, user h0lzi stated they got things working by simply uninstalling the VMWare tools in the guest and installing them from scratch. Has that been proven not to work? I've been pulled away on other things all morning, but want to try this out. Are you saying that is a non-starter?

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Thu, 16 Jul 2009 06:47:26 GMT

Hi !

To get it work again get fusion 2.0.4 :
1) remove macfuse 2.0.3 (in case of...)
2) remove vmware tools + shut down virtual machine
3) remove fusion with the installation of the 2.0.4
4) install macfuse 1.5.1 + fusion 2.0.4
5) reboot
6) restart fusion + virtual machine
7) reinstall vmware tools
8) reboot virtual machine

Then wait for the update that fixes this issue.

See ya !

Re: 2.0.5: Upgrade breaks network disk mapping

jptxs — Wed, 15 Jul 2009 21:40:20 GMT

trying to use the example that worked here, I tried to uninstall the VMWare Tools from my image, but I get the error attached, which says there is an invalid drive. The drive, Y:, was the drive that was mapped to the VMWare Shared Folders - which of course is the root of the issue.

When I can work on this more later, I may attempt to revert to an older snapshot and then remove and upgrade the tools from there.

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Wed, 15 Jul 2009 06:54:54 GMT

Hi Steve,

Thx for the fast answer, what I am asking for is that we can use fusion the way it was. I understand the trouble you are into and I thank you for your work.
We'll go back to 2.0.4 until the problem is solved.

Regards + THx !

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 14 Jul 2009 16:47:48 GMT

Hi there
I am not sure what you are asking exactly.

This is a bug, which requires me to add support for undocumented requests to our network file system driver.
First though, I have to find out how these are used, what the arguments and replies
should be, not easy, when it is not documented. Then, I have to prove this is the required fix and the problem gis addressed.

Then we have to issue a fix in a release, which will probably be in a point release after the next Fusion major release.
It is probably too late for the major Fusion release at this point, but I will try to get it in if I can find out the undocumented details in time.

However, this is not likely to be fixed in a release immediately. It will be fixed though, and I can let you know when the bug
is fixed internally and to watch out for the next update that will contain it.

Currently, we have other more major bugs ahead of this one to be addressed but it will be fixed.
As for a workaround, I am not sure as what to suggest other than use WNET Windows APIs instead of the one you are currently
using. These go through a different code path. See http://msdn.microsoft.com/en-us/library/aa385478(VS.85).aspx.

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Tue, 14 Jul 2009 15:59:15 GMT

Hello,

Let me know ASAP please. So I can change the configuration on my clients' computers.

THx !

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Mon, 13 Jul 2009 16:25:56 GMT

Sorry for the delay, the website was down and then I had a multitude of stuff to get done.

However, this is generally a bug on our part and I am going to file it as such. It looks as though we are missing some missing IOCTL support in our driver
to handle connection information. Unfortunately, the reason that we are missing these is that they are undocumented. Sigh.
I will try and get this uncovered and so will then test them out and see if they definitely fix this issue. I think it it makes sense that it will, but would like to
be sure. I can easily reproduce this myself too.

Thanks.
Steve

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Mon, 13 Jul 2009 10:09:08 GMT

Hi !
Still no solution or ideas ?

Re: 2.0.5: Upgrade breaks network disk mapping

WoodyZ — Thu, 09 Jul 2009 12:53:45 GMT

desteban wrote: I'm somewhat surprised, however, seeing that I've an A: unit (????) and a D: unit VMware Tools. (????) --> see file attached

In the first place they are not called a "unit", they are called a "drive" and as I already explained in an earlier post the reason your seeing the Floppy A: Drive show in Windows Explorer and Device Manager is because regardless of whether or not one is assigned under the target Virtual Machine's Settings because the Virtual Machine's BIOS has the floppy defined by default and that's why it appears in both Windows Explorer and Device Manager.

The D: Drive is the CD/DVD and it has the VMware Tools ISO Image loaded in the picture and normally VMware Tools gets ejected after the install if all goes well so if you've already installed VMware Tools you can select Cancel VMware Tools Installation from the Virtual Machine menu and it should remove it from the D: Drive.

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Thu, 09 Jul 2009 08:09:00 GMT

steve goddard wrote:
Hi there,

=> Hi,

Sorry for the delay in responding, I am in the middle of urgent changes for the next major Fusion release.
So the file system for Shared Folders is working and drive mappings are accessible and the drive mappings

=> Yes they are from Windows Explorer

you are showing in your image of the dialog box is from which application exactly?

=> I showed the dialog box that you can get when you try to install new fonts on Windows XP PRO SP3 (whatever the version...) => . I chose this example because it has the same "file browser" interface in my program and the exact same results. And then I obtain , so NO Z:\ drive.

Is the application built on top of MacFuse?

=> No

On Windows (BTW which version, is it XP?)

=> Yes XP PRO SP3

explorer does think the drives for VMware Shared Folders are all connected? It looks
that way from the picutre of the icon , can you also do a "net use" from a command prompt too?

I hope the status field of the output
listing is probably blank for the Shared Folders mappings. Is that the case?

=> Yes NO OK STATUS

I need to know a little more about the application. My guess is that for some reason that it thinks the drives associated with the
VMware Shared Folders are not connected and so does not list them. But you state that this previously worked with version 2.0.4 Fusion
is my understanding correct?

=> With any previous versions, that the first time we encountered this problem

Steve

=> THx !

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Wed, 08 Jul 2009 17:53:22 GMT

Hi there,

Sorry for the delay in responding, I am in the middle of urgent changes for the next major Fusion release.
So the file system for Shared Folders is working and drive mappings are accessible and the drive mappings
you are showing in your image of the dialog box is from which application exactly? Is the application built on top of MacFuse?

On Windows (BTW which version, is it XP?) explorer does think the drives for VMware Shared Folders are all connected? It looks
that way from the picutre of the icon , can you also do a "net use" from a command prompt too? I hope the status field of the output
listing is probably blank for the Shared Folders mappings. Is that the case?

I need to know a little more about the application. My guess is that for some reason that it thinks the drives associated with the
VMware Shared Folders are not connected and so does not list them. But you state that this previously worked with version 2.0.4 Fusion
is my understanding correct?

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

manta — Tue, 07 Jul 2009 17:50:02 GMT

Hi Steve,

I also got a problem that should derivate from this update (2.0.5).

My config :

mbpro leo 10.5.7 Fusion 2.0.5 with win xp pro 32 sp3

The problem :

I got the Z drive on explorer and can use it without prob
What's going wrong is that I have to link files that lie on Z:\ with applications. The interface now shows me only the other network drives but not the Z:\ (or any letter mounted on \\.host\). . I do need this opportunity !

The problem occurred as soon as I upgraded from 2.0.4 to 2.0.5 (link with the new version of MacFuse ?).

I already reinstalled the vmware tools + checked the version of "C:\Windows\System32\vmhgfs.dll" and all seemed fine according to what you said.

Can you help me ?
THx !

Re: 2.0.5: Upgrade breaks network disk mapping

h0lzi — Tue, 30 Jun 2009 19:42:31 GMT

Ok just updated to 2.0.5 again. Removed Tools and installed them again. Works

So it's an update problem Thx

Re: 2.0.5: Upgrade breaks network disk mapping

WoodyZ — Tue, 30 Jun 2009 19:38:18 GMT

desteban wrote: No floppy disk, I'm afraid (MacBook Pro machine)

According to the picture you attached Windows shows a Floppy Drive, regardless of whether or not one is assigned under the target Virtual Machine's Settings because the Virtual Machine's BIOS has the floppy defined by default it appears in both Windows Device Manager and Windows Explorer regardless.

Re: 2.0.5: Upgrade breaks network disk mapping

etung — Tue, 30 Jun 2009 19:21:13 GMT

Remember that virtual hardware is different from physical hardware, so it's quite possible (and even likely) that the virtual machine has a (virtual) floppy drive and can be using a (virtual) optical drive even though the Mac's drive is not in use.

Re: 2.0.5: Upgrade breaks network disk mapping

desteban — Tue, 30 Jun 2009 19:17:34 GMT

No floppy disk, I'm afraid (MacBook Pro machine) ... as far as the D: unit I understand it has been mounted by the installation process ... is that correct? (I can not see it on the Mac's desktop ...

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 19:00:56 GMT

Looks as though you have a floppy disk, and you have a CDROM mounted, which is the VMware Tools ISO as your CDROM contents.

Glad that this works.

I will pass on this bug to the installer team, stating that upgrades fail.

Thanks.

Re: 2.0.5: Upgrade breaks network disk mapping

desteban — Tue, 30 Jun 2009 18:58:03 GMT

NEW - NEW - NEW

I've uninstalled VMware Tools, completely, and installed them again from scratch. It works now. I've got unit Z: back, working perfectly well.

I'm somewhat surprised, however, seeing that I've an A: unit (????) and a D: unit VMware Tools. (????) --> see file attached

David Esteban

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 18:56:53 GMT

David,

This helps tremendously, many thanks for providing this information. What was the previous version you had installed of Fusion VMware Tools?
The File Version you gave me looks odd, can you upload vmhgfs.dll and vmhfs1.dll from your VMs C:\Windows\System32 directory?

However, it looks as though the error is what suspected. The installer has pointed you at the mismatched vmhgfs.dll (user mode) part of the of file system
which deals with mapping drive letters. It should be version 8.0.10.0. (Fusion 2.0.4 vmhgfs.dll file version 8.0.2.0).

However, do you also have the vmhgfs.dll file located in the C:\WINDOWS\System32 directory? If so, is the 8.0.10.0 version?
If that is the case, you can modify the registry setting (as above using regedt32.exe):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmghfs\networkprovider
ProviderPath
REG_SZ
"C:\Windows\System32\vmhgfs.dll"

Then exit regedt32 and reboot the VM.
Try creating new drive letter mappings as I previously suggested.

If the version is different fthan 8.0.10.0 for vmhgfs.dll then the installer failed to install the latest version of the user mode component for the VMware Shared Folders file system.

Let me know how things go.

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

abenndance — Tue, 30 Jun 2009 18:23:29 GMT

What you suggest is something like what I did by accident. I'm no longer having the issue.

I messed up my attempt to downgrade back to 2.04 by forgetting to remove VMWare Tools before doing so. So I couldn't install the earlier version of VMWare tools, and the mapping problem still existed. At that point I uninstalled 2.04, went back to 2.05, tried to uninstall the tools, had the uninstaller crash several times, then decided to try to repair the VWWare Tools and do the uninstall again. Instead, the repair/remove options did not come up that time, and the installer installed the VMWare tools under 2.05 from scratch. Before uninstalling them and rolling back to 2.04 properly, I decided to check on the drive mapping... and it was working! So somewhere in that mess I may have forced a remapping of the Z: drive. I don't know.

I did try uninstalling and reinstalling the VMWare Tools before trying to downgrade, and that didn't work. Something in all the messy stuff I describe above did the trick, but I don't know what.

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 18:18:25 GMT

Furthermore, did anyone who ran into this issue, try uninstalling VMware tools first. Then rebooting the VM and installing the new tools from a clean restart?
If so did everything work after the reboot of the VM after the clean install?

Re: 2.0.5: Upgrade breaks network disk mapping

desteban — Tue, 30 Jun 2009 18:16:53 GMT

Answers to your questions:

After the upgrade to the 2.0.5 tools the Windows VM was rebooted, is that correct? --> YES

Then accessing your Z: drive gives you the error message, can you upload a screen shot of the error message? --> see it attached (I'm sorry, it's in Spanish, but fully understandable, I hope)

Also using a command prompt and issuing:
net use z: /D
net use z: file://.host/Shared Folders
cd /d z:\
This also results in an error too? --> same error

How about if you replace the z: above with a different drive letter? --> I did try it before, same problem

Can you access any drive letter mappings to VMware shared folders? --> no by mapping, I can access navigating from the desktop shortcut or from "My networks"

Furthermore, what does the registry setting key have (using regedt32.exe)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmhgfs\networkprovider\
Key: ProviderPath
Type: REG_SZ
Value: "C:\Windows\System32\vmhgfs1.dll"
Or
"C:\Windows\System32\vmhgfs.dll"
--> it says "C:\Windows\System32\vmhgfs1.dll"

If you use Explorer and right click on properties and version tab for this file, what does the "File Version:" say? --> 8.0.6001.18702

Hope it helps,

David Esteban

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 18:15:38 GMT

Thanks for the reply.

I suspect that the kernel mode driver and user mode DLL are not compatible here. For this new upgrade to work the correct matching user
mode DLL must match the driver which is why I asked about the registry setting, VM reboot questions. If the upgrade installer failed to get this
correct drive letter mappings will not work.

If I can get the information to the other two questions I may be able to tell you what to tweak to make it work. If it is an installer issue it is a different group
that is responsible, but I will reassign the bug to them that Eric filed.

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

h0lzi — Tue, 30 Jun 2009 17:45:26 GMT

How about if you replace the z: above with a different drive letter?

Can you access any drive letter mappings to VMware shared folders?

Since I downgraded. I can only answer these two:

Hopefully someone else can provide the other infos:

I tryed differend letter but this didn't help.

and I can't access any shared folder by drive letter mappings.

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 17:34:49 GMT

After the upgrade to the 2.0.5 tools the Windows VM was rebooted, is that correct?

Then accessing your Z: drive gives you the error message, can you upload a screen shot of the error message?

Also using a command prompt and issuing:

net use z: /D

net use z: "\\.host\Shared Folders"

cd /d z:\

This also results in an error too?

How about if you replace the z: above with a different drive letter?

Can you access any drive letter mappings to VMware shared folders?

Furthermore, what does the registry setting key have (using regedt32.exe):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmhgfs\networkprovider\

Key: ProviderPath

Type: REG_SZ

Value: "C:\Windows\System32\vmhgfs1.dll"

"C:\Windows\System32\vmhgfs.dll"

If you use Explorer and right click on properties and version tab for this file, what does the "File Version:" say?

I tried an upgrade from 2.0.4 to 2.0.5 and everything still continues to work for me. So I have something different or did something different.
Thanks.

Re: 2.0.5: Upgrade breaks network disk mapping

steve goddard — Tue, 30 Jun 2009 15:45:56 GMT

Yes, this is an annoying problem, will look into this today.

Thanks for reporting this.

Steve

Re: 2.0.5: Upgrade breaks network disk mapping

etung — Tue, 30 Jun 2009 00:40:43 GMT

Thanks for reporting this, I've filed PR 422610 about it.

Re: 2.0.5: Upgrade breaks network disk mapping

abenndance — Mon, 29 Jun 2009 22:20:48 GMT

I have the same problem with Fusion 2.05 and Win XP SP3. Running Fusion on OS 10.5.7.

Re: 2.0.5: Upgrade breaks network disk mapping

h0lzi — Mon, 29 Jun 2009 11:59:31 GMT

I have the same Problem.

I removed the network drive mapping and added it again.

This didn't help.

Guess there is a bug somewhere.

2.0.5: Upgrade breaks network disk mapping

desteban — Mon, 29 Jun 2009 09:22:47 GMT

After having installed the 2.0.5 upgrade in a Windows XP Professional SP3 guest I can not use anymore the unit Z: Shared Folders en ".host".
When trying I'm getting a message saying that the route is not valid anymore.
I can still navigate from the windows desktop shortcut, or from "my network sites", but can not map access.
Any solution?

David Esteban