WindowsAdvanced

How to Fix “Something Didn’t Go as Planned. No Need to Worry – Undoing Changes” Windows Update Error in Windows 11/10

A Windows PC may occasionally restart during an update and display a message similar to: “Something didn’t go as planned. No need to worry – undoing changes....

Bison Technical Team Enterprise IT specialists

Updated 29 Aug 2026 20 min read 0 total views

A Windows PC may occasionally restart during an update and display a message similar to:

“Something didn’t go as planned. No need to worry – undoing changes. Please keep your computer on.”

This message normally means that Windows attempted to install an update but encountered a problem during the installation, configuration, or restart phase. Windows then initiated a rollback to return the computer to its previous working state.

The rollback mechanism is designed to protect Windows from booting with an incomplete or damaged update. However, if the underlying problem is not corrected, Windows Update may download the same update again, restart the computer, fail again, and repeatedly display the same message.

This problem can occur with:

Windows 11 cumulative updates
Windows 10 cumulative updates
Monthly security updates
.NET Framework updates
Feature updates
Servicing updates
Driver updates delivered through Windows Update
Preview updates
Optional Windows updates

The solutions below progress from basic checks to advanced Windows servicing repairs.

What Does “Something Didn’t Go as Planned” Mean?

Windows updates normally pass through several stages:

Windows checks for available updates.
Update packages are downloaded.
Windows validates the packages.
Update files are staged in the component store.
Installation begins.
Some updates are configured while Windows is running.
The computer restarts.
Windows performs offline update operations.
The update is committed.
Windows starts normally.

If a critical operation fails during the later stages, Windows may determine that continuing with the partially installed update could leave the operating system unstable.

Windows therefore reverses the changes.

That is when you may see:

Something didn’t go as planned.

followed by:

No need to worry – undoing changes. Please keep your computer on.

Do not force the computer off while Windows is actively undoing the changes unless the system has clearly remained frozen for an abnormally long period and other recovery options are necessary.

Common Causes of the Error

There is no single cause for this Windows Update message. Common causes include:

1. Corrupted Windows Update Cache

Downloaded update packages are primarily stored under:

C:\Windows\SoftwareDistribution

If files in this location become incomplete or corrupted, Windows may repeatedly attempt to install a damaged update package.

2. Windows Component Store Corruption

Windows uses the component store located primarily under:

C:\Windows\WinSxS

for servicing and updating the operating system.

Corruption in the component store can prevent cumulative and feature updates from installing correctly.

3. Damaged System Files

Important Windows system files may be:

corrupted
missing
incorrectly modified
replaced by incompatible versions

System File Checker and DISM are commonly used to diagnose and repair these problems.

4. Insufficient Free Disk Space

Windows needs working space to:

download updates
extract packages
create temporary files
maintain rollback information
update the component store

A nearly full C: drive can therefore cause update failures.

5. Driver Compatibility Problems

An incompatible driver can prevent an update from completing.

Frequently involved categories include:

storage drivers
chipset drivers
display drivers
network adapters
Bluetooth drivers
audio drivers
third-party security filter drivers

6. Antivirus or Endpoint Security Interference

Third-party antivirus, endpoint security, anti-ransomware, application-control, or disk-filter software can sometimes interfere with Windows servicing operations.

7. Interrupted Update

An update can become corrupted if installation is interrupted because of:

sudden power failure
forced shutdown
laptop battery depletion
unexpected restart
unstable storage
system crash

8. Windows Update Service Problems

Windows Update depends on multiple services and components.

Problems involving services such as Windows Update, BITS, Cryptographic Services, or Windows Modules Installer can prevent successful installation.

9. Corrupted SoftwareDistribution or Catroot2 Data

Two important locations involved in Windows servicing are:

C:\Windows\SoftwareDistribution

and

C:\Windows\System32\catroot2

Resetting these locations can resolve persistent update problems.

10. VPN, Proxy or Network Restrictions

Windows may have difficulty downloading or validating update components when the computer is behind:

an incorrectly configured proxy
restrictive firewall
VPN
web-filtering appliance
DNS filtering system
corporate update policy

Before Troubleshooting: Let Windows Finish Undoing Changes

If Windows currently displays:

Undoing changes. Please keep your computer on.

allow the rollback process to complete.

