System Restore - 1st Try Didn't Fix, Repeat the Operation or Undo 1st?

What's the best practice if a System Restore operation doesn't fix the problem on the first try? Should I undo the System Restore operation and then try a different restore point or just try a different restore point?

The system recommended the most recent restore point, so I took that recommendation. But, although the system indicated that the System Restore operation was successful, SFC indicated otherwise.

I've got a few more older restore points. Should I give System Restore another shot, with an older restore point or do what?

Regards

I don't think it's hardware. I think it's corrupted files that System Restore isn't fixing. I've gone back to the next previous restore point and I got the same response from SFC. SFC found corrupted files that it couldn't repair and made entries into the CBS log. I ran SFC /scannow /offbootdir /offwindir from the boot-from-the- distribution-dvd, repair menu, cmd prompt window multiple times. That's where I performed the second System Restore operation. I'm at the point to where I'm going to attempt to identify the corrupted files from the CBS log and attempt to restore them from an old image.

tjg79 said:

I don't think it's hardware. I think it's corrupted files that System Restore isn't fixing. I've gone back to the next previous restore point and I got the same response from SFC. SFC found corrupted files that it couldn't repair and made entries into the CBS log. I ran SFC /scannow /offbootdir /offwindir from the boot-from-the- distribution-dvd, repair menu, cmd prompt window multiple times. That's where I performed the second System Restore operation. I'm at the point to where I'm going to attempt to identify the corrupted files from the CBS log and attempt to restore them from an old image.

What problems were you having before you ran SFC? System restore can only repair those files if you have a restore point taken before the files were changed/deleted/corrupted.
There are a few things that can cause that error in SFC.
Have you patched any files eg theme files to use a 3rd party theme? UX theme patcher and similar utilities can cause this.

Those CBS logs just give me a headache
One thing you could try is a repair Install/in-place upgrade. This can fix most issues within Windows when the install is corrupted.

Repair Install

From my review of the CBS log, it appears the aitagent.exe file, found in the C:\Windows\System32 folder is corrupted and the copy in the store is corrupted as well.

Can this file be restored individually from either the distribution DVD or an old image?

Regards

Code:

  Found: {l:32 b:Zhx4K9vYIH3fjOGilmvdV/75uGpmwTWhDYwAFBH92YA=} Expected: {l:32 b:qvSLV3iF03pjYE4B1RkMHzZwW14mxCMavuQuhvEe3rA=}
2015-10-27 11:25:27, Info                  CSI    00000356 [SR] Cannot repair member file [l:24{12}]"aitagent.exe" of Microsoft-Windows-Application-Experience-Application-Telemetry-Agent, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-27 11:25:27, Info                  CSI    00000357 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-a..ion-telemetry-agent_31bf3856ad364e35_6.1.7601.17514_none_3092574c7d41010b\aitagent.exe do not match actual file [l:24{12}]"aitagent.exe" :
  Found: {l:32 b:Zhx4K9vYIH3fjOGilmvdV/75uGpmwTWhDYwAFBH92YA=} Expected: {l:32 b:qvSLV3iF03pjYE4B1RkMHzZwW14mxCMavuQuhvEe3rA=}
2015-10-27 11:25:27, Info                  CSI    00000358 [SR] Cannot repair member file [l:24{12}]"aitagent.exe" of Microsoft-Windows-Application-Experience-Application-Telemetry-Agent, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-27 11:25:27, Info                  CSI    00000359 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2015-10-27 11:25:27, Info                  CSI    0000035a Hashes for file member \??\C:\Windows\System32\aitagent.exe do not match actual file [l:24{12}]"aitagent.exe" :
  Found: {l:32 b:Zhx4K9vYIH3fjOGilmvdV/75uGpmwTWhDYwAFBH92YA=} Expected: {l:32 b:qvSLV3iF03pjYE4B1RkMHzZwW14mxCMavuQuhvEe3rA=}
2015-10-27 11:25:27, Info                  CSI    0000035b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-a..ion-telemetry-agent_31bf3856ad364e35_6.1.7601.17514_none_3092574c7d41010b\aitagent.exe do not match actual file [l:24{12}]"aitagent.exe" :
  Found: {l:32 b:Zhx4K9vYIH3fjOGilmvdV/75uGpmwTWhDYwAFBH92YA=} Expected: {l:32 b:qvSLV3iF03pjYE4B1RkMHzZwW14mxCMavuQuhvEe3rA=}
2015-10-27 11:25:27, Info                  CSI    0000035c [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"aitagent.exe"; source file in store is also corrupted
2015-10-27 11:25:28, Info                  CSI    0000035d Repair results created:

Aitagent is something to do with Customer Experience Improvement. You should be able to get those files from your original disc. Take a full backup/system image before tampering with the files.

Brds7t7 said:

Those CBS logs just give me a headache
One thing you could try is a repair Install/in-place upgrade. This can fix most issues within Windows when the install is corrupted.

Repair Install

Repair installs are then followed by download all updates. It's not that much more of an effort to do a clean install.

From what I can see in the CBS log, only one file is corrupted, aitagent.exe, and the copy in the store is corrupted as well.

I would think it's worth the effort to try to restore this one file from either an old image or the distribution DVD.

Is there anyone here that knows how to do that?

Regards

tjg79 said:

Brds7t7 said:

Those CBS logs just give me a headache
One thing you could try is a repair Install/in-place upgrade. This can fix most issues within Windows when the install is corrupted.

Repair Install

Repair installs are then followed by download all updates. It's not that much more of an effort to do a clean install.

From what I can see in the CBS log, only one file is corrupted, aitagent.exe, and the copy in the store is corrupted as well.

I would think it's worth the effort to try to restore this one file from either an old image or the distribution DVD.

Is there anyone here that knows how to do that?

Regards

Repair installs are a lot easier than clean installs. They keep your programs, accounts, settings intact.

Anyway, you should be able to just copy the files from the DVD. If you have an old image you can restore from that. You would need to attach the vhd in disk management and copy the file.

You can also restore just that file by right-clicking on it and selecting "Restore Previous Versions". Provided you have enough shadow copies that go far enough back to before the file was corrupted.