W10 update error on (really) old laptop: SAFE_OS phase

Page 3 of 8 FirstFirst 12345 ... LastLast

  1. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #21

    I too get the error:
    0xC1900101 - 0x20017
    The installation failed in the SAFE_OS phase with an error during BOOT operation.
    My machine is a 10 years-old Alienware Predator 2 ALX x58 using a Core i7 975 chip, originally built for Vista, and back then was the most advanced machine outside of the commercial Xeon powered world.
    I had no problems whatsoever upgrading to 1709 when it came available but 1803 and 1809 have stumped the machine. I'm hoping MS will realise they have to fix whatever they took out
    I dual boot Win 7 Ultimate x64 with Win 10 Pro x64 and my main concern is next January I will have to upgrade Win 7 to Win 10 anyway.
    Does anyone have any idea if MS are discussing this subject? It was easy when I was an MS MVP to get information on this sort of thing but now I just have to rely on what I can see using a Google search.
    It's extremely annoying and frustrating.
      My Computer


  2. Posts : 30,117
    Windows 11 Pro x64 Version 23H2
       #22

    Have you tried the setupdiag exe for determining error. I have an old HP DV6000 built for Vista that is running and updating on the Fast Ring of the Insider Program. I have a Dell D630 built for XP on 1809 and a HP 530 running 1809. Got lucky with hardware they used but so far they have stayed in the game.

    This article talks to the specific log that should identify driver(s) causing the issue. (and run setupDiag)

    https://docs.microsoft.com/en-gb/win...dy_UpgradeTips
      My Computer


  3. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #23

    OK thanks, will try that.
      My Computer


  4. Posts : 30,117
    Windows 11 Pro x64 Version 23H2
       #24

    Hope it helps.
      My Computer


  5. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #25

    Well I tried once to upgrade- failed.
    Here's the log and I've attached the resulting zip file.
    My eyesight is such that I can't read for long unless it's really magnified so it takes a while longer than most to scan a document.
    Maybe someone here can take a look see what's stopping the upgrade.

    SetupDiag was unable to match to any known failure signatures.
    System Information:
    Machine Name = PETERSWIN10
    Manufacturer = System manufacturer
    Model = System Product Name
    HostOSArchitecture = x64
    FirmwareType = PCAT
    BiosReleaseDate = 20101222000000.000000+000
    BiosVendor = BIOS Date: 12/22/10 17:47:29 Ver: 08.00.15
    BiosVersion = 1202
    HostOSVersion = 10.0.16299
    HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
    TargetOSBuildString = 10.0.17763.402 (rs5_release_svc_prod3.190313-1840)
    HostOSLanguageId = 1033
    HostOSEdition = Professional
    RegisteredAV = Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,
    FilterDrivers = WdFilter,mfehidk,wcifs,luafv,Wof,FileInfo,
    UpgradeStartTime = 2019-04-05 4:20:54 PM
    FinalizeStartTime = 2019-04-05 4:53:04 PM
    UpgradeEndTime = 2019-04-05 5:44:25 PM
    UpgradeElapsedTime = 01:23:31
    CV = NVACo3+dtEOfY/QK
    ReportId = F850CC38-C3A8-4E73-BE5D-3344FE0EB30D

    Thanks ;-)
    Last edited by Ex_Brit; 05 Apr 2019 at 21:10.
      My Computer


  6. Posts : 30,117
    Windows 11 Pro x64 Version 23H2
       #26

    Hi Ex_Brit

    Could you run this command at a command prompt(admin) or and Powershell(admin) command line

    sigverif.exe

    Did it report anything.

    Please download this tool and install. Execute tool, when program starts click in the column name area and add the column for

    OEM INF

    What is OEM46.INF and OEM47.INF?

    From some of the data you provided they have a BlockMigration status and their binaries are not signed.

    W10 update error on (really) old laptop: SAFE_OS phase-image.png
      My Computer


  7. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #27

    Will do asap, but have to go out so will get back to you later. Thanks.
      My Computer


  8. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #28

    OK, here goes. I will warn you I really am clueless when it comes to this sort of thing.
    It found 1 driver unsigned which came up in a popup window.

    W10 update error on (really) old laptop: SAFE_OS phase-zzzodddll.jpg

    This appears to be a Microsoft Scanner driver and in Device Manager there is, at the bottom, a WSD item.
    Should I uninstall it and let Windows install it again?
    I couldn't find a column entitled OEM anything so will post the full log. This used to be a Dell/Alienware BIOS but subsequent updates for the BIOS from the ASUS website which were never offered by Dell wiped out the OEM. Plus the fact that the only OEM system this machine had was Vista. I replaced that with a full-retail copy of Windows 7 Ultimate.
    This Windows 10 is a "spare" copy so to speak in a separate partition from Win 7. I'm just hoping things will go OK eventually.
    Can't upgrades be forced to ignore unsigned drivers?
    W10 update error on (really) old laptop: SAFE_OS phase Attached Files
    Last edited by Ex_Brit; 06 Apr 2019 at 12:12.
      My Computer


  9. Posts : 783
    Win10 Pro - x64 latest build dual boot w/Win 11 Pro
       #29

    Footnote: I deleted that .dll and the accompanying .dll.mui and Windows made no effort to reinstall it, but another stab at updating failed yet again.....
    m hexed obviously ;-)
      My Computer


  10. Posts : 30,117
    Windows 11 Pro x64 Version 23H2
       #30

    Sorry Ex_Brit. I was rushing yesterday and forgot to provide the second link. My error.

    Please download this tool

    https://github.com/lostindark/Driver...es/tag/v0.9.10

    When this app, RPAR, is running right click where the column names are and add column OEM INF.

    The we ware looking for 46 and 47. Not sure, you may have wiped one out yesterday. Lets see what you get.
      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 07:45.
Find Us




Windows 10 Forums