New
#430
well, I just ran it again, it said Windows Resource Protection didn't find any integrity violations. Is it still plausible to run it to detect errors?
well, I just ran it again, it said Windows Resource Protection didn't find any integrity violations. Is it still plausible to run it to detect errors?
...Hello friends....
...Can someone help me to understand..., when I "run" sfc /scannow, in cbs.log, I found "thousand" of:
-Move File: Source = [....] "\SystemRoot\WinSxS\Temp\PendingRenames\...........cdf-ms", Destination = ......-
..what it means (about..), after the procedure (scannow), everything will be o.k.? is it a critical problem?
....Thanks for informations ..(if any or not..)
Hello Brink and thank you..
I didn't want to "bother" you, for a deep analyse...because soon (hoping..), I'll clean install...
But, very often (maybe always!) I see in cbs.log this "event" of -Move file....Destination...
...and I wanted to learn "at least"..what is about...Also I am sure other people have the same question...
...So I post the cbs.log where I see this procedure...and I attach also the sfcdetail.txt you asked, where..(surprise!)
...is just ONE!..only repair....I'm very interested to get any information...about..
Thanks again...
Attachment 258089 sfcdetails.txt
notis,
The SFC log shows that it found the file below corrupted. It was able to repair it, so you're all good. :)
C:\Windows\System32\lpremove.exeThat file is for MUI Language pack cleanup.
Thank you Brink.
....thanks for your patience too...
when I opened the file sfcdetails.txt in notepad it was empty, is that right?2. In the elevated command prompt, copy and paste the command below, and press Enter. (See screenshot below)
NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it.