Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0xC0000221

0xC0000221 bad image checksum and 0xC0000428 signature check failure at boot

14 min read Updated October 5, 2026 Windows Crashes & Boot Recovery

Fix it now

These are refusals, not crashes. Windows was asked to load a file, checked it, and would not trust the result. The file name on the screen decides what you do next – and if the name is winload.exe with 0xC0000428 or 0xC0000605, the machine is running a non-RTM Windows image that has passed its expiry date and no repair exists.

Run these from an elevated Command Prompt if Windows still starts

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
pnputil /enum-drivers
  1. Read the file name on the error screen first. It is the single most useful thing there.
  2. If it is winload.exe or winload.efi with 0xC0000428 or 0xC0000605, stop repairing. Microsoft documents both against a non-RTM image – preview, evaluation or trial – past its built-in expiry, and the only route is a reinstall or redeploy from production media.
  3. If the file belongs to Windows, repair it with the two commands above, and offline from the recovery environment if the machine will not start.
  4. If it belongs to a product you installed, get the current build from that vendor.
  5. Only then look at hardware. Microsoft names faulty RAM and a corrupted page file alongside disk errors as causes of a checksum mismatch, so run a memory diagnostic before replacing a drive – especially if the named file changes between attempts.

Booting with driver signature enforcement disabled is a way to get one working session, not a fix. A machine left in that state loads drivers nobody has vouched for.

If the machine starts normally with enforcement on, you are done. If not, the next section explains which of the three checks failed and what each one is really telling you.

Why it happens

Every executable image carries a checksum in its header, written when the file was built. The loader can recompute it and compare, which catches a file damaged in transit, truncated by an interrupted write, or read back from a failing sector. 0xC0000221 is that check failing. Microsoft describes it as a driver or a system DLL being corrupted, from a serious error in a driver or other system file – and, importantly, also from faulty hardware in the I/O path: a disk error, faulty RAM, or a corrupted page file.

Signature verification is a different question. 0xC0000428 is Windows saying it cannot verify the digital signature for the file. It is tempting to read that as an unsigned third-party driver, and sometimes it is. But the case Microsoft actually documents for this boot screen is winload.exe on an image that was never an RTM build: a preview or evaluation image with an expiry date, past that date. Microsoft’s documented remedy there is not a repair. It is to deploy again from a non-preview image, because a preview image’s expiry cannot be extended.

0xC0000605 is the same story stated plainly: Info, a component of the operating system has expired. Microsoft raises it from winload.exe on a non-RTM Windows image that has passed its built-in expiry. It is not a third-party driver certificate problem, and there is no repair – the machine is reinstalled or redeployed from a production image.

That matters because the popular explanation for a driver that stops loading – its signing certificate expired – is contradicted by Microsoft. A kernel-mode driver package whose signature is timestamped before the leaf signing certificate’s expiry keeps working after that certificate expires. So plain expiry is rarely why an old agent suddenly blocks a boot. Look instead for an untimestamped or revoked signature, or for a security feature that has newly started enforcing a check the machine was not applying before: memory integrity being turned on, Secure Boot, or a revocation list update.

A non-RTM Windows image has expired

You have this one if 0xC0000428 or 0xC0000605 naming winload.exe or winload.efi, on a machine built from a preview, evaluation or trial image, that has been running for months and stopped on a predictable date.

  1. Confirm what the image was. A preview or evaluation build is the whole answer and no repair applies.
  2. Restore from a recent backup only if you have one from before the expiry; it will expire again.
  3. Deploy the machine again from a production RTM image and move the data across.
  4. Do not spend time on drivers, certificates or signature enforcement. None of them is involved.

Microsoft states directly that there is no way to extend the expiry of a preview image. Treat any advice that offers one as wrong.

A Windows system file is damaged

You have this one if 0xC0000221 naming a file under the Windows folder that belongs to the operating system rather than to anything you installed.

  1. Run sfc /scannow from an elevated Command Prompt if Windows starts, and read the summary line.
  2. Follow with DISM /Online /Cleanup-Image /RestoreHealth so the component store itself is repaired.
  3. If Windows will not start, find the Windows volume in the recovery environment first, then run sfc /scannow /offbootdir=<vol>\ /offwindir=<vol>\Windows.
  4. Check free space. Microsoft suggests keeping 10 to 15 per cent of the volume free, because servicing needs room to work.

A security feature has started enforcing a check

