Windows Update is responsible for delivering security fixes, cumulative updates, bug fixes, drivers, servicing components, and Windows feature updates. Normally these updates install automatically, but sometimes Windows repeatedly downloads an update and then fails to install it.

You may encounter messages such as:

• Updates failed
• Install error
• Download error
• Pending install
• Retry
• Something went wrong
• We couldn't complete the updates
• Undoing changes made to your computer
• Installation failed
• Restart required, followed by another failed installation

You may also receive an error code such as:

0x800f081f

0x800f0831

0x80070005

0x80070002

0x80070003

0x80070057

0x80070570

0x800705b4

0x80070422

0x80073712

0x80240034

0x80246007

0x800f0922

0xC1900101

The important point is that Windows Update failure is not a single problem. The cause can be damaged update files, Windows component-store corruption, insufficient disk space, a stopped service, incompatible drivers, security software, network problems, or an incomplete previous update.

This guide provides a systematic troubleshooting procedure rather than repeatedly clicking Retry.

1. Before Troubleshooting: Record the Error

Go to:

Settings → Windows Update → Update history

Look for the update that failed.

Record:

• KB number, for example KBxxxxxxx
• Error code
• Update name
• Date of failure
• Whether it is a cumulative, security, .NET, driver, or feature update

This information can significantly reduce troubleshooting time.

For example:

2026-xx Cumulative Update for Windows 11 – Failed – 0x800f081f

is much more useful diagnostically than simply knowing that Windows Update failed.

2. Restart Windows Before Doing Anything Advanced

A restart sounds basic, but it is important.

Windows servicing operations frequently require a restart to:

• replace files currently in use,
• complete pending servicing operations,
• finish driver installation,
• finalize cumulative updates,
• release locked update files.

Use:

Start → Power → Restart

Do not simply shut down and immediately power the computer back on.

After restarting:

Settings → Windows Update → Check for updates

If the same update fails again, continue troubleshooting.

3. Check Available Disk Space

Windows Update requires free space for downloaded packages, temporary files, component servicing, rollback data, and installation files.

Open:

File Explorer → This PC

Check the free space on C:.

If the drive is nearly full, remove unnecessary files before attempting the update again.

You can also use:

Settings → System → Storage → Temporary files

Possible cleanup items include:

• Temporary files
• Delivery Optimization files
• Recycle Bin
• Temporary Windows installation files
• Windows Update cleanup, when available

Be careful before deleting the Downloads folder or other personal files.

For large feature upgrades, having considerably more free space than the bare minimum is preferable.

4. Check Date, Time, and Time Zone

Incorrect system time can cause authentication and connectivity problems.

Go to:

Settings → Time & language → Date & time

Enable:

Set time automatically

and verify the correct time zone.

Then select Sync now, if available.

5. Disconnect Unnecessary USB Devices

If a major Windows upgrade is failing, temporarily disconnect unnecessary peripherals such as:

• USB storage devices
• External hard drives
• Printers
• Scanners
• USB Wi-Fi adapters
• Card readers
• Docking accessories

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

This is particularly useful when an update fails because of a driver or hardware compatibility problem.

6. Temporarily Disable VPN or Proxy Software

A VPN or incorrectly configured proxy can interfere with communication with Windows Update services.

Temporarily disconnect your VPN and try Windows Update again.

To inspect the WinHTTP proxy configuration, open Command Prompt as Administrator and run:

netsh winhttp show proxy

If the computer is supposed to use a corporate proxy, do not reset it without consulting the network administrator.

7. Run the Windows Update Troubleshooter

For current Windows 11 installations, Microsoft recommends using the Windows Update troubleshooter/Get Help diagnostics.

Go to:

Settings → System → Troubleshoot → Other troubleshooters

Find:

Windows Update

and select:

Run

Follow the instructions and restart Windows afterward.

Then check for updates again.

8. Check Important Windows Update Services

Press:

Win + R

Type:

services.msc

and press Enter.

Check services associated with Windows servicing, especially:

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 randomly change service startup types based on unofficial optimization guides. The important point is that required Windows servicing components must not have been deliberately disabled by optimization, privacy, debloating, or Windows Update blocking utilities.

