[SOLVED] Win 10 update not working

jack99 · Apr 15, 2022

Hello,
I came across this forum in the hope that someone might be able to help me before I have to reinstall win 10.
I am having trouble updating win 10 to win 11. I have tried through the win updater as well as the media creation tool but to no avail.
I have also tried the sfc scan which shows all is well while the DISM scan shows error 2.
After running the component scanner and sfcfix programs, I am attaching their log files here.

I have been searching on the web for fixes but none have worked so far.

Would be nice if someone can help me with this as this seems to be a helpful forum.

Thanks in advance.

P.S windows is able to install other updates through the updater, it is only with the win 11 that it is not working.

x BlueRobot · Apr 20, 2022

Could you please provide your WindowsUpdate.log using the instructions from this thread - Troubleshooting Windows Update Log Errors

jack99 · Apr 20, 2022

Hello,

thanks for the reply.
here it is.

x BlueRobot · Apr 20, 2022

Rich (BB code):

2022/04/20 14:34:19.8135819 5316  984   Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
2022/04/20 14:34:19.8135879 5316  984   Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
2022/04/20 14:34:19.8136643 5316  984   EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 743468BA-A535-48E1-B4EE-4859BD8DE51C.1, idExpr=57
2022/04/20 14:34:19.8136700 5316  984   Agent           *FAILED* [80070032] Evaluate Installed rule, updateId = {{743468BA-A535-48E1-B4EE-4859BD8DE51C}.1}
2022/04/20 14:34:19.8150547 5316  984   Handler         *FAILED* [80070032] Method failed [AppxPackage::Initialize:232]
2022/04/20 14:34:19.8150598 5316  984   Handler         *FAILED* [80070032] Method failed [AppxApplicabilityData::Initialize:549]
2022/04/20 14:34:19.8151282 5316  984   EEHandler       *FAILED* [80070032] EvaluateManifestBasedRule failed for update 743468BA-A535-48E1-B4EE-4859BD8DE51C.1, idExpr=56
2022/04/20 14:34:19.8151341 5316  984   Agent           *FAILED* [80070032] Evaluate Installable rule, updateId = {{743468BA-A535-48E1-B4EE-4859BD8DE51C}.1}

There appears to be lots of request not supported errors in your Windows Update log and unable to connect to the network errors. Are you running any third-party firewalls or security programs?

jack99 · Apr 20, 2022

No, none whatsoever. Just the default windows firewall.

x BlueRobot · Apr 20, 2022

Let's ensure that your Windows Firewall is set to its default settings, with the following command from an elevated command prompt:

Rich (BB code):

netsh advfirewall reset

In addition, from an elevated command prompt, please enter the following in succession:

Rich (BB code):

Net Start bits
Net Start wuauserv
Net Start appidsvc
Net Start cryptsvc

jack99 · Apr 21, 2022

Alright did that. Appidsvc was started. Tried the update afterwards but it failed at around 70%.

x BlueRobot · Apr 21, 2022

Could you please provide a fresh Windows Update log?

jack99 · Apr 21, 2022

I tried updating again and it went to around 88% I think and then gave the same error as above. Attaching the log.

x BlueRobot · Apr 21, 2022

Rich (BB code):

2022/04/21 22:02:40.1183293 11732 2776  Handler         Using the update's service stack dll file 'C:\WINDOWS\SoftwareDistribution\Download\ee7bcc7d812eebbcc2ea3f4a52fa80ea\Metadata\UpdateAgent.dll' 
2022/04/21 22:02:40.8207206 11732 2776  WIL             *FAILED* [8007139F] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\helper\osdeploymenthelper.cpp, line = 777
2022/04/21 22:02:40.8207239 11732 2776  WIL             *FAILED* [8007139F] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\installer\osinstaller.cpp, line = 651
2022/04/21 22:02:40.8225942 11732 2776  WIL             *FAILED* [8007139F] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\handler\uhosdeployment.cpp, line = 634
2022/04/21 22:02:40.8293637 11732 2776  WIL             *FAILED* [8007139F] file = onecore\enduser\windowsupdate\client\engine\agent\updatemanager.cpp, line = 13873
2022/04/21 22:02:40.8295168 16260 15260 ComApi          *FAILED* [8007139F] ISusInternal:: IsCommitRequired

Looks like it failed on a different error code this time.

ERROR_INVALID_STATE winerror.h
# The group or resource is not in the correct state to
# perform the requested operation.

Could you please run the following command from an elevated command prompt again:

Rich (BB code):

DISM /Online /Cleanup-Image /RestoreHealth

Please provide the CBS log, along with, the DISM log as well.

jack99 · Apr 21, 2022

Some update.
I deleted the software distribution folder + started in clean boot mode and tried to run windows update again in the hope that it might work but no luck. I also tried the windows installation agent but it gives error about not having permission to write to the installation folder.
I am attaching the windows update log, the CBS log and running DISM throws error 2, log attached as well.

x BlueRobot · Apr 22, 2022

Rich (BB code):

