hssp
Contributor
Contributor

Shared Folders - Windows 10 upgrade from 15.11.

Jump to solution

Hello,

yesterday was recorded by Microsoft upgrade from Windows 10.

since I can no longer edit the shard folders as network drive.
it is the "vmware-host" no longer found (net use z: "\\ vmware-host\Shared Folders").

Has anyone a solution for this?


my computer:
Apple Mac mini with el captiain, VMware Fusion 8:02 with windos 10 pro 64 bit


Eckhard

39 Replies
TELSi
Contributor
Contributor

Same problem occuring to my setup. OSX 10.11.6 running Fusion 8.5

Guest operating system Windows 10.

When installing anniversary update, all my taskbar shortcuts vanish and mirrored folders on Desktop are not working.

Also my mapped network drive to our win sbs 2008 server stopped working.

Internet acces was no prob.

When trying to remove VM Ware Tools using Add / remove programs, it was not completly removed.

VGA driver as well as network drivers still were intact.

I also tried setting REgistry Keys (vmhgfs). It did not do any good. Same problem.

Reinstalling and removing afterwards also caused problems.

Removing devices and stopping services manually also did not do any good.

After reboot, everything was back up.

So I did a roll back to pre anniversary version.. Everything is fine now.

Are you familiar with these problems. When will there be a Fusion update which takes care of these problems?

0 Kudos
octaverodrigues
Contributor
Contributor

Thanks a lot for saving our time.

Good job !

0 Kudos
anto87
Contributor
Contributor

Hello. I have a virtualised Windows 10 64 bit with anniversary update installed on a mac os Sierra. Once I did the update in Windows from previous version to anniversary update (now I have the build 1607) I have a problem. I can access the shared folders but first time i open them I have to wait 2 minutes and I hear the Windows sound foreground. Before I didn't have this problem. It is a problem because some times when I close my shared folders and I reopen it after some minutes I have to wait another time two minutes and Windows makes the sound Windows Foreground.wav. Is there a way to resolve that? I've tried to uninstall and reinstall vmware tools and using the register key given by Steve. Thanks a lot if someone can resolve me that! Vmware tools are installed correctly and I have vmware fusion version 8.5.0, the last available.

0 Kudos
ElViejo
Contributor
Contributor

This worked for me, after reboot.

Nevertheless, thanks very much for saving me a lot of time and irritation.

You posted this in Nov 2015, and now it's Sept 2016, and searching the VMWare website didn't find it. DuckDuckGo did.  ving me a lot of time and irritation. You posted this in Nov 2015, and now it's Sept 2016, and searching the VMWare support website didn't find it. DuckDuckGo did. 

0 Kudos
anto87
Contributor
Contributor

Hello, someone has a solution for me? Shared folders works, but I think that don't load automatically because when I try to acces them I have to wait some times that Windows open them. The vmware tools are installed correctly. Thanks.

I was forced to undo the anniversary update because when any program has to access my shared folder files I had to wait time that Windows load them. When there will be a solution I will return to anniversary update. Now I am in build 1511. With anniversary update I've tried also the registry key by Steve.

0 Kudos
Cintos
Contributor
Contributor

An overnight update to Win 10 instance created this issue for me.  I followed the regedit suggestions and corrected the term to "vmhgfs,RDPNP, LanmanWorkstation,web client" and problem instantly fixed. Now, I need to get a handle on un-controlled overnight updates, as I did in Win 7, because the restart of an active system destroyed 12 hours of work....

0 Kudos
anto87
Contributor
Contributor

Hi Cintos, I've used the key mentioned, "vmhgfs,RDPNP, LanmanWorkstation,web client". I could access the vmware folder but I had every time to wait some minutes that Windows loads them. I don't know why.

0 Kudos
anto87
Contributor
Contributor

Hi Steve, I have the snapshot for Windows 10 build 1607 so I made some tries but the problem that I have to wait minutes when open shared folders are present. I've checked these registry Keys:

HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