This is especially relevant if the PC previously used software designed to permanently disable Windows Update.

9. Repair Windows Component Store with DISM

A corrupted Windows component store is one of the major reasons updates repeatedly fail.

Open:

Command Prompt → Run as administrator

Run:

DISM /Online /Cleanup-Image /CheckHealth

Then:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

The final command can take considerable time.

Do not close the Command Prompt simply because the percentage appears to remain unchanged for several minutes.

When DISM completes successfully, restart the computer.

10. Run System File Checker

After DISM, open Command Prompt as Administrator and run:

sfc /scannow

SFC verifies protected Windows system files and attempts to replace corrupted versions.

Possible results include:

Windows Resource Protection did not find any integrity violations

No protected system-file corruption was detected.

Windows Resource Protection found corrupt files and successfully repaired them

Restart Windows and try the update again.

Windows Resource Protection found corrupt files but was unable to fix some of them

Further component-store or offline repair may be required.

A useful repair sequence is therefore:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart Windows afterward.

11. Reset Windows Update Components

If Windows repeatedly downloads the same update, remains stuck, or reports corrupted/missing update files, reset the Windows Update cache.

Open Command Prompt as Administrator.

Stop the relevant services:

net stop wuauserv
net stop bits
net stop cryptsvc

Rename the Windows Update cache:

ren %windir%\SoftwareDistribution SoftwareDistribution.old

Rename the cryptographic update catalog cache:

ren %windir%\System32\catroot2 catroot2.old

Start the services again:

net start cryptsvc
net start bits
net start wuauserv

Restart Windows.

Now go to:

Settings → Windows Update → Check for updates

Windows will recreate the required update-cache folders.

Is it safe to rename SoftwareDistribution?

Normally, yes. Renaming the folder does not uninstall Windows itself.

Windows automatically creates a new SoftwareDistribution folder.

However, the visible Windows Update history stored locally may be affected even though already installed updates remain installed.

12. Do Not Rename Catroot Instead of Catroot2

A common mistake in online troubleshooting instructions is confusing:

C:\Windows\System32\catroot

with:

C:\Windows\System32\catroot2

For the standard Windows Update cache reset procedure, catroot2 is the folder normally renamed.

Do not randomly delete Windows system folders.

13. Reset Network Stack if Downloading Updates Fails

If updates cannot download or repeatedly lose connection, network configuration may be involved.

Open Command Prompt as Administrator and run:

ipconfig /flushdns
netsh winsock reset

Restart Windows.

If necessary, test whether normal Microsoft websites and other HTTPS websites open correctly.

On corporate systems, also investigate:

• DNS configuration
• firewall rules
• proxy settings
• endpoint security
• SSL inspection
• WSUS policies

14. Check for Drive Errors

File-system problems can also interfere with Windows servicing.

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For problems requiring offline repair, Windows may recommend a restart or a command such as:

chkdsk C: /f

Because /f can require exclusive access to the system volume, Windows may ask whether the scan should run at the next restart.

Back up important data before performing extensive disk troubleshooting, particularly if the drive is showing other symptoms of failure.

15. Check the Exact Windows Update Error Code

Error codes provide important clues.

Error 0x800f081f

This commonly indicates that Windows cannot find required source files or that the component store requires repair.

Try:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If DISM itself reports that source files cannot be found, a compatible Windows ISO or another valid repair source may be required.

Error 0x800f0831

This can be associated with Windows component-store/package problems.

Start with:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Then restart Windows and try the update again.

Error 0x80070005

This means Access Denied.

Possible causes include:

• damaged permissions,
• registry permission changes,
• file-system permission changes,
• security software interference,
• servicing-component permissions.

Do not indiscriminately give Everyone full control over Windows system folders as a workaround.

Permission-related servicing failures should be diagnosed carefully.

Error 0x80070570

This generally indicates corrupted or unreadable data/files.

Check:

• Windows component store,
• system files,
• file system,
• storage health.

Start with DISM and SFC.

Error 0x80070422

This frequently appears when Windows Update or another required service has been disabled.

This is particularly common on computers where Windows Update was intentionally disabled using:

