Upgrade stuck at "PREOOBE" 88% from 20181 up to 21301

[Joachim_Otahal]

Hi there! Fighting it for quite a while...

Miglog.xml, section:

<Session Name="Main apply (Machine Independent)" Type="Online">

Last entries:

		<MigUnit Name="&lt;PC-JOU\Default User&gt;\hardware\hardware\phone_and_modem\Microsoft-Windows-TapiSetup (CCSIAgent)">
			<Action Type="apply-success" Class="Action,CMXEPlugin,C:\$WINDOWS.~BT\Work\MachineIndependent\Working\agentmgr\CCSIAgent,%SYSTEM32%\TapiMigPlugin.dll,{cf3b7cbe-c86a-4561-93a8-30e8036170a3},Apartment,Default"/>
		</MigUnit>
		<MigUnit Name="&lt;PC-JOU\Default User&gt;\Microsoft-Windows-WMI-Core (CCSIAgent)">
			<Action Type="apply-success" Class="Action,CMXEPlugin,C:\$WINDOWS.~BT\Work\MachineIndependent\Working\agentmgr\CCSIAgent,%windir%\system32\migration\WMIMigrationPlugin.dll,{401F8281-A9B6-49F9-9F71-8AEA167EEEFD},Apartment,Default"/>
		</MigUnit>
		<MigUnit Name="&lt;PC-JOU\Default User&gt;\Microsoft-Windows-Virtualization-Vmswitch-Migration-Replacement (CCSIAgent)">
			<Action Type="apply-success" Class="Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,microsoft-windows-virtualization-vmswitch\VmSwitchMigrationPlugin.dll,{3847B669-8830-4373-A943-D990963766A5},Apartment,Default"/>
		</MigUnit>
		<MigUnit Name="&lt;PC-JOU\Default User&gt;\Microsoft-ActiveDirectory-WebServices (CCSIAgent)">
			<Action Type="apply-success" Class="Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-ActiveDirectory-WebServices\adwsmigrate.dll,{06996584-9164-4CD2-BD44-3DEC24314516},Apartment,Default"/>
		</MigUnit>

Screenshot during that stuck period (Thanks setup.exe /diagnosticprompt enable shift+F10):

Any ideas? This time it was not tapi, maybe because I for removed "your phone" and reinstalled it through the store.

[#2]

Insider Feedback Hub : https://aka.ms/AAaymjb

[#3]

@Joachim_Otahal Did you ever figure this out? My windows server 2019 --> 2022 upgrade is doing the exact same thing. 88% preoobe stall, same logs and everything.

[#4]

Nope. it simply worked a few Month later. As for Server 2019 to Server 2022: That never failed for my scenarios.