The Key ProviderOrder is: "vmhgfs,RDPNP, LanmanWorkstation,webclient"

I've checked also this key:

HKEY_LOCAL_MACHINE\ SYSTEM\ControlSet001\Control\NetworkProvider

The key ProviderOrder is: "vmhgfs,RDPNP, LanmanWorkstation,webclient"

These Keys are correctly in this way, so I didn't modify them, because I've uninstalled and reinstalled vmware tools. So for now I've back to Windows 10 1511.

Thanks

0 Kudos
Luism74
Contributor
Contributor

Hello Steve,

     I did this but my problem continue.   This happened when I upgrade to Fusion 8.5 couple weeks ago.  

     Today I reinstall the VWTools, but nothing change.

I have Windows 10

Could you give me an idea?

0 Kudos
WIZZs
Enthusiast
Enthusiast

It might be useful to mention that this registry setting must be done on the client, not the host.

See also related issue Re: Shared folders not accessible after installing Windows 10 update 1607

0 Kudos
Erutan409
Contributor
Contributor

I created this PowerShell script that I setup to run at system startup (Task Scheduler) for when future updates keep resetting this:

Set-Location HKLM:\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

$reg = (Get-ItemProperty -Path .\).ProviderOrder

if ($reg -match "^vmhgfs$" -eq $false) {

    Set-ItemProperty . ProviderOrder ("vmhgfs," + ($reg -replace "(.*?)(?:vmhgfs,)?(.*)", '$1$2'))

}

0 Kudos
SmudgeSpot
Contributor
Contributor

Erutan409‌, thanks for creating the PowerShell script.  That is a great idea to use it at startup to fix the registry entry if anything changes it.

However, there are some issues with your regular expressions.

  1. The -match will always be false because it is checking if vmhgfs is the only content, which will never be true.
  2. The -replace pattern is not doing what I think you are trying to do, [keep anything before and after the text vmhgfs, (if it exists)]

Here is my update to your script.

Set-Location HKLM:\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

$reg = (Get-ItemProperty -Path .\).ProviderOrder

if ($reg -match "^vmhgfs" -eq $false) {

    Set-ItemProperty . ProviderOrder ("vmhgfs," + ($reg -replace ",?vmhgfs", ''))

}

The changes I've made are

  1. Since we care if vmhgfs is not at the start of the list, we need to remove the trailing $ character in the -match pattern.
  2. The -replace pattern will simply remove any vmhgfs entries it finds in the list.  Since we are prepending the vmhgfs, text to the list after the replacements, it will always end up how we need.

In my situation, the vmhgfs was in the middle of the list RDPNP,LanmanWorkstation,webclient,vmhgfs,MfeEpePcNP, as it was moved to the end by a Windows update then McAfee was installed and appended to the end of the list.

Your script added vmhgfs to the front of the list but didn't remove the one in the middle.

Using my version of the script, it always ends up properly as vmhgfs,RDPNP,LanmanWorkstation,webclient,MfeEpePcNP

Hope this helps
It's not God that I have a problem with. It is his fan club that I can not stand.
Erutan409
Contributor
Contributor

You're right about the $ anchor at the end. It was a typo when I posted it in the code snippet. It was supposed to be a comma.

The replace is intentional and correct. It's meant to capture the vmhgfs and disregard it from everything else, regardless of how it's being captured/replaced.

I'm glad it helped.

0 Kudos
Eugenios
Enthusiast
Enthusiast

the solution provided, with or without the script, was good for 1511

When I upgraded to 1607 though, it makes no difference

We are back to the original issue and I do have vmhgfs in the front

Any thoughts?

0 Kudos
Sachmodog
Contributor
Contributor

‌My shared folder issue initially came about after NET framework was installed prompted by another new program. After changing registry  I needed to log off and back on guest and host b4 it worked.  Not sure why that was necessary given Steve's certainty on the matter. All working fine now. Thanks very much Steve.

0 Kudos
XOR42
Contributor
Contributor

