[SOLVED] Error Code 800700A1-2000C in windows update

[hisham]

Hi,
When trying to upgrade from Win7 to Win 10, I got systimaticaly the error code 800700A1-2000C.
I tried to execute the sfc /scannow are recommended but it fails t 50% and seems that some windows update files are corrupted. Error: STATUS_FILE_CORRUPT_ERROR
I tried to install different microsft fix for the error that I have in the logs but still not resolved. The complete scan log is here.

Thanks for your support.

 

[hisham]

Still trying to find what is wrong, I isolated this error from the log that seems to be the only CSI error:

2016-02-01 07:22:56, Info                  CSI    0000007b [SR] Beginning Verify and Repair transaction
2016-02-01 07:23:02, Info                  CSI    0000007e [SR] Verify complete
2016-02-01 07:23:02, Info                  CSI    0000007f [SR] Verifying 100 (0x0000000000000064) components
2016-02-01 07:23:02, Info                  CSI    00000080 [SR] Beginning Verify and Repair transaction
2016-02-01 07:23:05, Info                  CSI    00000082 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, 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
2016-02-01 07:23:08, Info                  CSI    00000086 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, 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
2016-02-01 07:23:08, Info                  CSI    00000087 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery"
2016-02-01 07:23:08, Info                  CSI    0000008a [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2016-02-01 07:23:08, Info                  CSI    0000008c [SR] Verify complete
2016-02-01 07:23:08, Info                  CSI    0000008d [SR] Verifying 100 (0x0000000000000064) components
2016-02-01 07:23:08, Info                  CSI    0000008e [SR] Beginning Verify and Repair transaction
2016-02-01 07:23:12, Info                  CSI    00000091 [SR] Verify complete
2016

 

[hisham]

Still with my issue
I managed to fix the scan bloackage, the scan is now 100% complete, errors found but not corrected.
When I tried to upgrade, it progress until arround 60% and failed with a blue screen and the error : 0xc000000f.

Do you have any idea how can I progress on this issue?

thanks,

 

[Aura]

Hi hisham :)

My name is Aura and I'll be assisting you with your issue. How are you trying to upgrade to Windows 10? Via Windows Update, or the Media Creation Tool? Or maybe the .iso directly?

 

[hisham]

Hello Aura,

I used the Microsoft Update and it fails, I tried with Media creation tool and same issue.
I recovered the system to the original version (mabufacturer one) and tried with the Media Creation tool, win 10 install start and then go with a blue screen.

Now, I dont have any idea about how to continue this upgrade operation.
Thanks,

 

[Aura]

Hum, since you are encountering a BSOD when trying to upgrade, I think you should seek assistance in the BSOD, Crashes, Kernel Debugging instead. It's true that the issue here is that you cannot upgrade to Windows 10, but the BSODs you have could help us understand what you're having, and the helpers there have the expertise needed to tell us what is causing these BSODs. You can tell them that I sent you and they can communicate with me if they want to work together on your case :)

https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/

 

[hisham]

Submitted here.
Thanks,

 

[hisham]

This post can be closed as explained in my BSOD post, the issue is closed now.

Thank you Aura for your time and support.

 

[Aura]

Thank you hisham for letting us know what your issue was and how you solved it :)

And you're welcome :)