Exchange Server Subscription Edition (SE) is now available

I upgraded the first Exchange 2019 server to Subscription Edition (SE).
Before the upgrade, I set the server into maintenance mode using the following commands:

Set-ServerComponentState $ServerName -Component HubTransport -State Draining -Requester Maintenance Set-ServerComponentState $ServerName -Component ServerWideOffline -State Inactive -Requester Maintenance

I confirmed all components were set to Inactive by running Get-ServerComponentState.
Then I proceeded with the SE installation.

At the final stage of the installation, an error occurred:

Configuring Microsoft Exchange Server

Preparing Setup .............................................................. Completed
Stopping Services ........................................................... Completed
Language Files .............................................................. Completed
Removing Exchange Files ..................................................... Completed
Preparing Files ............................................................. Completed
Copying Exchange Files ...................................................... Completed
Language Configuration ...................................................... Completed
Restoring Services .......................................................... Completed
Language Configuration ...................................................... Completed
Exchange Management Tools ................................................... Completed
Mailbox Role: Transport Service ............................................. Completed
Mailbox Role: Client Access Service ......................................... Completed
Mailbox Role: Mailbox Service ............................................... Completed
Mailbox Role: Frontend Transport Service .................................... Completed
Mailbox Role: Client Access Frontend Service ................................ Completed
Finalizing Setup ............................................................ 100%

Then the following PowerShell block failed with an error:

$error.Clear() $windir = $env:windir $appPools = &"$windir\system32\inetsrv\appcmd.exe" list apppool foreach ($appPool in $appPools) 

...

After a reboot, all services appeared to be running normally and I was able to open Exchange Management Shell (EMS).
Then I tried running:

powershell

Set-ServerComponentState $ServerName -Component ServerWideOffline -State Active -Requester Maintenance Set-ServerComponentState $ServerName -Component HubTransport -State Active -Requester Maintenance

However, all components still remain in Inactive state.

Could you please help explain what might have caused this and how to fix it?
Thank you.