deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/deployment/upgrade/resolution-procedures.md
Greg Lindsay 3c2c617ee4 change log file location
2020-01-17 16:03:33 -08:00

46 KiB
Raw Blame History

title, ms.reviewer, manager, ms.author, description, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, audience, author, ms.localizationpriority, ms.topic
title ms.reviewer manager ms.author description keywords ms.prod ms.mktglfcycl ms.sitesec ms.pagetype audience author ms.localizationpriority ms.topic
Resolution procedures - Windows IT Pro laurawi greglin Discover general troubleshooting procedures for dealing with 0xC1900101, the generic rollback code thrown when something goes wrong during a Windows 10 upgrade. deploy, error, troubleshoot, windows, 10, upgrade, code, rollback, ITPro w10 deploy library deploy itpro greg-lindsay medium article

Resolution procedures

Applies to

  • Windows 10

Note

This is a 200 level topic (moderate).
See Resolve Windows 10 upgrade errors for a full list of topics in this article.

0xC1900101

A frequently observed result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:

  • The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp,
  • Event logs: $Windows.~bt\Sources\Rollback*.evtx
  • The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018).

To resolve a rollback that was caused by driver conflicts, try running setup using a minimal set of drivers and startup programs by performing a clean boot before initiating the upgrade process.

See the following general troubleshooting procedures associated with a result code of 0xC1900101:

Code
0xC1900101 - 0x20004
Cause
Windows Setup encountered an error during the SAFE_OS with the INSTALL_RECOVERY_ENVIRONMENT operation.
This is generally caused by out-of-date drivers.
Mitigation
Uninstall antivirus applications.
Remove all unused SATA devices.
Remove all unused devices and drivers.
Update drivers and BIOS.
Code
0xC1900101 - 0x2000c
Cause
Windows Setup encountered an unspecified error during Wim apply in the WinPE phase.
This is generally caused by out-of-date drivers.
Mitigation
Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Contact your hardware vendor to obtain updated device drivers.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
Code
0xC1900101 - 0x20017
Cause
A driver has caused an illegal operation.
Windows was not able to migrate the driver, resulting in a rollback of the operating system.
This is a SafeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software.
Mitigation
Ensure that all that drivers are updated.
Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers.
For more information, see Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8.1, and Windows 10 setup log file locations.
Update or uninstall the problem drivers.
Code
0xC1900101 - 0x30018
Cause
A device driver has stopped responding to setup.exe during the upgrade process.
Mitigation
Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Contact your hardware vendor to obtain updated device drivers.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
Code
0xC1900101 - 0x3000D
Cause
Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation.
This can occur due to a problem with a display driver.
Mitigation
Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Update or uninstall the display driver.
Code
0xC1900101 - 0x4000D
Cause
A rollback occurred due to a driver configuration issue.
Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.
This can occur because of incompatible drivers.
Mitigation
Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
Review the rollback log and determine the stop code.
The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example is not representative of all cases: 
Info SP     Crash 0x0000007E detected
Info SP       Module name           :
Info SP       Bugcheck parameter 1  : 0xFFFFFFFFC0000005
Info SP       Bugcheck parameter 2  : 0xFFFFF8015BC0036A
Info SP       Bugcheck parameter 3  : 0xFFFFD000E5D23728
Info SP       Bugcheck parameter 4  : 0xFFFFD000E5D22F40
Info SP     Cannot recover the system.
Info SP     Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.

Typically, there is a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:

  1. Make sure you have enough disk space.
  2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
  3. Try changing video adapters.
  4. Check with your hardware vendor for any BIOS updates.
  5. Disable BIOS memory options such as caching or shadowing.
Code
0xC1900101 - 0x40017
Cause
Windows 10 upgrade failed after the second reboot.
This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.
Mitigation

Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see How to perform a clean boot in Windows.

Ensure that you select the option to "Download and install updates (recommended)."

