Main Forum > General Computer Support

Need Help Replacing Corrupted Files Windows 7

<< < (3/5) > >>

sparkyg:
The HDD is a month old. Can't understand the bad block problem-could that be a result of the clonezilla process?. The sfcfixit ran and found nothing. I have attached the text file. I'll try the hdsentinel. Thanks again.

Boggin:
I've never used a clone - much prefer Windows system image, but bad sectors is physical damage and I think you should be enquiring about a RMA for a replacement.

You hadn't knocked or dropped it prior to installing had you, as that can damage a HDD.

I'm not sure where all of those bad signatures have come from unless that was corruption from the failed HDD - perhaps after getting a replacement HDD you should factory reset.

I thought Julian would have come back on those.

Have those commands resolved the not genuine message ?

sparkyg:
I am still having windows validation issues. I searched this weekend on the error code at the bottom of the activation window. error 0x8004fe21. Much of what I find points to a windows update that caused this problem in Windows 7 users.

Per the site

From what I can tell, the KB3004394 update does not install a catalog file on 64-bit windows 7. It does on Windows 8.1 (C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_1_for_KB3004394~31bf3856ad364e35~amd64~~6.3.1.0.cat), so VBox works fine there.

The result of the missing .cat file is that VBox (nor SysInternal's SigCheck.exe for that matter) is not able to verify the authenticity of c:\windows\system32\crypt32.dll and wintrust.dll. If we cannot find any valid signature for the files, we have to assume that they have been tampered with and are forced to abort application loading. These two dlls are important for validating other components, so there is absolutely no way we can ignore this.

Some sites recommend running the MGA Diag tool which I did and have attached. Some point to a problem with a bad set of Intel Rapid Storage Technology drivers and recommend replacing the driver with iata_enu.exe but I don't believe I have that intel Raid driver but might be mistaken

I also found a tool sfcfixit.exe which claims to fix the corrupt files in the sfc scan. I haven't tried that either.

Wanted to check back here and see what you would recommend.

Much thanks

Boggin:
SFCFix.exe had already came back clean just as your sfc /scannow did from the CBS log.

Given all of the bad signatures and that missing .cat file, do you not think the easiest route with this would be to factory reset with the recovery disk ?

Julian:
if you can... try rolling back your chipset drivers and reinstall them it's an issue with intel chipset drivers.

Navigation

[0] Message Index

[#] Next page

[*] Previous page