Server 2025+ IP LTSC Builds

Thank you for that. Consequently, I cannot find that 'About Windows" popup in your pictures. Was this a new install you just made? I've installed 25 > 22 > 19 > 16 > 12, I wonder if there's something resident from ages ago. The ISO I have that I've installed I believe is from uupdump called 'Windows Server 2025 26063.1.240216-1326.GE_RELEASE_SERVER_X64FRE_EN-US.ISO'. I couldn't get these to install over each other due to the Setup failed in SECOND_BOOT phase with an error during MIGRATE_DATA operation error I was seeing. They sure don't make this easy!

 

Popup is command "winver".

 

I've always installed Datacenter and I don't remember why.

 

Same actually but I know my silly reason going way back to 2003-2004 - it was the most ridiculously expensive "OP" option compared to whatever hardware I was running it on at the time... possibly my Opteron (165? 170?).
Yes... running the most costly version "just because".

 

I don't dare trying to install as I know it will fail on the second boot phase. again.

 

I cannot wait for this to no longer be insider at this point, so things like PUBG stop crashing out due entirely to the fact it's an insider version.
Soon... please, o gods of Microsoft, soon...
Though that "print screen button" issue still badly needs fixed...

 

You need to login to view this posts content.

 

Trying this on my Pi 5 asap.

 

Using the previous method (WOR Flasher on Pi -> point to ISO -> setup to sd card -> install to usb SSD...
IT WORKS! And so far it seems very snappy, too.
Now to kill smartscreen etc.
(Small update - manually adding in the latest UEFI files to WOR Flasher helps. And it is now possible to install from microsd to the same microsd without it breaking!)

 

It only took 10-15 minutes total too. (A fair bit longer on microsd but still very reasonable.)

 

For the record 3.7.7 is released and (thanks God) it works perfectly in 26085

 

I have a problem with build 26085.
Sometimes when I try to mount the Windows ISO with explorer, it freezes and I have to restart explorer to make work again

 

Mild note, the custom cursor problem appears to have been solved as of this update too.

 

I'm having troubles with domain network, no matter what I do the network profile stay public, albeit I can join and leave the domain at will.

Never had such problem before with any Windows version including Server 11 previous builds (I skipped 26080, so no idea if it was affected as well)

 

26085 works terribly for me on VMware ESXi 8.0. Upon promoting it to a domain controller, it goes into a boot loop. There are no such problems with 26080.

 

Having a weird issue as well, I have a 2022 VM DHCP server running on 26085, it can hand out DHCP addresses to other VMs, but to nothing outside of that.