Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, August 21, 2016 3:57 PM
Am having issues with VSS within a Windows 10 guest OS. Host is Windows Server 2012 R2.
I understand Integration Services are now made available via Windows Update.
Need to do a uninstall, reinstall or repair of integration services within a Windows 10 guest os.
When I attempt to mount the vmguest.iso, it reports that the most current integration services are already installed 10.0.15806.0.
What is best way to do this without recreated the Win 10 VM from scratch?
All replies (12)
Sunday, August 21, 2016 9:32 PM
Check the machine with System file check (SFC) Scan and Repair System Files & DISM to fix things SFC cannot (guide by Team ZigZag) as the integration services are built in, hopefully that will help.
Beyond that what VSS writers are showing the issue? What does 'vssadmin list writers' show for the State and Last error on the VSS writers?
Sunday, August 21, 2016 10:46 PM
Thanks for replying. When I do a vssadmin list writers on the host machine (WS12R2), ALL return last state of stable with no errors.
I've since run DISM and SFC /scannow per guide on the Win 10 guest OS successfully.
However when do a powershell command of Get-VMIntegrationservice -VMName [vmname_here], it returns all services as enabled = true. But VSS shows a non-recoverable error and says PrimaryStatus shows "Non-Recoverable Error" and SecondaryStatus shows "The Protocol Version of the component..."
The guest OS appears to be crashing when the Server Backup attempts to take a snapshot.
Is there anything that can be done to correct this VSS error? or restore VSS functionality within the guest. I suspect this was caused by some sort of Windows Update on the host but cannot seem to pinpoint it.
I understand Integration Services for Win 10 are now done via Windows Update. When I attempt to mount the Integration Services .ISO on the guest and run setup, it reports that the most current integration services have been installed within the Win 10 guest OS. I cannot find a way to force a re-install or repair.
Thanks.
Monday, August 22, 2016 1:03 PM
Well can't see a way to reinstall the Integration Services.
If you take a manual check point on the Windows 10 Guest does that work? If so after that what does the status show with Get-VMIntegrationservice? Just wondering if it is the way the server backup is calling it. What is the complete "The Protocol Version of the component..." error? (you might need to pipe Get-VMIntegrationservice to Format-List or Out-GridView to see the reset of the error)
Monday, August 22, 2016 2:20 PM
If you take a manual check point on the Windows 10 Guest does that work? If so after that what does the status show with Get-VMIntegrationservice? Just wondering if it is the way the server backup is calling it. What is the complete "The Protocol Version of the component..." error? (you might need to pipe Get-VMIntegrationservice to Format-List or Out-GridView to see the reset of the error)
Yes. A manual checkpoint of the Win 10 guest works. Here's the details of the error when run from the WS2012R2 host:
Enabled : True
OperationalStatus : {NonRecoverableError, ProtocolMismatch}
PrimaryOperationalStatus : NonRecoverableError
SecondaryOperationalStatus : ProtocolMismatch
StatusDescription : {Non-Recoverable Error, The protocol version of the component installed in the virtual
machine does not match the version expected by the hosting system}
PrimaryStatusDescription : Non-Recoverable Error
SecondaryStatusDescription : The protocol version of the component installed in the virtual machine does not match the
version expected by the hosting system
ComputerName : SERVER
Name : VSS
Id : Microsoft:4FE1D1C4-A0F9-48C7-B599-B48D74525AF5\5CED1297-4598-4915-A5FC-AD21BB4D02A4
IsDeleted : False
VMId : 4fe1d1c4-a0f9-48c7-b599-b48d74525af5
VMName : Windows 10 x64 - VM
VMSnapshotId : 00000000-0000-0000-0000-000000000000
VMSnapshotName :
Key :
Monday, August 22, 2016 3:42 PM
To me it would appear Windows 10 is ok if a manual check point works. What is the difference when you say "when run from the WS2012R2 host:" as a manual check point would be run from the host?
Monday, August 22, 2016 4:19 PM
To me it would appear Windows 10 is ok if a manual check point works. What is the difference when you say "when run from the WS2012R2 host:" as a manual check point would be run from the host?
Sorry for confusion - when I run the command above from the WS12R2 server, it returns that info about the Win 10 VM.
Is there any way to display the VSS protocol version on the HOST and the GUEST, perhaps in registry?
Both host and guest OS each have all current Windows Updates applied. The Win 10 VM reports that it has the most up to date integration services installed.
Monday, August 22, 2016 5:33 PM
Normally to get the version of the integration services would be to get the version number of C:\Windows\system32\vmms.exe, but that is not present on my 10586. Looking further comparing it to the Anniversary update 14393 it appears to be missing two services;
Hyper-V Host Compute Service C:\Windows\system32\vmcompute.exe
Hyper-V Virtual Machine Management C:\Windows\system32\vmms.exe
So not quite sure what role they play but appear missing to me on 10586. Also it get the same protocol error for the Time sync services on 10586.
Do check points work ok if the machine the guest is off? (it can't report versions then)
EDIT the 10493 also runs Hyper-V so that explains the differences to me (nested Hyper-V)
Monday, August 22, 2016 6:22 PM
My Win 10 VMs are running 10586 also. Incidentally they were previously Win 7 VMs upgraded to Win 10 which could be a factor. Although all Win 10 windows updates have been applied within the VM, would there be any value in running the Win 10 ver 1607 installer over top of the OS?
Yes, the checkpoints to appear to work if the guest is off.
Monday, August 22, 2016 7:11 PM
Well my test is on a 2016 TP5 host, but I can standard check point a 14393 powered on, and standard check point fails on 10586 if it is powered on.
Besides 1607 is the latest general release so guess you will end up on that at some point anyway...
Monday, August 22, 2016 9:39 PM
Unfortunately an upgrade from 10586 to the latest 1607 build didn't resolve the issue either.
Monday, August 22, 2016 10:05 PM
I have edited above as released my 10493 with my initial testing was running nested Hyper-V, so the guest was running Hyper-V as a service as well so that explains the extra the services I am seeing.
My 10493 are clean installs so not sure if that is the difference. Does the upgrade 1607 show the same error in Get-VMIntegrationservice? and do manual checked points with Hyper-V Management fail?
Tuesday, August 23, 2016 5:43 AM
Hi miles267,
Considering you are using a Server 2012R2 hyper-v, it is recommended to ask for help from our Server forum.
Hyper-V
https://social.technet.microsoft.com/Forums/windowsserver/En-us/home?forum=winserverhyperv
Best regards
Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected]