1 2 3 Previous Next 35 Replies Latest reply on Feb 24, 2017 6:55 PM by XOR42 Go to original post Branched to a new discussion.
      • 30. Re: Shared Folders - Windows 10 upgrade from 15.11.
        Erutan409 Lurker

        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'))
        }
        
        • 31. Re: Shared Folders - Windows 10 upgrade from 15.11.
          Smudge Novice

          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.
          1 person found this helpful
          • 32. Re: Shared Folders - Windows 10 upgrade from 15.11.
            Erutan409 Lurker

            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.

            • 33. Re: Shared Folders - Windows 10 upgrade from 15.11.
              Eugenios Lurker

              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?

              • 34. Re: Shared Folders - Windows 10 upgrade from 15.11.
                Sachmodog Lurker

                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.

                • 35. Re: Shared Folders - Windows 10 upgrade from 15.11.
                  XOR42 Lurker

                  > "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

                  1 2 3 Previous Next