Windows 10: Windows 11 22H2 update fails with 0xC1900101 - 0x30017

Hi folks,I've been pulling my hair out trying to get this update to take on my machine. Typically I get the 0x30017 suffix on the error, but I've also seen the 0x20017 suffix on the error as well. Things I have tried:sfc /scannowDISM /Online /Cleanup-Image /RestoreHealthClean boot and installBoot from USB after I disabled device guard and secure boot Upgrade option wasn't allowedThe second option to do a custom install wanted me to decrypt my drive first, have not pursued this yetMount the ISO and run setup.exe as adminUse the USB and run setup.exe as admin from thatRun setupdiag.exe to see

:)

 

Upgrade to 1803 version fails with 0xc1900101-0x30017 error

Speed Fan

 

Upgrade to 1803 version fails with 0xc1900101-0x30017 error

I'm done with the rest of the scans too.

https://www.dropbox.com/s/arpmhyj2kb...2CC%29.7z?dl=0

I've pasted the results of all three drives into the same text file. Drives F,E & C(OS) in that order.

I guess I'm ready with the backups too. I have a backup from a week or so back and that should be enough if need be. I've also familiarized myself with the Driver Verifier procedure. So, that will be the next step, right?

edit: I've since made a find. Yesterday, I made the mistake of not searching whole of C: for the drivers. I only looked in the Windows folder. The LUMDriver happens to belong to one of the softwares I've installed: CATIA. Maybe uninstalling it should take care of that, hopefully.
@zbook - would it be OK for me to run the driver verfier now or should I first try uninstalling CATIA?

 

Error 0xC1900101 - 0x30017

Hello,

I recently tried to upgrade my licensed Windows 7 Professional to Windows 10 using the MS upgrade tool. Upon installation, my PC screen went blank and flickered intermittently, showing no further signs of completion of upgrade process.

Later the windows automatically reversed the installation and restored my computer to Windows 7. Upon restore, the error displayed was 0xC1900101 - 0x30017. I could not find the right trouble for the error given. Can Microsoft community help and support
by sharing step by step guidance to resolve this issue and upgrade to Windows 10.