Exchange 2019 CU15: Abort with error "Cannot start service"

I am now having problems updating to CU15 on the second Exchange 2019 CU14 server. The CU15 setup aborts in my environment on a Windows Server 2022 with January updates at step 4 of 16 with the following error:

Error:
Cannot start service WinMgmt on computer '.'.

With the first server, I wasn't quite sure whether the server would have needed a restart after all. In this case, however, there was no need for a restart. The server was freshly restarted before the installation, as the February updates were also installed directly here. So the error message occurs on Windows Server 2022 with January and February updates.

Since I had already seen the error once, I looked directly at the service. The "Windows Management Instrumentation" service has started:

So I restarted the server and ran the setup again. The CU 15 setup loads normally again and now reports the Exchange services that are not started because they were previously deactivated by the setup:

In addition, I now have these little ugly graphic errors (the black boxes). By the way, the first server showed exactly the same behavior, but crashed at step 5 of 17, because preparations were made in the Active Directory beforehand:

I would actually see that as a quirk or peculiarity of my surroundings if it weren't for that little annoying something:

Setup no longer considers it necessary to display a progress bar for the languages from step 6 of 14. Nothing happens in the ExchangeSetup.log either:

The last entry in the setup log is this one:

[02.18.2025 19:53:11.0144] [1] Finished updating performance counter strings

Only the Task Manager is still alive. ExSetupUI.exe keeps starting processes there with the names "Console Window Host" and "Load Perfon Counters":

The two processes start briefly, provide a little CPU load and are then terminated again.

I wanted to cancel the setup on the first server, but then I thought to myself: "Let it run, at some point it will tell me what the problem is".

After 35 minutes of waiting and zero progress in the log file or in the setup GUI, the step is suddenly at 100% and it continues with the next steps:

From now on, the setup runs normally again and can also be completed successfully:

Nothing happened in the Exchange setup log for a good 35 minutes (same time on both servers):

All in all, the Exchange CU15 setup took a good hour, which I think is actually okay:

I have not yet been able to find out what is causing this behavior, but I still have a few servers ahead of me and can take a closer look. Has anyone perhaps also observed this behavior?