Will usually have to be scraped from actual OEM machines once Server 2025 is released (or shortly before).
So Windows Server 2025 looks to be based on Windows 11 24H2. Windows 11 has lots of requirements for processor and TPM. Most of these are not enforced for Server, apparently. I got Server 2025 running just fine on some Dell Optiplex 980 in my lab. These are first generation Core i7-870 with 16GB RAM. Also running Hyper-V with another Server 2025 VM on this same machine, as a spare domain controller. The performance is... actually not terrible.
Has anyone tested Window 2025 PE boot image? It seems that Get-Disk, Get-Partition and other similar Powershell commands do not work (just returning zero results). In the same time diskpart shows disks correctly. Also the commands worked as expected in the Windows 2022 PE image.
I am testing windows server 2025 eval german. Everything seems fine after clean Installation but Windows update stops Windows defender with update Installation and it is not possible to reactivate defender manually again.
It can only be fixed by new LangPacks, or already localized source (e.g. Danish ISO, if they create one) you could also try to modify install.wim prior installation remove en-us LP, and add da-dk LP
NO! Affected Product Versions The following Windows product versions are confirmed to be affected by CVE-2024-38063: Windows 10 Version 1809: 10.0.17763.6189 Windows Server 2019: 10.0.17763.6189 Windows Server 2019 (Server Core Installation): 10.0.17763.6189 Windows 10 Version 1903: 10.0.18362.9000 Windows 10 Version 1909: 10.0.18363.9000 Windows 10 Version 2004: 10.0.19041.8040 Windows 10 Version 20H2: 10.0.19042.8040 Windows 11 Version 21H2: 10.0.22000.1000 Windows Server 2022: 10.0.20348.9000