2022-04-21 23:54:19, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.19043, Running architecture=amd64, Number of processors=16
2022-04-21 23:54:19, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.19041.844
2022-04-21 23:54:19, Info                  DISM   DISM.EXE: Executing command line: DISM  /Online /Cleanup-Image /RestoreHealth
2022-04-21 23:54:19, Info                  DISM   DISM Provider Store: PID=15840 TID=15880 Connecting to the provider located at C:\WINDOWS\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2022-04-21 23:54:19, Info                  DISM   DISM Manager: PID=15840 TID=15880 physical location path: C:\ - CDISMManager::CreateImageSession
2022-04-21 23:54:19, Info                  DISM   DISM Manager: PID=15840 TID=15880 Event name for current DISM session is Global\{D5A8C168-AFAC-4FE1-A1A5-95A24B9EDE01} - CDISMManager::CheckSessionAndLock
2022-04-21 23:54:19, Info                  DISM   DISM Manager: PID=15840 TID=15880 Create session event 0x210 for current DISM session and event name is Global\{D5A8C168-AFAC-4FE1-A1A5-95A24B9EDE01}  - CDISMManager::CheckSessionAndLock
2022-04-21 23:54:19, Info                  DISM   DISM Manager: PID=15840 TID=15880 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2022-04-21 23:54:19, Error                 DISM   DismHostLib: Failed to create dismhost.exe servicing process.
2022-04-21 23:54:19, Error                 DISM   DISM Manager: PID=15840 TID=15880 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0x80070002)
2022-04-21 23:54:19, Warning               DISM   DISM Manager: PID=15840 TID=15880 A problem ocurred loading the image session. Retrying...  - CDISMManager::CreateImageSession(hr:0x80070002)
2022-04-21 23:54:19, Info                  DISM   DISM Manager: PID=15840 TID=15880 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2022-04-21 23:54:19, Error                 DISM   DismHostLib: Failed to create dismhost.exe servicing process.
2022-04-21 23:54:19, Error                 DISM   DISM Manager: PID=15840 TID=15880 Failed to create Dism Image Session in host. - CDISMManager::LoadRemoteImageSession(hr:0x80070002)
2022-04-21 23:54:19, Error                 DISM   DISM Manager: PID=15840 TID=15880 Failed to load the image session from the temporary location: C:\Users\asadz\AppData\Local\Temp\DCB76004-2994-48E9-8223-14D0E7417967 - CDISMManager::CreateImageSession(hr:0x80070002)
2022-04-21 23:54:19, Error                 DISM   DISM.EXE: Could not load the image session. HRESULT=80070002
2022-04-21 23:54:19, Error                 DISM   DISM.EXE: Unable to start the servicing process for the image at 'C:\'. HRESULT=80070002

Let's ensure that DISM hasn't become corrupt. Could you please run SFCFix using the following instructions:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, please run the following command from an elevated command prompt:

Rich (BB code):

sfc /scannow

Once complete, could you please try the same DISM command as before but with a Process Monitor trace running, please see the instructions below on how to do so:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Please run DISM /Online /Cleanup-Image /RestoreHealth just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.

jack99 · Apr 22, 2022

Here it is.

Link for the procmon and cbs log file.
https://umeauniversity-my.sharepoin...9CnCyR46MHcDMBF9bQsSKlicihr9s3EW62XQ?e=qidhi3

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-22 13:14:12.200
Microsoft Windows 10 Build 19043 - amd64
Using .zip script file at C:\Users\asadz\OneDrive - Umeå universitet\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe

Successfully copied file C:\Users\asadz\AppData\Local\niemiro\Archive\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe.

Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2022-04-22 13:14:13.741
Script hash: w0J1dFGa8ZSCTbC4RwwbD1KV84OPTIMxBATVRZLyu2I=
----------------------EOF-----------------------

x BlueRobot · Apr 22, 2022

Thanks, could you please open an elevated command prompt and then enter the following command:

Code:

fsutil hardlink list C:\WINDOWS\System32\Dism\DismHost.exe

Please post the output of the command.

Additionally, please run the attached FRST64 script:

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.

jack99 · Apr 22, 2022

First command output

Code:

Microsoft Windows [Version 10.0.19043.1645]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>fsutil hardlink list C:\WINDOWS\System32\Dism\DismHost.exe
\Windows\System32\Dism\DismHost.exe
\Windows\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.19041.746_none_092d70d1898e5ff9\DismHost.exe

C:\WINDOWS\system32>

Fixlog output

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 22-04-2022
Ran by Asad (22-04-2022 16:44:49) Run:1
Running from C:\Users\asadz\OneDrive - Umeå universitet\Desktop
Loaded Profiles: Asad
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
[-HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dismHost.exe]
*****************

Restore point was successfully created.
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\dismHost.exe => removed successfully

==== End of Fixlog 16:44:50 ====

x BlueRobot · Apr 22, 2022

Thanks, could you please try DISM again?

jack99 · Apr 22, 2022

Code:

Microsoft Windows [Version 10.0.19043.1645]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1645

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Alright, seems to work. Should I try to update or?

x BlueRobot · Apr 22, 2022

Yes, please do.

jack99 · Apr 22, 2022

Thank you and your team for your help. It updated without any hitches. Now running windows 11. Please have a cup of coffee(a small donation) on me.

x BlueRobot · Apr 22, 2022

Thank you very much and glad you were able to update with no issues now.

[SOLVED] Win 10 update not working

Contributor

Attachments

Administrator

Contributor

Attachments

Administrator

Contributor

Administrator

Contributor

Attachments

Administrator

Contributor

Attachments

Administrator

Contributor

Attachments

Administrator

Attachments

Contributor

Administrator

Attachments

Contributor

Administrator

Contributor

Administrator

Contributor

Administrator