> "It might be useful to mention that this registry setting must be done on the client, not the host -WIZZs

Thanks for pointing that out, WIZZs.  I am still wet behind my VM ears.  Had I seen your post earlier, it would have saved me several hours of research and testing.  All of the previous posts I browsed made no mention of Guest only.  Since I knew I could reset the guest VM to its previous snapshot, I tried the Guest VM 1st and it worked.  However, it didn't take at first - even after a restart. I had to also re-install VM Tools, then the "vmware-host" folder with the Shared Folders sub-folder showed up.

DEAD MACHINE NAME WALKING:

Somewhere along the way, after multiple restarts, VM Tools re-installs, ad nauseam, and before I successfully applied the registry tweak, I somehow ended up with a strange sole device in my Windows Explorer Network branch of one of my Guest VMs, called "DESKTOP-etc" that was inaccessible to me due to an access rights error. I am not sure if it ever was accessible or when it appeared.  Strangely, a parallel VM (sprouted form the same VM Snapshot start point), had no Machine name in the network tree before applying the registry tweak.  Anyone have any thoughts about what this "desktop" node is, whether I should attempt to get rid of it, and, if so, how?  Since I don't have access rights, it's an inaccessible orphan with no apparent purpose.

TWEAK SUCCESS:

After applying the Registry Tweak to my 1st Guest image, I ended up with the sought after "vmware-host" node which contained (tada!) the Shared Folders branch with the host path I needed.  I then looked at my my 2nd, parallel VM Snapshot and the tweak I applied to the 1st VM instance had no ancillary effect on the 2nd (as I expected).  So, I applied the same tweak to that VM and the "vmware-host" node appeared after a restart without any other shenanigans.  Oddly, this 2nd Snapshot path also did not have the strange DESKTOP-XXXXXX machine node.  So, the 2nd Snapshot path is looking exactly as expected.

NEED TO UPDATE ALL VM Snapshot PATHS:

We should add to WIZZs advice that the registry tweak needs to be applied to EACH VM Snapshot.  This is needed but tedious for those with many VMs and/or VMs with multiple snapshots.

Here is the VM Snapshot Manager's view of, in my case, 2 parallel Snapshot paths that would each need tweaking separately.

2017-02-22_20-45-30.jpg

The following steps are what I did for each of my VM Snapshot paths.

Scenario: I have a main VM Guest for running and testing apps under Windows Pro 10 x64.

This VM has 2 parallel VM snapshot paths.

1. "LR6, HR, HF, DCC" for running my photo apps Lightroom 6, Helicon's Remote & Focus, and DigiCamControl.

2. "Naked Latest" which is a base naked installation of W10 Pro without apps and the minimum utilities..
    I'm not being suggestive - it's just my Win 10 Pro without having been dressed up with anything.

To fix the registry issue and create snapshots with OS & App updates, here are my steps:

Do for each VM path (in my case, "LR6, HR, HF, DCC" and "Naked Latest") within each Windows 10 VM you may have:


1. At the "You Are Here" node of each, search for and apply all Windows and other application updates.

2. Tweak the Registry of that current VM guest's instance as per the numerous posts in this thread. To wit:

    a. Open RegEdit and find path: HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Control\NetworkProvider\Order

    b. The Data value should read something like: "RDPNP, LanmanWorkstation,webclient"

    c. Change it to: "vmhgfs,RDPNP, LanmanWorkstation,webclient"

    d. Export the updated registry key (e.g., as "W10HostShareFix.Reg") to a folder or the desktop of that VM instance for an easy reset if a Win10 update undoes it.
        I wrote "local Guest folder" because if the tweak is later undone, you won't be able to access your host's folders 😉

    e. Exit RegEdit

3. Create a new snapshot of the current "You Are Here" VM state, naming it to some temp. E.g., "Naked Latest 2".

4. Delete the previous parent snapshot, e.g,  "Naked Latest" ... this can take many minutes while the VM image is reorganized.