Depending on the PC, update, storage speed, and amount of work being reversed, this process can take time.

Repeatedly turning off the computer during rollback can make Windows servicing corruption worse.

Once Windows successfully returns to the desktop, begin troubleshooting.

Solution 1: Restart Windows

After Windows finishes rolling back the failed update:

Sign in normally.
Save all open files.
Select Start → Power → Restart.
Allow Windows to boot normally.
Try Windows Update again.

A proper restart can clear pending operations and temporary servicing conditions.

Solution 2: Check Free Disk Space

Open:

File Explorer → This PC

Check the available space on the Windows system drive, normally:

C:

If the drive is almost full, remove unnecessary data before attempting the update again.

You can also open:

Settings → System → Storage

Review:

Temporary files
Windows Update cleanup
Recycle Bin
Downloads
Delivery Optimization files
Temporary Internet files

Be careful before deleting the contents of the Downloads folder.

Solution 3: Disconnect Unnecessary USB Devices

Temporarily disconnect nonessential external hardware such as:

USB hard drives
flash drives
printers
scanners
webcams
USB adapters
docking devices
card readers

Keep only essential devices such as the keyboard, mouse, monitor, and required network connection.

Restart the PC and retry the update.

Solution 4: Disable VPN or Proxy Temporarily

If you use a VPN, disconnect it temporarily.

Check the Windows proxy configuration under:

Settings → Network & Internet → Proxy

If an unnecessary manual proxy is configured, disable it temporarily and test Windows Update again.

Do not remove a proxy configuration required by your organization without consulting the network administrator.

Solution 5: Run the Windows Update Troubleshooter

On current Windows 11 installations, Microsoft provides automated Windows Update diagnostics through the Get Help/troubleshooting experience.

You can also check:

Settings → System → Troubleshoot → Other troubleshooters

Locate Windows Update and run the available troubleshooter.

Allow Windows to diagnose the system and apply recommended fixes.

Restart the computer afterward and retry Windows Update.

Solution 6: Identify Which Update Is Failing

Before performing advanced repairs, identify the failed KB number.

Open:

Settings → Windows Update → Update history

Look under sections such as:

Quality Updates
Driver Updates
Definition Updates
Other Updates

Look for entries marked as failed.

For example:

2026-xx Cumulative Update for Windows 11 ... (KBxxxxxxx)

Write down the KB number.

This is particularly useful because the same update may repeatedly trigger the rollback.

Solution 7: Run System File Checker

Open Command Prompt as Administrator.

Run:

SFC /SCANNOW

Allow the scan to reach 100%.

Possible results include:

No integrity violations

Windows did not detect damaged protected system files.

Corrupt files were found and successfully repaired

Restart Windows and retry the update.

Corrupt files were found but some could not be repaired

Proceed to DISM repair.

Solution 8: Repair Windows Component Store Using DISM

Open Command Prompt as Administrator.

Run:

DISM /Online /Cleanup-Image /CheckHealth

Next run:

DISM /Online /Cleanup-Image /ScanHealth

Then run:

DISM /Online /Cleanup-Image /RestoreHealth

DISM checks and repairs the Windows component store used by Windows servicing.

The RestoreHealth operation may take considerable time and may appear to pause at certain percentages. Do not terminate it simply because the percentage temporarily stops changing.

After DISM completes successfully, run:

SFC /SCANNOW

again.

Restart Windows and retry Windows Update.

Microsoft documents DISM followed by SFC as a supported approach for repairing Windows Update/component-store corruption.

Solution 9: Reset Windows Update Components

If the problem continues, resetting the Windows Update cache is one of the most effective advanced troubleshooting procedures.

Open Command Prompt as Administrator.

Run:

net stop wuauserv

net stop bits

net stop cryptsvc

Now rename the Windows Update cache folders:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 catroot2.old

Restart the services:

net start cryptsvc

net start bits

net start wuauserv

Restart Windows.

Windows will recreate the required update cache directories.

Then open:

Settings → Windows Update → Check for updates

and allow Windows to download the update again.

Important

Do not permanently delete Windows servicing folders such as WinSxS.

Renaming SoftwareDistribution and catroot2 is substantially different from manually deleting critical component-store files.

Solution 10: Check Windows Update Services

