How Do I Specify Windows Update Repair Source in Registry?


  1. Posts : 4
    Windows 10
       #1

    How Do I Specify Windows Update Repair Source in Registry?


    Good morning and Happy New Year!

    Within my organization's environment, we have a small number of machines that occasionally fail to install updates as a result of missing assembly files (error code: 0x80073701). When this occurs, the Windows Update agent - in some cases, but not all - will attempt a repair (still unclear as to why this inconsistency exists). When attempting repair, it tries to locate a repair source in order to run a process that appears similar to DISM /online /cleanup-image /restorehealth. However, because the repair source is currently not configured in our environment, it attempts to use Microsoft's Windows Update servers by default. Our firewall is not set to allow this and so the process reports that it is unable to resolve the repair source.

    Now, I am aware that this can be configured using Group Policy (Computer Configuration -> Administrative Templates -> System -> Specify Settings for optional component...). However, I am curious as to whether or not this can also be configured in the registry?

    Additionally, I have a related question: When using a WIM file as a repair source, must that WIM first be mounted? I think that it has to, but wanted to verify as the last time I ran DISM's restorehealth feature, I pointed it to an unmounted WIM file. The process completed successfully but didn't appear to repair anything.

    Thank you!
      My Computer


  2. Posts : 650
    10 preview 64bit
       #2

    Hi wkizzlejr,

    That error code is an identifier that a "building block", for want of a better description, is missing/corrupt within a PREVIOUS update that the current update needs to access, and becaue of this the new update fails.
    Allthough W10 is a new system parts of previous OS's have been carried over; the Update process is one of them.
    Within an update, there are Packages and inside of these are even more sublayers
    KB123456 > Packages > Cat/Mum
    Thats not all tho
    All updates migrate thru CBS and CSI, and within the CSI operation even more pre-update processing takes pace, and
    inside these
    Components > Payload
    Your problem will be within
    Cat/Mum/Components or Payload.

    The CBS log should point towards the problematic Update and the errors within it.
    (not sure if the DISM log does, the old SURT did, and could be fixed using it)

    Post the logs.

    As for the restore health command was the latter
    /Source:wim:E:\sources\install.wim:1 /limitaccess
    Where wim:E is the repair source, DVD/USB/ISO from another GOOD machine

    MS ITPro - DISM tutorial

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-or-remove-packages-offline-using-dism
    Not sure if the term package in this scenario actually relates to a Windows update package.

    I do know of another tool that will identify and can insert/replace the missing/corrupt entries,
    BUT as your running behind a Server with GPO restrictions!!!,

    If all the affected machines have IDENTICAL errors that would infer that this group of received a Bad server patch, or that their GPO's are slightly different from the unaffected machines.


    Roy
      My Computer


  3. Posts : 56,103
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #3

    wkizzlejr said:
    Good morning and Happy New Year!

    Within my organization's environment, we have a small number of machines that occasionally fail to install updates as a result of missing assembly files (error code: 0x80073701). When this occurs, the Windows Update agent - in some cases, but not all - will attempt a repair (still unclear as to why this inconsistency exists). When attempting repair, it tries to locate a repair source in order to run a process that appears similar to DISM /online /cleanup-image /restorehealth. However, because the repair source is currently not configured in our environment, it attempts to use Microsoft's Windows Update servers by default. Our firewall is not set to allow this and so the process reports that it is unable to resolve the repair source.

    Now, I am aware that this can be configured using Group Policy (Computer Configuration -> Administrative Templates -> System -> Specify Settings for optional component...). However, I am curious as to whether or not this can also be configured in the registry?

    Additionally, I have a related question: When using a WIM file as a repair source, must that WIM first be mounted? I think that it has to, but wanted to verify as the last time I ran DISM's restorehealth feature, I pointed it to an unmounted WIM file. The process completed successfully but didn't appear to repair anything.

    Thank you!
    Good morning, and Happy New year @wkizzlejr

    Yes the image (ISO) should be mounted first, with the mount command or opened with Explorer (both right-click context options). System will assign drive letter. Example command line here. Sub the mounted drive letter for "G".

    DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:G:\sources\Install.wim:1 /LimitAccess
      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 08:39.
Find Us




Windows 10 Forums