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

Anonymous

2022-09-21T04:46:37+00:00

No, Intel i5-6200U, it's a HP laptop.

ok good to know., thanks for sharing.

Please see my edit above. Good luck!
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-22T02:02:07+00:00

As a sidenote, Dev builds are prone to bugs and failures. If you are going to continue on the WIP, you should make regular backups and be prepare to clean install anytime.

I know the risks.

But if I'm on an experimental version, it's partly to help Windows improve and avoid major bugs in stable versions, but if they don't pay enough attention to us, it's normal that they end up releasing versions with problems (as has happened several times).

I haven't tested the build released this week (25206), but I think the bug will continue.

I think the problem where it isn't possible to run Windows in a virtual machine through Hyper-V and with more than one core may be related to ours.

Out of curiosity, how many cores does your laptop processor have?
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-22T02:22:59+00:00

I think the problem where it isn't possible to run Windows in a virtual machine through Hyper-V and with more than one core may be related to ours.

Out of curiosity, how many cores does your laptop processor have?

IDK about Hyper-V but I run Insider builds on VMware Workstation without any problems.

In fact, I enable encription and TPM just to clean install the builds, then I disable them to make the VM faster and WU continues to update any build normally.

This is not the case for Beta or RP builds on the laptop itself (yellow zone) where I can't clean install (*) and WU refuses to update them even though it is fully compliant except for the CPU

This is MS blocking W11 installations except for Dev builds on devices previously allowed.

I have an i3-6006U, 2 cores 4 threads

(*) it can be done using hacks. 😁
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-22T07:18:46+00:00

As a sidenote, Dev builds are prone to bugs and failures. If you are going to continue on the WIP, you should make regular backups and be prepare to clean install anytime.

I know the risks.

But if I'm on an experimental version, it's partly to help Windows improve and avoid major bugs in stable versions, but if they don't pay enough attention to us, it's normal that they end up releasing versions with problems (as has happened several times).

I haven't tested the build released this week (25206), but I think the bug will continue.

I think the problem where it isn't possible to run Windows in a virtual machine through Hyper-V and with more than one core may be related to ours.

Out of curiosity, how many cores does your laptop processor have?

25206 not working. confirmed.
Was this answer helpful?

0 comments No comments