STATUS_CONTEXT_MISMATCH 0xC0000719 Fix – Two Triggers

Quick Answer (for the impatient)

Back up your data first. Log in as a local admin. Delete the corrupted user's profile registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, delete the matching C:\Users\username folder, then reboot. Profile recreated fresh. If that doesn't work, run net stop server && net stop workstation && net start workstation && net start server as admin.

Why You're Seeing 0xC0000719

This error shows up as a crash when you launch an app — often Chrome, Outlook, or a custom line-of-business tool. The system says "context didn't match the target." In plain English: Windows tried to load your user settings (the "context") but found garbage instead of a valid profile.

The culprit here is almost always a corrupted ntuser.dat file. That's the registry hive that holds your personal settings. If it gets partially overwritten or truncated — from a forced shutdown, a failing drive, or a botched Group Policy update — every app that reads from HKEY_CURRENT_USER fails with this code.

Second most common cause: an SMB (network file sharing) race condition on Windows 10 1909 and later. When the workstation service and the server service get out of sync during heavy file I/O, the context broker in the kernel throws 0xC0000719.

Fix Steps (Start Here)

1. Isolate the user. Log in as a different user (local admin). If the error stops, you've confirmed profile corruption.
2. Back up the broken profile. Copy C:\Users\[username] to an external drive. You'll restore Documents, Desktop, etc. later.
3. Remove the registry entry. Open Regedit as admin. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

   Find the SID for your user (look for the folder with your username in the ProfileImagePath value). Delete the entire SID key.
4. Delete the folder. Delete C:\Users\[username]. Yes, the whole thing. You backed it up, right?
5. Reboot. Log in with the same user account. Windows creates a brand new profile from the default template. No more 0xC0000719.

Alternative Fix: SMB Race Condition

If the profile fix didn't work — or if the error only happens when you're accessing network shares — try this. Open Command Prompt as admin and run:

net stop server && net stop workstation && net start workstation && net start server

This restarts the two core SMB services in the correct order. The key is stopping them both, then starting workstation first. That forces the context broker to reinitialize cleanly. I've seen this fix 0xC0000719 on Windows 10 20H2 and Windows 11 22H2 after a Windows Update.

If Neither Fix Works

• Check disk integrity. Run chkdsk c: /f and reboot. Bad sectors in the profile NTFS metafile can mimic profile corruption.
• Remove third-party shell extensions. Use ShellExView to disable all non-Microsoft context menu handlers. Some VPN clients and cloud sync tools inject broken handlers that trigger this error.
• System File Checker. sfc /scannow then dism /online /cleanup-image /restorehealth. Less common, but a corrupted winsrv.dll can cause this.

Prevention Tip

Don't let users force shutdown their machines. That's the #1 cause of ntuser.dat corruption. If you manage a domain, set Group Policy to Disable the "Shut Down" button on the logon screen — users will stop mashing the power button. Also, enable Fast Startup in power options; it halts the kernel in a way that reduces profile file corruption risk.

For SMB-related cases, keep Windows fully patched. Microsoft fixed the race condition in KB5021233 (December 2022) — if you're still on an older build, you'll keep hitting it.