Unable to update Windows 11 Insider ( 0xC1900101 - 0x40017 )

Anonymous

Hi,

I had a problem for weeks. My device is in build 25174, and it's impossible for me to update Windows to later versions, like 25201 or 25197.

I have tried everything: clean flash, +100GB free space, DISM repairs, uninstall and update drivers, update from bootable USB... but impossible, always the same problem. It fails to turn on after the second reboot. (After reaching around 70% of the installation, it performs a reboot. Later it tries to start, but the Windows icon cannot be seen for more than a few moments and turns off as if the power was cut). Error code: 0xC1900101 - 0x40017

I've read that it might be a driver problem, but I can't find what it could be. I've been testing new versions for years and I don't remember changing drivers recently. Still, I deleted some and updated others, but I still have the same problem.

In addition, the version expired on the 15th, so since then, Windows has given me problems when doing some tasks. For example, I can't try to update again from Windows Update (but I've solved that for now by changing the device's current date).

~~Here are the update logs, if you need more, tell me which ones:~~ ~~https://1drv.ms/u/s!Ar5eavTB2nszjbQTLLxjKO_2AfwmWA?e=kZvzdZ~~ Thanks in advance!

Edit: As I expected, the update to 25182 was successful (so the version expired problem was resolved). And possibly if I update to 25188, it would also be successful (like hegdesaspect). I didn't update to that build due to the issue with .NET Framework 3.5.

So the problem is on 25193+ builds.

2nd Edit: After disabling Virtualization support in BIOS, I could update correctly. Now I am on 25201.

But I still have the same problem when I enable Virtualization on BIOS (when Windows boots, immediately my system turns off as if the power was cut; if I disable it again, it boots correctly).

Is this a bug or has Microsoft disabled virtualization support for non-compliant devices?

Final Edit: Finally, (in my case) it was a problem with the PxHlpa64 driver. I can see this is a known issue, there are reports from other users in this community that indicate it conflicts with Memory Integrity. At this moment, it's solved by removing it from the system.

Thanks to user iFish_木鱼 , since he found the solution having the same problem.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Hey guys, good news.

After ~4hours dig, I manage to fix this issue on both my pc&laptop finally.

Now I'm running on Windows 11 build 25262 with virtualization(SVM) enabled.

In my case, there is a system service named 'PxHlpa64', which comes from corel corporation, shutdown my windows 11 system on boot when SVM enabeld on 25188+.

Just disabled it via autoruns from sysinternals under drivers tab, problem resolved.

At the end I deleted everything about it found in registery.

Hope this information helps you.

Whole thing on my blog (https://blog.iccfish.com/?p=5241), refer to it if you need (in chinese).

0 comments

58 additional answers

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
Anonymous

2022-09-19T17:31:16+00:00

Or can I say this issue was due to virtualization? I can not upgrade to any versions after 25188 dut to extractly same issue even 25201 (after 75% reboot immediately and rollback to 25188 with 0xc1900101 - 0x40017 error).

Cause I need virtualization, so I guess I can only live on 25188 until MS fixed this issue?

It seems so, maybe never. Virtualization may no longer be available for non-compliant devices.

You can disable Windows Security-Device security - Core Isolation-Memory integrity. You could try that, then re-enable the Bios. If you could eventually get the system to check for the bad driver/s it might help.

I do not know if Security Virtualization uses space on the EFI System partition, which is limited in your case.

I disabled Memory Integrity some months ago. But now, I tried to access to that page, I get this error.

I don't know when, but Microsoft disabled support to Core Isolation for my device in some build.

If this was a bug on builds 25193+, we would have seen widespread reports but we haven't.

Could be a bug specific to PC brand/model, bios settings or something else. JMPO

In the Feedback Hub, there are people reporting the same problem with these builds. There is where I found that disabling virtualization in BIOS can fix this problem for some.

Without a doubt, although it does not appear in the changelogs, Microsoft made some changes in build 25193, related to virtualization, which makes many devices incompatible.

The question that remains is, was this on purpose, or is it a bug?
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-19T17:16:06+00:00

Or can I say this issue was due to virtualization? I can not upgrade to any versions after 25188 dut to extractly same issue even 25201 (after 75% reboot immediately and rollback to 25188 with 0xc1900101 - 0x40017 error).

Cause I need virtualization, so I guess I can only live on 25188 until MS fixed this issue?

If this was a virtualization bug on builds 25193+, we would have seen widespread reports but we haven't.

Could be a bug specific to PC brand/model, bios settings or something else IDK. JMPO
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-19T17:13:43+00:00

You can disable Windows Security-Device security - Core Isolation-Memory integrity. You could try that, then re-enable the Bios. If you could eventually get the system to check for the bad driver/s it might help.

I do not know if Security Virtualization uses space on the EFI System partition, which is limited in your case.
Was this answer helpful?

0 comments No comments