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

Anonymous
2022-09-16T20:17:50+00:00

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.

Windows Insider program | Windows Insider preview | Repair and recovery

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
2022-12-12T16:05:20+00:00

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).

Was this answer helpful?

1 person found this answer helpful.
0 comments

58 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-09-16T20:44:01+00:00

    Are you running on a compliant PC?

    Run: https://aka.ms/GetPChealthcheckapp

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-09-16T22:18:14+00:00

    I have looked at your logs and am at a loss to explain what they are showing. I assume you will confirm you are running the Education version of the Dev channel. Your log appears to show you are being updated to the Pro version so either this is normal or not. Someone who knows for sure needs to weigh in.

    This is the second failed upgrade where a 6th Gen processor and the Education version are involved.

    Beyond this, you might check your setuperr.log and check all the User Profiles situations regard things like SQL.

    Target OS: Detected Source Edition = [Education]

    MOUPG WIM Path [ C:\WINDOWS\SoftwareDistribution\Download\727fbf4b1a5026504ceb9fb2ef4ff942\professional_es-es.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.25201 (1000.0) ]

    MOUPG Architecture [ x64 ]

    MOUPG Edition [ Professional ]

    MOUPG Language [ es-ES ]

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2022-09-16T22:52:35+00:00

    Your log appears to show you are being updated to the Pro version so either this is normal or not. Someone who knows for sure needs to weigh in.

    This is the second failed upgrade where a 6th Gen processor and the Education version are involved.

    There are 2 versions, Education and Education Pro. IDK what to make of it, maybe WU gets confused 🤣

    It could be something in common to both cases and the fact that both have non-compliant devices.

    Was this answer helpful?

    0 comments
  4. 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