Skip to content

Windows Update error 0xC1900101: Driver error during upgrade

Updated

Cleared for publishing after the automated checks on .

What these 10 codes mean

This page covers 10 codes: 0xC1900101, 0xC1900101-0x20004, 0xC1900101-0x2000C, 0xC1900101-0x20017, 0xC1900101-0x30017, 0xC1900101-0x30018, 0xC1900101-0x3000D, 0xC1900101-0x4000D, 0xC1900101-0x40017, 0xC1900101-0x4001E.

0xC1900101: Driver error during upgrade

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101

SuffixPhaseWhat it means
0x2000CSP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the APPLY_IMAGE operation (phase 2, operation C). (Windows 10 upgrade error codes)
0x20017SP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the BOOT operation (phase 2, operation 17). (Windows 10 upgrade error codes)
0x30017SP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the BOOT operation (phase 3, operation 17). (Windows 10 upgrade error codes)
0x30018SP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the SYSPREP operation (phase 3, operation 18). (Windows 10 upgrade error codes)
0x3000DSP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the MIGRATE_DATA operation (phase 3, operation D). (Windows 10 upgrade error codes)
0x4000DSP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the MIGRATE_DATA operation (phase 4, operation D). (Windows 10 upgrade error codes)
0x40017SP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the BOOT operation (phase 4, operation 17). (Windows 10 upgrade error codes)
0x20004SP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the INSTALL_RECOVERY_ENVIRONMENT operation (phase 2, operation 4). (Windows 10 upgrade error codes)
0x4001ESP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the PRE_OOBE operation (phase 4, operation 1E). (Windows 10 upgrade error codes)

0xC1900101-0x20004: SAFE_OS / INSTALL_RECOVERY_ENVIRONMENT error

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x20004

SuffixPhaseWhat it means
0x20004SP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the INSTALL_RECOVERY_ENVIRONMENT operation (phase 2, operation 4). (Windows 10 upgrade error codes)

0xC1900101-0x2000C: Upgrade failed while applying the Windows image (SafeOS phase)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x2000C

SuffixPhaseWhat it means
0x2000CSP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the APPLY_IMAGE operation (phase 2, operation C). (Windows 10 upgrade error codes)

0xC1900101-0x20017: A driver caused an illegal operation (SafeOS boot failure)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x20017

SuffixPhaseWhat it means
0x20017SP_EXECUTION_SAFE_OSError in the SAFE_OS phase during the BOOT operation (phase 2, operation 17). (Windows 10 upgrade error codes)

0xC1900101-0x30017: A driver has caused a problem (first boot)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x30017

SuffixPhaseWhat it means
0x30017SP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the BOOT operation (phase 3, operation 17). (Windows 10 upgrade error codes)

0xC1900101-0x30018: A device driver stopped responding to setup

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x30018

SuffixPhaseWhat it means
0x30018SP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the SYSPREP operation (phase 3, operation 18). (Windows 10 upgrade error codes)

0xC1900101-0x3000D: Upgrade failed in the first boot phase while migrating data (display driver)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x3000D

SuffixPhaseWhat it means
0x3000DSP_EXECUTION_FIRST_BOOTError in the FIRST_BOOT phase during the MIGRATE_DATA operation (phase 3, operation D). (Windows 10 upgrade error codes)

0xC1900101-0x4000D: Rollback during the second boot phase (data migration)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x4000D

SuffixPhaseWhat it means
0x4000DSP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the MIGRATE_DATA operation (phase 4, operation D). (Windows 10 upgrade error codes)

0xC1900101-0x40017: Upgrade failed after the second reboot (faulty driver)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x40017

SuffixPhaseWhat it means
0x40017SP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the BOOT operation (phase 4, operation 17). (Windows 10 upgrade error codes)

0xC1900101-0x4001E: Upgrade failed in the second boot phase (PRE_OOBE)

The Setup Platform has encountered an unspecified error. (Windows 10 upgrade resolution procedures)

A generic rollback result code; in most cases the cause is a driver compatibility problem. The extend code after it tells the setup phase. (Windows 10 upgrade error codes)

Setup extended codes for 0xC1900101-0x4001E

