Corrupted files lingering after BSOD fix

[merkelsworld]

Hi there! Hope this is the right thread to discuss this in. Just recently had a BSOD "Critical_Service_Failed", and I was able to fix it, thankfully. Just to be safe though, I ran SFC/scannow, and it gave me the following error message:

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I've attached the CBS log file below. I've tried reading it through myself but I'm really not an expert with these things. This was my first time experiencing a BSOD, and my first time using command prompt as well. So I can't make heads or tails of the log file. And I'm worried that these lingering corrupted files might cause future issues, or another BSOD.

I did notice however, this line in the log...

CSI 00000061 [SR] Cannot repair member file [l:15]'bootmgr.efi.mui' of Microsoft-Windows-BootEnvironment-Core-BootManager-EFI.Resources, version 10.0.19041.4648, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

Could that be it?

Thanks so much to whoever might be able to help!

 

[x BlueRobot]

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.

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. 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 sfc /scannow again and please post the latest CBS log if it fails.

 

[merkelsworld]

Hi sorry for the delay in getting back to you. I've been out of town for a bit and away from my PC. I followed the steps and ran a SFC /scannow just in case, and it seems the CBS log came back positive, that it found corrupt files and was able to fix them.

This should have resolved the issue, I assume, and there's nothing more I should do?

If so, thanks so much!

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-11-03 13:33:27.975
Microsoft Windows 10 Build 19045 - amd64
Using .zip script file at C:\Users\Angela\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_10.0.19041.4597_none_25bed63d48f3eb95\DismApi.dll
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.19041.4648_nl-nl_ac7c519f2748a86c

Successfully copied file C:\Users\Angela\AppData\Local\niemiro\Archive\wow64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_10.0.19041.4597_none_25bed63d48f3eb95\DismApi.dll to C:\WINDOWS\WinSxS\wow64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_10.0.19041.4597_none_25bed63d48f3eb95\DismApi.dll.
Successfully copied file C:\Users\Angela\AppData\Local\niemiro\Archive\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.19041.4648_nl-nl_ac7c519f2748a86c\bootmgr.efi.mui to C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.19041.4648_nl-nl_ac7c519f2748a86c\bootmgr.efi.mui.

Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_10.0.19041.4597_none_25bed63d48f3eb95\DismApi.dll
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_microsoft-windows-d..cing-management-api_31bf3856ad364e35_10.0.19041.4597_none_25bed63d48f3eb95\DismApi.dll
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.19041.4648_nl-nl_ac7c519f2748a86c
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.19041.4648_nl-nl_ac7c519f2748a86c
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2024-11-03 13:33:28.581
Script hash: kzLdOsx9jLs82sTFT10z7WXTMMV5Mq/Ev7WV4k6/iQ4=
----------------------EOF-----------------------

 

[x BlueRobot]

This should have resolved the issue, I assume, and there's nothing more I should do?

It should have, do you mind running SFC and DISM again just to confirm?