Server 2025+ IP LTSC Builds

Bring on the desktop version, Microsoft!
(Trivia, KMS_VL_ALL works even though the scheduled tasks fail to create.)

 

Is "Azure Arc Setup" no longer un-installable? Unlike Server 2022 it does not appear anymore in Server Manager \ Features.

What is the best way to uninstall it? You can disable start on log-in but it is annoying when you're not going to add the server to Azure obviously )

Thanks

 

Now it has become a part of Features on Demand.

Code:

Dism /Online /Remove-Capability /CapabilityName:AzureArcSetup~~~~

 

I meant literally what I said, no more no less. Still I'll clarify... there is VISUALLY a new setup/GUI when you boot the install media for Windows Server 2025.
Hence the image, showing a new setup/GUI when you boot the install media for Windows Server 2025...

 

I understood perfectly what you wrote, I was just "thinking aloud" about what that option really meant for users.

Probably isn't exactly the feature stolen since vista, but better than nothing.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

need to check if it boots in UEFI mode now



boots fine, they fixed it

 

windows11.0-kb5037133-x64_LCU_1100.1.0.msu is compatible with this Server build now
but one weird thing: it wasn't integrated into winre.wim

Code:

============================================================
Updating winre.wim ...
============================================================

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Mounting image
[==========================100.0%==========================]
The operation completed successfully.

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Image Version: 10.0.26080.1

Processing 1 of 1 - Adding package Package_for_ServicingStack_1100~31bf3856ad364e35~amd64~~26080.1100.1.3
[==========================100.0%==========================]
The changes due to package Package_for_ServicingStack_1100 requires the current servicing session to be reloaded.
All the packages will be processed again.
The operation completed successfully.

windows11.0-kb5037133-x64_LCU_1100.1.0.msu

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Image Version: 10.0.26080.1

Processing 1 of 1 -
The operation completed successfully.

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Image Version: 10.0.26080.1

[==========================100.0%==========================]
The operation completed successfully.

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Image Version: 10.0.26080.1

[==========================100.0%==========================]
The operation completed successfully.

Deployment Image Servicing and Management tool
Version: 10.0.25398.1

Image File : F:\W10UI_10.39\winre.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.

"winre.wim" original size: 515222 KiB
Using LZX compression with 6 threads
Archiving file data: 1290 MiB of 1290 MiB (100%) done
"winre.wim" optimized size: 500716 KiB
Space saved: 14505 KiB

p.s. LCU reinstallation after cleanup is still broken on client build, so avoid it here as well

 

Open-Shell works good. I don't use StartIsBack.

 

updated via windows updates from 26060 to 26080. no issues.

 

Copilot is back and... refuses to be turned off/removed. The command line trick/registry edit no longer works, and it ignores the group policy to disable it.
Hearing this has happened in regular 11 now too.

 

Not to mention the 500+ MB wasted in edge webview (which is in system32, not program files, since few builds) and isn't easily removable, until some script genius comes out with a solution. Add this to 2GB wasted by edgium and we have the definition of bloat moved to the next level.

 

Two issues seem to persist with this one - the custom mouse pointer issue, although the "busy" one now seems to be what upsets it and has the white box problem, and the print screen clipping tool needing sometimes several presses or clicks to get it to show up. Beyond that... we're definitely getting close to "done" now.

 

I still can't figure out how this works. I don't get system level updates, only silly updates like their antivirus suite.

 

In order to get build updates you have to sign in as a insider.

 

Never been an insider in my life



Perhaps it's funny that it says Windows 11 not Server 11 / Server 2025