Checksum error, file possibly corrupt

Stubnortz

Commendable
Oct 15, 2016
5
0
1,510
Hi All, thanks in advance for your help!

When I turned my computer on this morning I was welcomed with the following error in white text on a black screen:

The file is possibly corrupt. The file header checksum does not match the computed checksum.

I tried booting into the BIOS but no matter what key I tap I get this error message. I searched the forums and saw various solutions to this error message but it seemed all solutions involved booting into the BIOS.

My system is here:

I would be incredibly grateful for your help!
 
You need to be able to get into bios to bypass this error, the link you added doesn't work so what motherboard do you have so we can see what key to hold down before starting PC

On another PC, download the Windows 10 media creation tool and use it to make a win 10 installer on USB
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
open command prompt
type chkdsk /f and press enter - hopefully this will fix problem
http://www.tenforums.com/general-support/50344-file-possibly-corrupt-file-header-checksum-does-not-match-t.html
 
Hi, I did this and got an error in the command window saying "The type of the file system is NTFS. Cannot lock current drive. Windows cannot run disk checking on this volume because it is write protected."

I then ran the check disk without the fix option and got the following:

"Stage 3: Examining security descriptors. 7 data files processed. Errors detected in the uppercase file."

However, I tried startup repair and that seems to have worked. It took about 30 seconds ("Windows is updating") and then it came to my desktop. Very strange, I am extremely grateful for your help!



 
startup repair runs similar commands so I hope its all you need

I would do this at desktop to make sure its fixed:
right click start button
choose command prompt (admin)
type SFC /scannow and press enter
once its run, copy/paste this command into same window:
DISM /Online /Cleanup-Image /RestoreHealth

DISM fixes the files SFC uses to fix windows, so if SFC had errors before, re run it now should fix them

If DISM asks for sources, I will give you those instructions if need be.
 
Hi, When I ran SFC it found corrupt files and was unable to fix some of them. I then ran DISM and that failed at about 94% (Error:1726). "The remote procedure call failed". I have error logs for both of these if they would be helpful?



 
that is a new one, DISM failing due to corruption.

Are you on the anniversary edition of Win 10?
right click start
choose run...
type winver and press enter
If this reads version 1607 then you can use the link below:

Microsoft's answer is to do this: http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

If you on a version other than 1607, I would go Here and click update now and it will download the Upgrade Assistant and if you run the assistant it will try to upgrade you to latest version of win 10 and could fix this error for you.
 
I am running version 1607. I attempted to do the repair of Windows 10 using a USB installation media (run the setup.exe file) and I get an error saying "Setup couldn't start properly. Please reboot your PC and try running Windows 10 Setup again".

I then tried to "refresh my pc" following these instructions. This gave me an error as well: "There was a problem resetting your PC. No changes were made".

It seems my computer is running OK, but I would really like to get everything completely fixed so nothing else like this happens again.

Again, thank you so much for your help!



 
Windows doesn't want to get fixed, it seems. The only way to fix it now is a fresh install as the files reset would use are the files DISM can't fix. So take your time and do that when you have backed up everything you want to save.