• registry modifications,
• Group Policy,
• optimization utilities,
• debloating tools,
• privacy utilities,
• custom scripts.

Restore the required Windows Update configuration and try again.

Error 0x800f0922

Possible causes include insufficient space, connectivity/VPN problems, or servicing-related issues.

Check:

• free disk space,
• VPN,
• network connectivity,
• Windows servicing health.

Error 0xC1900101

This family of errors is strongly associated with driver problems during Windows upgrades.

Investigate:

• chipset driver,
• storage controller driver,
• graphics driver,
• network driver,
• BIOS/UEFI,
• external hardware,
• third-party filter drivers.

Update important drivers from the computer or motherboard manufacturer's support site.

16. Update Drivers Before a Feature Upgrade

Driver problems are particularly important when Windows installs normally until a restart and then rolls back.

Check:

Device Manager

Look for:

• unknown devices,
• warning symbols,
• outdated storage drivers,
• old graphics drivers,
• problematic network adapters.

For OEM systems such as Dell, HP, Lenovo, Acer, ASUS, etc., check the manufacturer's support page for the exact computer model.

Important updates may include:

• BIOS/UEFI
• chipset
• Intel/AMD platform components
• storage controller
• GPU
• Wi-Fi
• Bluetooth

Do not install BIOS updates casually on an unstable computer. Ensure reliable power and follow the manufacturer's instructions.

17. Temporarily Remove Problematic Third-Party Security Software

Some third-party antivirus, endpoint security, disk encryption, firewall, or system-tuning software can interfere with a major Windows upgrade.

If there is evidence that such software is causing the problem, temporarily uninstall it, restart Windows, install the update, and reinstall a compatible version afterward.

Before removing business security software, confirm your organization's security policy.

Do not leave a business computer unnecessarily unprotected.

18. Perform a Clean Boot

If third-party software is interfering with the update, a clean boot can help identify the conflict.

Press:

Win + R

Enter:

msconfig

Under Services:

1. Select Hide all Microsoft services.
2. Disable unnecessary third-party services for troubleshooting.

Also review:

Task Manager → Startup apps

Disable unnecessary startup applications temporarily.

Restart Windows and try the update.

After troubleshooting, restore normal startup configuration.

19. Try Installing the Failed KB Manually

If one specific cumulative update repeatedly fails, note its KB number.

For example:

KBxxxxxxx

Search the official Microsoft Update Catalog for that KB number.

Choose the package that matches:

• Windows version,
• Windows release,
• architecture such as x64 or ARM64.

Install the package manually and restart.

Do not download Windows update packages from random third-party download websites.

20. Check Your Windows Version

Press:

Win + R

Type:

winver

This displays your Windows version and OS build.

You can also run:

systeminfo

Knowing the exact Windows version is important because update packages are release-specific.

21. Check Whether the Computer Is Managed by WSUS or Organization Policies

On a company PC, Windows Update may be controlled by:

• Group Policy
• WSUS
• Microsoft Intune
• Windows Update for Business policies
• RMM software
• endpoint-management software

In this situation, resetting Windows Update locally may not solve the root cause.

Run:

gpresult /h "%USERPROFILE%\Desktop\gpresult.html"

Open the generated report and inspect policies relating to Windows Update.

This step is particularly useful for domain-joined business computers and Windows Server environments.

22. Generate WindowsUpdate.log for Advanced Troubleshooting

Windows provides update logs that can help diagnose persistent failures.

Open PowerShell as Administrator and run:

Get-WindowsUpdateLog

Windows creates a readable WindowsUpdate.log file, typically on the desktop.

Search for:

error
failed
failure
0x

The log is particularly useful when Windows Update repeatedly fails with the same error.

23. Check CBS.log

For servicing and component-store problems, inspect:

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

CBS stands for Component-Based Servicing.

The log may contain information about:

• corrupt components,
• package installation failures,
• missing manifests,
• access-denied errors,
• servicing-stack problems.

You can search the file for terms such as:

error
failed
corrupt
0x800

Because CBS.log can be very large, correlate errors with the approximate time when the update failed.

24. Check DISM.log

DISM maintains its own log:

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

If:

