Forum Discussion

WithinRafael's avatar
WithinRafael
Copper Contributor
Jun 11, 2024

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 server with no problem but joining the domain immediately bricks the VM, 100% of the time.

 

The forest is running at functional level WS2016. I disabled all GPs and verified with gpresult they are not applied.

 

Safe mode boots if you need me to poke around. Am working to get a kernel debugger attached.

 

No memory dump is generated and disabling reboot on errors yields nothing.

Active Directory (AD)
Windows Server 2025
  • Reachdp's avatar
    Reachdp
    Copper Contributor
    Nov 24, 2024

    Some how credentials Gaurd is getting enabled but here is the work around to add below registries. 

    open elevated cmd or powershell prompt run reg add HKLM\System\CurrentControlSet\Control\Lsa /v LsaCfgFlags /d 0 /t REG_DWORD run reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard /v LsaCfgFlags /d 0 /t REG_DWORD
    Ensure the cmd operation completes successfully for both commands then proceed with joining domain. Give thump up if it works

  • Reachdp's avatar
    Reachdp
    Copper Contributor
    Nov 20, 2024

    Seeing the similar issue in AWS Ec2 instance for windows server 2025, and it goes to boot loop and shows AWS logo 
    While attempting to fix bcedit it had thrown the error- the boot configuration data store could not be opened. access is denied

  • mreinders's avatar
    mreinders
    Brass Contributor
    Nov 22, 2024

    With the final version (26100.1742) available, I would try installing that updated version, and then join to the domain and see if you get better results. If you have access to Visual Studio downloads or the Volume License portal on M365 admin center, you can get an updated ISO at the October (RTM) patch level.

  • WagnerCL's avatar
    WagnerCL
    Copper Contributor
    Nov 22, 2024

    same issue here, I've actually built a new 2025 EC2 instance, created a new forest (with domain and forest functional level in 2016), rebooted a couple of times and is working, i've created another EC2 instance with 2025, joined to the built-from-scratch AD domain, rebooted twice and it get's stuck in the AWS logo.

    Not sure what is the component failing here.

  • WagnerCL's avatar
    WagnerCL
    Copper Contributor
    Nov 22, 2024

    I've just upgraded forest and domain functional level to 2025 and provisioned anew EC2 instance, joined to the AD domain and same issue, get stuck in the AWS Logo

     

Resources