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-18T05:32:13+00:00

I just posted this on the other thread, something to consider as being the culprit IDK 🤷‍♂️

I clean installed 25201 using the official ISO and to my surprise the installer asked me to select which edition to install, this is new to this build. Normally, the installer would detect my laptop as being originally shipped with W10 Home SL (later upgraded to Pro) and install that version of W11 without asking but recently it was installing Pro on its own.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-17T17:45:09+00:00

Yes, BIOS, and all drivers, are updated.

I only use Windows Defender. And no, I tried updating without any external USB too (it's a laptop but usually I use a mouse and keyboard).

Now I will try to update without all the Intel software...

After uninstalling the Intel software, I still get the same error.

Now I'm going to try to upgrade to 25182 build.

Edit: As I expected, update to 25182 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.

I have updated the link of the logs and included logs of this update, maybe can be helpful to compare them.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-17T17:27:17+00:00

En Rollback log, en la línea 16, indica: última fase: 4, última operación (¿operación?): 23. ¿Hay alguna forma de saber qué es esa "operación"?

Cadena de fase actual: FirstBoot, End

Fase actual : 4

Operación actual : 23

Resultado actual: Desconocido

Tengo una pregunta más, el registro muestra una partición en HardDisk0\Partition1 que indica que es la partición MSR. ¿Podría adjuntar su imagen de Administración de discos para que podamos ver las particiones o decirnos cuál es la primera partición que muestra en el Disco 0?

¿Dónde podría estar su partición EFI del sistema, detrás de la partición C:?

Yes, the first partition is EFI.
Was this answer helpful?

0 comments No comments
Anonymous

2022-09-17T12:43:11+00:00

In Rollback log, on line 16, it indicates: last phase: 4, last op (operation?): 23. Is there any way to know what that "operation" is?

Current phase string : FirstBoot,End

Current phase : 4

Current op : 23

Current result: Unknown

I do have one more question, the log shows a partition on HardDisk0\Partition1 that indicates it is the MSR partition. Could you attach your Disk Management picture so we can see the partitions or tell us what the first partition you show on Disk 0?

Where might your System EFI partition be, behind the C: partition?
Was this answer helpful?

0 comments No comments