Proxmox 8.4.1 and Windows Internal Database (Remote Desktop Service)

eltonclemente

New Member
Oct 9, 2025
1
0
1
Hello everyone.

I have a data center running Proxmox 8.4.1.
My physical servers are identical:
ProLiant DL360 Gen11, 2x Intel(R) Xeon(R) Gold 5415+, 256GB RAM, BCM 5719 1Gb 4p BASE-T OCP Adapter, Broadcom P210tep NetXtreme-E Dual-port 10GBASE-T Ethernet PCIe Adapter – NIC.
Storage controller: HPE MR408i-o Gen11 with 2x 480GB SSD for Proxmox only.
My VMs are all on an HPE MAS2060 iISCSI 10G Ethernet storage.

I'm facing the following issue with both Windows Server 2016 Standard and Windows Server 2025 Standard. I create a VM and install the operating system, then try to install the Session-Based Windows Remote Desktop services. After some hardware tweaks, the VM installs, but upon restarting, Windows rolls back and removes the services.

I've seen a lot of comments about TLS 1.0 and 1.2 being active, among other things, and all attempts have been unsuccessful.

What's really strange is that the VM is newly installed. It doesn't have antivirus software. I've tried it offline, with an internet connection, and with all the updates applied (Windows Update). I've tried changing the hardware to use SSD, SATA, or IDE drives, all without success. I've tried with UEFI and SeaBIOS BIOS, and the same error occurs. Since this is also occurring regardless of the Windows Server version, it raises the possibility of some incompatibility between the VM's hardware configuration in Proxmox and Windows Server.

Oh... one detail: the problem occurs whenever the WID (Windows Internal Database) dependency needs to be installed.
If I install only Licensing Server, for example, which doesn't use WID, the installation goes smoothly. But WID is also required for the Connection Broker and the RDS Web Service.

Has anyone experienced this, or have any suggestions?