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-19T01:24:59+00:00

I have tried to update to 25201 again and I still get the same error.

Try 25201 ISO from AdGuard and see what happens, don't change any menu options.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-19T01:42:32+00:00

I tried Windows Update, official ISO, and this last time, a build compiled on my pc through uupdump.net (to update to 25182 I had to build the update through it since there isn't official ISO). I assume that Adguard is similar to uupdump.

Now, I will try to update disabling the hypervisor and uninstalling all Windows related software to that (Hyper-V, Windows Sandbox...).

I have also uninstalled two Microsoft drivers that appeared in the logs with strange messages.

I'll see what happens...
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-19T01:49:04+00:00

I assume that Adguard is similar to uupdump.

AdGuard has an special bonus on their ISO making menu, can't go into details here.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-19T14:24:28+00:00

It seems that using the professional version of Windows for the upgrade for an Education install is normal. So that question is answered. I will have more info regarding an unqualified system, after 22H2 is released to the public. The other thread seems to have failed for a different reason but it appears the CPU situation was not involved.

Your log shows the install was failing very early. Possibly, because of the difference in the Images being used.

These two lines tell me it failed early. An upgrade doesn't normally boot into the SafeOS unless there is a problem.

Info SP Neo installation path is turned off, pushing WIM apply to SafeOS phase

Info SP OPERATIONTRACK: Enqueue Operation: 41|Delay new OS apply

Failed Image

MOUPG WIM Path [ C:\WINDOWS\SoftwareDistribution\Download\b0af179b8f2a4ab062f71ceeef29326e\professional_en-us.esd ]

MOUPG Image Count [ 3 ]

MOUPG Install Count [ 1 ]

MOUPG WinPE Count [ 1 ]

MOUPG -------------------------

MOUPG Install Index [ 3 ]

MOUPG Product Name [ Microsoft® Windows® Operating System ]

MOUPG Version [ 10.0.25193 (1000.0) ]

MOUPG Architecture [ x64 ]

MOUPG Edition [ Professional ]

MOUPG Language [ en-US ]

Successful Image

MOUPG WIM Path [ E:\Sources\Install.wim ]

MOUPG Image Count [ 1 ]

MOUPG Install Count [ 1 ]

MOUPG WinPE Count [ 0 ]

MOUPG -------------------------

MOUPG Install Index [ 1 ]

MOUPG Product Name [ Sistema operativo Microsoft® Windows® ]

MOUPG Version [ 10.0.25201 (1000.0) ]

MOUPG Architecture [ x64 ]

MOUPG Edition [ Professional ]

MOUPG Language [ es-ES ]
Was this answer helpful?

0 comments No comments