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-20T02:17:17+00:00

Previously you said Ryzen 3, I based my search on that.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-20T02:10:51+00:00

Both of my laptop and PC can not upgrade to 25193+, and all just the extractly same isue.

They are all based on AMD Zen3, PC was AMD Zen3 5950x, laptop was AMD Zen3 5800H. So I think this issue has nothing to do with hardware compatibility.

Those 2 AMD processors are not listed as compatible with Windows 11.

Windows 11 supported AMD processors

Many devices like my laptop are yellow zone, meaning MS allowed them to continue despite not being fully compliant. I don't remember exactly when started but before I could clean install or update any channel, not anymore, only Dev now.

Microsoft warned us that W11 requirements were going increase as development went on, maybe that is the case here and they tighten the screws starting with 25193.

5950x was the latest desktop cpu from amd currently on sale.

5950X and 5900HX(my mistake, cpu model was 5900HX not 5800H) were all in the list.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-20T02:03:06+00:00

Both of my laptop and PC can not upgrade to 25193+, and all just the extractly same isue.

They are all based on AMD Zen3, PC was AMD Zen3 5950x, laptop was AMD Zen3 5800H. So I think this issue has nothing to do with hardware compatibility.

Those 2 AMD processors are not listed as compatible with Windows 11.

Windows 11 supported AMD processors

Many devices like my laptop are yellow zone, meaning MS allowed them to continue despite not being fully compliant. I don't remember exactly when started but before I could clean install or update any channel, not anymore, only Dev now. In order to clean install or update Beta or RP, I have to use hacks.

Microsoft warned us that W11 requirements were going increase as development went on, maybe that is the case here and they tighten the screws starting with 25193.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-20T01:38:57+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

Both of my laptop and PC can not upgrade to 25193+, and all just the extractly same isue.

They are all based on AMD Zen3, PC was AMD Zen3 5950x, laptop was AMD Zen3 5800H. So I think this issue has nothing to do with hardware compatibility.
Was this answer helpful?

0 comments No comments