I know, but it's for only 5 users. All roles of a domain controller, fileserver, printserver and client/server application.
Windows server 2019 to 2022 fails with error 0xC1900101 – 0x20017
I see this error is caused because of a driver. I have tried,
- Updating firmware and all drivers from HP
- Tried clean boot - disabled antivirus and all non-microsoft services.
I have Setuperr.log and Setupact.log files and don't know how to find out which driver is causing this problem.248783-setuperr.log
15 answers
Sort by: Most helpful
-
-
Anonymous
2022-10-10T15:53:29.347+00:00 It isn't recommended to install applications or other roles on a domain controller. A better option may be to install the hyper-v role (as only role) on host, then stand up virtual machines for the different roles. As to domain migration even a desktop pc could be used temporarily for migration purpose using an evaluation.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
-
Anonymous
2022-10-11T14:00:35.557+00:00 A new P2V image may help though its unlikely. Better solution may be the migration mentioned above.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
Jim Becher 1 Reputation point
2023-03-05T16:37:15.76+00:00 I just went thru the exact same thing. Server 2012R2 to Server 2022 upgrade. Failed with 0xC1900101-0x20017. I spent a couple days trying suggested things. None of them worked. I finally got around to looking at the partitions on the drive. The EFI partition was 200 MB, there was an extra 40 GB fat32 partition and a lot of unused space. I booted a partition tool. Made the 200MB EFI partition a 100MB partition, deleted all the other partitions except the C: and D: drives. Then expanded the C: and D: partition to the max. At that point the upgrade worked. Who would have thought?