Windows Setup encountered an error during the SAFE_OS with the INSTALL_RECOVERY_ENVIRONMENT operation. See the following general troubleshooting procedures associated with a result code of 0xC1900101: Code 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. The device install log is helpful if rollback occurs during the sysprep operation (extend code 0x30018). The device install log: $Windows.~bt\Sources\Rollback\setupapi\.Event logs: $Windows.~bt\Sources\Rollback*.evtx.The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp. Analysis of supplemental log files is often helpful, such as: The incompatible driver can cause blue screens, system hangs, and unexpected reboots. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. This result code can be thrown at any stage of the upgrade process, with the exception of the downlevel phase. 0xC1900101Ī frequently observed result code is 0xC1900101. You should also try running the free SetupDiag tool provided by Microsoft, which can automatically find the reason for an upgrade failure. If a Windows 10 upgrade fails, you can write down the error code that is displayed, or find the error code in the Windows Event Log or in the Windows Setup log files (ex: setuperr.log) and review the cause and solutions provided here. This article provides some common causes and solutions that are associated with specific upgrade error codes. For IT professionals, check more information in Resolve Windows 10 upgrade errors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |