# Windows 10 Feature Pack Deployment Issues **Last Updated On**: 06 Aug 2026 **19 minutes read** This page provides solutions for common error codes encountered during Windows 10 patch and feature pack installations in Endpoint Central and Endpoint Central. For Windows 11 installation errors, refer to the [Windows 11 installation errors knowledge base](https://www.manageengine.com/products/desktop-central/kb/patch-management/windows-11-feature-pack-errors.html). ## General Troubleshooting Steps Before proceeding with specific error resolutions, try these general steps first. - Restart the system and retry the deployment. - Ensure the ISO file is properly downloaded and not corrupted. - Check system requirements for the Windows 10 version you are trying to install. - Verify that no security policies (GPO, antivirus, endpoint security) are blocking the update. - Ensure the system has enough disk space. If the issue persists after following the relevant resolution steps below, refer to the official Microsoft documentation: - [Get help with Windows 10 upgrade and installation errors](https://support.microsoft.com/en-in/help/10587/windows-10-get-help-with-upgrade-installation-errors) - [Windows upgrade resolution procedures](https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures) If the problem still persists, [contact support](https://www.manageengine.com/patch-management/support.html). ## Error Code Reference Find your error code below and follow the recommended resolution steps. ### Error Code 50001 #### Possible Cause The required data cannot be retrieved from the ISO file. #### Resolution Logs are necessary to identify the exact reason. Contact [support](https://www.manageengine.com/patch-management/support.html) with the relevant log files. ### Error Codes 50002 / 50004 / Incorrect Function / Invalid Function / The System Cannot Find the File Specified #### Possible Cause Corrupted ISO file. #### Resolution Delete the existing ISO file from the patch store. Re-download the ISO file from the [Microsoft 365 Admin Center](https://admin.microsoft.com/adminportal/home#/subscriptions/vlnew) or using the media creation tool. Rename and copy the ISO file into the patch store, then redeploy the feature pack update. ### Error Code 50003 / Edition Mismatch #### Possible Cause You have the Enterprise edition of Windows 10 installed but are trying to deploy an ISO file for a different edition. #### Resolution Download and deploy the ISO file that matches your Windows 10 edition. ### Error Code 50005 / Access Is Denied #### Possible Cause GPO, antivirus, or endpoint security is configured to block external drive mounting or the launching of `setup.exe`, or access was denied during data migration. #### Resolution 1. Allow external drive mounting and the launching of `setup.exe` in your GPO, antivirus, or endpoint security configuration. 2. Ensure read/write access is granted to the following folders: `C:\Users\USERNAME\AppData`, `C:\Windows\System32`, and `C:\Apps`. 3. In File Explorer, navigate to the C: drive. Click **View** and enable the **Hidden items** checkbox. 4. Locate and rename the folder named `$WINDOWS.~BT`. 5. Redeploy the feature pack. ### Error Codes 50006 / -1047526908 / Language Mismatch #### Possible Cause You have downloaded the ISO file in a different language than your system's native language. #### Resolution Download the ISO file in the language that matches your system's configured language, then redeploy. ### Error Code 50007 / Version Mismatch #### Possible Cause The downloaded ISO file does not match the system's current OS version. For example, you have downloaded the ISO for Windows 10 1803 but are deploying it to a Windows 10 1809 device. #### Resolution Download the ISO file that matches your current OS version, then redeploy the feature pack. ### Error Code 50008 / Unable to Retrieve the Mounted Drive Letter #### Possible Cause GPO, antivirus, or endpoint security is configured to block PowerShell commands. #### Resolution Allow PowerShell commands in your GPO, antivirus, or endpoint security configuration, then redeploy the feature pack. ### Error Code 50009 #### Possible Cause The ISO file placed in the patches folder or patch store is below the minimum size threshold — less than 3 GB for 64-bit systems or less than 2 GB for 32-bit systems — indicating an incomplete or corrupted download. #### Resolution 1. Delete the ISO file from the patches folder on the client machine and redeploy the feature pack. 2. If the ISO file in the patch store is also below the minimum size, delete it from the patch store, re-download a complete ISO from the [Microsoft software download page](https://www.microsoft.com/en-in/software-download/windows10) or using the media creation tool, rename and copy it into the patch store, and redeploy. ### Error Code 50016 / Restart Pending #### Possible Cause A restart is pending from a previous feature pack installation. #### Resolution Restart the system to complete the Windows feature upgrade. ### Error Code 50019 #### Possible Cause Failure in extracting the ISO file — possibly due to access denied or a corrupted file. #### Resolution Logs are necessary to identify the exact reason. Contact [support](https://www.manageengine.com/patch-management/support.html) with the relevant log files. ### Error Code 50030 #### Possible Cause The ISO file contains an ESD file. During processing, the ESD extraction failed at one of the following steps: extracting the contents, locating the `sources` folder, copying `install.esd`, moving files to the `Windows` folder, or deleting the extracted folder. #### Resolution Logs are necessary to identify the exact reason for the ESD processing failure. Contact [support](https://www.manageengine.com/patch-management/support.html) with the relevant log files. ### Error Code 50032 #### Possible Cause Failure in constructing the `scheduler.xml` file required for creating the `setup.exe` process via Task Scheduler, or an error occurred while retrieving the result from the executed `setup.exe`. #### Resolution Logs are necessary to identify the exact reason. Contact [support](https://www.manageengine.com/patch-management/support.html) with the relevant log files. ### Error Code 50033 #### Possible Cause After ISO extraction, neither `install.wim` nor `install.esd` was found in the sources folder. #### Resolution Mount the uploaded ISO file and navigate to the `sources` folder to check for the presence of `install.esd` or `install.wim`. If neither file is present, download a new ISO file. ### Error Codes 183 / -2147023278 / Cannot Create a File When That File Already Exists *The process cannot access the file because it is being used by another process* #### Possible Cause `setup.exe` may already be running in the background. #### Resolution Open Task Manager and check whether the following tasks are running: `setup.exe`, `setuphost.exe`, Windows Installer, Windows Setup, or Modern Setup Host. If any are active, terminate them and redeploy the feature pack. ### Error Code -1047526904 / Feature Pack Blocked by Incompatible Application #### Possible Cause Incompatible applications on the system are blocking the upgrade. #### Resolution Navigate to `\logs\panther`. Open `scanresult.xml` and `Compatdata.xml` and search for the keyword `CompatibilityInfo BlockingType="Hard"`. This will list all incompatible applications installed on the computer. Uninstall or upgrade these applications, then redeploy the feature pack. ### Error Codes -1047526912 / -1047526910 / Minimum Requirements Not Met #### Possible Cause The system does not meet the minimum requirements to download or install the Windows 10 upgrade. #### Resolution Navigate to `\logs\panther`. Open `scanresult.xml` and `Compatdata.xml` and search for `CompatibilityInfo BlockingType="Hard"`. This lists which system requirements are not satisfied. - **Setup_InsufficientSystemPartitionDiskSpace** — The system reserved partition does not have enough space for the upgrade. Extend the system reserved partition space. - **Setup_HostIsBootedFromVHD** — The operating system is running in a native boot VHD (Virtual Hard Disk). OS upgrades are not possible in this configuration. - **Setup_PendingFirmwareUpdateWithPower** — A firmware update is pending due to a power event. Update the firmware and then redeploy the feature pack. Refer to the [Windows 10 minimum specifications page](https://www.microsoft.com/en-IN/windows/windows-10-specifications) to learn more about the minimum requirements. ### Error Code -1047527161 / Cleanup Pending from Previous Installation #### Possible Cause Error code `-1047527161` (0xC1900107) indicates that a cleanup operation from a previous installation attempt is still pending and a system restart is required to continue the upgrade. #### Resolution ##### Method 1 Restart the system and redeploy the feature pack update. ##### Method 2 1. In File Explorer, navigate to the C: drive. Click **View** and enable the **Hidden items** checkbox. 2. Locate and rename the folder named `$WINDOWS.~BT`. 3. Perform Disk Cleanup to remove residual files. Refer to [this Microsoft guide](https://support.microsoft.com/en-us/windows/free-up-drive-space-in-windows-85529ccb-c365-490d-b548-831022bc9b32) for steps. 4. Redeploy the feature pack update. ### %1 Is Not a Valid Win32 Application #### Possible Cause The dependency patch of the feature pack has been deployed directly. #### Resolution Scan the systems and check the Missing Patches list. Deploy the patch whose description starts with **Feature Pack Update**. ### Unable to Download the Dependency File from the Server #### Possible Cause A connectivity issue exists between the server and the agent. #### Resolution Redeploy the feature pack update. If the problem persists, [contact support](https://www.manageengine.com/patch-management/support.html). ### Error Code -2147010798 #### Possible Cause A file needed by Windows Update is likely damaged or missing. #### Resolution Repair your system files by running the following command from an elevated command prompt, then redeploy the feature pack update. ```bash DISM.exe /Online /Cleanup-image /Restorehealth ``` ### Error Code -1047527167 / Driver Problem #### Possible Cause A driver has caused a problem during the upgrade process. #### Resolution Disable or remove all third-party antivirus or antispyware software. Disconnect all peripheral devices except the mouse, keyboard, and display. Update all installed drivers and redeploy the feature pack. ### Error Codes -1047526939 / -1047526940 / -1047526941 / -1047526942 / Pre-Install Script Failure #### Possible Cause A pre-install script failed to execute or returned an error. If custom scripts are used to install software or apply group policy alongside the installation, an error in those scripts causes these error codes. #### Resolution Review your custom scripts for errors. Correct or delete the failing script and redeploy the feature pack. ### Error Codes 1073741819 / 1073740940 / 1073741584 / 1047527137 / Deployment Executable Crash #### Possible Cause An unexpected crash of the deployment executable files (`setup.exe` and `setuphost.exe`). #### Resolution Upgrade the system using the **January 2024 released ISO or a later version**. Download the ISO from the [Microsoft 365 Admin Center](https://admin.microsoft.com/adminportal/home#/subscriptions/vlnew) or using the media creation tool. ### Error Code 50031 / Feature Pack Installation Skipped — Same Version Recently Installed #### Possible Cause Redeploying with the same ISO build version within 3 days of a previous successful installation causes this error. #### Resolution To redeploy immediately, remove the following file from the affected system and then retry the deployment. ```bash C:\Program Files (x86)\ManageEngine\UEMS_Agent\logs\installed_fp_details.json ``` ### Error Code 50034 / Task Scheduler Failed to Create Windows Setup Task #### Possible Cause Task Scheduler failed to create a task for the Windows setup process during a Windows 10 to Windows 11 upgrade. #### Resolution Modify the registry on the affected system to use an alternative method for creating the Windows setup process. - **Header Key:** HKEY_LOCAL_MACHINE - **Sub Key (32-bit OS):** SOFTWARE\AdventNet\DesktopCentral\DCAgent\Patch\InternalSettings - **Sub Key (64-bit OS):** SOFTWARE\WOW6432Node\AdventNet\DesktopCentral\DCAgent\Patch\InternalSettings - **Value Name:** WinFPForceCreateProcess - **Data Type:** DWORD - **Value Data:** 1 Once added, retry the deployment. ### Error Code 50035 / Rollback Due to Antivirus #### Possible Cause A rollback occurred because antivirus software blocked the setup process. #### Resolution Check if antivirus is enabled and disable it before retrying the upgrade. To redeploy the same ISO build version immediately (without waiting 3 days), remove the following file from the affected system and then retry. ```bash C:\Program Files (x86)\ManageEngine\UEMS_Agent\logs\installed_fp_details.json ``` ### Error Code 1047526945 / System Out of Disk Space #### Possible Cause The installation cannot continue because the system is out of disk space. #### Resolution Free up disk space on the system drive and redeploy the feature pack. ### Error Code -1047526898 / Insufficient Free Disk Space #### Possible Cause The system does not have enough free space available to install the upgrade. #### Resolution Free up disk space on the system drive and redeploy the feature pack. ## Related - [Errors While Installing Windows 11](https://www.manageengine.com/products/desktop-central/kb/patch-management/windows-11-feature-pack-errors.html.html) - [Deploy Windows 10 Version 22H2 Feature Update](https://www.manageengine.com/products/desktop-central/how-to/patch-management/windows-10-feature-pack-deployment-22h2.html) - [Deploy Windows 10 Version 21H2 Feature Update](https://www.manageengine.com/products/desktop-central/how-to/patch-management/windows-10-feature-pack-deployment-21h2.html) - [Deploy Windows 10 Version 21H1 Feature Update](https://www.manageengine.com/products/desktop-central/how-to/patch-management/windows-10-feature-pack-deployment-21h1.html)