[SOLVED] Windows Update stops installing at 1% during reboot for KB5014699

[JayNDT]

Error code: (0x80073712)

 

[x BlueRobot]

It's the same error as before but with different components this time, apart from one which I've highlighted in red for my reference.

amd64_microsoft-windows-c..w64-deployment00110_31bf3856ad364e35_10.0.19041.1889_none_2305c07d52324ae2 
amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.19041.1889_none_8cf7696fd9b8860c 
amd64_product-onecore__du.._avrcptransport.inf_31bf3856ad364e35_10.0.19041.1_none_50980cbe6b2edfaf

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or WeTransfer and then just provide the link in your reply.

Export CBS hive

• Click on the Start button and in the search box, type regedit
• When you see regedit on the list, right-click on it and select Run as administrator.
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (.).
• Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.

 

[JayNDT]

Done

 

[x BlueRobot]

Please run the attached SFCFixScript with SFCFix and then attempt to update again, however, please do so with a Process Monitor trace running so if this error occurs again, we'll hopefully be able to repair them all at once.

 

[JayNDT]

https://www.dropbox.com/s/lahsbazmdibnnet/Logfile.zip?dl=1

 

[x BlueRobot]

Please run the attached SFCFixScript and then attempt to update again. If it fails, then please provide the latest CBS log(s).

 

[JayNDT]

Apologies for my ill computer...

 

[x BlueRobot]

Could you please provide your latest COMPONENTS and CBS subkey using the same instructions as before?

 

[JayNDT]

Done.

 

[x BlueRobot]

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[JayNDT]

Fix result of Farbar Recovery Scan Tool (x64) Version: 30-08-2022
Ran by dutta (18-09-2022 14:43:20) Run:5
Running from C:\Users\dutta\Desktop
Loaded Profiles: dutta
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg load HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
DeleteValue: HKLM\COMPONENTS\CanonicalData\Deployments\microsoft-w..oyment00100_31bf3856ad364e35_10.0.19041.1889_23109069522a2ef1|i!CBS_microsoft-windows-client-desktop-required-wow64-package0010~_9483a20eb18a9b15
DeleteValue: HKLM\COMPONENTS\CanonicalData\Deployments\product-one..ansport.inf_31bf3856ad364e35_10.0.19041.1_50980cbe6b2edfaf|i!CBS_microsoft-windows-client-desktop-required-package~31bf3856ad_62c17fa0f3646813
Reg: reg add HKLM\COMPONENTS\CanonicalData\Deployments\product-one..ansport.inf_31bf3856ad364e35_10.0.19041.1_50980cbe6b2edfaf /v i!CBS_microsoft-windows-client-desktop-required-package~31bf3856ad_a2b104d1cdc22baa /t REG_BINARY /d 9A000000000000004D6963726F736F66742D57696E646F77732D436C69656E742D4465736B746F702D52657175697265642D5061636B6167657E333162663338353661643336346533357E616D6436347E7E31302E302E31393034312E313532362E41394236443444363939463338383033383038423538413337393436383045383343354539453837463631334438343536393343463737353530413035454330 /f
cmd: dir C:\Windows\servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.*

*****************

Error: (0) Failed to create a restore point.

========= reg load HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========

The operation completed successfully.



========= End of Reg: =========

"HKLM\COMPONENTS\CanonicalData\Deployments\microsoft-w..oyment00100_31bf3856ad364e35_10.0.19041.1889_23109069522a2ef1\\i!CBS_microsoft-windows-client-desktop-required-wow64-package0010~_9483a20eb18a9b15" => removed successfully
"HKLM\COMPONENTS\CanonicalData\Deployments\product-one..ansport.inf_31bf3856ad364e35_10.0.19041.1_50980cbe6b2edfaf\\i!CBS_microsoft-windows-client-desktop-required-package~31bf3856ad_62c17fa0f3646813" => removed successfully

========= reg add HKLM\COMPONENTS\CanonicalData\Deployments\product-one..ansport.inf_31bf3856ad364e35_10.0.19041.1_50980cbe6b2edfaf /v i!CBS_microsoft-windows-client-desktop-required-package~31bf3856ad_a2b104d1cdc22baa /t REG_BINARY /d 9A000000000000004D6963726F736F66742D57696E646F77732D436C69656E742D4465736B746F702D52657175697265642D5061636B6167657E333162663338353661643336346533357E616D6436347E7E31302E302E31393034312E313532362E41394236443444363939463338383033383038423538413337393436383045383343354539453837463631334438343536393343463737353530413035454330 /f =========

The operation completed successfully.



========= End of Reg: =========


========= dir C:\Windows\servicing\Packages\Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.* =========

 Volume in drive C is Windows
 Volume Serial Number is 289D-B926

 Directory of C:\Windows\servicing\Packages

04/08/2022  19:36            10,824 Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.cat
04/08/2022  19:36               932 Microsoft-Client-License-Platform-Device-Licensing-Service-Package~31bf3856ad364e35~amd64~~10.0.19041.1865.mum
               2 File(s)         11,756 bytes
               0 Dir(s)  46,254,637,056 bytes free

========= End of CMD: =========


==== End of Fixlog 14:43:22 ====

 

[x BlueRobot]

Thanks, could you please try and update again. If it fails, then please provide the latest CBS logs.

 

[JayNDT]

Same old error...

 

[x BlueRobot]

It is different keys this time though and there only appears to be two as well. Please follow the same instructions as before and then attempt to update. Please then provide the CBS logs if it fails.

 

[JayNDT]

Did the fix but an error popped up in the log. The rest was fine, but I haven't updated yet.

========= reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Client-Desktop-Required-Package0510~31bf3856ad364e35~amd64~~10.0.19041.1889 /v CurrentState /t REG_DWORD /d 0x70 /f =========

ERROR: Invalid syntax.
Type "REG ADD /?" for usage.

 

[x BlueRobot]

Sorry, please try the one attached.

 

[JayNDT]

Here's the log, after the error.

 

[x BlueRobot]

Please run the following and then attempt to update again.

 

[JayNDT]

To save time, I've attach the CBS and fixlog.

Are these new keys being corrupted, or the same ones constantly? Do I need to update DISM each time, reboot and then try to update? It's sad to see my machine acting so ill to anything that could fix it.

 

[x BlueRobot]

One was the same as before and another was a new one. I doubt that DISM will make any difference here. Please find the latest fix attached.