Thank-you. I just troubleshot my third freshly installed Server 2025 vm with this issue but unlike the other two I didn't give up and just wipe and reinstall.
Credit to Gemini that gave me this:
Code: Select all
Get-WmiObject win32_service | ?{$_.Name -like "*vmicvss*"} | Select PathName
which gave me this output:
Code: Select all
PathName
--------
C:\WINDOWS\system32\svchost.exe -k VeeamHvVssGroupstemNetworkRestrictedRedirectionGuard -p
Which Gemini deemed to be "junk".
I needed to do two things to get checkpoints working again. First was to fix that value with:
Code: Select all
sc.exe config vmicvss binPath= "C:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p"
and second was to add vmicvss to the registry value:
"HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost\LocalSystemNetworkRestricted"
Code: Select all
$registryPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost"
$valueName = "LocalSystemNetworkRestricted"
# Check if the group exists and add vmicvss if it's missing
if (Test-Path $registryPath) {
$currentValues = Get-ItemProperty -Path $registryPath -Name $valueName -ErrorAction SilentlyContinue
if ($currentValues) {
if ($currentValues.$valueName -notcontains "vmicvss") {
$newValues = $currentValues.$valueName + "vmicvss"
Set-ItemProperty -Path $registryPath -Name $valueName -Value $newValues
Write-Host "Added vmicvss to Svchost group." -ForegroundColor Green
}
} else {
# Create the value if Veeam deleted it
New-ItemProperty -Path $registryPath -Name $valueName -Value @("vmicvss") -PropertyType MultiString
}
}
After that the service would start and I could make production checkpoints.
Some more context, the host output this with "No Contact" for VSS.
Code: Select all
Get-VMIntegrationService -VMName "TESTVM"
VMName Name Enabled PrimaryStatusDescription SecondaryStatusDescription
------ ---- ------- ------------------------ --------------------------
TESTVM Guest Service Interface False OK
TESTVM Heartbeat True OK
TESTVM Key-Value Pair Exchange True OK
TESTVM Shutdown True OK
TESTVM Time Synchronization True OK
TESTVM VSS True No Contact
And trying to start vmicvss on the guest:
Code: Select all
Start-Service -Name vmicvss -Verbose
VERBOSE: Performing the operation "Start-Service" on target "Hyper-V Volume Shadow Copy Requestor (vmicvss)".
Start-Service : Service 'Hyper-V Volume Shadow Copy Requestor (vmicvss)' cannot be started due to the following error:
Cannot start service vmicvss on computer '.'.
At line:1 char:1
+ Start-Service -Name vmicvss -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Start-Service],
ServiceCommandException
+ FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.StartServiceCommand
I hope this helps someone else in the future!