Forum Discussion
WithinRafael
Jun 11, 2024Copper Contributor
WS2025 Preview (26100.1) fails to boot after joining WS2016 forest
I installed WS2025 Preview (Datacenter, 26100.1) in a virtual machine and after joining the domain, the box is rendered unbootable (boot loops). I can reinstall and do other tasks as a standalone ser...
ChristianPohle
Dec 25, 2024Copper Contributor
We've the same Error. Setup the actual "Microsoft Windows Server 2025 Base" AMI (ami-01f52dc9cb63c603a) in EC2 and the Server works and reboots fine as long as we keep it as a standalone Server. As soon as we join the Domain the Server is stuck in the mentioned reboot loop. Out Domain is currently 2016 functional level.
Opened a ticket @ AWS Support, they mentioned the EC2Rescue Tool and I've analyzed a failing instance but there are no Eventlog Entries from the failed boots so it seems to occur before the eventlog Service starts (the reboot happened very fast tough).
As this Thread is from June 2024 I don't think there will be a solution soon....
ReachdpI'll try your settings with a Test server. Do you have a longer Time experience, that the Server runs stable? We are in the project to upgrade productive Servers....
- ReachdpDec 28, 2024Copper Contributor
By default 2025 boots UEFI boot mode an alternate is to use BIOS-Windows_Server-2025-English-Full-Base AMI to avoid this boot loop issue.