Vista Tutorial - System Files - SFC Command

I do believe sir, that this makes you da man! Thanks so much.

LOL, you're welcome Fishman.

Hi!

Yesterday I installed Vista SP2, but crashed during the reboot. After getting up again, Windows now says it is SP2, but I wanted to make sure that all system files are ok. So I ran SFC /verifyall, and no integrity violations were found, so far so good. When I create the sfcdetails.txt file to show only the [SR] lines from the CBS.log, still no anomalies are found. So everything looks okay!

But when I look in the CBS.log, nonetheless some non-empty POQ entries are created. It looks like there are only 3 kinds of created lines:
- Move File (a lot of PendingRenames in winsxs folder)
- Set File Information (for various files, but always attributes 000080)
- Set Key Value (in registry, for sysprep node, e.g. cleanup and generalize values)
In total there are about 1350 of such numbered items.

What could be the reason for this, and why are those lines created? And what should I do? Since Windows thinks it has SP2 installed and everything is uptodate, I don't want to fix what is not broken, so I don't want to let SFC actually repair things. Can I just let it be? Or will I have problems with future windows updates?

Thanks for your help in advance!

Kind greetings,
Jeroen

Hello Jeroen, and welcome to Vista Forums.

Since you SFC did not find anything wrong, I would not worry about it. I'm not certain what the lines are for, but it appears that it may just be some pending actions that will be done apon the next restart of the computer. You should be fine.

Shawn

Hello Brink,

Thank you for your fast response!

Those lines were created because I did SFC /verifyall (not a real /scannow), so I DON'T think they are in any queue, waiting to be executed. So I DON'T think they will be executed on the next restart?

But I DO keep wondering WHEN these lines eventually will come up. WHEN will be the next time a process (like Windows Update) does the real /scannow thing? Because THEN all of these lines MAY come up. And even for a very small future update, if ALL those lines will ALSO be generated at that time, THAT will be a MAJOR task. And when an update has got to do a thousand things, I'm not pretty sure all will go well.

So I'll keep worrying a bit for some time, in spite of your advice

Kind greetings,
Jeroen

Yeah, thanks!

Now are working fine my windows update...

You're welcome Hsfx, and welcome to Vista Forums.

Shawn

Hi Brink! I just wanted to say, thank you! That information was absolutely spot on and fixed my system. I had been staring at the Vista DVD dreading a full reinstall, but the sfc scannow command worked beautifully! There were a few file it could not repair ("user32" something) but it doesn't seem to matter.

Thank you again for the tutorial!!!

You're most welcome Cerebus, and welcome to Vista Forums.

Shawn

Hi JohnLug,

Windows Mail is an e-mail client like outlook but with less features as compared with that of outlook. However, windows mail is an integral part of the operating system(vista) whereas outlook is part of Microsoft Office suite. so, when you perform a repair installation the files of windows mail will be replaced since it a part of the windows operating system and outlook would remain the same. Inplace upgrade would make the necessary changes to the files of the windows folder only in the root drive.
So, outlook settings would remain the same. However you should always backup anything you do not want to lose just in case something goes wrong as mentioned by Shawn.



Anand