You have this one if 0xC0000428 naming a third-party driver, shortly after memory integrity was enabled, Secure Boot was turned on, or a revocation update was installed.

  1. Read the CodeIntegrity operational log in Event Viewer, under Applications and Services Logs, Microsoft, Windows. It names the file that was rejected, which the stop code does not.
  2. Get a currently signed build from the vendor rather than working around the check.
  3. If a feature was enabled immediately before the failure, turning it back off restores service while you source a signed driver – but treat that as temporary and reversible, not as the fix.
  4. Remove the driver package if no acceptable build exists.

0x00000145, SECURE_BOOT_VIOLATION, often accompanies this. It names no file: parameter 1 is a failure status and parameters 2 and 3 are the address and size of the Secure Boot policy. The CodeIntegrity log is where the file name lives.

Hardware in the I/O path

You have this one if The named file is different on different attempts, or a repair works once and the failure comes back within days.

  1. Image the drive first if the data matters. A /r pass reads every sector and is exactly the load a marginal drive fails under.
  2. Run a memory diagnostic with mdsched.exe. Microsoft lists faulty RAM and a corrupted page file alongside disk errors as causes of a checksum mismatch.
  3. Confirm the Windows volume letter in the recovery environment – it is rarely C: – and run chkdsk <vol>: /f /r against that.
  4. Repair the system files again afterwards, since anything that sat on relocated sectors may still be wrong.

Full reference

Three different checks, three different answers

Code What failed Published meaning What fixes it
0xC0000221 The image checksum A driver or system DLL is corrupted; the header checksum does not match Repair or replace the file; then check RAM, disk and page file
0xC0000428 Signature verification Windows cannot verify the digital signature for this file A correctly signed build – or, on winload.exe, a redeploy from RTM media
0xC0000605 An expiry date A component of the operating system has expired Reinstall or redeploy from a production image. No repair exists
0xC000012F An image load Not published by Microsoft Diagnose it like 0xC0000221: repair or replace the file
0x00000145 Secure Boot policy SECURE_BOOT_VIOLATION. Parameter 1 is a failure status; 2 and 3 are the policy address and size Read the CodeIntegrity log; the bug check names no file

What a driver signing certificate expiring actually does

Very little, on its own. Microsoft states that as long as driver packages are timestamped before the expiration date of the leaf signing certificate, the packages continue working. That single sentence disposes of the most popular explanation for these boot failures. If a driver that worked for years has stopped loading and nothing else changed, the candidates worth your time are an untimestamped signature, a certificate that has been revoked or blocklisted rather than merely expired, and a policy such as memory integrity or a Secure Boot revocation update that has newly begun enforcing something.

Removing a boot-blocking driver offline, safely

In the recovery environment the recovery image is X: and the Windows volume is usually D: or E:, almost never C:. A remove-driver command aimed at C: either fails or operates on the wrong image. And Microsoft warns that removing boot-critical drivers can make the image unbootable: oemNN.inf names are opaque, and pulling a storage or chipset driver leaves a machine with no route back.

  1. Find the Windows volume: run diskpart, then list volume, or check dir X:\ through dir Z:\ for a Windows folder.
  2. List what is installed: dism /image:<vol>\ /get-drivers /format:table.
  3. Confirm the original filename, provider and class of the package before you touch it. Never remove a storage, chipset or other boot-critical driver.
  4. Take a copy first: pnputil /export-driver <oemNN.inf> <folder> exports the package so the removal can be undone.
  5. Only then: dism /image:<vol>\ /remove-driver /driver:oemNN.inf.
  6. Restart and, if the machine starts, confirm with pnputil /enum-drivers that only packages you expect remain.

Checking the disk without finishing it off

chkdsk /r locates bad sectors and recovers readable information, and includes everything /f does. Microsoft notes that on large hard disks it takes a considerable time because it reads every sector, and that on an SSD it checks every sector’s physical integrity and replaces bad ones where it can. On a drive that is already returning errors that is a heavy, sustained workload. Take a sector-level image first, then run the check against the image or against a drive you have already copied.

Where to read what was actually rejected

Log or tool What it tells you
CodeIntegrity operational log The specific file whose signature or hash was rejected
System log Errors from the disk source, which point at hardware rather than signing
sfc /scannow output Whether Windows found and repaired its own damaged files
pnputil /enum-drivers Every third-party driver package on the machine, with its provider and version
dism /image:<vol>\ /get-drivers /format:table The same list against an offline image, from the recovery environment