Press:

Windows + R

Enter:

services.msc

Check important services including:

Windows Update

Service name:

wuauserv

Background Intelligent Transfer Service

Service name:

BITS

Cryptographic Services

Service name:

CryptSvc

Windows Modules Installer

Service name:

TrustedInstaller

Do not blindly force all services to one startup type. Windows uses trigger-start and demand-start behavior for several services.

The important point is to ensure that services have not been deliberately disabled by:

optimization utilities
privacy utilities
Windows Update blockers
debloating scripts
Group Policy
registry modifications
malware
previous troubleshooting tools

If Windows Update has intentionally been disabled by third-party software, reverse those changes before continuing.

Solution 11: Check Date and Time

Incorrect system time can interfere with secure communications and update operations.

Open:

Settings → Time & language → Date & time

Enable appropriate options such as:

Set time automatically

and verify the correct:

date
time
time zone

Then synchronize the clock and retry Windows Update.

Solution 12: Perform a Clean Boot

A clean boot helps determine whether third-party software is interfering with Windows Update.

Press:

Windows + R

Enter:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

This step is important.

Then temporarily disable the remaining non-Microsoft services.

Next open:

Task Manager → Startup apps

Disable unnecessary third-party startup programs.

Restart Windows and retry the update.

After troubleshooting, restore normal startup configuration.

Solution 13: Temporarily Remove Third-Party Antivirus

If the problem started after installing or upgrading third-party security software, the security application may be interfering with Windows servicing.

Temporarily uninstall the third-party antivirus or endpoint protection software if appropriate.

Restart Windows and retry the update.

Important: Do not leave the computer permanently unprotected. Reinstall or reactivate compatible security protection after troubleshooting.

In a managed corporate environment, consult the IT administrator before removing endpoint protection.

Solution 14: Check the Disk for Errors

File-system problems can also affect Windows Update.

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For a more comprehensive repair requiring a restart, you may use:

chkdsk C: /f

Windows may report that the volume is currently in use and ask whether the disk should be checked during the next restart.

Type:

Y

and restart the computer.

Solution 15: Update Important Device Drivers

Check your computer or motherboard manufacturer's support website for current drivers, especially:

chipset
storage controller
Intel/AMD platform drivers
graphics
network
Wi-Fi
Bluetooth
BIOS/UEFI

Driver incompatibility is particularly relevant when Windows Update fails during the restart or configuration stage.

Avoid downloading drivers from unknown third-party driver websites.

Solution 16: Manually Install the Failed KB Update

If Windows Update repeatedly fails on one specific KB, identify its KB number from:

Settings → Windows Update → Update history

You can then obtain the appropriate package from the official Microsoft Update Catalog.

Search using the KB number.

For example:

KBxxxxxxx

Select the package matching your:

Windows version
architecture
release/build
product

Download and install the package manually.

Restart when requested.

Solution 17: Check Whether the Update Is Already Partially Installed

Sometimes update history can become confusing after a rollback.

Press:

Windows + R

Enter:

winver

Record the Windows version and OS build.

You can also run:

systeminfo

from Command Prompt.

Compare the installed build with the update you are attempting to install.

This helps determine whether the update:

completely failed
partially installed
was superseded
was successfully installed despite misleading history

Solution 18: Check Event Viewer

Advanced users and IT administrators should examine Windows logs.

Press:

Windows + X → Event Viewer

Check:

Windows Logs → Setup

and:

Windows Logs → System

Also inspect Windows Update-related operational logs where applicable.

Look for events occurring at the exact time the update failed.

Useful information can include:

KB/package identity
error code
driver failure
servicing failure
CBS error
disk error
unexpected restart

Solution 19: Check CBS.log

Windows servicing records detailed information in:

C:\Windows\Logs\CBS\CBS.log

This file is particularly useful when:

SFC cannot repair files
DISM reports corruption
cumulative updates repeatedly fail
Windows servicing packages cannot be installed

Search near the time of failure for entries containing terms such as:

Error

Failed

Corrupt

or relevant package identities.

CBS.log analysis is primarily recommended for experienced administrators because many warnings and informational messages in the log do not indicate a critical problem.

Solution 20: Check DISM.log

DISM operations are logged at:

C:\Windows\Logs\DISM\dism.log

