HP_RECOVERY access -- Reading files from HP_RECOVERY

[keepplugging]

Using Windows 7 Home Premium 64-bit SP1

HP machine: not relevant (motherboard replaced)

sfc (System File Checker) complained "Hashes for file member <blah>.dll do not match actual file <blah>.dll" and "Could not reproject corrupted file <blah>.dll; source file in store is also corrupted"

I assume the corrupted files are in the HP_RECOVERY partition.

Is it possible for me to retrieve particular files from the HP_RECOVERY partition or the recovery discs?

[MKazi · Accepted solution]

@keepplugging

Thanks for reaching out to us on HP Support Forums. 🙂 I came across your post and would like to help.

I understand that you have an HP Pavilion p7-1370t Desktop PC and the System File Checker complained "Hashes for file member <blah>.dll do not match actual file <blah>.dll" and "Could not reproject corrupted file <blah>.dll; source file in store is also corrupted." I understand that you would like to know if you could retrieve particular files from the HP_RECOVERY partition or the recovery discs.

I would like to know if any other changes (apart from motherboard replacement, either hardware or software) took place on the laptop after which this issue may have started. Also, if the motherboard was replaced by HP or somewhere else. Because the operation system is tattooed to the motherboard in an HP computer.

I would like to mention that such specific files cannot be retrieved from the recovery partition or the recovery disks. 

However, if this issue started recently, then you could perform a system restore to the operating system to an earlier date when everything worked fine. If system restore does not help then you may try to reinstall Windows and that will erase all information. So it's better to backup the data before reinstalling Windows.

I hope this information helps. Feel free to let me know if you have any questions. Cheers! 

[keepplugging]

I had a local computer store replace the original Foxconn motherboard with an Asus.  At the time, I did not know how tightly entangled the OS and the motherboard are.  "Tattooed" is a good term for it!

The files about which sfc complained were modified before 2012, so either something corrupted them after that time, or the files in system32 did not match the files in winsxs originally.

Anyhow, my system is running.

Advice to others: immediately upon a new Windows installation, or immediately upon acquiring a machine with the OS pre-installed, backup all files, and run sfc.

(Aside: I replaced the motherboard because when I tried to "upgrade" to Windows 10, the result was a bricked motherboard.  Web-search for "windows 10 brick".)