Computers that run Citrix VDA
You may see this message after you upgrade a computer from Windows 10, version 1511 to Windows 10, version 1607. After the second system restart, the system generates this error and then rolls back to the previous version. This problem has also been observed in upgrades to Windows 8.1 and Windows 8.

This problem occurs because the computer has Citrix Virtual Delivery Agent (VDA) installed. Citrix VDA installs device drivers and a file system filter driver (CtxMcsWbc). This Citrix filter driver prevents the upgrade from writing changes to the disk, so the upgrade cannot complete and the system rolls back.

Resolution

To resolve this problem, install Cumulative update for Windows 10 Version 1607 and Windows Server 2016: November 8, 2016.

You can work around this problem in two ways

Workaround 1

  1. Use the VDA setup application (VDAWorkstationSetup_7.11) to uninstall Citrix VDA.
  2. Run the Windows upgrade again.
  3. Reinstall Citrix VDA.

Workaround 2

If you cannot uninstall Citrix VDA, follow these steps to work around this problem:

  1. In Registry Editor, go to the following subkey: 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}\CtxMcsWbc
  2. Change the value of the Start entry from 0 to 4. This change disables the Citrix MCS cache service.
  3. Go to the following subkey: 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
  4. Delete the CtxMcsWbc entry.
  5. Restart the computer, and then try the upgrade again.

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

0x800xxxxx

Result codes that start with the digits 0x800 are also important to understand. These error codes indicate general operating system errors, and are not unique to the Windows upgrade process. Examples include timeouts, devices not functioning, and a process stopping unexpectedly.

See the following general troubleshooting procedures associated with a result code of 0x800xxxxx:


Code
80040005 - 0x20007
Cause
An unspecified error occurred with a driver during the SafeOS phase.
Mitigation

This error has more than one possible cause. Attempt quick fixes, and if not successful, analyze log files in order to determine the problem and solution.
Code
0x80073BC3 - 0x20009
0x80070002 - 0x20009
0x80073B92 - 0x20009
Cause
The requested system device cannot be found, there is a sharing violation, or there are multiple devices matching the identification criteria.
Mitigation

These errors occur during partition analysis and validation, and can be caused by the presence of multiple system partitions. For example, if you installed a new system drive but left the previous system drive connected, this can cause a conflict. To resolve the errors, disconnect or temporarily disable drives that contain the unused system partition. You can reconnect the drive after the upgrade has completed. Alternatively, you can delete the unused system partition.
Code
800704B8 - 0x3001A
Cause
An extended error has occurred during the first boot phase.
Mitigation

Disable or uninstall non-Microsoft antivirus applications, disconnect all unnecessary devices, and perform a clean boot.
Code
8007042B - 0x4000D
Cause
The installation failed during the second boot phase while attempting the MIGRATE_DATA operation.
This issue can occur due to file system, application, or driver issues.
Mitigation

Analyze log files in order to determine the file, application, or driver that is not able to be migrated. Disconnect, update, remove, or replace the device or object.
Code
8007001F - 0x3000D
Cause
The installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.
Mitigation

Analyze log files in order to determine the files or registry entries that are blocking data migration.

This error can be due to a problem with user profiles. It can occur due to corrupt registry entries under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList or invalid files in the \Users directory.

Note

If a previous upgrade did not complete, invalid profiles might exist in the Windows.old\Users directory.

To repair this error, ensure that deleted accounts are not still present in the Windows registry and that files under the \Users directory are valid. Delete the invalid files or user profiles that are causing this error. The specific files and profiles that are causing the error will be recorded in the Windows setup log files.
Code
8007001F - 0x4000D
Cause
General failure, a device attached to the system is not functioning.
Mitigation

Analyze log files in order to determine the device that is not functioning properly. Disconnect, update, or replace the device.
Code
8007042B - 0x4001E
Cause
The installation failed during the second boot phase while attempting the PRE_OOBE operation.
Mitigation