DISM /Online /Cleanup-Image /RestoreHealth

fails, inspect this log for additional information.

25. When DISM Reports "Source Files Could Not Be Found"

Sometimes this command:

DISM /Online /Cleanup-Image /RestoreHealth

fails because Windows cannot obtain the files required to repair the component store.

In this situation, use a compatible Windows installation image as a repair source.

The ISO should closely match the installed:

• Windows edition,
• architecture,
• language,
• release/build.

After mounting a suitable Windows ISO, advanced administrators can use the appropriate install.wim or install.esd image as the DISM repair source.

The exact command depends on the ISO, image type, and correct image index, so do not blindly copy a /Source: command without first checking the installation media.

26. Find the Correct WIM/ESD Index

If using an ISO for DISM repair, first determine the available Windows editions.

For an install.wim, for example:

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

Replace D: with the mounted ISO drive letter.

If the ISO contains:

install.esd

use the corresponding ESD file instead.

Select the image index matching the Windows edition installed on the PC.

Using an incorrect image source can cause DISM repair to fail.

27. Check for a Pending Restart

Windows Update may not proceed correctly when another installation is waiting for a restart.

Restart Windows and check again.

Also look at:

Settings → Windows Update

for messages such as:

Restart required

or:

Pending restart

Complete the pending operation before beginning advanced repairs.

28. If Windows Says "We Couldn't Complete the Updates – Undoing Changes"

This usually means Windows started installing an update during boot but encountered a problem and rolled back.

Possible causes include:

• corrupted update package,
• component-store corruption,
• driver incompatibility,
• insufficient disk space,
• third-party security software,
• interrupted previous servicing,
• storage/file-system errors.

After Windows successfully rolls back:

1. Back up important files.
2. Check disk space.
3. Run DISM.
4. Run SFC.
5. Reset Windows Update components.
6. Restart.
7. Try the update again.

If it is a feature upgrade, investigate drivers as well.

29. If Windows Update Is Stuck at 0%

Check:

• internet connectivity,
• VPN,
• proxy,
• BITS,
• Windows Update service,
• firewall/security software.

Restart Windows before assuming the update is permanently stuck.

If the problem repeatedly returns, reset the Windows Update components.

30. If Windows Update Is Stuck at 100%

Do not immediately force shutdown.

Windows may still be:

• verifying packages,
• committing component-store changes,
• preparing installation,
• processing servicing operations.

On slower PCs or systems with hard disks, this can take significant time.

A forced shutdown during servicing can create additional corruption.

Only investigate further if the system clearly remains unresponsive for an abnormal period and there is evidence that update processing has stopped.

31. Avoid Random "Windows Update Fix" Registry Files

Many websites provide .reg, .bat, PowerShell, or "optimizer" utilities claiming to repair Windows Update instantly.

Be cautious.

Such tools may:

• disable Windows Update,
• modify service permissions,
• disable BITS,
• modify Group Policy,
• disable Defender,
• alter registry permissions,
• remove servicing components.

This can make the original problem considerably worse.

Prefer documented Microsoft troubleshooting methods.

32. Recommended Windows Update Repair Sequence

For most computers, use this order:

Step 1: Restart Windows.

Step 2: Record the KB number and error code.

Step 3: Check disk space.

Step 4: Run Windows Update Troubleshooter.

Step 5: Check required Windows services.

Step 6: Run:

DISM /Online /Cleanup-Image /RestoreHealth

Step 7: Run:

sfc /scannow

Step 8: Restart.

Step 9: Try Windows Update.

If it still fails:

Step 10: Reset SoftwareDistribution and catroot2.

Step 11: Restart.

Step 12: Try the failed KB manually.

If it is a feature update:

Step 13: Investigate drivers, BIOS, security software, and incompatible applications.

If Windows servicing itself appears damaged:

Step 14: Consider an in-place repair installation.

This approach moves from relatively low-impact troubleshooting toward more advanced repair.

33. Advanced Windows Update Reset Command Set

For experienced administrators, the commonly useful reset sequence is:

net stop wuauserv
net stop bits
net stop cryptsvc

ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren %windir%\System32\catroot2 catroot2.old