If:

DISM /Online /Cleanup-Image /RestoreHealth

fails, inspect this log for the underlying error.

A common advanced situation is that DISM itself cannot obtain the files required to repair the component store.

What If DISM Says “Source Files Could Not Be Found”?

DISM normally attempts to obtain required repair content from configured servicing sources, which may include Windows Update.

If DISM cannot obtain the required files, you may need a compatible Windows installation image.

Mount a Windows ISO corresponding as closely as possible to the installed:

Windows edition
language
architecture
release
servicing level

Assume the mounted ISO appears as:

D:

Determine whether it contains:

D:\sources\install.wim

or:

D:\sources\install.esd

You can inspect available editions with a command such as:

DISM /Get-WimInfo /WimFile:D:\sources\install.wim

Then use the correct image index as the repair source.

Example:

DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:INDEX /LimitAccess

Replace INDEX with the correct image index.

Do not blindly use index 1 because different installation media can contain different editions at different indexes.

After DISM succeeds, run:

SFC /SCANNOW

and restart Windows.

Solution 21: Remove a Recently Failed Update from Windows Recovery

If Windows can no longer boot normally after the update, enter the Windows Recovery Environment.

Possible path:

Troubleshoot → Advanced options → Uninstall Updates

You may see options such as:

Uninstall latest quality update

or:

Uninstall latest feature update

Try removing the update that caused the boot problem.

This is especially useful when the computer enters a repeated:

install → restart → fail → undo changes

cycle.

Solution 22: Use System Restore

If System Restore was enabled before the problem started:

Open Windows Recovery Environment and select:

Troubleshoot → Advanced options → System Restore

Select a restore point created before the failed update.

System Restore can reverse certain:

driver changes
registry changes
system-file changes
application installations

while generally leaving personal documents intact.

Still, important data should always be backed up before major recovery operations.

Solution 23: Pause Windows Update Temporarily

If the update repeatedly fails even after Windows successfully rolls it back, temporarily pausing updates can prevent Windows from immediately repeating the installation while you troubleshoot.

Open:

Settings → Windows Update

and use the available Pause updates option.

This is a temporary workaround—not a permanent solution.

Security updates should not be indefinitely disabled.

Solution 24: Perform an In-Place Repair Upgrade

If Windows boots normally but Windows Update remains damaged despite:

Windows Update reset
DISM
SFC
driver updates
clean boot
manual KB installation

consider an in-place repair installation.

Use official Windows installation media compatible with the installed Windows version.

Launch:

setup.exe

from within Windows.

Where supported, select the option to keep:

Personal files and apps

A repair installation can replace damaged Windows components while preserving applications, files, and most settings.

Important

Always create a complete backup before performing an in-place repair.

Solution 25: Reset Windows as a Last Resort

If servicing corruption is severe and repair installation does not solve the issue, Windows provides recovery/reset options.

Open:

Settings → System → Recovery

Review:

Reset this PC

Depending on the selected option, Windows may allow you to keep personal files while reinstalling the operating system.

However, applications may need to be reinstalled.

Create a complete backup first.

Recommended Troubleshooting Sequence for IT Engineers

Instead of randomly applying fixes, use this sequence:

Step 1: Allow rollback to finish.

Step 2: Identify the failed KB and error code.

Step 3: Restart Windows.

Step 4: Verify adequate C: drive space.

Step 5: Disconnect unnecessary peripherals.

Step 6: Disable VPN/proxy temporarily.

Step 7: Run Windows Update troubleshooter.

Step 8: Run:

DISM /Online /Cleanup-Image /RestoreHealth

Step 9: Run:

SFC /SCANNOW

Step 10: Reset SoftwareDistribution and catroot2.

Step 11: Restart and retry Windows Update.

Step 12: Perform a clean boot if the update still fails.

Step 13: Check/update chipset, storage, graphics, and network drivers.

Step 14: Try manually installing the failed KB.

Step 15: Examine CBS.log, DISM.log, and Event Viewer.

Step 16: Use a matching repair source if DISM cannot repair Windows.

Step 17: Perform an in-place repair installation if servicing remains corrupted.

This sequence minimizes unnecessary changes while progressively moving toward more invasive repairs.

Useful Windows Update Repair Commands

Check component-store health