This error has more than one possible cause. Attempt quick fixes, and if not successful, analyze log files in order to determine the problem and solution.

Other result codes


Error code Cause Mitigation
0xC1800118 WSUS has downloaded content that it cannot use due to a missing decryption key. See Steps to resolve error 0xC1800118 for information.
0xC1900200 Setup.exe has detected that the machine does not meet the minimum system requirements. Ensure the system you are trying to upgrade meets the minimum system requirements.
See Windows 10 specifications for information.
0x80090011 A device driver error occurred during user data migration. Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
0xC7700112 Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk. This issue is resolved in the latest version of Upgrade Assistant.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
0x80190001 An unexpected error was encountered while attempting to download files required for upgrade. To resolve this issue, download and run the media creation tool. See Download windows 10.
0x80246007 The update was not downloaded successfully. Attempt other methods of upgrading the operating system.
Download and run the media creation tool. See Download windows 10.
Attempt to upgrade using .ISO or USB.
Note
Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the Volume Licensing Service Center.
0x80244018 Your machine is connected through a proxy server. Make sure Automatically Detect Settings is selected in internet options. (Control Panel > Internet Options > Connections > LAN Settings).
0xC1900201 The system did not pass the minimum requirements to install the update. Contact the hardware vendor to get the latest updates.
0x80240017 The upgrade is unavailable for this edition of Windows. Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator.
0x80070020 The existing process cannot access the file because it is being used by another process. Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see How to perform a clean boot in Windows.
0x80070522 The user doesn’t have required privilege or credentials to upgrade. Ensure that you have signed in as a local administrator or have local administrator privileges.
0xC1900107 A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade. Restart the device and run setup again. If restarting the device does not resolve the issue, then use the Disk Cleanup utility and clean up the temporary files as well as the System files. For more information, see Disk cleanup in Windows 10.
0xC1900209 The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications. Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See Windows 10 Pre-Upgrade Validation using SETUP.EXE for more information.
You can also download the Windows Assessment and Deployment Kit (ADK) for Windows 10 and install Application Compatibility Tools.
0x8007002 This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403) Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760)
The error 80072efe means that the connection with the server was terminated abnormally.
To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN.
0x80240FFF Occurs when update synchronization fails. It can occur when you are using Windows Server Update Services on its own or when it is integrated with System Center Configuration Manager. If you enable update synchronization before you install hotfix 3095113, WSUS doesn't recognize the Upgrades classification and instead treats the upgrade like a regular update. You can prevent this by installing hotfix 3095113 before you enable update synchronization. However, if you have already run into this problem, do the following:
  1. Disable the Upgrades classification.
  2. Install hotfix 3095113.
  3. Delete previously synched updates.
  4. Enable the Upgrades classification.
  5. Perform a full synch.
For detailed information on how to run these steps check out How to delete upgrades in WSUS.
0x8007007E Occurs when update synchronization fails because you do not have hotfix 3095113 installed before you enable update synchronization. Specifically, the CopyToCache operation fails on clients that have already downloaded the upgrade because Windows Server Update Services has bad metadata related to the upgrade. It can occur when you are using standalone Windows Server Update Services or when WSUS is integrated with System Center Configuration Manager. Use the following steps to repair Windows Server Update Services. You must run these steps on each WSUS server that synched metadata before you installed the hotfix.
  1. Stop the Windows Update service. Sign in as a user with administrative privileges, and then do the following:
    1. Open Administrative Tools from the Control Panel.
    2. Double-click Services.
    3. Find the Windows Update service, right-click it, and then select Stop. If prompted, enter your credentials.
  2. Delete all files and folders under c:\Windows\SoftwareDistribution\DataStore.
  3. Restart the Windows Update service.

Other error codes


Error CodesCauseMitigation
0x80070003- 0x20007 This is a failure during SafeOS phase driver installation. Verify device drivers on the computer, and analyze log files to determine the problem driver.
0x8007025D - 0x2000C This error occurs if the ISO file's metadata is corrupt."Re-download the ISO/Media and re-attempt the upgrade.

