Server Windows 2019 RDS won't start after server restart. How to fix?

Question

Windows Server

A problem has appeared.
server 2019
raised RDS services (standard deployment on one server)
After restarting the server, it is impossible to log in via rdp.
Error message:

"Не удается подключиться к удаленному компьютеру. Повторите попытку подключения. Если проблема повторится, обратитесь к владельцу удаленного компьютера или администратору сети."

You can only log in locally, or through the IPMI console.
Events in the Server Manager show the following:

код 1296
  
При получении пакета перенаправления от посредника подключений к удаленному рабочему столу в клиенте посредника подключений произошла ошибка.
Пользователь: --------
Ошибка: Посредник подключений к удаленному рабочему столу не готов к RPC.

код 1306
  
Клиенту посредника подключений к удаленному рабочему столу не удалось перенаправить пользователя ----------
Ошибка: NULL

код 1280
  
Службам удаленных рабочих столов не удалось присоединиться к посреднику подключений на сервере .......
Ошибка: Текущее асинхронное сообщение отброшено асинхронным диспетчером, так как существует новое сообщение, которое переопределит текущее.

Previously, restarting the following services in a row helped:

Licensing Service, Remote Procedure Call Locator (RPC), Remote Slave Connection Broker Service. table, Remote Desktop Services User Mode Port Forwarder, Microsoft iSCSI Initiator Service (also after the server reboot, another server loses the ICSI disk, and until the service is restarted, it will not see it).

and after that we will restart the "Remote Desktop Services", if they are restarted immediately, without restarting the above. then an error will be thrown that the service did not respond in time. and in the end it hangs in a stop state.

If all this is done, then access is restored.

I tried to do DISM /Online /Cleanup-Image /RestoreHealth indicating the source of the wim package (he did not do it without it), wrote that it was restored, but the problem remained.

Tried reinstalling the entire RDS role. The problem remained the same. after reboot it is necessary to do restart of the services specified above.
Today this algorithm did not help.
If you set the security level to rdp instead of "negotiate", you will still be able to access without restarting the services.
I had to leave the rdp security level for now, but in the collections I do not see user sessions, although they are logged in and working.

in events continues to appear errors that I wrote above 1306 and 1296
I can not solve this problem for several months.
I came across similar situations on the forums, but either no solution was found there, or there are no answers at all.

What could be? how to fix without reinstalling the system?