net start cryptsvc
net start bits
net start wuauserv

Restart Windows afterward.

Then run:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart once more and check Windows Update.

34. When to Consider an In-Place Repair Upgrade

If Windows Update continues failing despite:

• component reset,
• successful disk checks,
• DISM,
• SFC,
• driver troubleshooting,
• manual update attempts,

Windows servicing itself may be damaged.

An in-place repair installation can reinstall Windows system components while normally retaining installed applications, settings, and personal files when the correct options are selected.

Use official Microsoft Windows installation media that matches the installed system.

Before proceeding:

• back up important files,
• confirm Windows edition,
• confirm architecture,
• ensure adequate disk space,
• temporarily suspend incompatible security/encryption products when appropriate,
• ensure stable power.

During Setup, verify that the option to keep your required files and applications is selected before proceeding.

35. Windows 10 Users Should Note Support Status

Standard support for Windows 10 ended on October 14, 2025.

A Windows 10 computer may continue functioning, but its servicing situation depends on the edition, update channel, and whether it participates in an applicable extended security program.

For eligible hardware, migrating to a supported Windows 11 release should be considered instead of treating an unsupported Windows 10 installation as a permanent solution.

36. Important Precautions for Business Computers

Before performing advanced Windows Update repairs on a production PC or server:

• Back up important data.
• Create a restore/recovery plan.
• Record the current Windows build.
• Record the failed KB number.
• Check whether BitLocker/device encryption is enabled.
• Keep recovery information available.
• Verify business-critical software compatibility.
• Avoid BIOS updates during unstable power conditions.
• Do not modify system-folder permissions without understanding the consequences.
• Do not remove corporate security software without authorization.

For servers, Remote Desktop servers, accounting servers, database servers, or line-of-business application servers, perform updates during a planned maintenance window.

Frequently Asked Questions (FAQ)

1. Why does Windows Update keep failing?

Common causes include corrupted update files, damaged Windows components, insufficient disk space, incompatible drivers, stopped services, third-party security software, networking problems, and incomplete previous updates.

2. What should I try first?

Restart the computer, record the update error code, check disk space, and run the Windows Update troubleshooter.

3. Is it safe to run SFC /scannow?

Yes. System File Checker is a built-in Microsoft Windows tool designed to verify and repair protected system files.

4. Is DISM /RestoreHealth safe?

Yes, when used correctly. It is a standard Windows servicing command used to repair the Windows component store.

5. Should I run DISM or SFC first?

A useful repair sequence for servicing corruption is:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM repairs the component store that SFC may rely upon for replacement files.

6. What is the SoftwareDistribution folder?

It is a Windows folder used for Windows Update data, including downloaded update content and related information.

Its normal location is:

C:\Windows\SoftwareDistribution

7. Can I delete SoftwareDistribution?

It can be recreated by Windows, but renaming it during troubleshooting is often preferable because it provides an easy rollback path.

8. What is catroot2?

catroot2 is a Windows system folder used during update and cryptographic servicing operations.

Its location is:

C:\Windows\System32\catroot2

9. Should I delete the catroot folder?

Do not confuse catroot with catroot2. Standard Windows Update reset procedures typically work with catroot2, not the catroot folder.

10. Why does the same Windows update download repeatedly?

The update cache may be corrupted, the installation may be failing after download, or Windows servicing may not be completing successfully.

11. What does error 0x800f081f mean?

It commonly indicates that Windows cannot locate source files required for servicing or that component-store repair is required.

12. How do I fix 0x800f081f?

Start with:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If DISM cannot locate source files, a compatible Windows installation image may be required as the repair source.

13. What does error 0x80070005 mean?

It means Access Denied and commonly points to a permissions-related problem.

14. What does error 0xC1900101 mean?

It commonly indicates a driver-related problem during a Windows upgrade.

15. Can antivirus cause Windows Update failure?

Yes. Third-party antivirus or endpoint security software can occasionally interfere with servicing, particularly during major upgrades.

16. Can low disk space stop Windows Update?

Yes. Windows needs working space for downloads, extraction, servicing, installation, and rollback.

17. Can a VPN cause Windows Update problems?

