Problem with wifes notebook ;-)

[frankhaas]

hi, i have problems to update my wifes notebook for months
i tried sfc /scannow and dism ... (for more times) - but it ended with dism error 126.

i have the same error with another notebook, but this will be another thread.

THX for your help!

 

[frankhaas]

:-(

no idea? or is it not to solve?


thx!

 

[philc43]

Hello frankhaas

Thank you for your patience as we work through the various threads. We are all volunteers and work in our spare time.

Please can you zip up the complete CBS folder as instructed in step 4 of the posting instructions.

Thanks!

 

[frankhaas]

thx so much! i'm patient, but i really thought, it might be not to solve.

in the cbs-log-folder is just the cbs.log file. nothing else. (cbs.zip in post1).
if you need more - please tell me.

 

[philc43]

Do you have a cleaner program which is deleting log files? I would have expected more files with history going back further in time.

Please try and repeat the steps to rerun SFC and DISM in the posting instructions and then resubmit a new CBS folder.

 

[frankhaas]

maybe i cleaned the log directory when i started with this thread. i repeated the steps with sfc and dism (dism had error 126) - i zipped the whole log-directory (with cbs and dism and windows update ...)

thx for your help - and take as much time as you need. i'm not in hurry.

 

[philc43]

Hello frankhaas,

I've looked through the logs and can see that there are a number of files that could not be repaired.

2022-11-09 13:41:51, Info                  CSI    00000238 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1411, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    00000239 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.1411, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023a [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.1411, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023b [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1411, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023c [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023d [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023e [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1440, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2022-11-09 13:41:51, Info                  CSI    0000023f [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1411, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked

I have created a fix for these which you can apply by following the steps below:

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.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Attach the contents of this file into your next post for me to analyse please.

Afterwards please rerun steps 1, 2 and 4 from the posting instructions.

 

[frankhaas]

thanks for your help - but it seems we aren't where we want to be.
logs attached...
dism still error 126

 

[frankhaas]

oops - i forgot the sfcfix.txt

 

[philc43]

That SFCFix.txt file does not show the expected result. Did you drag the zip file over the exe file as instructed in step 5?

Please repeat the instructions in post #7

Thanks

 

[frankhaas]

uaaa - i'm such a fool - i upped the wrong log-file ... sorry for that. (a log when i started sfcfix.exe without script-file)

the right one attached. thanks for your patience with me.

 

[Maxstar]

Hi,

Please run DISM again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the DISM command.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) 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 the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.

 

[frankhaas]

thx so much for your help!

here is the wetransfer-link:

Logfile.zip

 

[Maxstar]

Which of the following messages do you see after running DISM?

Error: 126 The driver store for the image could not be opened.
Error: 126 The specified module could not be found.

 

[frankhaas]

it's in german - which means: dism couldn't be initialized in the local folder

 

[Maxstar]

Please do the following to check a file.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

 

[frankhaas]

here is sfcfix-log, unfortunately not better :-(

 

[Maxstar]

The last script was only a file scan.

Open an elevated commandprompt and run the following commands. Copy and paste the result in your next post.

certutil -hashfile "%systemroot%\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.18362.1316_none_38cd7dd38da2984c\DismProv.dll" SHA256
certutil -hashfile "%systemroot%\System32\Dism\DismProv.dll" SHA256

 

[frankhaas]

C:\WINDOWS\system32>certutil -hashfile "%systemroot%\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.18362.1316_none_38cd7dd38da2984c\DismProv.dll" SHA256
SHA256-Hash von C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..ing-management-core_31bf3856ad364e35_10.0.18362.1316_none_38cd7dd38da2984c\DismProv.dll:
53adc268be41f3f779a4e7776deb72d7b464eff40e2f76dd0cdc4c2f38033bfb
CertUtil: -hashfile-Befehl wurde erfolgreich ausgeführt.

C:\WINDOWS\system32>certutil -hashfile "%systemroot%\System32\Dism\DismProv.dll" SHA256
SHA256-Hash von C:\WINDOWS\System32\Dism\DismProv.dll:
53adc268be41f3f779a4e7776deb72d7b464eff40e2f76dd0cdc4c2f38033bfb
CertUtil: -hashfile-Befehl wurde erfolgreich ausgeführt.

 

[Maxstar]

Hi,

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.

dir /s /a %systemroot%\System32\Dism > "%userprofile%\Desktop\Dirlist.txt"