You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling a "run once" startup item in the Startup Manager reported success but did nothing — the item still ran at the next boot. The scan lists both the Run and RunOnce registry keys, and SetEnabledAsync keyed purely off the entry's scope, so disabling a RunOnce entry wrote the "disabled" blob to …\Explorer\StartupApproved\Run\{name} and returned success. But Windows has no StartupApproved\RunOnce subkey and never consults StartupApproved for RunOnce keys, so the command still executed on the next boot while the UI showed "Disabled" — a system-mutation toggle that silently lied to the (non-technical) user. SetEnabledAsync now detects a RunOnce entry and returns a truthful non-success with a plain-language message ("Run-once item — runs next boot, then removes itself; cannot be disabled here.") instead of writing an ineffective blob. The item stays visible so the user still knows it's scheduled to run once.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
SysManager 1.52.95 is out!
Download from GitHub Releases
[1.52.95] - 2026-07-11
Fixed
RunandRunOnceregistry keys, andSetEnabledAsynckeyed purely off the entry's scope, so disabling aRunOnceentry wrote the "disabled" blob to…\Explorer\StartupApproved\Run\{name}and returned success. But Windows has noStartupApproved\RunOncesubkey and never consultsStartupApprovedforRunOncekeys, so the command still executed on the next boot while the UI showed "Disabled" — a system-mutation toggle that silently lied to the (non-technical) user.SetEnabledAsyncnow detects aRunOnceentry and returns a truthful non-success with a plain-language message ("Run-once item — runs next boot, then removes itself; cannot be disabled here.") instead of writing an ineffective blob. The item stays visible so the user still knows it's scheduled to run once.Verify the download
Expected SHA256:
5E01E39BAC90BA6C937039D1FAB10B81720ACBA619C7D2A0FFD89E921E181CE8Beta Was this translation helpful? Give feedback.
All reactions