This forces Server 2022 to behave like a client OS for the Startup tab.
Contrary to what the message implies, this is . It’s a design choice by Microsoft, stemming from a fundamental difference between client Windows (10/11) and Windows Server.
The Task Manager message will still appear, but your custom startup item will work. Task Manager simply reports that no system-wide enabled startup items exist.
Yes. If you’re running a Remote Desktop Session Host (RDSH), a Citrix server, or a shared workstation environment on Server 2022, you may legitimately need per-user startup applications. startup items are not enabled on this system server 2022
Again, this bypasses the Task Manager UI but does not change the informational message.
On Windows 10/11, the Task Manager’s lists user-specific startup items from:
Example PowerShell command:
For 90% of admins, the best fix is —just ignore it and manage startup processes via services. For RDS or VDI hosts, use the registry tweak above.
The critical question: Should you enable startup items?
The message "Startup items are not enabled on this system server 2022" is not a call to action—it is a notification that you are running a secure, server-optimized operating system. Unlike client Windows, Server 2022 does not encourage user-space auto-start applications, and Task Manager simply reflects that reality. This forces Server 2022 to behave like a
Configure Startup Applications in Windows - Microsoft Support
“Startup items are not enabled on this system.”