DISM /Online /Cleanup-Image /CheckHealth

Perform detailed component-store scan

DISM /Online /Cleanup-Image /ScanHealth

Repair Windows component store

DISM /Online /Cleanup-Image /RestoreHealth

Check and repair protected system files

SFC /SCANNOW

Check system drive online

CHKDSK C: /SCAN

Schedule disk repair

CHKDSK C: /F

Stop Windows Update

net stop wuauserv

Stop BITS

net stop bits

Stop Cryptographic Services

net stop cryptsvc

Rename Windows Update download database

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

Rename catalog database

ren C:\Windows\System32\catroot2 catroot2.old

Restart Cryptographic Services

net start cryptsvc

Restart BITS

net start bits

Restart Windows Update

net start wuauserv

Important: Do Not Randomly Delete WinSxS

Some online troubleshooting guides recommend deleting files manually from:

C:\Windows\WinSxS

This should not be done.

WinSxS is the Windows component store and is essential for:

Windows Update
Windows servicing
optional Windows features
DISM repair
system-file recovery

Deleting arbitrary files from WinSxS can convert a repairable Windows Update problem into serious operating-system corruption.

Use supported servicing tools such as DISM instead.

Why Does Windows Keep Installing the Same Failed Update?

Windows Update may continue offering the same update because Windows still determines that the required KB or servicing state is missing.

The cycle becomes:

Download update → Install → Restart → Installation fails → Undo changes → Windows starts → Update offered again

The correct solution is therefore usually to identify and repair the reason installation fails rather than permanently disabling Windows Update.

Can I Turn Off the PC While It Says “Undoing Changes”?

Normally, no.

Windows may be restoring:

registry changes
servicing packages
boot configuration
system files
component-store information

Interrupting this operation can potentially leave Windows in a less recoverable condition.

Keep laptops connected to AC power during major updates and rollback operations.

Does “Undoing Changes” Mean My Personal Files Are Deleted?

Normally, no.

The rollback process primarily reverses operating-system changes made by the failed update.

Your personal documents should generally remain unaffected.

Nevertheless, maintaining regular backups is strongly recommended because disk problems, corruption, or unrelated hardware failures can occur independently of Windows Update.

How to Prevent This Problem in the Future

You cannot prevent every Windows Update failure, but you can reduce the risk.

Before major updates:

Maintain sufficient free space on C:
Keep chipset and storage drivers current.
Avoid forcibly shutting down Windows during updates.
Keep laptops connected to power.
Remove unnecessary USB storage devices during major upgrades.
Maintain reliable backups.
Avoid unsupported Windows “debloat” and update-disabling scripts.
Do not manually modify WinSxS.
Keep third-party security products compatible with your Windows version.
Investigate recurring update failures instead of permanently disabling updates.

Frequently Asked Questions (FAQ)

1. What does “Something didn’t go as planned” mean in Windows Update?

It means Windows encountered a problem while installing or configuring an update and decided to roll back the update to restore the previous working state.

2. Why does Windows say “No need to worry – undoing changes”?

Windows is reversing changes made by the failed update so the operating system can return to its previous configuration.

3. Should I switch off my PC during “Undoing changes”?

Normally, no. Allow Windows to complete the rollback. Interrupting servicing operations can potentially cause additional corruption.

4. How long can “Undoing changes” take?

The time varies depending on the update, computer performance, storage speed, and number of changes being reversed. SSD-based computers are generally faster than systems using older mechanical hard drives.

5. Why does the same Windows update keep failing?

Possible causes include corrupted update files, component-store corruption, damaged system files, incompatible drivers, insufficient disk space, third-party software interference, or servicing problems.

6. Will resetting SoftwareDistribution delete my personal files?

No. SoftwareDistribution contains Windows Update-related data, not normal user documents.

Windows recreates the required update cache after it is reset.

7. Is it safe to rename the SoftwareDistribution folder?

Yes, renaming it after stopping the appropriate Windows Update services is a commonly used Windows Update troubleshooting procedure.

8. What is the catroot2 folder?

The catroot2 directory is used by Windows during update and cryptographic operations. Corrupted data in this folder can contribute to Windows Update failures.

9. Should I delete the catroot folder too?

No. Do not randomly delete similarly named system folders. The commonly reset update directory is:

