> ## Documentation Index > Fetch the complete documentation index at: https://windows-errorssolveguide.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Advanced Fixes for Windows Error 0x80070002 (DISM & More) > Apply advanced repair techniques for persistent Windows error 0x80070002 using DISM, registry edits, and Windows component store repair. [Fix Error Now →]() If you've already worked through the basic troubleshooting steps and error 0x80070002 still appears when you run Windows Update, you're dealing with a deeper system issue. These advanced fixes target corrupted Windows image files, damaged Update components, misconfigured registry entries, and more — giving you the best chance of resolving the error without a full reinstall. ## Fix 1: Run DISM to Repair Windows Image The Deployment Image Servicing and Management (DISM) tool repairs the Windows component store — the underlying source that SFC and Windows Update both rely on. If the component store itself is damaged, SFC and the Update Troubleshooter cannot fix the problem on their own. DISM reaches out to Windows Update servers to pull down uncorrupted replacement files. > [!NOTE] > > The RestoreHealth command requires an active internet connection and can take **20–30 minutes** to complete depending on your connection speed and the extent of the damage. Do not close the terminal window while it runs. **1. Open Command Prompt as Administrator** Right-click the **Start** button and select **Windows Terminal (Admin)** or **Command Prompt (Admin)**. Click **Yes** at the UAC prompt. **2. Check the image health** Run the following command to perform a quick check of the component store: ```powershell theme={null} DISM /Online /Cleanup-Image /CheckHealth ``` Review the output. If it reports the image is repairable, proceed to the next step. **3. Restore the Windows image** Run the full repair command. This downloads and replaces any corrupted files: ```powershell theme={null} DISM /Online /Cleanup-Image /RestoreHealth ``` **4. Restart and run Windows Update** Once DISM completes and reports success, **restart your PC** and try Windows Update again. ## Fix 2: Reset Windows Update Components Manually Sometimes the Windows Update services and associated folders become locked in a broken state that automated tools cannot fix. Manually stopping all related services, renaming the corrupted cache folders, and restarting the services gives Windows Update a completely clean slate. **1. Open an elevated Command Prompt** Right-click **Start** → **Windows Terminal (Admin)** or **Command Prompt (Admin)**. **2. Stop all Windows Update related services** Run each of the following commands in sequence, pressing **Enter** after each one. The commands stop the four Windows Update-related services, rename the corrupted cache folders, and restart everything fresh: ```cmd theme={null} net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old net start wuauserv net start cryptSvc net start bits net start msiserver ``` Windows automatically recreates the SoftwareDistribution and catroot2 folders fresh when the services restart. **3. Retry Windows Update** Open **Settings** → **Windows Update** and click **Check for updates**. Allow the update process to run fully before checking whether the error recurs. ## Fix 3: Re-register Windows Update DLLs Corrupted or unregistered Windows Update DLL files can prevent the update service from functioning correctly, triggering error 0x80070002. Running `regsvr32` against each of these files forces Windows to re-register them, restoring the component linkages that the update process depends on. **1. Open Command Prompt as Administrator** Right-click **Start** → **Windows Terminal (Admin)** or **Command Prompt (Admin)**. Click **Yes** at the UAC prompt. **2. Re-register all Windows Update DLL files** Run the following commands one at a time, pressing **Enter** after each. You should see a success dialog for each DLL: ```cmd theme={null} regsvr32 wuapi.dll regsvr32 wuaueng.dll regsvr32 wuaueng1.dll regsvr32 wucltui.dll regsvr32 wups.dll regsvr32 wups2.dll regsvr32 wuweb.dll ``` **3. Restart your PC** After all DLLs have been re-registered successfully, **restart your PC** to allow the changes to take effect. **4. Run Windows Update** Open **Settings** → **Windows Update** and click **Check for updates** to verify the error is resolved. ## Fix 4: Check and Repair Registry Entries Damaged or missing registry entries in the Windows Update configuration key can cause error 0x80070002. You can inspect and correct these entries using the Registry Editor. > [!WARNING] > > The Windows Registry is critical to your operating system. Incorrect edits can cause system instability or prevent Windows from booting. **Back up your registry before making any changes**: open Registry Editor (**Win + R** → `regedit`), click **File** → **Export**, choose **All** as the export range, and save the backup to a safe location such as your desktop or an external drive. Navigate to the following key in Registry Editor: ```text theme={null} HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate ``` Inside this key, verify that values such as `AccountDomainSid`, `PingID`, and `SusClientId` are present and correctly formed. If you see any values that appear blank, contain garbled characters, or are missing entirely compared to a reference system, delete the affected values and allow Windows Update to regenerate them automatically on its next run. After making any changes, close Registry Editor and restart your PC before testing Windows Update again. ## Fix 5: Perform a Windows Repair Install (In-place Upgrade) A Windows repair install — also called an in-place upgrade — reinstalls Windows system files over your existing installation while keeping all your personal files, apps, and settings intact. This is one of the most thorough fixes available because it replaces every core Windows file without requiring you to back up and restore your data. > [!TIP] > > A repair install is one of the most effective last-resort fixes before committing to a full clean reinstall. It resolves deep system file corruption that DISM and SFC cannot address, yet takes far less time than starting from scratch. **1. Download the Windows Media Creation Tool** Go to the official Microsoft website and download the **Media Creation Tool** for your version of Windows (10 or 11). Run the tool once it downloads. **2. Choose 'Upgrade this PC now'** In the Media Creation Tool, select **Upgrade this PC now** and click **Next**. The tool downloads the latest version of Windows directly. **3. Select 'Keep personal files and apps'** When prompted to choose what to keep, select **Keep personal files and apps**. This ensures none of your data is removed during the repair process. **4. Complete the upgrade** Click **Install** and allow the process to run. Your PC will restart several times. Once complete, Windows Update should function correctly. ## Fix 6: Reset Windows Update via PowerShell Script If you prefer to run a single script that handles service management and cache clearing in one pass, use the following PowerShell commands. Open PowerShell as Administrator (**Win + X** → **Windows Terminal (Admin)**) and run the block below: ```powershell theme={null} Stop-Service -Name wuauserv, bits, cryptSvc, msiserver Remove-Item -Path "$env:SystemRoot\SoftwareDistribution\*" -Recurse -Force Start-Service -Name wuauserv, bits, cryptSvc, msiserver ``` This script stops all four Windows Update-related services simultaneously, forcibly removes all contents of the SoftwareDistribution cache folder, and then restarts the services. After the script completes, open Windows Update and check for updates to confirm the error is gone. ## Frequently Asked Questions > **Will these fixes delete my personal files?** > > No. Every fix on this page is a repair operation that targets Windows system components only. Your documents, photos, videos, and installed applications are not touched. The only exception is the in-place upgrade (Fix 5), which explicitly preserves your files and apps as part of the process — so you're still protected. > **How long does DISM take to run?** > > The `CheckHealth` command completes in under a minute. The `RestoreHealth` command typically takes **20–45 minutes** on average, though it can take longer on slower internet connections or heavily damaged installations. Keep your PC plugged in and connected to the internet while it runs. > **What if none of these fixes work?** > > If error 0x80070002 persists after exhausting every fix on this page, there are two remaining paths. First, contact **Microsoft Support** directly at support.microsoft.com — their agents can run remote diagnostics and escalate to engineering teams if necessary. Second, perform a **clean Windows installation** using the Media Creation Tool, selecting the option to erase your drive. This resolves any underlying corruption completely, though you will need to reinstall your applications and restore your files from a backup. ## Need More Help? > **[Basic Fixes](/0x80070002/fix-windows-update-error-0x80070002)** > > Start with the simpler solutions — run the troubleshooter, clear the update cache, and check your system clock before trying advanced repairs. > **[What Causes Error 0x80070002?](/0x80070002/causes-of-error-0x80070002)** > > Learn what triggers error 0x80070002 at the root level so you can prevent it from coming back after you've fixed it. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.