Prevent Screen Saver remembers your preferences between sessions using a small JSON settings file. When the app starts, it reads this file to decide whether to show the main window, whether to re-activate protection automatically, and which hotkey to register. All changes are written to disk automatically — there is no Save button.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/proteo5/Prevent-Screen-Saver/llms.txt
Use this file to discover all available pages before exploring further.
Settings File Location
The settings file is stored in your Windows user profile’s local application data folder:C:\Users\YourName\AppData\Local\PreventScreenSaver\settings.json. The directory is created automatically the first time settings are saved.
Full Settings Structure
settings.json
Settings are written automatically every time a value changes — for example, when you toggle protection, enable the hotkey, or change the startup registration. You never need to manually save.
Start with Windows
Enabling Start with Windows makes Prevent Screen Saver launch automatically each time you sign in to Windows.How the registry entry is written
How the registry entry is written
Enabling Start with Windows writes a string value to the Windows registry under:The value name is Disabling Start with Windows deletes this value. Because the key lives under
PreventScreenSaver and the stored data is the full quoted path to the executable, for example:HKCU (the current user hive), no administrator rights are required.The stored registry path is always the full quoted path to
PreventScreenSaver.exe. If you move the application to a different folder after enabling startup, disable and re-enable Start with Windows to update the path.Start Minimized
| Setting | Default | Description |
|---|---|---|
StartMinimized | true | When true, the app starts hidden in the system tray without displaying the main window. |
true (the default), launching the app — whether manually or via the Start with Windows registry entry — places it directly into the tray. The main window is never shown until you explicitly open it via Tray > Open.
Setting StartMinimized to false causes the main window to appear on screen when the app launches.
Last Protection Active
| Setting | Default | Description |
|---|---|---|
LastProtectionActive | false | When true at startup, the app attempts to re-activate protection automatically. |
LastProtectionActive is true when the app starts, it immediately calls StartProtection() to restore the previous active state. This means if you were running with protection active when you last used the app, it will be active again the next time the app launches — without any manual interaction.
How LastProtectionActive Is Maintained
The app keeps this value accurate automatically:
- Set to
truewhenever protection is activated (via tray, hotkey, or main window button). - Set to
falsewhenever protection is deactivated. - Set to
falseon a clean exit — protection always stops when you choose Tray > Exit, and the setting is updated before the app closes.
On a clean exit, the app explicitly saves
LastProtectionActive = false to disk before closing. This ensures that restarting the app after a normal exit begins in the Idle state, which is the safe default.Settings Reference
| Setting | Type | Default | Description |
|---|---|---|---|
StartMinimized | bool | true | Hide the main window on launch; show only the tray icon. |
LastProtectionActive | bool | false | Re-activate protection automatically on the next launch. |
HotkeyEnabled | bool | true | Register the global hotkey at startup. |
HotkeyPresetId | string | ctrl-alt-p | The key combination preset to use for the hotkey. |
