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

[tjg79]

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

 

[Hacb]

well, try an older restore point after backing up your data in case you lose things by going back, if that fails you have a hardware issue, not a software one.

 

[tjg79]

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.

 

[Brds7t7]

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.

 

[tjg79]

I wasn't having any issues prior to a system lockup or freeze when running imgburn to burn a DVD. I depressed the reset button to restart. Then I notice the boot was a bit slower, so I ran SFC and it detected problems that it couldn't fix. My first effort was a restore point, then SFC to see if the issue was fixed; it wasn't. Then, a boot into the repair screen and multiple runs of SFC /scannow /offbootdir /offwindir, and another restore point, but the issue wasn't resolved. I've run chkdsk on the last boot and then SFC again, I've still got problems that SFC can't fix.

Regards

View attachment 374565

 

[Brds7t7]

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.

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[tjg79]

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

  Found: {l:32 b:Zhx4K9vYIH3fjOGilmvdV/75uGpmwTWhDYwAFBH92YA=} Expected: {l:32 b:qvSLV3iF03pjYE4B1RkMHzZwW14mxCMavuQuhvEe3rA=}
2015-10-27 11:25:27, Info                  CSI    00000356 [SR] [B]Cannot repair member file [l:24{12}]"aitagent.exe"[/B] 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] [B]Cannot repair member file [l:24{12}]"aitagent.exe" of Microsoft-Windows-Application-Experience-Application-Telemetry-Agent[/B], 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] [B]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[/B]
2015-10-27 11:25:28, Info                  CSI    0000035d Repair results created:

 

[Brds7t7]

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.

 

[tjg79]

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.

http://www.sevenforums.com/tutorials/3413-repair-install.html

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

 

[Brds7t7]

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.

http://www.sevenforums.com/tutorials/3413-repair-install.html

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.

 

[tjg79]

I loaded an old image into vhd and copied the aitagent.exe file, booted to the repair cmd prompt, renamed the original file with the ".old" ext and copied the new file from the old image into the /system32 folder. It appeared to clean up some of the errors, but not to the point that I get a good SFC result.

The only installs I do at this point are clean installs.