Solved How acurate is create restore?.

[skipper84]

Hi. how accurate is windows restore?. I done a fresh install again this morning. After I formatted and got onto the desktop first time I created a restore point. I installed mother board drivers. Created another restore point. I did sfc/scannow in the command system and no violations where found. I then made another restore point and installed the updates every time doing a create restore point. I did this this on every bunch of updates I did including optional. I also did sfc/scanow on all. Everything went fine until I installed Microsoft silver light and did the scannow in the command system where it said violations where found. I did a complete restore to just be for I installed Microsoft silver light and restarted PC and did scannow. The violation was gone. I installed Microsoft silver light again threw updates and this time was fine and no violation or corrupted files where found like the first time. But how accurate is windows restore and why you think it found corrupted violation files in first place?. Thanks.

 

[NoelDP]

System restore is pretty much 100% accurate - or it doesn't work at all. Bear in mind that it doesn't monitor or back up all changes made (mostly, it totally ignores user data).

As far as SFC is concerned, that is also pretty much 100% accurate - it usually does fault detection a second time on found problems.
Without seeing the relevant CBS data from the failing scan, I couldn't comment on potential causes, but the usual suspects are

failing hardware
power outages/spikes
user error
bad update
'others'

 

[skipper84]

I got the CBS log does this contain personal info as I would put it up here in a wrap code #

but it does look like a windows update problem.

 

[NoelDP]

There's no confidential data in the CBS logs - or any of the files in the Logs folder, so far as I know.

Copy the whole CBS folder (in C:\Windows\Logs) to the desktop, and zip it up then attach it to your reply, or upload it to a fileshare site and post a link

 

[skipper84]

File

 

[NoelDP]

There are no errors in any of the 3 SFC scans in that file - perhaps it's in the latest CBSPersist file?

 

[skipper84]

What does this mean then.

015-05-24 16:47:04, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

Its got that in quite a places in the text.

 

[NoelDP]

It's very common - and simply means (so far as I've been able to work out) that the file is no longer present in the WU downloads folder. It can be ignored.

 

[skipper84]

Thanks. Thought it was big problem with a lot of failed in the log and corrupted files in the scannow command. thanks again.