Forum Discussion
Andy Dawson
Oct 15, 2017MVP
Windows 10 1709 Upgrade Removed 'Saved Critical' and 'Off Critical' Hyper-V machines
My laptop has been upgraded to 1709 over the weekend and I've hit a snag folllwing completion of the process. I have a series of Hyper-V VMs that were hosted on external drives that were not connect...
andrew bell techienumber1
Oct 24, 2017Copper Contributor
sorry that was slightly wrong I found what is up in the registry it not in services
silly me if hyper-v is active in registry the system will not run
silly me if hyper-v is active in registry the system will not run
- Ghislain PellandDec 26, 2017Copper Contributor
The symbolic links under C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines are the issue.
If you changed the default location where your virtual machines are located, the symbolic links will point to the default location after the upgrade to 1709.
First stop the Virtual Machine Management Service (Vmms.exe).
Use PowerShell to recreate all the symbolic links under C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines to point to the right location.
Find were the actual symbolic link is pointing with:
Get-ChildItem 4E899B2D-955E-4836-A295-D79B53301F7F.xml | fl *
Recreate the symbolic link with:
New-Item -ItemType SymbolicLink -Name 4E899B2D-955E-4836-A295-D79B53301F7F.xml -Target "V:\Hyper-V\Virtual Machines\4E899B2D-955E-4836-A295-D79B53301F7F.xml"
Restart the Virtual Machine Management Service (Vmms.exe).