This document will provide solution for some of the common error codes you might face while installing Windows 10.
|
Error due to can't get the data from the ISO |
Logs are necessary to find what is the exact reason. |
|
Corrupted ISO File |
Delete the existing ISO File from the patch store. Then, re-download the ISO file from MS365 Admin Center or using the media creation tool and rename and copy the ISO file in the patches store and re-deploy the feature pack update. |
|
Edition Mismatch This error occurs if you have the Enterprise edition of Windows 10 but try to deploy ISO file of other editions. |
Kindly download and deploy the ISO file that's applicable to your edition. |
|
You might have configured GPO / Antivirus / EndPoint Security to block external drives and launching of setup.exe [OR] Access was denied to migrate the data. |
Follow the below steps to resolve the issue,
|
|
Language Mismatch This error occurs if you've downloaded the ISO file in a different language than your system's native language. |
Kindly download the ISO file in your correct applicable language.
|
|
Version Mismatch This issue occurs if you've downloaded the ISO file mismatches with the systems' OS version. Say, You've downloaded the ISO file for Winodws 10 1803 but deploy it to Windows 10 1809 |
To resolve this issue, kindly download the ISO file that's applicable to your OS version.
|
|
Unable to retrieve the mounted drive letter You might have configured GPO / Antivirus / EndPoint Security to block powershell commands. |
Allow powershell commands in the GPO / Antivirus / EndPoint Security and then re-deploy the feature pack. |
|
ISO file placed in the patches folder/ patch store is less than 3 GB for windows 10 x64 bit machine or less than 2 GB for windows 10 x86 bit machine. |
To resolve the issue, Delete the ISO file in the patches folder of client machine and redeploy the feature pack If the size of the ISO file present in the patch store is also lesser than the prescribed size then delete the existing ISO File from the patch store. Then, re-download the ISO file from VLSC or using the media creation tool and rename and copy the ISO file in the patches store and re-deploy the feature pack update. |
|
Restart Pending from the previous Feature Pack Installation. |
Restart the system to complete the windows feature upgrade. |
|
This error represents the failure of the extraction of the ISO. This can be caused by multiple reasons, such as Access denied, Corrupted file |
Logs are necessary to find what is the exact reason |
|
This error occurs If the given ISO file has ESD
|
Logs are necessary to find what is the exact reason for the failure of processing of ESD. |
|
This error occurs if the system already has the same version of the feature pack successfully installed. |
To resolve this error, the feature pack reinstallation will be automatically skipped as the same version has already been installed successfully.
|
|
If the failure of the construction of the scheduler.xml which is essential for creating the process for setup.exe using task scheduler or failed to get the result from the executed setup.exe |
Logs are necessary to find what is the exact reason for the failure of this error code |
|
During the initial validation of ISO, after extraction search for install.wim or install.esd. If either of them was not found, this error will be thrown |
Need to check the ISO file whether it is the proper Windows ISO. kindly mount the uploaded ISO file and go to sources folder then check install.esd / install.wim file is present or not.If the file is not present, you need to download the new ISO file. |
|
Setup.exe might be already running in the background |
To fix this issue, open Task Manager and check whether the following tasks are running
If the any of the above tasks are running, kill the tasks and try deploying the feature pack again. |
|
Incompatible apps present in the system is blocking the upgrade |
|
|
Your PC doesn’t meet the minimum requirements to download or install the upgrade to Windows 10 |
|
|
The Unknown error code : -1047527161 (0xC1900107) indicates "A cleanup operation from a previous installation attempt is still pending, and a system restart is required to continue the upgrade." |
Method 1: Restart the system and Re-deploy the feature pack update.
Method 2:
|
|
This error occurs when you have deployed the dependency patch of feature pack. |
Scan the systems and check the missing patches list. Deploy the patch where its description starts with "Feature Pack Update". |
|
There might be connectivity issue between server and agent |
|
|
A file needed by Windows Update is likely damaged or missing |
Try repairing your system files,
|
|
A driver has caused a problem. |
|
|
A preinstall script failed to execute or returned an error. |
You are using Custom Script that can set up a few things right along with the installation. These scrips can install software, apply group policy, and so on. If you are receiving any of these error codes, then there is a problem with the script. |
|
An unexpected crash of the deployment executable files (setup.exe & setuphost.exe) |
Upgrade the system by uploading January 2024 released ISO or later. The user can download ISO from Microsoft 365 admin centre or else using Media Creation Tool manually. |
Also, Refer the official Microsoft documents attached below:
https://support.microsoft.com/en-in/help/10587/windows-10-get-help-with-upgrade-installation-errors
https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures
If still problem persists, contact support
Check the errors you might encounter while installing Windows 11