C:\Windows\System32\catroot2

10. Should I run SFC or DISM first?

For persistent Windows Update/component-store problems, running:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

SFC /SCANNOW

is a strong troubleshooting sequence because SFC relies on Windows servicing resources when repairing protected system files.

11. What does DISM RestoreHealth do?

DISM checks the Windows component store and attempts to repair servicing corruption. The component store is critical to Windows Update and system-file repair.

12. What if DISM RestoreHealth fails?

Record the DISM error code and examine:

C:\Windows\Logs\DISM\dism.log

If required repair files cannot be obtained, use a compatible Windows installation image as a repair source.

13. Can antivirus cause Windows Update failure?

Yes. Some third-party security products or filter drivers can interfere with Windows servicing. Temporarily removing the software can help determine whether it is responsible.

14. Can low disk space cause “Something didn’t go as planned”?

Yes. Windows requires free disk space to download, stage, install, and roll back updates.

15. Can a faulty SSD or hard drive cause Windows Update failures?

Yes. File-system errors, storage corruption, or failing storage hardware can cause repeated update installation problems.

Recurring disk errors should be investigated independently of Windows Update.

16. Can I manually install the failed update?

Yes. If you know the KB number, the appropriate standalone package may be available from the official Microsoft Update Catalog.

17. Where can I find the failed KB number?

Open:

Settings → Windows Update → Update history

Look for failed or recently attempted updates.

18. Can outdated drivers cause this error?

Yes. Storage, chipset, graphics, network, and other low-level drivers can cause update compatibility problems, particularly during major Windows upgrades.

19. Can I permanently disable Windows Update to solve the problem?

Disabling Windows Update does not repair the underlying problem and can leave the PC without important security updates.

It is better to diagnose and correct the cause.

20. Will an in-place repair installation delete my applications?

When the appropriate Windows installation media and supported repair path are used, Windows Setup can generally provide an option to keep personal files and applications.

Always create a backup before proceeding.

21. What should I do if Windows cannot boot after the failed update?

Enter Windows Recovery Environment and try:

Troubleshoot → Advanced options → Uninstall Updates

You can also consider:

Startup Repair
System Restore
Safe Mode
Command Prompt
other recovery options

depending on the exact failure.

22. Is “Something didn’t go as planned” a specific Windows Update error code?

No. It is a general rollback message. The actual cause may have a separate hexadecimal error code recorded in Windows Update history, Event Viewer, CBS.log, or servicing logs.

23. Which logs are useful for diagnosing this problem?

Important diagnostic sources include:

C:\Windows\Logs\CBS\CBS.log

C:\Windows\Logs\DISM\dism.log

and relevant Event Viewer logs.

24. Does this error mean Windows needs to be reinstalled?

Usually not.

Most cases should first be investigated using:

Windows Update troubleshooting
DISM
SFC
update component reset
driver troubleshooting
clean boot
manual KB installation

A repair installation or reset should generally be considered only after less invasive troubleshooting fails.

25. What is the best quick repair sequence?

For a Windows installation that still boots normally:

Restart the computer.
Check available disk space.
Run the Windows Update troubleshooter.
Run DISM /Online /Cleanup-Image /RestoreHealth.
Run SFC /SCANNOW.
Reset Windows Update components if necessary.
Restart.
Check for updates again.

If the same update still fails, identify its KB number and exact error code before proceeding with more advanced troubleshooting.

Conclusion

The Windows Update message “Something didn’t go as planned. No need to worry – undoing changes” indicates that Windows could not safely complete an update and rolled the operating system back to its previous state.

The message itself is not the root cause. The underlying problem may involve corrupted update files, Windows component-store corruption, damaged system files, insufficient disk space, incompatible drivers, security software, interrupted servicing, or another Windows Update problem.

For most systems, the recommended troubleshooting approach is to first allow Windows to complete the rollback, identify the failed KB/error code, run the Windows Update troubleshooter, repair the Windows component store with DISM, run System File Checker, and reset the Windows Update cache if necessary.

Persistent failures should be investigated using CBS.log, DISM.log, Event Viewer, driver compatibility checks, and manual KB installation. If Windows servicing remains damaged after these procedures, an in-place repair installation can often repair the operating system without requiring a clean Windows installation.