• 0xC1900101-0x20017, SAFE_OS phase with an error during BOOT operation

    Home » Forums » AskWoody support » Windows » Windows 7 » Win7 beyond End-of-life » 0xC1900101-0x20017, SAFE_OS phase with an error during BOOT operation

    • This topic has 8 replies, 3 voices, and was last updated 5 years ago.
    Author
    Topic
    #2257643

    The W7ESUI.cmd has bought me some time by allowing Windows 7 Updates now I want to upgrade to Windows 10. I think I am very close yet can’t complete the install.

    I have removed an Intel Graphics Driver so that a generic driver will allow the upgrade.
    Microsoft Security Essentials need to be removed from Windows 7.

    I tried upgrading to Windows 10 – 1809 (via ISO); didn’t work, as well as the Media Creation Tool 1909.
    I think it created the Windows 10 OS and was trying to boot into it, but keeps failing {W7toW10Upgrade.png}. It just never gets Windows 10 started and is stuck like it is about to start Windows 10 with the circular timing icon.

    One article I found:
    https://support.microsoft.com/en-gb/help/927521/windows-vista-windows-7-windows-server-2008-r2-windows-8-1-and-windows

    From this article https://www.repairwin.com/fix-windows-10-upgrade-error-0xc1900101-0x20017-installation-failed-in-the-safe_os-phase-during-boot-operation/, there is mention of the SoftwareDistribution folder, is this affected by W7ESUI.cmd?

    Windows Update Troubleshooter also found some problems. Windows Update says there is a problem but I was hoping it wouldn’t affect the upgrade.{TroubleShoot-1-Fix-2.PNG}

    I am about to give up if it is not less than 10 steps. I have taken a peek at WindowsUpdate.log; kind of interesting. Another PC has the same W7 to W10 upgrade problem (and other problems) and I am looking at CBS.log to fix it. My guess is that both PC’s have the same problem  setting but I don’t know what it is (manual telemetry has been turned off, . Hopefully it is a one step solution because by buying a new PC, the Product Key can upgrade it to Windows 10 Pro.

    What do people think?
    Am I nearly finished the install?
    Is this easy or too hard?

    • This topic was modified 5 years ago by KP.
    Viewing 5 reply threads
    Author
    Replies
    • #2257654

      One question comes to mind – did you ever run the GWX Control Panel or one of the other Win10 blockers back when MS was forcing Win10 on Win7 computers? The GWX-CP (and maybe some of the others) did a Registry Entry that prevented the. upgrade.

    • #2257670

      Here’s a couple of links that might help (thanks @abbodi86 )

      https://support.microsoft.com/en-us/help/10587/windows-10-get-help-with-upgrade-installation-errors

      https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors

      And his comment on the script:

      safe_os phase is related to winre.wim and migrating drivers/settings

      the script does not remove any related settings, nor it touch SoftwareDistribution folder

      1 user thanked author for this post.
      KP
    • #2257836

      I blocked the Windows 10 Update in 2016 using GWX and would have “un-done” it once we were no longer allowed to upgrade. I am pretty sure it was removed but will double-check.

    • #2257838

      The second link looks like some items to try. Thanks @PKCano, @abbodi86.

      My next attempt will be SetupDiag. Let’s see how it goes and how difficult it is.

      Looking at the Troubleshooting Upgrade Errors link, we can see I am in 2, Safe OS phase, but I do not get as far as the screen shot in the article.

      This is has given me some items to try out and and the Level 300 things should be do-able for me.

      If there are any DISM articles/commands that might be useful here, please post. I did try 3 DISM recovery commands but only one works in Windows 7.

      Thanks again.

      • This reply was modified 5 years ago by KP.
      • #2257842

        DISM doesn’t help Win7.

        You can try in an elevated Command Prompt (if you haven’t already):
        chkdsk /f
        Reboot and let it run, then in the elevated Command Prompt:
        sfc /scannow

        There is a process for cleaning the Windows Update datastore that is a little more involved. If you want to try that, let me know.

        1 user thanked author for this post.
        KP
        • #2257850

          I didn’t post everything I tried but on a problematic PC, I have been trying these things; that PC is still a work-in-progress.

          A lot of articles mention drivers so perhaps SetupDiag or Troubleshooting Upgrade Errors will point me to logs and help narrow down the software conflict. It has to be something I have done on both PC’s.

    • #2257840

      (manual telemetry has been turned off,

      addendum: turning off telemetry manually AKB2000012

      • This reply was modified 5 years ago by KP.
    • #2261727

      From KP (who had trouble posting this):

      Windows 10 1809 Upgrade succeeded. It was a GWX registry setting. Thank @PKCano.
      From a Woody article, I checked the following:

      If you are an IT professional, you can set the following registry keys to disable notifications:
      Registry location: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Gwx
      DWORD name: DisableGwx
      Value data: 1
      Registry location: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
      DWORD name: DisableOSUpgrade
      Value data: 1

      This was the case on one PC. The PC that I decided to upgrade, has
      Registry location: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate
      DWORD name: AllowOSUpgrade
      Value data: 0

      so I changed it to one and re-tried the upgrade, this time success. The upgrade was run offline until I installed the Monthly Cumulative Updates that downloaded before hand.

      Once I got pass the First Boot Phase, I was pass my problem.

      One Windows 7 PC was semi-functioning with crashes and corrupt dll’s (me, experimenting with Registry Cleaners) so I decide to upgrade it although the lap screen is near EoL (works attach to external monitor, though).

      It took a good 5 minutes to start while running the Windows 10 setup program, before you realize it is running so it give some time.

      Although it says there are issues with the Display Graphics Adapter and Microsoft Security Essentials (MSE), the upgrade works around them. It installed a generic basic graphics driver (even though a compatible driver exists on the Microsoft Update Catalog) and the upgrade uninstalled MSE. The great thing about the in-place upgrade, is it left a lot of programs in-place and did not uninstalled them, Super!

      For completeness, I checked older articles (1, 2) and

      Registry location: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\OSUpgrade
      DWORD name: ReservationsAllowed
      Value data: 0 or 1

      This key has been removed, probably with a Microsoft patch post-July-2016.

      I don’t remember all the things I had to do in 2016, to do the Windows 10 upgrades so YMMV. My guess is I uninstalled GWX Control Panel and thought the Windows Update patch would reset the Registry keys.

      I tried to post this a few times this week, hence the post upgrade comment.
      Post Upgrade: It is working well, seems slow on the startup which is why I think people want an SSD Drive.

      1 user thanked author for this post.
      KP
    Viewing 5 reply threads
    Reply To: 0xC1900101-0x20017, SAFE_OS phase with an error during BOOT operation

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: