Unable to Update KB5042320, Wrong Path?

Question

Hello,

I have this issue and after doing a number of things, Update Trouble Shooter, created a recover partition, even though I have 32 GB memory installed, but nothing worked.

I did find mention of an error log...C:\Windows\Logs\WinREAgent\setuperr.log. I reviewed this and found this entry....

2024-11-23 11:52:01, Error 0x80070003 in PushButtonReset::Path::AreEqual (base\reset\util\src\filesystem.cpp:805): Failed to get attributes for [\?\D:$WinREAgent\Backup\WinRE.wim][gle=0x00000003]

2024-11-23 11:52:01, Error [0x018068] CSI 00000025 (F) Failed execution of queue item Installer: WinRE Servicing Installer ({29194b27-704c-49cc-b251-094354712ebd}) with HRESULT HRESULT_FROM_WIN32(ERROR_PATH_NOT_FOUND). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

2024-11-23 11:52:02, Error CSI 00000044 (F) Installer: WinRE Servicing Installer Binary Name: wcp.dll ErrorCode: 80070003 Phase: 39 Mode: Delta Component: NONE[gle=0x80004005]

2024-11-23 11:52:03, Error CBS Exec: An error occurred while committing the transaction, the transaction has been rolled back. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]

2024-11-23 11:52:03, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]

2024-11-23 11:52:52, Error CBS Failed to perform operation. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]

2024-11-23 11:52:52, Error 0x800f0922 in DismAddPackageByPath (base\diagnosis\srt\winreagent\tools\winreupdateinstaller\servicinghelper.cpp:227): [WinREUpdInst] Failed to add DISM package from path [C:\Windows\SoftwareDistribution\Download\Install\windows10.0-kb5034441-x64.cab]

2024-11-23 11:52:52, Error 0x800f0922 in wmain (base\diagnosis\srt\winreagent\tools\winreupdateinstaller\main.cpp:143): [WinREUpdInst] Failed to add DISM package by path[gle=0x0000007a]

2024-11-23 11:56:26, Error [TiWorker.exe] winreHashWimFile: Failed to hash [D:$WinREAgent\Scratch\update.wim]: 0x3

2024-11-23 11:56:26, Error 0x80070003 in GenerateEncodedHash (base\diagnosis\srt\winreagent\lib\operations\src\verifynewwinrehash.cpp:22): Failed to hash wim file [D:$WinREAgent\Scratch\update.wim][gle=0x00000003]

2024-11-23 11:56:26, Error 0x80070003 in WinREAgent::VerifyNewWinREHash::InternalExecute (base\diagnosis\srt\winreagent\lib\operations\src\verifynewwinrehash.cpp:58): Failed to generate hash of update WinRE[gle=0x00000003]

2024-11-23 11:56:26, Error 0x80070003 in WinREAgent::Operation::Execute (base\diagnosis\srt\winreagent\lib\operations\src\operation.cpp:167): Internal failure to execute operation[gle=0x00000003]

2024-11-23 11:56:26, Error 0x80070003 in WinREAgent::Executor::Commit (base\diagnosis\srt\winreagent\dll\executor.cpp:1356): Failed to execute operation [VerifyNewWinREHash][gle=0x00000003]

2024-11-23 11:56:26, Error 0x80070003 in WinREAgent::WinREServicingManager::Commit (base\diagnosis\srt\winreagent\dll\winreservicingmanager.cpp:526): Failed to commit WinRE servicing[gle=0x00000003]

2024-11-23 11:56:26, Error 0x80070003 in PushButtonReset::Path::AreEqual (base\reset\util\src\filesystem.cpp:805): Failed to get attributes for [\?\D:$WinREAgent\Backup\WinRE.wim][gle=0x00000003]

What I find interesting is that my primary drive is C: but I do have a D: drive where it is an image backup of C: that I do monthly. So, why is the windows update looking in D: instead of C:?

Is there a way to fix this?

Regards, Dean.

***moved from Windows / Windows 10 / Windows update, recovery, and backup***

Answer 1

Hello  DeanHinson，

Thank you for posting in Microsoft Community forum.

This could be due to a misconfiguration or corruption in the system settings. Here are a few steps you can try to resolve this issue:

1. Check Drive Letters:

Ensure that the drive letters haven't been switched or misconfigured. You can do this by going to Disk Management (press Win + X and select Disk Management) and verify the drive letters.

1. Run System File Checker (SFC):

This tool can help fix corrupted system files. Open Command Prompt as an administrator and run the following command:

sfc /scannow

This will scan for and attempt to repair any corrupted files.

1. Run DISM Tool:

The Deployment Imaging Service and Management Tool can help fix Windows image corruption. Open Command Prompt as an administrator and run the following command:

DISM.exe /Online /Cleanup-image /Restorehealth

This will take some time to complete.

1. Check Registry Settings:

Sometimes, the registry might have incorrect paths. Open Registry Editor (regedit) and navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Ensure that the ProgramFilesDir and Windows values point to the correct drive (C:).

1. Windows Update Troubleshooter:

Use the built-in Windows Update Troubleshooter to diagnose and fix update issues. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters, and run the Windows Update troubleshooter.

1. Reinstall WinRE:

If the above steps don't work, you might need to reinstall the Windows Recovery Environment. You can use the Windows Media Creation Tool to create a bootable USB drive and reinstall Windows, which should also reinstall WinRE.

I hope the information above is helpful.

If you have any question or concern, please feel free to let us know.

Best Regards,

Haijian Shan

Answer 2

Hello Haijian,

I tried all except #6. I do not want to re-install windows. I am afraid then I would have to re-install everything else.

After the update failed, the troubleshooter found this, but I cannot make heads/tails what it is trying to tell me...

Windows Update	Publisher details

Issues found
	Check for Windows Update issues<br>Check for Windows Update issues<br>Detects issues related to Windows Update.	Detected
	Resolve Windows Update issues	Completed	<br>	---	---

Potential issues that were checked
Some security settings are missing or have been changedSome security settings are missing or have been changed	Issue not present
Check for missing or corrupt filesCheck for missing or corrupt files	Issue not present
Service registration is missing or corruptService registration is missing or corrupt	Issue not present

Issues found	Detection details

	5	Check for Windows Update issues	Detected		<br>	---	---	---	---
Detects issues related to Windows Update.
		Resolve Windows Update issues	Completed	<br>	---	---		<br>	---	<br>	Resolves common Windows Update issues.	<br>		WaaSMedicService	<br>	---	<br>		Issues remediated by :WinRETargetingPlugin	<br>	---

Potential issues that were checked	Detection details

		Some security settings are missing or have been changed	Issue not present		<br>	---	---	---	---

		Check for missing or corrupt files	Issue not present		<br>	---	---	---	---

		Service registration is missing or corrupt	Issue not present		<br>	---	---	---	---

Detection details
IsPostback_RC_PendingUpdates
---
	IsPostback: False	<br>	---

WaaSMedicService
	Issue found by :WinRETargetingPlugin	<br>	---

IsPostback_RC_PendingUpdates
	IsPostback: True	<br>	---

Service Status
	Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException	<br>	---

Service Status
	Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException	<br>	---

| Collection information | | Computer Name: | DESKTOP-KL9EABT | | --- | --- | | Windows Version: | 10.0 | | --- | --- | | Architecture: | x64 | | --- | --- | | Time: | Tuesday, November 26, 2024 9:38:00 AM | | --- | --- |

Publisher details
Background Intelligent Transfer Service
Find and fix problems that may prevent background downloads from working
Package Version:	3.5
---	---
Publisher:	Microsoft Windows
---	---

| Windows Network Diagnostics | | Detects problems with network connectivity. | | Package Version: | 4.0 | | --- | --- | | Publisher: | Microsoft Windows | | --- | --- |

| Windows Update | | Resolve problems that prevent you from updating Windows. | | Package Version: | 9.3 | | --- | --- | | Publisher: | Microsoft Windows | | --- | --- |

| Windows Update | | Resolve problems that prevent you from updating Windows. | | Package Version: | 9.2 | | --- | --- | | Publisher: | Microsoft Corporation | | --- | --- |

After I deleted the D: drive mapping, the setuperr.log still points to the physical hard drive. harddrive0....

2024-11-26 00:23:36, Error [TiWorker.exe] winreHashWimFile: Failed to hash [\?\GLOBALROOT\device\harddisk0\partition1$WinREAgent\Scratch\update.wim]: 0x3

2024-11-26 00:23:36, Error 0x80070003 in GenerateEncodedHash (base\diagnosis\srt\winreagent\lib\operations\src\verifynewwinrehash.cpp:22): Failed to hash wim file [\?\GLOBALROOT\device\harddisk0\partition1$WinREAgent\Scratch\update.wim][gle=0x00000003]

2024-11-26 00:23:36, Error 0x80070003 in WinREAgent::VerifyNewWinREHash::InternalExecute (base\diagnosis\srt\winreagent\lib\operations\src\verifynewwinrehash.cpp:58): Failed to generate hash of update WinRE[gle=0x00000003]

2024-11-26 00:23:36, Error 0x80070003 in WinREAgent::Operation::Execute (base\diagnosis\srt\winreagent\lib\operations\src\operation.cpp:167): Internal failure to execute operation[gle=0x00000003]

2024-11-26 00:23:36, Error 0x80070003 in WinREAgent::Executor::Commit (base\diagnosis\srt\winreagent\dll\executor.cpp:1356): Failed to execute operation [VerifyNewWinREHash][gle=0x00000003]

2024-11-26 00:23:36, Error 0x80070003 in WinREAgent::WinREServicingManager::Commit (base\diagnosis\srt\winreagent\dll\winreservicingmanager.cpp:526): Failed to commit WinRE servicing[gle=0x00000003]

2024-11-26 00:23:36, Error 0x80070003 in PushButtonReset::Path::AreEqual (base\reset\util\src\filesystem.cpp:805): Failed to get attributes for [\?\GLOBALROOT\device\harddisk0\partition1$WinREAgent\Backup\WinRE.wim][gle=0x00000003]

So, there has to be somewhere where the system has this pointer?

I scanned the registry for winreHashWimFile, but found nothing.

Is there not any other thing I can do?

Regards, Dean.