Alternatively, re-create installation media the Media Creation Tool.

0x80070490 - 0x20007An incompatible device driver is present. Verify device drivers on the computer, and analyze log files to determine the problem driver.
0xC1900101 - 0x2000c An unspecified error occurred in the SafeOS phase during WIM apply. This can be caused by an outdated driver or disk corruption. Run checkdisk to repair the file system. For more information, see the quick fixes section in this guide.
Update drivers on the computer, and select "Download and install updates (recommended)" during the upgrade process. Disconnect devices other than the mouse, keyboard and display.
0xC1900200 - 0x20008 The computer doesn’t meet the minimum requirements to download or upgrade to Windows 10.

See Windows 10 Specifications and verify the computer meets minimum requirements.

Review logs for compatibility information.

0x80070004 - 0x3000D This is a problem with data migration during the first boot phase. There are multiple possible causes. Analyze log files to determine the issue.
0xC1900101 - 0x4001E Installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation. This is a generic error that occurs during the OOBE phase of setup. See the 0xC1900101 section of this guide and review general troubleshooting procedures described in that section.
0x80070005 - 0x4000D The installation failed in the SECOND_BOOT phase with an error in during MIGRATE_DATA operation. This error indicates that access was denied while attempting to migrate data. Analyze log files to determine the data point that is reporting access denied.
0x80070004 - 0x50012 Windows Setup failed to open a file. Analyze log files to determine the data point that is reporting access problems.
0xC190020e
0x80070070 - 0x50011
0x80070070 - 0x50012
0x80070070 - 0x60000 		These errors indicate the computer does not have enough free space available to install the upgrade. To upgrade a computer to Windows 10, it requires 16 GB of free hard drive space for a 32-bit OS, and 20 GB for a 64-bit OS. If there is not enough space, attempt to free up drive space before proceeding with the upgrade.

Note

If your device allows it, you can use an external USB drive for the upgrade process. Windows setup will back up the previous version of Windows to a USB external drive. The external drive must be at least 8GB (16GB is recommended). The external drive should be formatted using NTFS. Drives that are formatted in FAT32 may run into errors due to FAT32 file size limitations. USB drives are preferred over SD cards because drivers for SD cards are not migrated if the device does not support Connected Standby.

Modern setup errors

Also see the following sequential list of modern setup (mosetup) error codes with a brief description of the cause.

