Skip to content

Event ID 50: Windows failed to provision VSM Master Encryption Key

Windows Event ID Lookup: What Windows event IDs mean: 4625, 4624, 4740, 6008, 41, 7045, 1102 and 3,000 more, with Windows' own message text, the fields and what to check.

Look up a Windows event ID from Event Viewer, a SIEM alert or a log export: what it means, the fields it records, and what to check. Many IDs are used by more than one source (event 41 is both a Kernel-Power crash and a boot error), so every definition is shown, the one people usually mean first. The message text is Windows' own, read from the event providers of Windows 10.0.26200.0, 2026-10-28; the notes are ours, based on Microsoft's security auditing reference.

Try: 4625, 4624, 4740, 6008, 41, 1074, 7045, 1102, 4104, 1149

Windows failed to provision VSM Master Encryption Key.

Event 50
Kernel-Boot
System log
Error
Message and fields (as Event Viewer shows them)
Windows failed to provision VSM Master Encryption Key. Using cached copy status: …. Primary Blob Unseal Status: …. Backup Blob Unseal Status: …. Pca2023 Protector Unseal Status: …. LostOemPk Protector Unseal Status: …. Backup Blob Validity Check Status: …. Backup Blob Validity Check Result: …. Pca2023 Protector Validity Check Status: …. Pca2023 Protector Validity Check Result: …. Primary Blob Reseal Status: …. Backup Blob Reseal Status: …. Pca2023 Protector Reseal Status: …. New key generation status: …. Sealing status: …. TPM PCR mask: …. Tpm Counter validation status: …. Tpm Counter creation status: …. Backup sealed blob used: …. Pca2023 Protector cleaned up post upgrade status: ….

The time service detected a time difference of greater than … milliseconds for … seconds.

Event 50
Time-Service
System log
Warning
Message and fields (as Event Viewer shows them)
The time service detected a time difference of greater than … milliseconds for … seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.

Remote Connection Manager has taken too long to process begin-connect-message for session

Event 50
TerminalServices-LocalSessionManager
TerminalServices-LocalSessionManager/Operational log
Warning
Message and fields (as Event Viewer shows them)
Remote Connection Manager has taken too long to process begin-connect-message for session …

Activity Transfer

Event 50
WMI-Activity
WMI-Activity/Operational log
Information
Message and fields (as Event Viewer shows them)
Activity Transfer