How to Stop Server Manager Opening Automatically on Windows Server 2022/2025

Server Manager launching on every login is default behaviour going back many Server versions, and the fix is exactly the same on Server 2022 and 2025 as it was on 2016 — this one hasn’t changed, but it’s worth having documented against current version numbers.

Method 1: The checkbox (fastest)

While Server Manager is open, look at the bottom-left corner of the window for Do not start Server Manager automatically at logon, and tick it. That’s it — no restart needed, it takes effect on the next login.

Method 2: PowerShell (for remote/scripted setups)

If you’re configuring this on a Server Core install (no GUI to click a checkbox on) or want to script it across many servers:

Get-ScheduledTask -TaskName ServerManager | Disable-ScheduledTask

Server Manager’s auto-launch is implemented as a scheduled task (under Microsoft\Windows\Server Manager), so disabling that task has the same effect as unticking the box — this is the only option on Server Core, since there’s no Server Manager window to open in the first place.

To re-enable later:

Get-ScheduledTask -TaskName ServerManager | Enable-ScheduledTask

Method 3: Group Policy (for disabling across many servers centrally)

If you manage a fleet of servers and want this set consistently without touching each one individually:

1. Open Group Policy Management, edit (or create) a GPO linked to your servers’ OU.
2. Navigate to Computer Configuration > Administrative Templates > System > Server Manager.
3. Enable Do not display Server Manager automatically at logon.
4. Link the GPO to the relevant OU and let it apply on the next Group Policy refresh (or run gpupdate /force on a server to apply immediately for testing).

This is the best option if you’re provisioning servers at scale and don’t want to rely on someone remembering to tick the checkbox manually on each one.

If it comes back after Windows Update

Occasionally a cumulative update resets scheduled-task-based customisations. If Server Manager starts reappearing after a patching cycle, it’s worth checking the scheduled task state again rather than assuming the setting was somehow reverted by mistake — this is a known (if infrequent) side effect of some servicing stack updates touching default scheduled tasks.