5. Rename the new VM image back to the previous parent name, e.g., "Naked Latest"

6. Update the description of the Snapshot with the current date and anything else you want to note.

7. For all other active VM points within all remaining Win10 VMs, repeat from Step 1. 
    In my example, that would be and and all VM active points within the "LR6, HR, HF, DCC" VM.

When done, all Win10 VM instances will be tweaked for Host Shared Folder and those images will have all the latest updates.

The only fly in the ointment is a small one (for those with multiple snapshots in a linear time series.  That is, 2 or more Snapshots within the same VM Snapshot path.  You can only update one snapshot point in a linear time series because the very act of going to it will reset your environment to that moment in time, erasing all that Snapshot's children.  Those with such Snapshot lineages need to choose which snap to update as that will obviously become the last and only one.  You could just update the last one so as to save the earlier snapshots but any subsequent attempt to go back to an earlier Snapshot will naturally wipe out all the later children Snapshots.  Sorry if this is tediously obvious to the veterans here.  I had to think a bit about it.   That's why I like to create parallel snaps for different scenarios and keep each of those parallel paths down to one snapshot.  If testing furiously, I might create several in a time series but only for a short period of time.

Please excuse an glaring mistakes or obvious tidbits.  I'm still naive about VMWare and welcome any comments or corrections,

Hope I've helped those who may be as green as me.

-xor42

0 Kudos
jacshon121
Contributor
Contributor

Here is how to fix Windows 10 update troubleshooter

Search troubleshoot in windows 10 taskbar search box.

Now, click on troubleshoot from the left menu.

Now, click on windows update icon on the right side.

Now, click on run the troubleshooter from the expanded option.

Click on try troubleshooting as administrator.

Source:- http://merabheja.com/fix-windows-10-update-problems/

0 Kudos
burdavis
Contributor
Contributor

I am having what I believe is a similar issue:

I have been running a Windows 7 VM on a MacOS host for years, and successfully reading and writing to a shared folder on the Mac file system.

I just setup a Windows 10 VM, specified that same shared folder, and I am able to read from it but not write to it.

Specifically, I can open an Excel file but when I try to save I get the error "Document not saved". Same misbehavior when in PowerPoint.

I can successfully save the file to the virtual file system of the VM (for example, to the Windows 10 desktop), but I am unable to save the file back to the shared folder.

I have uninstalled and reinstalled VMTools (restarting the VM as I went), no luck. Also tried another folder as shared folder, no luck.

I checked the reg key specified in this thread, and it is set as specified.

Anyone have any suggestions?

Versions: VMWare Fusion 8.5.10; MacOS 10.11.6; Windows 10 Enterprise, Version 1809, Build 17763.973

0 Kudos
wila
Leadership
Leadership

Different issue.

This was fixed with an update.

If I am not mistaken then you can save files to the share via Windows Explorer and it is only Microsoft Office that can't save to that share.

The update was in Fusion 14.1

VMware Workstation 14.1 Pro Release Notes

Not sure, but there's a reasonable chance that it might be a VMware Tools patch and you can try a newer vmware tools if you have no possibility of upgrading (as I notice you are running a very legacy version of macOS as well)

Of course using a newer vmware tools on such an old version of VMware Fusion is entirely unsupported, but your Fusion already is unsupported..

http://www.vmware.com/go/tools

As always backup your VM before you try something like this.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
bakosric
Contributor
Contributor

Hello,

I am Richard Bakos. I am using vmware workstation 15 player. In vmware I have  windows 10 ltsc. My problem is, that this virtual machine is connexting a windows network. On this network we have another windows 10 pc with shared folder. In virtual machine i can ping this computer, but when I want to access the shared folder \\192.168.5.101 the file explorer not browsing. I get windows error message: windows can not connect to 192.168.5.101. But my host computer windows 10 can connect to this shared folder. The vmware windows can ping this ip address, just can not browsing the shared folder. Do you have any idea how can access to sharex folder?

Thank you very much!

0 Kudos