While troubleshooting failed windows updates (like 0x8007370b and others) DISM Restorehealth fails (error 14091)

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Takeshino
    PCHF Member
    • Nov 2022
    • 1

    #1

    While troubleshooting failed windows updates (like 0x8007370b and others) DISM Restorehealth fails (error 14091)

    So the original issue is that after my GPU (RTX3080) inexplicably “failed”, slowing down booting, attempts to repair and a windows 11 to go install to a crawl, and after I sent it for repairs and they couldn’t find any fault and gotten it back it worked (maybe cable fuckery). Anyway, both while I was using an old RTX2070S as a holdover and after I got it back system updates fail, either download errors (0x80070020) or install errors (0x8007370b). Currently, I see the following updates: KB5018427, KB5018496, KB5018341. Following the troubleshooting steps on Get Help led me to run DISM Restorehealth, which fails at random percentages, but always with the same error code, 14091. Here’s the last one I ran:

    Code:
    C:\Windows\System32>Dism /Online /Cleanup-Image /ScanHealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.1
    
    Image Version: 10.0.22621.1
    
    [===========================86.4%================== ]
    Error: 14091
    
    The name of an attribute in an identity is not within the legal range.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Here’s a Pastebin of dism.log. I also ran MemTest at the recommendation of another forum thread, but that went through without any errors, although I might not have tested the RAM sticks separately, I don’t really understand the program that well tbh.
    I’m currently on OS build 22621.1, PC info: Motherboard: MSI B450 Gaming Pro Carbon AC CPU: AMD 3700x GPU: Nvidia 3080 SSD: 2 Sabrent Nvme gen 3 PSU: Corsair RM850x
  • Bruce
    PCHF Moderator
    • Oct 2017
    • 10697

    #2
    with all those errors, and an old build, I’d be getting the latest OS release via the Windows Media Creation Tool to create a bootable USB stick.

    only have the boot drive connected.
    change your BIOS boot order to boot from the stick first and during the install process, delete all your drive partitions.

    you may be looking at a faulty drive to explain your many errors.

    Comment

    • Rustys
      PCHF Member
      • Jul 2016
      • 7862

      #3
      Abandoned closed.

      showing solved on other forum by poster

      Comment

      Working...