Troubleshooting

Troubleshooting

The script says "Error: This script requires administrative privileges"

S1SS checks for administrator rights on launch. If not elevated:

1. Close the current window.
2. Open the Start menu, type PowerShell, right-click Windows PowerShell, and select Run as administrator.
3. Navigate to the script and run it again.

Alternatively, right-click saveSupport.ps1 and choose Run with PowerShell — note this does not automatically elevate; if file operations silently fail, use the elevated window method above instead.

Execution Policy

If you see an error like:

File cannot be loaded because running scripts is disabled on this system.

PowerShell's execution policy is blocking the script. The simplest fix for running a local script in an elevated window:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
.\saveSupport.ps1

-Scope Process applies only to this window session and does not change the system-wide policy permanently.

"No Steam ID directories found" or "Saves directory does not exist"

S1SS looks for saves at:

%USERPROFILE%\AppData\LocalLow\TVGS\Schedule I\Saves\

If this path does not exist:

• Confirm Schedule 1 is installed and has been launched at least once (the game creates the Saves directory on first run).
• Confirm the game was installed for the current Windows user account (not another user on the same machine).

If you have never created a save in-game, the Saves\<SteamID>\ path will be empty and S1SS will report no saves found.

Files don't move / backup appears to succeed but the vault is empty

This is typically caused by running without administrator privileges. The script's admin check currently prints a warning but does not forcibly exit — it continues and file operations may silently fail without elevation.

Fix: always run as administrator.

The vault entry I restored did not overwrite the game slot correctly

S1SS copies the vault folder contents into SaveGame_N using Copy-Item -Recurse -Force. If the target slot had extra files not present in the vault entry, those files remain. Schedule 1 loads whichever save data is present, so this should not normally cause problems, but if you encounter unexpected behavior:

1. Delete the target slot (D → Active → select the slot).
2. Restore again.

Known source bug: restore fails with a Copy-Item destination error

Set-RestorePath returns a plain string, but the restore code calls $restorePath.FullName on it. In PowerShell 5.1 a property access on a string returns $null, so Copy-Item receives a null destination and fails with an error about the destination path.

If restore throws a Copy-Item error and the vault entry looks correct, this is the cause. The fix belongs in the script code (replace $restorePath.FullName with $restorePath), not in your environment. Until a patched release is available, see the GitHub issues page.

Multiple Steam accounts on one machine

S1SS uses the first directory found inside TVGS\Schedule I\Saves\. If you have multiple Steam accounts, only the first account's saves are shown. There is no workaround in the current version — run the script while the intended account's Saves directory appears first in the folder listing.

Report a Bug

Open an issue on GitHub with:

• What you did
• What you expected
• What actually happened (copy the error message if any)
• Your Windows version and PowerShell version ($PSVersionTable in a PowerShell window)