sfc /scannow not working

zephyr

zephyr

Member
Joined
Jul 27, 2023
Posts
23
I was trying to rebuild my search thumbnail cache so I ran ie4uinit.exe -show. It gave an output that `ie4uinit.exe is not recognized as an internal or external command`
so for this I wanted to do sfc /scannow and I got another failed output which said `Windows Resource Protection could not start the repair service.`

I have tried:
- net start trustedinstaller
- DISM /online /cleanup-image /RestoreHealth
- ICACLS C:Windowswinsxs
- restarted my pc after these but no luck
 
Did you run it in an elevated prompt?

The following is the proper way to delete/reset the icon cache.

Cmd prompt as admin run each cmd separately:-

ie4uinit.exe -show

taskkill /IM explorer.exe /F (your desktop will go blank)

DEL /A /Q "%localappdata%\IconCache.db"

DEL /A /F /Q "%localappdata%\Microsoft\Windows\Explorer\iconcache*"

shutdown /p (your computer will immediately shutdown)

_______________________________________________________________

What was the output after running this? - DISM /online /cleanup-image /RestoreHealth
 
xrobwx71 said:
Did you run it in an elevated prompt?

The following is the proper way to delete/reset the icon cache.

Cmd prompt as admin run each cmd separately:-

ie4uinit.exe -show

taskkill /IM explorer.exe /F (your desktop will go blank)

DEL /A /Q "%localappdata%\IconCache.db"

DEL /A /F /Q "%localappdata%\Microsoft\Windows\Explorer\iconcache*"

shutdown /p (your computer will immediately shutdown)

_______________________________________________________________

What was the output after running this? - DISM /online /cleanup-image /RestoreHealth
Click to expand...
I used "run as admin"
- after running ie4uinit.exe -show the output is

Code: 
`'ie4uinit.exe' is not recognized as an internal or external command,
  operable program or batch file.`

After running DISM /online /cleanup-image /RestoreHealth, my output is
Code: 
C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth


Deployment Image Servicing and Management tool
Version: 10.0.18362.900


Image Version: 10.0.18362.1082


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

However running sfc /scannow doesnt work after DISM
 
Try to run SFC in Safe mode. Still the same error?
 
@DR M nope it doesnt work. I have researched it a lot and I think my windows recovery tools got corrupted. winsxs folder probably.
I cant even use usb media tool to repair my windows.
I cant update windows through settings.
 
How did that start? Any possibility for a malware infection?
 
No, but probably because power outage, idk since when it was corrupt because sfc didn't work for quite a while and i didn't think much of it
 
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running sfc /scannow 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.
j8MhY5V.png

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.
 
Thanks, could you please provide the CBS log(s) as well? They should be available in the following directory:

Code: 
%systemroot%\Logs\CBS

Additionally, please run the following FRST script and then provide the output in your next post:

FRST Script
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.
 

Attachments

Thanks, could you please provide the CBS logs as well? Please include the .cab files which are marked as persist.

If you're unsure what %systemroot% maps to, then it is C:\Windows\.
 
zephyr said:
Idk where the cab files are
Click to expand...
They're in the same directory which you copied the CBS.log file from, they'll have "persist" in their name, just copy all the files from C:\Windows\Logs\CBS into a .zip file and if there was only the CBS.log which you've attached then don't worry about it.

Additionally, please run the following command from command prompt and then post the output in your next post:

Code: 
dir %systemroot%\Logs\CBS
 
There is no persist file in my cbs folder. There is only CBS.log and FilterList.log

as for the output from the cmd
Code: 
C:\Windows\system32>dir %systemroot%\Logs\CBS
 Volume in drive C has no label.
 Volume Serial Number is 563F-56A8


 Directory of C:\Windows\Logs\CBS


27-Jul-23  06:02 PM    <DIR>          .
27-Jul-23  06:02 PM    <DIR>          ..
01-Aug-23  07:16 PM        14,114,525 CBS.log
27-Jul-23  06:02 PM               814 FilterList.log
               2 File(s)     14,115,339 bytes
               2 Dir(s)  83,380,305,920 bytes free
 
In addition to the previous posts, could you please run FRST again as described in post #12 to provide some more information to look at:

1. Run FRST with the attached fixlist.txt.
2. When the Fixlog is created, click OK and then press the Scan button to perform a regular scan.

Attach the following files: Fixog.txt, FRST.txt and Addition.txt to your next post.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top