Cannot install Windows 11 - Error 0xc1900101

I was hoping the new release (10.0.22000.65) might install successfully, but nope, same 0xc1900101 error.

My concern has nothing to do with Windows 11. My concern is with the installer.

I will assume that the installer program is not 50 million lines of code long.

I've solved it! I have two SSDs on my PC, and I remove the after one（Toshiba 512G）, and it works! If you have two SSDs too you can try it

Hmmm, I have two SSD's in my system also...I'll give that a try and see what happens.

I am in the same camp as you. I can scrub my computer completely clean and start all over again. I am not inclined to do that because I expect Microsoft get their stuff together enough for it to work the way it should. I have been receiving windows 10 updates for many years without a single issue. Now that windows 11 is out in the preview mode that seems to have perplexed the Win11 developers.

Dude relax, don't you start jumping down Microsoft's butt this early in the game. This is the reason why we're invited to test the O/S, so that they can work out the bugs. If you can't handle it at this level, then perhaps you should throttle back on the level of beta tester you wish to be. I can't believe your reaction is at this level already. Perhaps you shouldn't even *be* a beta tester, based on the lack of patience you appear to have. Besides, it isn't Microsoft who's telling you to scrub your system down, That's just what other Beta testers are saying they've done, to get Windows 11 to install. You are correct however, you shouldn't have to bring your system down to a "clean" install, in order for Windows 11 to be happy enough to complete its install, and I'm pretty sure Microsoft's developers feel the same way as you do. I'm sure Microsoft would rather you NOT scrub down your O/S, so they can find the problem and work it through. I would expect a complaint such as yours to be made, once the software is officially released, not when they're first releasing the beta O/S to their beta testers, on their first beta release. You're expected to be *helping them* work out their bugs, not bad-talking them because you expect their 50 million lines of code to work perfectly in their not-so-perfect release. And I have not seen anywhere in this forum where Microsoft is saying this issue is related to drivers in any way. Again that's just another beta tester's opinion as to what the problem may be. This error code could have nothing at all to do with drivers. I've read one person say that their TPM isn't a real TPM, that's it's nothing more than some firmware coming from their CPU. That is exactly the configuration I have currently as well. It could be the reason why we're having this issue. Microsoft may be expecting for us to have a REAL TPM module on our motherboards, not lines of code coming from our CPUs that are pretending to be a TPM.

It is always reassuring to see technical professionals such as yourself provide useful feedback to the windows 11 challenge..

My expectation is that Microsoft, in their infinite wisdom, would be able to understand that there are millions of different configured computers. And in that wisdom, they would solve their own challenges.

If Microsoft is smart enough to understand the innocuous error message encountered while trying to install windows 11, then they should be smart enough to tell me exactly which driver is offensive.