Save open work and back up important files. Use instructions for your exact device and software version. If Windows cannot start, see the startup guide.
Work through these checks
0 of 3 complete01Run the DISM StartComponentCleanup command to purge outdated and corrupted update logs.
- Run the DISM StartComponentCleanup command to purge outdated and corrupted update logs.
Check whether the original symptom still occurs.
If it does not helpContinue only if this check applies to your device. Consult its manufacturer if you are unsure.
02Use the System File Checker (sFC) tool to scan and restore missing assemblies.
- Use the System File Checker (sFC) tool to scan and restore missing assemblies.
Check whether the original symptom still occurs.
If it does not helpContinue only if this check applies to your device. Consult its manufacturer if you are unsure.
03Check the CBS.log file to identify and manually reinstall the missing package identifiers.
- Check the CBS.log file to identify and manually reinstall the missing package identifiers.
Check whether the original symptom still occurs.
If it does not helpContinue only if this check applies to your device. Consult its manufacturer if you are unsure.
Possible causes
- Missing assembly metadata required for verifying cumulative update configurations.
- Corrupted Component-Based Servicing (CBS) log references in the system registry.
- Interrupted installation steps from previously attempted updates.
Was this helpful?
Your progress is saved on this device.