Mountain Duck Auto Start warning #619
Description
Running Windows "debloat"-scripts might cause Windows to malfunction, i.e. packaged applications aren't automatically started on startup anymore.
This can be easily checked on a non-working system by running the PowerShell command
Get-Item HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System On a working system:
Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies Name Property ---- -------- System ConsentPromptBehaviorAdmin : 5 ConsentPromptBehaviorEnhancedAdmin : 1 ConsentPromptBehaviorUser : 3 DSCAutomationHostEnabled : 2 EnableCursorSuppression : 1 EnableFullTrustStartupTasks : 2 EnableInstallerDetection : 1 EnableLUA : 1 EnableSecureUIAPaths : 1 EnableUIADesktopToggle : 0 EnableUwpStartupTasks : 2 EnableVirtualization : 1 PromptOnSecureDesktop : 1 SupportFullTrustStartupTasks : 1 SupportUwpStartupTasks : 1 TypeOfAdminApprovalMode : 1 ValidateAdminCodeSignatures : 0 dontdisplaylastusername : 0 legalnoticecaption : legalnoticetext : scforceoption : 0 shutdownwithoutlogon : 1 undockwithoutlogon : 1 SoftwareSASGeneration : 1 Crucially, the two entries for packaged autostart to work (in Mountain Ducks case) are EnableFullTrustStartupTasks: 2 and SupportFullTrustStartupTasks: 1, these can be recreated to get Mountain Duck to automatically restart again.
Alternatively, reinstall Windows without debloating.