I have a couple legacy apps that run in Windows 8 compatibility. I used to be able to run them as startup apps in Windows 10 but they will not run as startup apps in Windows 11. They do run in Windows 11 after I have started up. Is there a way around this?
📎 AI Summary:
The thread discusses why legacy apps set to Windows 8 compatibility no longer launch automatically at startup in Windows 11, even though they work after the user manually starts them. The main solution offered is to avoid the normal Startup folder and instead create a Task Scheduler task triggered “at log on” with a delay and (if needed) “run with highest privileges,” ensuring the compatibility settings apply to the actual executable rather than only a shortcut. Overall, the sentiment is practical and mildly frustrated, with contributors framing the issue as a common Windows 11 startup behavior/quirk and offering a reliable workaround.
The thread discusses why legacy apps set to Windows 8 compatibility no longer launch automatically at startup in Windows 11, even though they work after the user manually starts them. The main solution offered is to avoid the normal Startup folder and instead create a Task Scheduler task triggered “at log on” with a delay and (if needed) “run with highest privileges,” ensuring the compatibility settings apply to the actual executable rather than only a shortcut. Overall, the sentiment is practical and mildly frustrated, with contributors framing the issue as a common Windows 11 startup behavior/quirk and offering a reliable workaround.
Solution
Hi Beppino46 — yes, this is a common Windows 11 quirk. The compatibility layer and/or elevation prompts can prevent legacy Win32 programs from launching reliably during the normal Startup sequence. The simplest, reliable workaround is to run the app from a Scheduled Task (trigger: At logon) — that lets you (a) delay the launch until the desktop is ready and (b) run elevated without a UAC prompt if configured correctly.
Below are a few options (GUI + command-line) and why they work.
Quick checklist (do these first)
Below are a few options (GUI + command-line) and why they work.
Quick checklist (do these first)
- Make sure the compatibility setting is applied to the actual .exe (right‑click the EXE → Properties → Compatibility → set “Run this program in compatibility mode for: Windows 8”). Applying it only to a shortcut can...
- Joined
- Mar 14, 2023
- Messages
- 114,159
Hi Beppino46 — yes, this is a common Windows 11 quirk. The compatibility layer and/or elevation prompts can prevent legacy Win32 programs from launching reliably during the normal Startup sequence. The simplest, reliable workaround is to run the app from a Scheduled Task (trigger: At logon) — that lets you (a) delay the launch until the desktop is ready and (b) run elevated without a UAC prompt if configured correctly.
Below are a few options (GUI + command-line) and why they work.
Quick checklist (do these first)
GUI steps (recommended)
Below are a few options (GUI + command-line) and why they work.
Quick checklist (do these first)
- Make sure the compatibility setting is applied to the actual .exe (right‑click the EXE → Properties → Compatibility → set “Run this program in compatibility mode for: Windows 8”). Applying it only to a shortcut can fail.
- If “Run this program as an administrator” is checked, that will trigger a UAC prompt at startup and block automatic start. Remove that check and use a Scheduled Task with elevated privileges instead (below).
GUI steps (recommended)
- Start → type Task Scheduler → open it.
- Right‑click Task Scheduler Library → Create Task (not “Create Basic Task”).
- General tab:
- Name: Start My Legacy App
- Choose “Run only when user is logged on” if the app shows UI. If it must run elevated, check “Run with highest privileges.”
- Configure for: Windows 10 / Windows 11 (choose the latest option available).
- Triggers tab:
- New → Begin the task: “At log on”
- Select the specific user or “Any user” as needed.
- (Important) Check “Delay task for:” and choose 30 seconds–1 minute. This lets Windows finish startup and apply compatibility shims before the app runs.
- OK.
- Actions tab:
- New → Action: Start a program
- Program/script: full path to your app EXE (e.g., C:\Program Files\OldApp\old.exe)
- Start in (optional): folder containing the EXE
- OK.
- Conditions / Settings: adjust as needed (uncheck “Stop the task if it runs longer than…” if the app runs long).
- OK to save. Test by right‑click → Run. Then sign out/back in to confirm it starts automatically.
- Scheduled Task runs after logon and can be delayed so compatibility shims and user shell are fully available.
- “Run with highest privileges” in a task that runs for the logged-on user can start elevated without showing a UAC prompt at login (avoids blocking).
- Create a small script that waits then launches the app:
- PowerShell example:
- Start-Sleep -Seconds 30
- Start-Process "C:\Path\to\app.exe"
- Save as StartLegacyApp.ps1 or wrap in a .cmd and put a shortcut to it into shell:startup (Win+R → shell:startup).
- Note: if the app requires elevation, the Startup folder will cause a UAC prompt and fail to auto-start — Task Scheduler is preferred in that case.
- If the app depends on network or services, choose a trigger like “At log on” plus a longer delay, or add a trigger “On connection to user session” / “On workstation unlock”.
- Check Task History in Task Scheduler (enable history) to see failures.
- If you used “Run whether user is logged on or not”, Windows will prompt for credentials when creating the task — storing credentials has security implications; prefer “Run only when user is logged on” for apps that display UI.
- If nothing runs at all at startup, try disabling Fast Startup in Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → uncheck “Turn on fast startup”.
- the full path to the EXE(s),
- whether they require admin rights or show UI,
and I’ll provide the exact Task Scheduler settings or a ready-made schtasks / PowerShell command you can paste to create the task.
jensendickens
Member
- Joined
- Nov 9, 2025
- Messages
- 5
I completely agree with your concerns regarding legacy apps and their compatibility with Windows 11. It's frustrating when applications that worked seamlessly in previous versions of Windows suddenly face issues in a new environment. Windows 11 has introduced several changes, particularly in how it manages startup applications and system compatibility, which can affect older software.I have a couple legacy apps that run in Windows 8 compatibility. I used to be able to run them as startup apps in Windows 10 but they will not run as startup apps in Windows 11. They do run in Windows 11 after I have started up. Is there a way around this?