SuffixPhaseWhat it means
0x4001ESP_EXECUTION_OOBE_BOOTError in the OOBE_BOOT phase during the PRE_OOBE operation (phase 4, operation 1E). (Windows 10 upgrade error codes)

Code facts

0xC1900101: Driver error during upgrade

Code as Windows shows it0xC1900101
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x20004: SAFE_OS / INSTALL_RECOVERY_ENVIRONMENT error

Code as Windows shows it0xC1900101-0x20004
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x2000C: Upgrade failed while applying the Windows image (SafeOS phase)

Code as Windows shows it0xC1900101-0x2000C
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x20017: A driver caused an illegal operation (SafeOS boot failure)

Code as Windows shows it0xC1900101-0x20017
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x30017: A driver has caused a problem (first boot)

Code as Windows shows it0xC1900101-0x30017
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x30018: A device driver stopped responding to setup

Code as Windows shows it0xC1900101-0x30018
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x3000D: Upgrade failed in the first boot phase while migrating data (display driver)

Code as Windows shows it0xC1900101-0x3000D
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x4000D: Rollback during the second boot phase (data migration)

Code as Windows shows it0xC1900101-0x4000D
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x40017: Upgrade failed after the second reboot (faulty driver)

Code as Windows shows it0xC1900101-0x40017
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

0xC1900101-0x4001E: Upgrade failed in the second boot phase (PRE_OOBE)

Code as Windows shows it0xC1900101-0x4001E
TypeWindows setup extended code
Symbolic nameMOSETUP_E_SETUP_PLATFORM
Hexadecimal, 8 digits0xC1900101
Decimal (unsigned)3247440129
Decimal (signed 32-bit)-1047527167
GroupWindows Update errors

Read with care

  • Not a standard HRESULT (R bit set without the N bit, MS-ERREF 2.1): it is a Windows Setup result code; do not split it into facility and error number. ([MS-ERREF]: HRESULT, Windows 10 upgrade error codes)
  • Microsoft's upgrade error codes page suggests reading the last four digits of a code that starts with C as an NTSTATUS value. For this code that gives 0x00000101 STATUS_ALERTED, which is not what Microsoft's setup tables say this code means. Use the setup tables instead. (Windows 10 upgrade error codes, [MS-ERREF]: NTSTATUS)
  • Microsoft says these phase and operation values reflect the Windows 10 upgrade process (version 1607) and might change in later releases. (Windows 10 upgrade error codes)

Code facts: Windows 10 upgrade resolution procedures (Microsoft Learn, CC BY 4.0), checked Nov 14, 2026.

Code facts: Windows 10 upgrade error codes (Microsoft Learn, CC BY 4.0), checked Nov 14, 2026.

Where this error shows up

This code shows up while Windows Update or a Windows upgrade is downloading, installing or setting up.

Applies to

  • 0xC1900101: Windows 11 and Windows 10 (as listed at the top of the Microsoft page). The page notes Windows 10 support ended 14 Oct 2025.
  • 0xC1900101-0x20004: Windows 10 (page: 'Applies to: Windows 10'). Windows 10 support ended on October 14, 2025 (note on Microsoft support pages such as Get help with Windows upgrade and installation errors).
  • 0xC1900101-0x2000C: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x20017: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x30017: Windows 11 and Windows 10 (upgrade help page has the row in both tabs)
  • 0xC1900101-0x30018: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x3000D: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x4000D: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x40017: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)
  • 0xC1900101-0x4001E: Windows 10 upgrade pages (Microsoft says the extend codes apply to Windows 10 version 1607 and might change)

Try these first

These steps carry no risk flag in the data. They keep the order of the full list below, which is not reordered. A step without a flag is not a promise that it is safe for your computer.

33 steps to try, in order

Steps are grouped by the Microsoft page they come from. The page lists only what those pages give; other causes of 0xC1900101 are not covered. 18 steps are flagged.

If this page and Microsoft's page differ, follow Microsoft's page.

Microsoft also gives general steps that cover these codes: see the general steps in the Windows Update errors group. Each block there says which codes its Microsoft page gives the steps for.

From: Get help with Windows upgrade and installation errors

Source: Get help with Windows upgrade and installation errors (Microsoft Support), checked Nov 14, 2026. Summary in our own words; Microsoft's page has the full steps.

0xC1900101: Microsoft's steps for every 0xC1900101 variant on its upgrade help page (Windows 11 and Windows 10 tabs).

