W10 1909 EOL and upgrade fails! 0xC1900101 DELL Inspiron 5565

Page 1 of 2 12 LastLast
  1. Silverhand92's Avatar
    Posts : 21
    Windows 10 Pro x64
       #1

    W10 1909 EOL and upgrade fails! 0xC1900101 DELL Inspiron 5565


    I hope this topic title grabs the attention of somebody with a lot of ideas how to help.
    As it states, I'm getting snarked at that Windows 10 1909-18363.1556 has reached end of service.

    I've tried to update to 20H1, 20H2, 21H1, 21H2..... Whichever might work.
    I keep, unfortunately - running into this message...
    "installation failed during safe os phase with an error during boot operation"
    and the error code 0xc1900101. I think that the other part of the error message is 0x20017, but can't be sure as one of my attempts to bypass this error was to back-up my data externally and try a refresh to factory OS settings, then update from there. (Of COURSE that didn't work... Why would I figure that would work?)

    At this point, I have run out of ideas, and I'm reaching out for help...
    I really don't want to be stuck "out of date" or "out of service" with 1909. I'd rather get properly updated.
      My Computer

  2. dalchina's Avatar
    Posts : 34,237
    Win 10 Pro (1903) (2nd PC is 21H2)
       #2

    Hi, that error number is typical of a driver failing to be migrated.

    Please get a copy of setupdiag.exe from MS (free)- run that and post outcome. It attempts to analyse the upgrade logs and match against known cases.

    Analysing upgrade failures can be tedious and daunting with no certain outcome guaranteed - witness the many lengthy threads you can find on tenforums (simply search the site for your error number - I assume you've done that already?)

    Log files:
    https://docs.microsoft.com/en-us/win...rade/log-files
    https://support.microsoft.com/en-us/...8-e9c6714349b9

    setuperr.log, setupact.log are typical ones to inspect.

    What security software do you have installed?

    Upgrade phases:
    https://docs.microsoft.com/en-us/win...upgrade-errors

    installation failed during safe os phase with an error during boot operation
    ->
    1. SafeOS phase: Errors most commonly occur during this phase due to hardware issues, firmware issues, or non-microsoft disk encryption software.

      Since the computer is booted into Windows PE during the SafeOS phase, a useful troubleshooting technique is to boot into Windows PE using installation media. You can use the media creation tool to create bootable media, or you can use tools such as the Windows ADK, and then boot your device from this media to test for hardware and firmware compatibility issues.
      Tip
      If you attempt to use the media creation tool with a USB drive and this fails with error 0x80004005 - 0xa001a, this is because the USB drive is using GPT partition style. The tool requires that you use MBR partition style. You can use the DISKPART command to convert the USB drive from GPT to MBR. For more information, see Change a GUID Partition Table Disk into a Master Boot Record Disk.

      Do not proceed with the Windows 10 installation after booting from this media. This method can only be used to perform a clean install which will not migrate any of your apps and settings, and you will be required re-enter your Windows 10 license information.
      If the computer does not successfully boot into Windows PE using the media that you created, this is likely due to a hardware or firmware issue. Check with your hardware manufacturer and apply any recommended BIOS and firmware updates. If you are still unable to boot to installation media after applying updates, disconnect or replace legacy hardware.
      If the computer successfully boots into Windows PE, but you are not able to browse the system drive on the computer, it is possible that non-Microsoft disk encryption software is blocking your ability to perform a Windows 10 upgrade. Update or temporarily remove the disk encryption.
    Perform a routine disk check (Hard Disk Sentinel is excellent) and if ok, run chkdsk c: /scan from an admin command prompt.

    Also post a screenshot of your partitions using a 3rd party partition manager such as Minitool Partition Wizard thus
    W10 1909 EOL and upgrade fails! 0xC1900101  DELL Inspiron 5565-screenshot-.png

    I really don't want to be stuck "out of date" or "out of service" with 1909. I'd rather get properly updated.
    - it's unlikely you'll notice much difference functionally with later builds. I've kept one PC on 1903 as that was the last build on which Windows search was still fully functional- before MS broke it in 2 particular ways.
      My Computers


  3. Posts : 588
    Windows 10 Pro 21H2 x64
       #3

    Well, good news, looks like the system is from the pre-UEFI era, so you can go ahead with making an MBR-style partition.

    Back when DDR2 was made=That's more than old enough to be a legacy BIOS.
      My Computers

  4. Silverhand92's Avatar
    Posts : 21
    Windows 10 Pro x64
    Thread Starter
       #4

    RJARRRPCGP said:
    Well, good news, looks like the system is from the pre-UEFI era, so you can go ahead with making an MBR-style partition.Back when DDR2 was made=That's more than old enough to be a legacy BIOS.
    Actually, my desktop is in storage right now. My laptop is a Dell Inspiron 15-5565 with a 7th Gen AMD-A9 CPU and 8GB/DDR3 with a 1TB non-SSD harddrive, and while the BIOS shows a Legacy Mode; its default config is UEFI.
    To answer dalchina's question; The laptop came with McAfee LiveSafe, but the subscription is expired, so I've switched over to Windows Defender.
    I'm trying to upload the error logs, but the attachment manager on this forum seems to be having trouble getting the files uploaded.
      My Computer

  5. dalchina's Avatar
    Posts : 34,237
    Win 10 Pro (1903) (2nd PC is 21H2)
       #5

    Hi, thank you for your reply.


    The output from setupdiag.exe should be short.

    The log files themselves are hard to read.

    You can upload larger files by zipping them. There are size limits, and only certain types are accepted.

    Confirm you have uninstalled any 3rd party security programs.
      My Computers

  6. Silverhand92's Avatar
    Posts : 21
    Windows 10 Pro x64
    Thread Starter
       #6

    OK, so I can confirm that the W10 is a fresh boot after factory OS restore.
    It does come with McAfee LiveSafe, but with the McAfee subscription expired, I have removed it and switched over to Windows Defender.

    The log files are attched below, except for setupact.log, due to the forums' attachment uploader crashing when trying to attach that one.

    SetupDiagResults.log
    setuperr.log
      My Computer

  7. dalchina's Avatar
    Posts : 34,237
    Win 10 Pro (1903) (2nd PC is 21H2)
       #7

    Thank you for your reply.

    Again
    Perform a routine disk check (Hard Disk Sentinel is excellent) and if ok, run chkdsk c: /scan from an admin command prompt.

    Also post a screenshot of your partitions using a 3rd party partition manager such as Minitool Partition Wizard
    due to the forums' attachment uploader crashing when trying to attach that one.
    Please post a screenshot of the 'crash' - did you receive an error message?

    Note - again you can zip - compress large files and upload as ***.zip. That will be a much smaller file.

    setupdiag.exe does not help with diagnosis in this case.

    Please check that your BIOS is up to date.

    *** setuperr.log shows you have NOT successfully removed McAfee.
    If you have uninstalled it, now search for its manual uninstaller and use that.



    Have you been offered an upgrade by Windows Update, or have you ONLY been attempting this manually?

    If you haven't been offered an upgrade by Windows Update, there may be an incompatibility and a MS Safeguard Hold may apply.

    Please checking your BIOS version, update it necessary, and try using the MS update assistant:
    https://support.microsoft.com/en-us/...a-fba2ac36fb3f
      My Computers

  8. Silverhand92's Avatar
    Posts : 21
    Windows 10 Pro x64
    Thread Starter
       #8

    To answer your questions;

    I'd like to keep 3rd party software to a minimum, so as not to have them interfere with the update/upgrade.
    I don't have Hard Drive Sentinel or MiniTools downloaded or installed.

    Dell's BIOS includes a system integrity test and the HDD and RAM passed. It's not a hardware issue. Not unless it's one that's so obscure that it would register the tests as passed.

    The uploader crashing doesn't give me any error or anything like that, it just freezes the Microsoft Edge page until it says;
    "This page has crashed! Edge will attempt to recover the page and restore any lost data. Please be patient while we recover this for you."

    Afterward, I get back the page where I'm posting, but none of the logs that I was trying to add to it are attached.
    (Although I finally got them working.)

    My system's BIOS is kept in check by Dell SupportAssist (and actually updated this morning to BIOS 1.2.0.0. vs. 1.1.0.9.)
    The update is being offered by Windows Update, but it gives me that error when I attempt to complete the installation, either through the automatic process, or by downloading the package and attempting to finish the upgrade manually.
    Being that the update is offered automatically, it shouldn't be a compatibility issue. Otherwise, it wouldn't be pushed out automatically.

    Finally got this to attach:

    setupact.zip
      My Computer

  9. dalchina's Avatar
    Posts : 34,237
    Win 10 Pro (1903) (2nd PC is 21H2)
       #9

    I'd like to keep 3rd party software to a minimum, so as not to have them interfere with the update/upgrade.
    I don't have Hard Drive Sentinel or MiniTools downloaded or installed.
    Repeatedly going round hte same thing simply wastes time.

    1. There is a portable version of HDS. Have you looked?
    2. There is a portable version of MPW. Have you looked?

    *** setuperr.log shows you have NOT successfully removed McAfee.
    If you have uninstalled it, now search for its manual uninstaller and use that.


    Your latest log shows loads of McAfee references.

    I won't move on or address others meanwhile.

    N.B.
    0xC1900101 - 0x20017 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.
    Which logs did you upload?
    Last edited by dalchina; 14 Oct 2021 at 08:43.
      My Computers

  10. jimbo45's Avatar
    Posts : 11,057
    Windows / Linux : Arch Linux
       #10

    Hi folks
    I've got one computer that can't even install any Windows version after 1809 -- install isos etc won't boot gives BSOD on boot -- missing boot device or things like that-- and the computer is not really that old either -- has a 4 core AMD opteron CPU with R3 graphics (built in). The only Windows systems I can get on this machine after build 1809 are VM's !!!!

    I think it's the only time that I've never been able to install a current retail working version of Windows !!!!

    I can't even boot a WINPE USB on it either whether in MBR or UEFI mode -- so there is obviously some rogue hardware out there. It can boot Macrium however but again only on USB devices of 8GB or less. Won't handle NTFS UEFI boot in any shape or form either.

    I've relegated this machine to the function of a NAS server which it does OK running Fedora. Good for backups etc - but it shows how there are always the odd rogue machines out there which absolutely refuse to run newer versions of Windows.

    (I've a couple of much older machines that can run W10 without issue !!! -- INTEL processors -- so probably why I'm forever biased against AMD processors and Mobos -- YMMV on that one however - it's just my experience).

    Cheers
    jimbo
      My Computer


 

  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 18:10.
Find Us




Windows 10 Forums