What not to do

  • Do not leave driver signature enforcement disabled. It removes one of the few checks between a kernel driver and the operating system, and usually prevents other security features from working.
  • Do not chase an expired certificate on a machine showing 0xC0000605. That code is an expired Windows image, not an expired driver.
  • Do not replace a drive on 0xC0000221 without testing memory first. A corrupted page file and faulty RAM are documented causes and produce the same symptom.
  • Do not remove driver packages by deleting files. Use dism /remove-driver or the vendor’s own removal tool, and export first.
  • Do not treat a repeat failure as bad luck. A checksum mismatch that returns after a successful repair is a hardware statement.

When a licence is the actual fix

Most of this costs nothing: repairing a Windows file, testing memory and installing a current free driver are all free, and an expired preview image needs a redeploy rather than a purchase. There is one case where money is genuinely the fix. If the file blocking the boot belongs to an endpoint agent whose vendor no longer produces a build for your Windows version, or whose signature has been revoked rather than merely expired, no repair command will make Windows accept it and disabling the check leaves the machine trusting anything. Start with what you already own: Microsoft Defender Antivirus ships in Windows at no extra cost and removes the third-party kernel driver from the picture entirely. Where you need centrally managed protection instead, Sophos Intercept X Advanced is one supported route, maintained against current Windows builds with current signing and updated centrally rather than machine by machine. Arco supplies Sophos licences and will size the tier and seat count to the machines you actually need to cover – and will say so if Defender already covers you.

Every code this article covers

Code What it points at Source
0xC0000221 A driver or a system DLL is corrupted: the file header checksum does not match the expected checksum. Microsoft also names faulty hardware in the I/O path – a disk error, faulty RAM or a corrupted page file Microsoft Learn
0xC0000428 Windows cannot verify the digital signature for this file. The case Microsoft documents for this boot screen is winload.exe on a preview image past its expiry date, resolved by deploying from a non-preview image Microsoft Learn
0xC0000605 A component of the operating system has expired: a non-RTM image – preview, evaluation or trial – past its built-in expiry. There is no repair; the machine is reinstalled or redeployed. It is not a driver signing problem Microsoft Learn
0xC000012F Seen alongside the image validation failures above. Microsoft publishes no meaning for this value that we could reach, so treat it as an image the loader would not accept and diagnose it as you would 0xC0000221 not published by the vendor
0x00000145 SECURE_BOOT_VIOLATION: Secure Boot policy enforcement could not start. Parameter 1 is the failure status; parameters 2 and 3 are the address and size of the policy. It names no file, so pair it with the CodeIntegrity operational log Microsoft Learn

Confirm the fix worked

  1. The machine starts normally with driver signature enforcement active.
  2. sfc /scannow reports no integrity violations.
  3. The CodeIntegrity operational log records no further rejections after a restart.
  4. pnputil /enum-drivers lists only driver packages you expect, at current versions.
  5. If hardware was suspected, a full memory diagnostic pass and a drive health check both come back clean.

Questions people ask about this

My driver’s certificate expired. Is that why it stopped loading?

Probably not. Microsoft states that driver packages timestamped before the expiry of the leaf signing certificate continue working. Plain expiry is rarely the cause. Look for an untimestamped or revoked signature, or a security feature such as memory integrity that has newly started enforcing a check.

I see 0xC0000605 on winload.exe. What driver is at fault?

None. Microsoft publishes that screen as a component of the operating system having expired, raised on a non-RTM image – preview, evaluation or trial – past its expiry date. There is no repair and no driver involved. The machine has to be reinstalled or redeployed from a production image.

Can I permanently turn off driver signature enforcement?

You can put a machine in a state where it loads unsigned drivers, and you should not. It removes one of the few checks standing between a kernel driver and the operating system, usually breaks other security features, and does nothing about the underlying problem.

Is a bad image checksum a sign of malware?

It can be, but damage is more common. Interrupted writes, bad sectors, faulty memory and a corrupted page file all produce it. Run a full offline scan to settle the question, then repair the file – rather than assuming either answer.

Why did it work yesterday and not today?

Something started enforcing a check, or something got damaged. The common triggers are memory integrity or Secure Boot being enabled by an update or a policy, a revocation list update, and hardware in the I/O path beginning to fail. On an evaluation or preview build, the trigger is simply the date.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Domain controller will not boot – 0xC00002E2 directory services init failure Free Fix DPC_WATCHDOG_VIOLATION 0x00000133 – PC freezes then blue screens Free Fix MANUALLY_INITIATED_CRASH 0x000000E2 and missing memory dump files Free Fix Disk I/O device error 0x8007045D during Windows repair, backup or setup
โ† Back to Knowledge Base