Ask a new question

I am unable to Enable Windows RE after using MBR2GPT successfully.

I checked and found winre.wim was missing. Retrieved a copy from my Win10 DVD install.wim file. Copied it and reagent.xml files into my System 32 Recovery folder and tried again. Still failed, this time with 3bc3 code. I am stuck and not sure what to do now. I tried to upload screenshots from disk manager and command line but I can't make it work (sorry!). Here is data from reagentc /info

Windows RE status: Disabled

Windows RE loaction:

BCD identifier: 00000000-0000-0000-0000-0000000000000

Recovery Image location:

Recovery image index: 0

Custom image location:

custom image indes: 0

Disk Manager shows Disk 0 with 3 partitions

Partition 1 479MB Healthy (recovery Partition)

Partition 3 100MB Healthy (EFI System Partition)

C: Healthy (Boot, Pagefile, Crash Dump, Basic Data Partition 953GB NTFS

Partition Style is GUID Partition Table (GPT)

I need to fix this so that I can proceed to enable Secure Boot and update to Win 11.

Please help!

Image

Image

|
Answer
Answer

WinRE is enabled.

Yes. 0xc1900101-0x20017 is a driver (or outdated BIOS) issue. Please update the chipset drivers and BIOS for your motherboard. Then, enable Memory Integrity in Windows Security.

Re-run the setup and let me know if you still get the error.

______________________________________________________________________________________________________
Ramesh, Windows Shell MVP 2003-2012.
If this post resolves your issue, pls mark it as an Answer.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Answer
Answer

Hi Ramesh,

Win 11 now installed but it was tough.

You were correct that the 2 drivers identified by Core Protection: PxHIpa64.sys from Corell and Wdcsam64_prewin8.sys did cause the update problem. Fixing the first was easy. I just went into the System 32 folder and renamed the file with a .old. That fixed it as a problem. The WD driver was MUCH tougher. First, I could find no driver with this name anywhere. I looked carefully. There was a driver WDcsam64.sys but deleting it in AutoRun did nothing. Trying to delete or rename it in the System 32 folder didn't work. And I got a message saying it was in use! I soon found that the actual ID of the file was oem0.inf. I tried deleting it in the INF folder and renaming, but neither worked. Finally, I found online a suggestion to run as Admin >pnputil /enum-drivers which gave me a list with full details. In that long list, 2 were from WD and they were WDscan64.sys. Their actual file names were oem0.inf and oem99.inf. Then I ran>pnputil /delete-driver <>for each and it worked! Win 11 update is complete.

I did not find it necessary to follow instructions from Microsoft to uninstall all AV (ESET and Malware Bytes) and Shadow Protect.

I may still have some messes in my Win 11 OS. Don't know. I will follow up with Gigabyte to ensure that I have their latest drivers and those they recommend for the Intel chipset. If you have any other diagnostic suggestions to check if my install is working well, I'll happily try them. I recall that you did analyze a log file that showed a number of BSODs. Is there more checking/fixing I should do? So far, I've seen no obvious problems.

MANY thanks for your help. Without it, I would have failed and had to do a clean install, complicated by having to reinstall lots of non OS applications.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated April 17, 2025 Views 198 Applies to: