# Troubleshooting Errors in Windows Updates Last Updated On: 16 Oct 2026 15 minutes read Learn how to troubleshoot and resolve common Windows Update errors, such as component store corruption, missing files, or .NET update failures. **Note** If you are using build **11.5.2627.01 or later**, you can use the **Windows OS Repair Utility** to repair component store corruption. Refer to [this page](https://www.manageengine.com/products/desktop-central/help/patch_management/kb/windows-os-repair-utility.html) for detailed steps. ## Problem At times, you may encounter an error during the installation of Windows updates. `0x8007000D` (`-2147024883`) means **The data is invalid**. Check the failure stage. For package or download validation, see [Invalid-data patch installation troubleshooting](https://www.manageengine.com/vulnerability-management/help/patch-management/patch-installation-failure-invalid.html). `-2145124329` (`0x80240017`, `WU_E_NOT_APPLICABLE`) means the update is not applicable. Check OS build, edition, architecture, prerequisites, and whether it is already installed. This code alone does not indicate component-store corruption. See [patch applicability checks](https://www.manageengine.com/vulnerability-management/help/patch-management/patch-issues.html). ## Cause Corrupted or missing Windows Update component files can prevent detection, download, or installation and cause repeated servicing failures. Check the exact error and failure stage before selecting a repair procedure. Invalid package data or an inapplicable update does not by itself establish component-store corruption. Retain the full error and Windows servicing logs if the cause is unclear. For an unlisted vendor installer result, including an unknown negative result from an application or driver installer, follow [Other Installation Failures](https://www.manageengine.com/vulnerability-management/help/patch-management/patch-deployment-troubleshooting.html#unknown-installer-results). Record the exact numeric result, Patch ID, product/version, and failure time, and provide the installer and agent logs. Check vendor-specific guidance before applying a Windows servicing repair. ## Resolution Choose the relevant procedure: - [For Windows .NET updates](https://www.manageengine.com/vulnerability-management/kb/patch-management/troubleshooting-errors-in-windows-updates.html#dot-net-updates) - [For Windows OS updates](https://www.manageengine.com/vulnerability-management/kb/patch-management/troubleshooting-errors-in-windows-updates.html#os) ### For Windows .NET updates 1. Search for patch ID **108183 - Microsoft .NET Framework Repair Tool** in Supported Patches. If it is not listed, go to **Patch Database Settings → Windows**, enable **Optional Updates**, and search again. 2. Select the patch and click **Install patch**. 3. Deploy the configuration to the affected targets. 4. After successful execution, retry the failed patches. If the issue persists: 1. Uninstall and reinstall the affected .NET Framework version, where appropriate. 2. Restart the system, perform a patch scan, and deploy the failed patches if they remain in Missing Patches. 3. If the issue still persists, follow the Windows OS update resolution below. ### For Windows OS updates If repair does not resolve the failure, retain its deployment result and record the original Patch ID or KB, full error, Windows build, and reboot/retry result. Collect affected agent action logs and Windows servicing logs. Do not extend the ISO-based client repair procedure below to Windows Server. For server servicing diagnosis, see [Microsoft's Windows Server invalid-data troubleshooting](https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates). 1. Search for **Component Store Cleanup (Patch ID: 105979)** in Supported Patches. If it is not listed, go to **Patch Database Settings > Windows**, enable **Optional Updates**, and search again. Follow the [Component Store Cleanup procedure](https://www.manageengine.com/vulnerability-management/help/patch-management/reverting-changes-patch-failure-configuring-windows-updates.html#resolution). This update is distinct from the OS-specific Windows update component restore updates below. 2. Select the patch and click **Install patch**. 3. Deploy the configuration to affected targets. 4. After successful execution, retry the failed patches. If the issue persists, deploy the **Windows update component restore patch** using Patch Manager Plus. This repair is intended to address operating-system servicing issues without removing user data; back up important data before performing OS repair operations. **Note** **The ISO-based restore procedure applies only to Windows 10 and Windows 11 client systems, not Windows Server. For server machines, contact the operating system vendor.** #### Downloading the ISO file **Note** **Applicable from build 2605 and above:** Manual ISO upload is not mandatory for Windows update component restore. **Key points:** 1. Dependency patches do not appear in the Uploaded Patches view by default. 2. The system automatically handles ISO download and deployment during restore. 3. If ISO download fails, the dependency patch appears in Uploaded Patches for manual intervention. 4. If a previously uploaded ISO is available, deployment continues using that file. 5. If previously uploaded patches are later deleted, the dependency patch does not appear in Uploaded Patches but is automatically downloaded again on the next deployment attempt. - When manual upload is required, download the Windows ISO from VLSC through [Microsoft 365 Admin Center](https://admin.microsoft.com/) or [MSDN](https://msdn.microsoft.com/en-us/index.html). - You can also obtain eligible ISO media from the [Microsoft Software Download Center](https://www.microsoft.com/en-in/software-download/windows10), subject to licensing requirements. - Ensure that the ISO matches the target computer's edition, architecture, version, and OS language. #### Deploying the Windows update component restore patch using Patch Manager Plus If the console lists the Windows update component restore update as a Feature Pack, locate it in Feature Packs and follow the OS-specific ISO selection or upload procedure. **Windows update component restore patches by operating system and version** | Operating System | Version | Update ID | Description | |---|---|---|---| | Windows 10 | 22H2 | 110870 | Windows update component restore for Windows 10 (22H2) | | | 22H2 | 110041 | Dependency Patch for Windows 10 (22H2) - October 2022 Update (x64) (Manual Upload Required) | | Windows 11 | 21H2 | 111125 | Windows update component restore for Windows 11 (21H2) | | | 21H2 | 109021 | Dependency Patch for Windows 11 (21H2) - October 2021 Update (x64) (Manual Upload Required) | | Windows 11 | 22H2 | 111126 | Windows update component restore for Windows 11 (22H2) | | | 22H2 | 109939 | Dependency Patch for Windows 11 (22H2) - September 2022 Update (x64) (Manual Upload Required) | | Windows 11 | 23H2 | 111127 | Windows update component restore for Windows 11 (23H2) | | | 23H2 | 110951 | Dependency Patch for Windows 11 (23H2) - October 2023 Update for enterprise (x64) (Manual Upload Required) | | Windows 11 | 24H2 | 111893 | Windows update component restore for Windows 11 (24H2) (Deployment-Only) | | | 24H2 | 111894 | Dependency Patch for Windows 11 (24H2) - October 2024 Update for enterprise (x64) (Manual Upload Required) | | Windows 11 | 25H2 | 112755 | Windows update component restore for Windows 11 (25H2) (Deployment-Only) | | | 25H2 | 112734 | Dependency Patch for Windows 11 (25H2) Enterprise (x64) (Manual Upload Required) | **Note** After deploying Windows update component restore patches, restart the system before proceeding with further deployments. **Manual ISO upload (when required):** 1. Navigate to **Patches → Downloaded Patches → Upload Patches** and select **All Patches** in the filter. ![Select All Patches filter in Upload Patches](https://www.manageengine.com/patch-management/images/troubleshooting-windows-updates-error-1.png) 2. Find the required dependency patch and click **Upload** in the **Action** column. ![Upload action for required patch](https://www.manageengine.com/patch-management/images/troubleshooting-windows-updates-error-2.png) 3. Select the ISO file, choose a checksum type, and enter the checksum value. ![Upload ISO with checksum](https://www.manageengine.com/patch-management/images/troubleshooting-windows-updates-error-3.png) 4. Once the checksum is validated, click **Upload**. For checksum calculation, [refer here](https://technastic.com/check-md5-checksum-hash/). 5. After uploading the dependency patch, deploy the matching Windows update component restore patch from **Feature Packs** if it is listed there; otherwise use the applicable update view, including **Supported Patches** on consoles that list it there. If the Windows update still fails after repair and a manual installation also fails, contact Microsoft or the OS vendor for further diagnosis. ## Related - [Fix "Failure Configuring Windows Updates: Reverting Changes"](https://www.manageengine.com/patch-management/kb/patch-management/reverting-changes-patch-failure-configuring-windows-updates.html) - [Windows 11 Feature Pack Deployment Issues](https://www.manageengine.com/patch-management/kb/patch-management/windows-11-feature-pack-errors.html)