How to fix 0xC0000719 error in Windows?

0xC0000719 is a Windows status code that shows up in two places: on a blue recovery screen at startup that names \hiberfil.sys, and as Status: 0xC0000719 in a Device not migrated event in Device Manager. The startup error means the saved hibernation image could not be resumed. The Device Manager event is often harmless.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2, from Microsoft's NTSTATUS reference and recovery documentation.

What error 0xC0000719 means and where you see it

0xC0000719 is an NTSTATUS code, a status value used inside Windows and its drivers. Microsoft's NTSTATUS reference names it STATUS_CONTEXT_MISMATCH with the text "The provided context did not match the target." In plain words: Windows had saved information about something, and when it came back to it, the saved information did not fit what it found.

That one meaning shows up in two very different situations. Which one you have decides the fix, so look at where you saw the code before you do anything.

• At startup, with hiberfil.sys. A blue recovery screen appears instead of the sign-in screen and names the file \hiberfil.sys with error code 0xc0000719. hiberfil.sys is the file in the root of drive C: where Windows saves memory for hibernation and for Fast Startup. Windows could not resume from it.
• In Device Manager, as Status. In a device's Properties > Events tab you see a Device not migrated entry. Its text ends with Status: 0xC0000719. This is the form people search as status: 0xc0000719 or status 0xc0000719.
• Other spellings. 0xc0000719, error code 0xc0000719 and error 0xc0000719 are all the same code. 0x0000719 is a typo with one zero missing; it is the same code too.

A Device not migrated entry with Status 0xC0000719 (Windows 10, as posted on Microsoft Q&A)