Result code Message Description
0XC1900100 MOSETUP_E_VERSION_MISMATCH An unexpected version of Setup Platform binaries was encountered. Please verify the package contents.
0XC1900101 MOSETUP_E_SETUP_PLATFORM The Setup Platform has encountered an unspecified error.
0XC1900102 MOSETUP_E_SHUTDOWN_BLOCK Unable to create or destroy the shutdown block message.
0XC1900103 MOSETUP_E_COMPAT_TIMEOUT The compatibility issues were not resolved within the required time limit.
0XC1900104 MOSETUP_E_PROCESS_TIMEOUT The installation process did not complete within the required time limit.
0XC1900105 MOSETUP_E_TEST_MODE The installation process is being used in a test environment.
0XC1900106 MOSETUP_E_TERMINATE_PROCESS The installation process was terminated.
0XC1900107 MOSETUP_E_CLEANUP_PENDING A cleanup operation from a previous installation attempt is still pending. A system reboot is required.
0XC1900108 MOSETUP_E_REPORTING An error has occurred and the result value must be consolidated for telemetry purposes.
0XC1900109 MOSETUP_E_COMPAT_TERMINATE The installation process was terminated during the actionable compatibility phase.
0XC190010a MOSETUP_E_UNKNOWN_CMD_LINE The installation process was launched with an unknown command-line argument.
0XC190010b MOSETUP_E_INSTALL_IMAGE_NOT_FOUND The installation image was not found.
0XC190010c MOSETUP_E_AUTOMATION_INVALID The provided automation information was invalid.
0XC190010d MOSETUP_E_INVALID_CMD_LINE The installation process was launched with an invalid command-line argument.
0XC190010e MOSETUP_E_EULA_ACCEPT_REQUIRED The installation process requires that the user accept the license agreement.
0XC1900110 MOSETUP_E_EULA_CANCEL The user has chosen to cancel for license agreement.
0XC1900111 MOSETUP_E_ADVERTISE_CANCEL The user has chosen to cancel for advertisement.
0XC1900112 MOSETUP_E_TARGET_DRIVE_NOT_FOUND Could not find a target drive letter.
0XC1900113 MOSETUP_E_EULA_DECLINED The user has declined the license terms.
0XC190011e MOSETUP_E_FLIGHTING_BVT The installation process has been halted for testing purposes.
0XC190011f MOSETUP_E_PROCESS_CRASHED The installation process crashed.
0XC1900120 MOSETUP_E_EULA_TIMEOUT The user has not accepted Eula within the required time limit.
0XC1900121 MOSETUP_E_ADVERTISE_TIMEOUT The user has not accepted Advertisement within the required time limit.
0XC1900122 MOSETUP_E_DOWNLOADDISKSPACE_TIMEOUT The download disk space issues were not resolved within the required time limit.
0XC1900123 MOSETUP_E_INSTALLDISKSPACE_TIMEOUT The install disk space issues were not resolved within the required time limit.
0XC1900124 MOSETUP_E_COMPAT_SYSREQ_TIMEOUT The minimum requirements compatibility issues were not resolved within the required time limit.
0XC1900125 MOSETUP_E_COMPAT_DOWNLOADREQ_TIMEOUT The compatibility issues for download were not resolved within the required time limit.
0XC1900126 MOSETUP_E_GATHER_OS_STATE_SIGNATURE The GatherOsState executable has invalid signature.
0XC1900127 MOSETUP_E_UNINSTALL_ALLOWED_ABORT The user has chosen to abort Setup to keep Uninstall option active.
0XC1900128 MOSETUP_E_MISSING_TASK The install cannot continue because a required task is missing.
0XC1900129 MOSETUP_E_UPDATEMEDIA_REQUESTED A more up-to-date version of setup will be launched to continue installation
0XC190012f MOSETUP_E_FINALIZE_ALREADY_REQUESTED The install cannot continue because a finalize operation was already requested.
0XC1900130 MOSETUP_E_INSTALL_HASH_MISSING The install cannot continue because the instance hash was not found.
0XC1900131 MOSETUP_E_INSTALL_HASH_MISMATCH The install cannot continue because the instance hash does not match.
0XC19001df MOSETUP_E_DISK_FULL The install cannot continue because the system is out of disk space.
0XC19001e0 MOSETUP_E_GATHER_OS_STATE_FAILED The GatherOsState executable has failed to execute.
0XC19001e1 MOSETUP_E_PROCESS_SUSPENDED The installation process was suspended.
0XC19001e2 MOSETUP_E_PREINSTALL_SCRIPT_FAILED A preinstall script failed to execute or returned an error.
0XC19001e3 MOSETUP_E_PRECOMMIT_SCRIPT_FAILED A precommit script failed to execute or returned an error.
0XC19001e4 MOSETUP_E_FAILURE_SCRIPT_FAILED A failure script failed to execute or returned an error.
0XC19001e5 MOSETUP_E_SCRIPT_TIMEOUT A script exceeded the timeout limit.
0XC1900200 MOSETUP_E_COMPAT_SYSREQ_BLOCK The system does not pass the minimum requirements to install the update.
0XC1900201 MOSETUP_E_COMPAT_SYSREQ_CANCEL The user has chosen to cancel because the system does not pass the minimum requirements to install the update.
0XC1900202 MOSETUP_E_COMPAT_DOWNLOADREQ_BLOCK The system does not pass the minimum requirements to download the update.
0XC1900203 MOSETUP_E_COMPAT_DOWNLOADREQ_CANCEL The user has chosen to cancel because the system does not pass the minimum requirements to download the update.
0XC1900204 MOSETUP_E_COMPAT_MIGCHOICE_BLOCK The system does not pass the requirements for desired migration choice.
0XC1900205 MOSETUP_E_COMPAT_MIGCHOICE_CANCEL The user has chosen to cancel because the system does not pass the requirements for desired migration choice.
0XC1900206 MOSETUP_E_COMPAT_DEVICEREQ_BLOCK The system does not pass the device scan to install the update.
0XC1900207 MOSETUP_E_COMPAT_DEVICEREQ_CANCEL The user has chosen to cancel because the system does not pass the device scan to install the update.
0XC1900208 MOSETUP_E_COMPAT_INSTALLREQ_BLOCK The system does not pass the compat scan to install the update.
0XC1900209 MOSETUP_E_COMPAT_INSTALLREQ_CANCEL The user has chosen to cancel because the system does not pass the compat scan to install the update.
0XC190020a MOSETUP_E_COMPAT_RECOVERYREQ_BLOCK The system does not pass the minimum requirements to recover Windows.
0XC190020b MOSETUP_E_COMPAT_RECOVERYREQ_CANCEL The user has chosen to cancel because the system does not pass the minimum requirements to recover Windows.
0XC190020c MOSETUP_E_DOWNLOADDISKSPACE_BLOCK The system does not pass the disk space requirements to download the payload.
0XC190020d MOSETUP_E_DOWNLOADDISKSPACE_CANCEL The user has chosen to cancel as the device does not have enough disk space to download.
0XC190020e MOSETUP_E_INSTALLDISKSPACE_BLOCK The system does not pass the disk space requirements to install the payload.
0XC190020f MOSETUP_E_INSTALLDISKSPACE_CANCEL The user has chosen to cancel as the device does not have enough disk space to install.
0XC1900210 MOSETUP_E_COMPAT_SCANONLY The user has used the setup.exe command line to do scanonly, not to install the OS.
0XC1900211 MOSETUP_E_DOWNLOAD_UNPACK_DISKSPACE_BLOCK The system does not pass the disk space requirements to download and unpack media.
0XC1900212 MOSETUP_E_DOWNLOAD_UNPACK_DISKSPACE_MULTIARCH_BLOCK The system does not pass the disk space requirements to download and unpack multi-architecture media.
0XC1900213 MOSETUP_E_NO_OFFER_FOUND There was no offer found that matches the required criteria.
0XC1900214 MOSETUP_E_UNSUPPORTED_VERSION This version of the tool is not supported.
0XC1900215 MOSETUP_E_NO_MATCHING_INSTALL_IMAGE Could not find an install image for this system.
0XC1900216 MOSETUP_E_ROLLBACK_PENDING Found pending OS rollback operation.
0XC1900220 MOSETUP_E_COMPAT_REPORT_NOT_DISPLAYED The compatibility report cannot be displayed due to a missing system component.
0XC1900400 MOSETUP_E_UA_VERSION_MISMATCH An unexpected version of Update Agent client was encountered.
0XC1900401 MOSETUP_E_UA_NO_PACKAGES_TO_DOWNLOAD No packages to be downloaded.
0XC1900402 MOSETUP_E_UA_UPDATE_CANNOT_BE_MERGED No packages to be downloaded.
0XC1900403 MOSETUP_E_UA_CORRUPT_PAYLOAD_FILES Payload files were corrupt.
0XC1900404 MOSETUP_E_UA_BOX_NOT_FOUND The installation executable was not found.
0XC1900405 MOSETUP_E_UA_BOX_CRASHED The installation process terminated unexpectedly.

Related topics