Can't upgrade 1809 to 1909

  1. kingalp's Avatar
    Posts : 4
    Windows 10
       #1

    Can't upgrade 1809 to 1909


    Hello! I've been trying the better part of a couple days to get my Windows 10 install up to the latest version. I'm trying to upgrade version 1809 build 17763.914 to the latest November update (1909). After the update not working, I tried to use my USB installer with the newest version of the ISO file straight from MS.

    I tried several times and took advice from multiple sources, but nothing seemed to work. My current version of windows is currently fully updated, by the way. After going through the process to 100% and rebooting, I get a login screen and login to this error:

    We couldn't install Windows 10
    We've set your PC back to the way it was right before you started installing Windows 10.

    0xC1900101 - 0x20017
    The installation failed in the SAFE_OS phase with an error during BOOT operation


    After several attempts and keeping a close eye on my setuperr.log files, I managed to fix at least some potential issues and reduce the log down to 11 lines:

    2020-01-04 13:22:51, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #38# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = b58 ('\REGISTRY\MACHINE\SYSTEM\Setup'), vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2020-01-04 13:22:51, Error CSI 00000002 (F) STATUS_OBJECT_NAME_NOT_FOUND #37# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:31]'\Registry\Machine\SYSTEM\Setup\', vn = [l:7 ml:8]'Compact', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2020-01-04 13:22:53, Error CSI 00000003 (F) STATUS_OBJECT_NAME_NOT_FOUND #70# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = a40 ('\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts'), vn = [l:21 ml:22]'Arial Nova (TrueType)', kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2020-01-04 13:22:53, Error CSI 00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #69# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:69]'\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\', vn = [l:21 ml:22]'Arial Nova (TrueType)', ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2020-01-04 13:28:24, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
    2020-01-04 13:29:35, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
    2020-01-04 13:31:21, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
    2020-01-04 13:31:21, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
    2020-01-04 13:32:09, Error MOUPG Finalize: Error obtaining Update and Shutdown Key: [0x80070002][gle=0x000000b7]
    2020-01-04 13:32:18, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume5\EFI\Microsoft\Boot (kd_*_*.dll). Last Error = 0x6[gle=0x00000006]
    2020-01-04 13:32:18, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume5\EFI\Microsoft\Boot (kdstub.dll). Last Error = 0x6[gle=0x00000006]


    Up until this point I had been starting the upgrade without the "Automatically download updates" option checked off, to try to simplify the process, and when I attempted again with it on, my setuperr.log file went up to 21 lines. I believe the root cause is in the 11 lines above, but I'll include the log file as an attachment anyone for someone who wants to try to help.

    I'm not too familiar with parsing these setuperr.log files, so help from anybody who is familiar with debugging this sort of thing is greatly appreciated. All of MS's official help articles are completely useless.

    Thanks to anybody with any suggestions, I'm pretty stuck on this & really do not want to format my drive and start from fresh. Any help is greatly appreciated.
    Can't upgrade 1809 to 1909 Attached Files
      My Computer

  2. dalchina's Avatar
    Posts : 31,773
    Win 10 Pro (1903)
       #2

    Hi, there are search results matching the last two lines e.g.

    https://answers.microsoft.com/en-us/...b-3f70af7cd417
      My Computers

  3. kingalp's Avatar
    Posts : 4
    Windows 10
    Thread Starter
       #3

    Thanks for the reply dalchina, that was one of the few lines from that log that I didn't try googling (gave up before then). I did consider trying to rebuild the BCD on my own, but considering all my other ideas that went nowhere, I was a bit discouraged, lol. I'll give this a shot, and if successful hopefully this post will help other people with a similar issue.
      My Computer


  4. Posts : 38,716
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    The displayed error code was 0xC1900101 - 0x20017
    This error code is usually seen when there is a problematic driver.

    Usually the backup options for failed Windows upgrades includes:
    reset save files
    reset save files equivalent
    clean install

    These require the re-installation of drivers and applications

    Please indicate if you want to troubleshoot.

    If you do then please perform these steps:

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    10) wmic recoveros get autoreboot
    11) wmic recoveros get DebugInfoType
    12) bcdedit /enum {badmemory}

    13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    14) Make sure that there is no over clocking while troubleshooting

    15) There are log collectors used in another forum room.
    Run each V2 and DM and upload results into this thread
    BSOD - Posting Instructions
      My Computer

  5. kingalp's Avatar
    Posts : 4
    Windows 10
    Thread Starter
       #5

    Well I finally got my system updated, dalchina pointed me in the right direction.

    The fix given from that direction was to get into recovery and run "bootrec /Rebuildbcd" but while my installation was successfully scanned, trying to add to boot list resulted in the error: "The requested system device cannot be found." I'm not sure if that was caused because I'm booting with UEFI, or if it's because of how my UEFI is a little bit jank(don't ask).

    But, the real fix was going into recovery mode, and using the command prompt to run "bootrec /Fixboot"

    After that I ran the installer again, and this time after reboot the installation actually continued.

    Thanks for the help & replies, and hopefully this can help someone out who has the same exact issue as me.
      My Computer


  6. Posts : 38,716
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Please upload results from V2 and DM into this thread.
      My Computer

  7. dalchina's Avatar
    Posts : 31,773
    Win 10 Pro (1903)
       #7

    Sounds one useful step along the way... let us know if it completes, bearing in mind the error number.

    First thing when it's completed- create a new base (full) Windows disk image using e.g. Macrium reflect free-paid + large enough external storage for image files, and continue routinely with e.g. differential images (free version).

    tenforums members tirelessly recommend disk imaging so you have second chance in many situations.
      My Computers

  8. kingalp's Avatar
    Posts : 4
    Windows 10
    Thread Starter
       #8

    dalchina said:
    Sounds one useful step along the way... let us know if it completes, bearing in mind the error number.

    First thing when it's completed- create a new base (full) Windows disk image using e.g. Macrium reflect free-paid + large enough external storage for image files, and continue routinely with e.g. differential images (free version).

    tenforums members tirelessly recommend disk imaging so you have second chance in many situations.
    Yes, the update completed successfully. Thanks again for the help, and imaging is a great idea but I typically just backup all my important files to my backup server. My preferred imaging method is linux dd, but that's just me as it can be quite a pain getting a reasonable file size.
      My Computer

  9. dalchina's Avatar
    Posts : 31,773
    Win 10 Pro (1903)
       #9



    Backing up files is utterly and completely different to imaging. There is simply no comparison.

    Images are a complete compressed copy of the ENTIRE partition imaged.

    With an image you can-
    - recover Windows (or any imaged disk or partition) to a new disk if your old one fails.
    - extract any file from a mounted image
    - recover from ransomware or severe virus by restoring an image created before that occurred
    - often avoid having to reinstall Windows
    - have several different dates to which you can restore your imaged partitions
    - transfer your installed Windows to another PC
    - recover from unbootable situations without days of technical help and someone else's time (and possibly having to do a clean install)

    Avoiding clean installing means you avoid long periods of reconfiguration, lost program licenses, realising there's some data you don't have backed up.

    If you are comparing backing up and imaging, I'm afraid you don't understand its value and why so many tenforums members use and recommend it.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:54.
Find Us




Windows 10 Forums