If Cove Backup fails to backup System State because of Windows Cryptographic Service errors and Volume Shadow Copy service with the following errors or similar:

System State\ASR Writer\BCD\?\Volume{7ac063a6-0000-0000-0000-100000000000}\Boot\<VSSFileGroup>

System State\System Writer\System Files\C:\ProgramData\Microsoft\Crypto\<VSSFileGroup>\SystemKeys

System State\System Writer\System Files\C:\ProgramData\Microsoft\Crypto\<VSSFileGroup>\SystemKeys

Then the Windows Cryptographic Service needs restarted using the following powershell script or commands to allow the next backup to complete:

Powershell:

# Requires -RunAsAdministrator

Write-Host “Stopping Volume Shadow Copy…” -ForegroundColor Yellow
Stop-Service -Name “vss” -Force

Write-Host “Stopping Cryptographic Services…” -ForegroundColor Yellow
Stop-Service -Name “cryptsvc” -Force

# Small pause to allow services to completely release files

Start-Sleep -Seconds 3

Write-Host “Starting Cryptographic Services…” -ForegroundColor Green
Start-Service -Name “cryptsvc”

Write-Host “Starting Volume Shadow Copy…” -ForegroundColor Green
Start-Service -Name “vss”

Write-Host “Services successfully restarted!” -ForegroundColor Cyan

Then launch the Cove backup manager for the problem device and run a fresh backup to verify the script fixed what it needed to.

Command Prompt:

net stop cryptsvc
net start cryptsvc

If that doesn’t do it, may need to restart Volume Shadow Copy Service instead using:

net stop vss
net start vss

And if neither of those do it, start here since there may be a permissions issue for the Cryptographics service

https://me.n-able.com/s/article/Cove-System-State-backup-error-VSS-writer-System-Writer-is-missing-Please-ensure-that-Cryptographic-Services-service-has-enough-rights-because-of-incorrect-COM-Security-settings

More about the Cryptographic Service according to Gemini:

The Windows Cryptographic Services (CryptSvc) manages certificates, digital signatures, and system integrity in Windows. When a backup fails during Volume Shadow Copy (VSS), it is often because the VSS System Writer (which relies on CryptSvc) lacks the proper security rights or service permissions to query vital system files.