Yes. VPN or proxy configurations can sometimes interfere with update connectivity.

18. Can I manually install a failed update?

Yes. Identify the KB number and obtain the appropriate package from the official Microsoft Update Catalog.

19. Where can I find Windows Update logs?

A readable Windows Update log can be generated using:

Get-WindowsUpdateLog

20. Where is CBS.log?

It is normally located at:

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

21. Where is DISM.log?

It is normally located at:

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

22. Why does Windows say "Undoing changes made to your computer"?

Windows attempted to install an update but encountered a failure and rolled the system back to its previous state.

23. Will resetting Windows Update delete my files?

Resetting the Windows Update cache using the normal procedure does not delete your personal documents. Nevertheless, important data should always be backed up before advanced system troubleshooting.

24. Will renaming SoftwareDistribution uninstall installed updates?

No. Renaming the update-cache folder does not normally uninstall already installed Windows updates.

25. Why does Windows Update fail after restarting?

If downloading succeeds but installation fails during reboot, investigate servicing corruption, drivers, disk problems, security software, and pending system operations.

26. Can a bad driver prevent Windows from updating?

Yes. Driver incompatibility is especially important for Windows feature upgrades and errors in the 0xC1900101 family.

27. Should I update BIOS to fix Windows Update?

Only when there is a compatibility reason or the PC manufacturer recommends it. BIOS updates should be performed carefully with stable power.

28. What if DISM /RestoreHealth fails?

Record the DISM error code and inspect:

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

If required repair files cannot be downloaded, you may need a compatible Windows ISO as the repair source.

29. Can I repair Windows without formatting the computer?

Often, yes. An in-place repair installation can reinstall Windows system components while retaining applications and personal files when the appropriate options are available and selected.

30. When should I reinstall Windows completely?

A clean installation should generally be a later option after appropriate backups and after repair methods such as DISM, SFC, update-component reset, driver troubleshooting, and in-place repair have been considered.

Final Troubleshooting Checklist

When Windows Update keeps failing, use this checklist:

1. Record the KB number and error code.
2. Restart Windows.
3. Check free disk space.
4. Verify internet connectivity.
5. Disconnect unnecessary peripherals.
6. Disable VPN temporarily.
7. Run Windows Update Troubleshooter.
8. Check Windows Update-related services.
9. Run DISM RestoreHealth.
10. Run SFC /scannow.
11. Restart Windows.
12. Reset SoftwareDistribution and catroot2 if required.
13. Check storage/file-system health.
14. Check drivers and Device Manager.
15. Check BIOS/firmware when relevant.
16. Investigate third-party antivirus/security software.
17. Try the failed KB manually.
18. Review WindowsUpdate.log, CBS.log, and DISM.log.
19. Check organizational policies on managed computers.
20. Consider an in-place repair installation if Windows servicing remains damaged.

The most important diagnostic information is the exact Windows Update error code and failed KB number. Two computers showing "Windows Update failed" may have completely different underlying causes, so troubleshooting should be based on the actual error rather than repeatedly clearing files or reinstalling Windows.

 

#WindowsUpdate #WindowsUpdateError #Windows11 #Windows10 #WindowsTroubleshooting #WindowsRepair #UpdateFailed #WindowsUpdateFailed #WindowsUpdateFix #Windows11Update #Windows10Update #DISM #DISMRestoreHealth #SFC #SFCScannow #SystemFileChecker #WindowsRepairCommands #WindowsUpdateTroubleshooter #SoftwareDistribution #Catroot2 #WindowsUpdateCache #WindowsUpdateService #BITS #CryptographicServices #WindowsServices #WindowsError #WindowsErrorCodes #WindowsUpdateStuck #CumulativeUpdate #SecurityUpdate #FeatureUpdate #WindowsUpgrade #WindowsDrivers #DriverError #WindowsUpdateComponents #WindowsUpdateReset #ComponentStore #CBSLog #DISMLog #WindowsUpdateLog #MicrosoftUpdateCatalog #KBUpdate #WindowsSupport #PCRepair #LaptopRepair #ComputerRepair #ITSupport #TechnicalSupport #WindowsTips #WindowsKnowledgebase