0xC1900101-0x20017, 0xC1900101-0x30017: Microsoft's upgrade help page lists 0xC1900101 0x20017 and 0x30017 in one table row.

  1. Update Windows and drivers, then check Device Manager

    Disables or removes drivers

    Run Windows Update more than once and install everything it offers, including hardware and some third-party driver updates; Microsoft also points to the Windows Update troubleshooter.

    For hardware you added yourself, get driver updates and install instructions from its maker's website.

    Open Device Manager (type device manager in the taskbar search box), open each category and look for a device with a yellow exclamation mark. Right-click (or press and hold) it and choose Update Driver Software or Uninstall.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  2. Unplug hardware you don't need

    Take off external storage, drives, docks and other add-ons that aren't needed for basic use. For the 0x20017 and 0x30017 variants Microsoft says to disconnect everything except the mouse, keyboard and display.

  3. Remove third-party security software

    Changes security settings

    Uninstall non-Microsoft security software for the upgrade, after checking that you know how to reinstall it and have its product keys. Windows Defender keeps protecting the PC meanwhile.

    For 0x20017 and 0x30017 the page says to disable or remove third-party antivirus or antispyware.

    Microsoft advises: If you remove security software, first make sure you know how to reinstall it and that any product keys are on hand. Windows Defender helps protect the device in the meantime. (Get help with Windows upgrade and installation errors)

  4. Ask for updated drivers (0x20017, 0x30017)

    For the 0x20017 and 0x30017 variants Microsoft says to get updated device drivers from the hardware maker.

  5. Disable or remove third-party antivirus

    For 0xC1900101-0x20017, 0xC1900101-0x30017.

    Changes security settings

    Turn off or uninstall any non-Microsoft antivirus or antispyware on the PC.

    Before you uninstall it, make sure you know how to reinstall it and have its product keys or activation details at hand; Windows Defender protects the PC meanwhile (Microsoft's advice for removing security software on the same page).

    Microsoft advises: If you remove security software, first make sure you know how to reinstall it and that any product keys are on hand. Windows Defender helps protect the device in the meantime. (Get help with Windows upgrade and installation errors)

  6. Disconnect peripherals

    For 0xC1900101-0x20017, 0xC1900101-0x30017.

    Unplug every peripheral except the mouse, keyboard and display.

  7. Get updated drivers

    For 0xC1900101-0x20017, 0xC1900101-0x30017.

    Ask the hardware maker for updated device drivers.

From: Troubleshoot problems updating Windows

Source: Troubleshoot problems updating Windows (Microsoft Support), checked Nov 14, 2026. Summary in our own words; Microsoft's page has the full steps.

0xC1900101: Microsoft's page asks you to back up your personal files before trying its fixes.

  1. Uninstall network or graphics drivers

    Disables or removes drivers

    In Device Manager, open Network adapters or Display adapters, right-click the adapter and choose Uninstall device.

    Restart the PC afterwards so the change takes effect.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  2. Update network or graphics drivers

    In Device Manager, right-click the network or display adapter, choose Update driver and then Search automatically for drivers.

From: Windows 10 upgrade resolution procedures

Source: Windows 10 upgrade resolution procedures (Microsoft Learn), checked Nov 14, 2026. © Microsoft, licensed under CC BY 4.0. Steps shortened and reworded by PC Driver Update.

0xC1900101, 0xC1900101-0x2000C, 0xC1900101-0x20017, 0xC1900101-0x30018, 0xC1900101-0x3000D, 0xC1900101-0x4000D: Microsoft's Windows 10 upgrade resolution procedures (a page for IT professionals; applies to Windows 10).

0xC1900101-0x40017: Microsoft's Windows 10 upgrade resolution procedures (IT page; applies to Windows 10). The row also covers PCs with Citrix VDA (1511 to 1607 upgrades) with a cumulative update and two workarounds, one of which edits the registry; those are not repeated here.

  1. Supplemental log files (IT)

    Windows 10 only.

    Analysis of supplemental log files is often helpful: the minidump $Windows.~bt\Sources\Rollback\setupmem.dmp, the event logs $Windows.~bt\Sources\Rollback*.evtx, and the device install log $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log (helpful when the rollback happens during sysprep, extend code 0x30018).

  2. Uninstall antivirus applications

    For 0xC1900101-0x20004.

    Windows 10 only.

    Changes security settings

    Uninstall antivirus applications.

    Microsoft advises: If you remove security software, first make sure you know how to reinstall it and that any product keys are on hand. Windows Defender helps protect the device in the meantime. (Get help with Windows upgrade and installation errors)

  3. Remove unused SATA devices

    For 0xC1900101-0x20004.

    Windows 10 only.

    Changes disks

    Remove all unused SATA devices.

    Microsoft advises: Back up your personal files before you try these fixes. (Back up and restore with Windows Backup)

  4. Remove unused devices and drivers

    For 0xC1900101-0x20004.

    Windows 10 only.

    Disables or removes drivers

    Remove all unused devices and drivers.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  5. Update drivers and BIOS

    For 0xC1900101-0x20004.

    Windows 10 only.

    Changes BIOS or firmware

    Update drivers and BIOS.

    Our advice: Back up your files first, and follow your PC maker's instructions for BIOS or firmware settings and updates. How to: Windows recovery environment

  6. Disconnect peripherals

    For 0xC1900101-0x2000C, 0xC1900101-0x30018, 0xC1900101-0x3000D.

    Windows 10 only.

    Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.

  7. Get updated drivers

    For 0xC1900101-0x2000C, 0xC1900101-0x30018.

    Windows 10 only.

    Contact your hardware vendor to obtain updated device drivers, and ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.

  8. Update drivers and find the problem drivers

    For 0xC1900101-0x20017.

    Windows 10 only.

    Disables or removes drivers

    Ensure that all drivers are updated.

    Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers.

    Update or uninstall the problem drivers.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  9. Check the device install log (IT)

    For 0xC1900101-0x30018.

    Windows 10 only.

    The page says the device install log $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log is helpful when the rollback happens during the sysprep operation (extend code 0x30018).

  10. Update or uninstall the display driver

    For 0xC1900101-0x3000D.

    Windows 10 only.

    Disables or removes drivers

    Update or uninstall the display driver.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  11. Check the rollback logs (IT)

    For 0xC1900101-0x4000D.

    Windows 10 only.

    Check supplemental rollback logs for a setupmem.dmp file, or event logs for unexpected reboots or errors, and determine the stop code from the rollback log in $Windows.~BT\Sources\Rollback. Typically there's a dump file to analyze.

  12. Basic troubleshooting if you can't debug the dump

    For 0xC1900101-0x4000D.

    Windows 10 only.

    Disables or removes driversChanges BIOS or firmware

    Make sure you have enough disk space.

    If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.

    Try changing video adapters.

    Check with your hardware vendor for any BIOS updates.

    Disable BIOS memory options such as caching or shadowing.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

    Our advice: Back up your files first, and follow your PC maker's instructions for BIOS or firmware settings and updates. How to: Windows recovery environment

  13. Clean boot, then upgrade

    For 0xC1900101-0x40017.

    Windows 10 only.

    Changes boot or startup

    Clean boot into Windows, and then attempt the upgrade (see How to perform a clean boot in Windows).

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

    Microsoft advises: Keep track of what you change so you can undo it, and return the PC to a normal startup when you are done. (How to perform a clean boot in Windows)

From: Upgrade fails and generates error code 0xC1900101-0x20017

Source: Upgrade fails and generates error code 0xC1900101-0x20017 (Microsoft Learn), checked Nov 14, 2026. © Microsoft, licensed under CC BY 4.0. Steps shortened and reworded by PC Driver Update.

0xC1900101-0x20017: Microsoft's dedicated page for this code (written for IT professionals; applies to Windows client and Windows Server). It asks for a backup and recovery plan before you upgrade.

  1. Check the upgrade prerequisites

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Make sure that the computer meets the requirements for Windows (see Windows 11 requirements) or Windows Server.

  2. Review event logs

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Use Event Viewer to review the system logs for events that might be related to driver or hardware issues; fix any issue you can, then try the upgrade again.

  3. Update Windows and third-party drivers

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Use the Windows Update Check for updates function (several times if needed) to install available Important updates, hardware updates and driver updates.

    Check third-party drivers and download any updates from the hardware manufacturer's website.

  4. Check Device Manager for errors

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Disables or removes drivers

    Open Device Manager (devmgmt.msc) and look for devices marked by a yellow exclamation mark (you might have to expand each category).

    Right-click a marked device and select either Update Driver Software or Uninstall. After all errors are resolved, try the upgrade again.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  5. Check the BIOS

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Changes BIOS or firmware

    Make sure that the BIOS and firmware for the device are up to date; if necessary, check the device manufacturer's website.

    Our advice: Back up your files first, and follow your PC maker's instructions for BIOS or firmware settings and updates. How to: Windows recovery environment

  6. Repair or remove unsigned drivers

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Disables or removes drivers

    Open an administrative Command Prompt window and run sigverif; in the File Signature Verification tool select Start. After it runs, it lists any unsigned drivers (Advanced > View Log shows the log).

    For a detailed check the page uses the Sysinternals sigcheck tool (sigcheck64 -i <DriverPath>, or sigcheck -i on 32-bit Windows).

    To repair unsigned drivers: install updated versions, or uninstall and reinstall them; to restore a catalog file, reinstall the driver or copy the catalog file from another device. If none of this works, uninstall the affected driver and try the upgrade again.

    Microsoft advises: Save your work and close all apps first. If Windows doesn't reinstall the driver after the restart, update the driver from Device Manager. (Update drivers through Device Manager in Windows)

  7. Remove conflicting software

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Changes security settings

    Try to disable any third-party anti-virus and anti-malware applications, and reconfigure or remove software that's known to cause conflicts (the page names CrowdStrike). Then try the upgrade again.

    Microsoft advises: If you remove security software, first make sure you know how to reinstall it and that any product keys are on hand. Windows Defender helps protect the device in the meantime. (Get help with Windows upgrade and installation errors)

  8. Clean restart

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Changes boot or startup

    Sign in as administrator, type msconfig in the search box and select System Configuration. Select Services > Hide all Microsoft services > Disable all.

    Select Startup > Open Task Manager, disable each startup item, close Task Manager, then in System Configuration select Startup > OK and restart.

    After the restart, try the upgrade again. If you see the Download and install updates option during installation, make sure that you select it.

    Microsoft advises: Keep track of what you change so you can undo it, and return the PC to a normal startup when you are done. (How to perform a clean boot in Windows)

  9. Remove nonessential external hardware

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Disconnect all peripheral devices except the mouse, keyboard and display devices, and disconnect or disable network adapters that you don't use for the upgrade. Then try again.

    To avoid driver conflicts for the removed devices, the page says the Download and install updates option should be disabled during this installation.

  10. Check local user accounts

    For 0xC1900101-0x20017.

    Written for IT administrators.

    Removes user accounts

    Open Computer Management (compmgmt.msc), select Computer Configuration > System Tools > Local Users and Groups > Users (the path as the page writes it), and remove any user accounts that aren't used or are extraneous.

    Microsoft advises: Removing a user account also deletes that account's sign-in details and data from this PC. (Manage user accounts in Windows)

  11. Replace the computer

    For 0xC1900101-0x20017.

    Written for IT administrators.

    If the issue persists, consider replacing the computer.

Stop and get help

If these steps do not fix the problem, or you are not sure about a step, stop and get help from Microsoft Support or from the maker of your PC. Stop at once if the data on this computer is at risk: back up your files first, or ask a professional before you go on.

Dates and review

Automated checksfirst check: ; second check: ; third check: ; fourth check:
Microsoft pages read
  • Get help with Windows upgrade and installation errors: read , the Microsoft page is dated Feb 18, 2026
  • Troubleshoot problems updating Windows: read , the Microsoft page is dated Sep 24, 2026
  • Windows 10 upgrade resolution procedures: read , the Microsoft page is dated Feb 12, 2026
  • Windows 10 upgrade error codes: read , the Microsoft page is dated Feb 12, 2026
  • [MS-ERREF]: HRESULT: read , the Microsoft page is dated Nov 20, 2024
  • [MS-ERREF]: NTSTATUS: read , the Microsoft page is dated Oct 30, 2024
  • Upgrade fails and generates error code 0xC1900101-0x20017: read , the Microsoft page is dated Feb 12, 2026
Review statusCleared for publishing after the automated checks on .