WaaSMedicService problem -- Issue found by :WinRETargetingPlugin

I just got the idea from a reply on a reddit post that all the problems are most likely caused by oem1.inf(heci.inf) --

"One thing we've had in going W10 22H2 to W11 22H2 is driver issues. If you have a device that tried and failed, you look in c:$windows.~bt\sources\panther for CompatData*.xml files. There would show if any inf files have BlockMigration="True". It's an old problem that happened with W10 build upgrades in the past with XPS and PDF writer printers. Find the inf file in c:\windows\inf and open with notepad to see what printer the file is associated with. I remove the driver as we don't use those printers anyway. The following will remove, substitute the inf file name you want to remove.

pnputil /delete-driver oem1.inf /force"(from Windows Upgrade problems)

Unfortunately, I was unable to uninstall it with Driver Store Explorer, and I don't know whether uninstalling using the above command will have any impact on the system. Do you have any suggestions on this?

Could you help me check BlockMigration status?

The Microsoft Print to PDF and XPS drivers show up as "BlockMigration" drivers on every setup log. They're false positives. They definitely don't block the setup. The OEM numbers for the two drivers vary from system to system.

Here's the log from a Windows 11 system where the setup completed successfully.

I just got the idea from a reply on a reddit post that all the problems are most likely caused by oem1.inf(heci.inf) --

"One thing we've had in going W10 22H2 to W11 22H2 is driver issues. If you have a device that tried and failed, you look in c:$windows.~bt\sources\panther for CompatData*.xml files. There would show if any inf files have BlockMigration="True". It's an old problem that happened with W10 build upgrades in the past with XPS and PDF writer printers. Find the inf file in c:\windows\inf and open with notepad to see what printer the file is associated with. I remove the driver as we don't use those printers anyway. The following will remove, substitute the inf file name you want to remove.

pnputil /delete-driver oem1.inf /force"(from Windows Upgrade problems)

Unfortunately, I was unable to uninstall it with Driver Store Explorer, and I don't know whether uninstalling using the above command will have any impact on the system. Do you have any suggestions on this?

Could you help me check BlockMigration status?

I think you misunderstood me, if one or some drivers were the culprit, why did the first in-place upgrade complete successfully? (After that, I didn't add any new driver)

If you say drivers are not the culprit, why do you think 0xC1900101 occurs? The Microsoft documentation says 0xC1900101 (regardless of the extended error code) is related to drivers or BIOS.

Windows 10 upgrade error codes - Windows Client | Microsoft Learn: https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/windows-10-upgrade-error-codes

Windows 10 upgrade resolution procedures - Windows Client | Microsoft Learn: https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/windows-10-upgrade-resolution-procedures

Also, some tutorial videos related to the in-place upgrade mentioned that after running the media creation tool, the user will be asked to choose whether to update the driver, but I didn't find such option. I'm worried that I may ignore it. Does the 22h2 media tool have such option?

If you meant dynamic updates, they're enabled by default during the setup. Dynamic update installs the latest drivers if they have been published by the OEMs.

Latest version of applicable drivers that have been already published by manufacturers (OEMs and/or IHVs) into Windows Update and specifically targeted for Dynamic Update.

(Source)

I didn't mean "legacy BIOS". I meant a system that's old and outdated. On such systems, installing the latest builds can be challenging. You don't know which driver is blocking the setup.

// heci.inf didn't cause any problems, why do you think the problem is caused by the driver? //

As I said, removing drivers is a trial-and-error solution because the logs didn't indicate which driver caused the issue. Having a driver written in 2010 is definitely a suspect, And the error code 0xC1900101 is drivers or BIOS related, according to the Microsoft documentation.

Since my troubleshooting steps didn't help, you may wait to see if others have a fix for you.

I think you misunderstood me, if one or some drivers were the culprit, why did the first in-place upgrade complete successfully? (After that, I didn't add any new driver)

Also, some tutorial videos related to the in-place upgrade mentioned that after running the media creation tool, the user will be asked to choose whether to update the driver, but I didn't find such option. I'm worried that I may ignore it. Does the 22h2 media tool have such option?

I didn't mean "legacy BIOS". I meant a system that's old and outdated. On such systems, installing the latest builds can be challenging. You don't know which driver is blocking the setup.

// heci.inf didn't cause any problems, why do you think the problem is caused by the driver? //

As I said, removing drivers is a trial-and-error solution because the logs didn't indicate which driver caused the issue. Having a driver written in 2010 is definitely a suspect, And the error code 0xC1900101 is drivers or BIOS related, according to the Microsoft documentation.

Since my troubleshooting steps didn't help, you may wait to see if others have a fix for you.