Installing and Updating Sally

Sally needs no installer. A release is a .zip file for your platform (x64, x86 or ARM64); unpack it to a folder you can write to, for example C:\Tools\Sally, and run sally.exe. Keep the plugins, toolbars and utils folders next to sally.exe. Your settings are kept per user, outside the folder, so an update never touches them.

To update from Sally:

Open Plugins/Check Version/Check For New Versions and click Check Now (Check Version can also check on its own at an interval you choose).
When a newer release is reported, click Install and Restart.
Sally downloads the release, checks it against the SHA-256 checksum published with it, unpacks it and asks you to confirm.
Every Sally window started from the same folder closes, the files are replaced, and Sally starts again and tells you how it went.

To update from a release you downloaded (also offline):

Download the release's .zip file for your platform and, if you can, its Sally-v<version>-SHA256SUMS.txt into the same folder.
Drop the .zip file onto utils\salupdate.exe in your Sally folder, or run utils\salupdate.exe <path to the .zip>.
The updater names the installed and the new version (and asks before installing an older one), says whether Sally is running, and asks once. Sally closes, the files are replaced, and Sally starts again.

--yes	Answers every question with Yes and runs without messages; errors are still shown. The outcome is written to the log (see below).
--install <folder>	Updates the Sally in that folder instead of the one the updater is in.

Run salupdate.exe without a file to undo an update that was interrupted, for example by a power failure.

What an update changes

Only the files of the release are replaced. Files that are not part of it, such as an exported configuration or files you added, are left alone.
Nothing is changed until the new files are ready, and if any file cannot be replaced, every file is put back exactly as it was.
Windows Explorer keeps Sally's shell extension (utils\salextx64.dll, or salextx86.dll or salextARM64.dll) loaded. The updater renames the loaded file aside, for example to salextx64.dll.sally-old, and puts the new one in its place; Sally deletes the old copy at a later start, once Explorer no longer uses it. No restart of Windows is needed.
A Sally folder under Program Files asks for administrator permission once, for replacing the files only.

Before a package is installed, the updater makes sure it is a Sally release for your processor and refuses a package that would write outside the Sally folder. A package that does not match its published SHA-256 checksum is refused; one without a checksum to compare with is installed only after you confirm.

Where to look if something goes wrong

The updater's log and its last result: %LOCALAPPDATA%\Sally\Update\salupdate.log and result.txt. Downloads are kept in the same folder until the update is done.
You can always update by hand: close Sally and unpack the new release over the Sally folder. If Windows reports salextx64.dll as in use, rename that file and copy again.
Sally 1.0.35 and older have no updater; update them by hand once.

Installing and Updating Sally

To update from Sally:

To update from a release you downloaded (also offline):

What an update changes

Where to look if something goes wrong

See Also