Device SWD\MMDEVAPI{0.0.1.00000000}.{98cd4dff-961f-44d5-9a68-746042da58a5} was not migrated due to partial or ambiguous match.
Last Device Instance Id: SWD\MMDEVAPI{0.0.0.00000000}.{b995c36b-fdae-4b3d-b707-e76960b35554}
Class Guid: {c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
Location Path:
Migration Rank: 0xF00000000000F120
Present: false
Status: 0xC0000719

Why 0xC0000719 appears: the causes, ranked

At startup, the cause is most often a hibernation image that was cut off or no longer matches the PC: a power loss, a forced shutdown or a battery that ran out while Windows was saving it. Less often the hardware changed between shutdown and start, such as RAM, an SSD or a BIOS update. Rarely the disk has errors where hiberfil.sys sits.

Users on Quora and Reddit report the startup error right after cleaning a PC and reseating the CPU cooler, and on laptops that ran out of battery. Both fit the same pattern: the saved image no longer matched the hardware. The second start usually works.

How to fix error 0xC0000719 in Windows 11 and 10

Fixes 1 to 5 are for the startup error with hiberfil.sys, in the order that costs least. Fix 6 is for the Device not migrated entry in Device Manager. Fix 7 is for both when the problem keeps coming back.

Fix 1. Power the PC off completely and start it cold

5 minutesLow riskYou see the blue recovery screen with \hiberfil.sys and 0xc0000719 at startup.

The error comes from one failed attempt to resume a saved image. A full power off clears the hardware state, and on the next start Windows often discards the image it cannot use and boots fresh. Users report that the second start works in many cases.

1. Hold the power button for 10 seconds until the PC is fully off.
2. Unplug every USB device except the keyboard and mouse: drives, docks, phones, printers and hubs.
3. On a desktop, switch off the power supply or unplug the cable for 30 seconds. On a laptop, plug in the charger.
4. Press the power button to start the PC.
5. If the recovery screen offers to continue, press Enter and let Windows start normally.

Fix 2. Delete hiberfil.sys from the Windows recovery environment

15 to 30 minutesRead the warningThe hiberfil.sys 0xc0000719 screen comes back after Fix 1 and Windows does not start.

Windows tries to resume from hiberfil.sys as long as the file holds a saved image. Deleting it from outside Windows leaves nothing to resume, so the next start is a normal boot. Windows creates a new file later (Fix 3).

First open the recovery environment. After two or three failed starts Windows opens it by itself; select Advanced options. Step by step: Run Startup Repair. You can let Startup Repair run once first: it sometimes clears the resume on its own.

1. Select Troubleshoot > Advanced options > Command Prompt.
2. Type dir /a C:\hiberfil.sys and press Enter. If it says the file is not found, try D: and E: instead of C:. The recovery environment often gives the Windows drive another letter.
3. On the drive where the file is found, type attrib -s -h C:\hiberfil.sys and press Enter (use your letter).
4. Type del C:\hiberfil.sys and press Enter.
5. Type exit and press Enter.
6. Select Continue to start Windows.

Recovery environment Command Prompt (replace C: with the drive where the file is found)

dir /a C:\hiberfil.sys
attrib -s -h C:\hiberfil.sys
del C:\hiberfil.sys
exit

Fix 3. Rebuild the hibernation file with powercfg

5 minutesLow riskWindows starts again after the startup error, or after Fix 1 or Fix 2.

Turning hibernation off makes Windows delete hiberfil.sys, and turning it on creates a clean new one. This replaces a damaged file that could cause 0xC0000719 again at the next resume or Fast Startup.

1. Right-click Start and select Terminal (Admin). On Windows 10, select Windows PowerShell (Admin).
2. Select Yes when Windows asks for permission.
3. Type powercfg /h off and press Enter. This deletes hiberfil.sys.
4. Type powercfg /h on and press Enter. This creates a new hiberfil.sys.
5. Restart the PC with Start > Power > Restart.
6. Then use Shut down, wait a minute and start the PC again to test Fast Startup.

Terminal (Admin)

powercfg /h off
powercfg /h on

Fix 4. Turn off Fast Startup when the error follows a shut down

3 minutesLow riskThe 0xc0000719 screen appears after Shut down and a new start, but not after Restart.

With Fast Startup, Shut down saves the Windows kernel and its drivers to hiberfil.sys and resumes from it at the next start. Restart does not use the file. When only Shut down fails, the saved image is the problem, and turning Fast Startup off removes the resume.

1. Press Win + R, type powercfg.cpl and select OK.
2. In the left pane, select Choose what the power buttons do.
3. Select Change settings that are currently unavailable.
4. Under Shutdown settings, clear Turn on fast startup (recommended).
5. Select Save changes.

The full procedure with Windows 11 screenshots: Turn off Fast Startup.

Fix 5. Check the disk and repair Windows system files

20 to 60 minutesLow riskThe startup error returns after Fix 3 and Fix 4, or the PC had a power loss or crash.

hiberfil.sys is one large file on drive C:. File system errors or bad sectors under it, or damaged Windows power components, can corrupt each new image. CHKDSK repairs the file system, and SFC with DISM repairs Windows files.

1. Check drive C: for file system errors and bad sectors. Step by step: Check a disk for errors (chkdsk).
2. Restart so CHKDSK can finish if it asks to run at the next start.
3. Repair Windows system files with SFC and DISM. Step by step: Run DISM and SFC to repair Windows system files.
4. Restart, then do Fix 3 once more so a new hiberfil.sys is written.

• CHKDSK finds bad sectors: back up your files now. A failing drive will damage hiberfil.sys again.
• SFC repairs files: restart, then do Fix 3 once more so the new hiberfil.sys is written by repaired components.
• Both report nothing: the disk and Windows are fine; go to Fix 7.

Fix 6. Fix the device behind a Device not migrated entry

10 to 15 minutesLow riskYou see Status: 0xC0000719 in a Device not migrated entry, or a USB device stopped working after a Windows update, as in the question above.

The entry says Windows could not carry the device's old settings over after an update, so it set the device up again. That is harmless when the device works. When it does not, a clean driver reinstall makes Windows set it up from scratch.

1. Right-click Start and select Device Manager.
2. Right-click the device that does not work, or the one you saw in the event, and select Properties.
3. Open the Events tab and read the entries: Device not migrated, then Device configured and Device started below it mean Windows set the device up again.
4. Select the Device not migrated entry. If the text says Present: false, the device is not connected and needs no fix.
5. If the device is present and does not work, continue with the driver reinstall below.

Reinstall the driver of that device, and for USB problems also the drivers under Universal Serial Bus controllers. Step by step: Update, roll back or reinstall a driver.

If Device Manager also shows a yellow mark on the device, or Event Viewer logs a Kernel-PnP error for it, follow our guide to Kernel-PnP Event ID 411. It reads the device and its Problem code.

Fix 7. Update the chipset driver and the BIOS

20 to 40 minutesRead the warningThe startup error keeps coming back after Fixes 1 to 5, or USB devices fail on every port after Fix 6.

Hibernation, Fast Startup and USB controllers all depend on the chipset driver and the firmware's power settings. An old chipset driver or BIOS can write or read the saved image wrongly, and both are updated only by the PC or motherboard maker.

1. Press Win + R, type msinfo32 and press Enter.
2. Note System Manufacturer, System Model and BIOS Version/Date.
3. Open the support page of your PC or motherboard maker and find your exact model.
4. Install the newest chipset driver first and restart.
5. If the maker lists a newer BIOS, install it with the maker's tool or instructions and let the PC restart by itself.
6. Do Fix 3 once more, then test Shut down and a new start twice.

If 0xC0000719 continues: what to read and when it is hardware

Windows writes what happened at each start to Event Viewer. Open it with Win + R, eventvwr.msc, then Windows Logs > System. Look for Kernel-Power and Kernel-Boot entries at the time of the error, and for Disk or Ntfs errors that point to the drive.

• The error came right after a hardware change: put the old part back or reseat the new one. Users report the error after reseating a CPU cooler and RAM, and a clean start once the parts sat well.
• Run a memory test if the PC also crashes at other times: How to test your RAM with Windows Memory Diagnostic. Bad RAM corrupts the saved image.
• Disk errors in the System log or bad sectors from CHKDSK: back up and replace the drive.
• Contact the PC maker with your model, BIOS version, the time of the error and the Kernel-Power entries. HP and MSI owners report the error in the makers' forums, so name the error code in your request.

If nothing else works and Windows starts, a repair install keeps your files and apps and replaces Windows system files: Reinstall Windows without losing files.

How to keep 0xC0000719 from coming back

Frequently asked questions

What does error code 0xc0000719 mean?

It is the NTSTATUS value STATUS_CONTEXT_MISMATCH, which Microsoft describes as "The provided context did not match the target." Windows saved information about something and later found it did not match. At startup that saved information is the hibernation or Fast Startup image in hiberfil.sys, so Windows cannot resume. In Device Manager it is a device's old settings that did not match after an update, logged as a Device not migrated entry.

What is hiberfil.sys and can I delete it?

hiberfil.sys is a hidden system file in the root of drive C:. Windows writes the contents of memory to it when the PC hibernates, and the kernel and drivers when you shut down with Fast Startup on. You can remove it safely, but only with powercfg /h off while Windows runs, or from the recovery environment when Windows does not start (Fix 2). Deleting it loses only the hibernated session, not your saved files.

How do I fix hiberfil.sys error 0xc0000719 when Windows will not start?

Power the PC off fully with the power button, unplug USB devices and start again (Fix 1). If the recovery screen returns, open Advanced options, then Command Prompt, find the drive that holds hiberfil.sys with dir /a C:\hiberfil.sys, remove its hidden and system attributes and delete it (Fix 2). Windows then starts without trying to resume. Once it runs, rebuild the file with powercfg /h off and powercfg /h on (Fix 3).

What does Status: 0xC0000719 in a Device not migrated event mean?

It means that after a Windows update, Windows could not match the saved settings of a device to the device it found, so it set the device up again. The entry says the device was not migrated due to partial or ambiguous match. If the text shows Present: false, the device is not connected and nothing needs fixing. If a present device stopped working, reinstall its driver (Fix 6).

Does 0xC0000719 stop my USB ports from working?

Not by itself. A Device not migrated entry with Status 0xC0000719 is a record of how Windows set a device up after an update. When USB devices really fail on every port, the cause is usually the USB controller or chipset driver. Reinstall the drivers under Universal Serial Bus controllers (Fix 6) and update the chipset driver and BIOS from your PC maker (Fix 7).

Is 0xc0000719 on Windows 11 different from Windows 10?

No. The code and its meaning are the same on Windows 11 and Windows 10, and the fixes on this page work on both. Paths differ only in small details, such as Terminal (Admin) on Windows 11 and Windows PowerShell (Admin) on Windows 10. Windows 10 no longer gets support since 14 October 2025, so a recurring error on Windows 10 may not get a fix from the PC maker.

Is 0x0000719 the same error as 0xC0000719?

Almost certainly yes. 0x0000719 is how the code is often typed when the C is dropped, and the searches for it lead to the same hiberfil.sys and Device not migrated reports. If you see 0x00000719 in a different program, such as an installer, read the full message: a code without the leading C can be a different kind of error, and this page would then not apply.

Will I lose my files when I delete hiberfil.sys?

No. Your documents, photos and apps stay where they are. You lose only what was open in memory when the PC hibernated or shut down with Fast Startup, for example a document you had not saved. That is why the recovery screen error is worth a cold start first (Fix 1): if Windows can still resume, it keeps that session.

Should I turn off hibernation for good?

Only if you do not use it. Without hibernation, powercfg /h off frees several gigabytes on drive C: and the startup error with hiberfil.sys cannot happen, but Fast Startup goes with it, so cold starts take a few seconds longer. If you use hibernation on a laptop, rebuild the file instead (Fix 3) and keep it on.

I searched for накопитель (drive). Does this page help?

This page is about the Windows error 0xC0000719, in English. If your drive appears in the message, the startup error with hiberfil.sys concerns the system drive C:, where Windows keeps the hibernation file. Fix 2 and Fix 5 cover that drive: deleting the file from the recovery environment and checking the disk for errors.