If S.A.K. Utility will not start, the usual causes are a Windows SmartScreen warning, a data folder the app cannot write to, a ZIP that was not fully extracted, or a copy already running. Each has a quick fix below. S.A.K. Utility is portable, so it needs its whole folder together, and permission to write in that folder.
When to use this
Use this when double-clicking sak_utility.exe shows a warning or an error, or seems to do nothing.
What you need
- The folder you extracted from the ZIP.
- 64-bit Windows 11 or Windows 10. The release is tested on Windows 11. Windows 10 is not part of release testing, and very old builds of it will not work.
You do not need to install anything. There is no installer, and the Microsoft runtime files the app needs come in the ZIP.
Steps
Windows says "Windows protected your PC"
This is SmartScreen, a Windows check on newly downloaded programs. It warns when a file is not yet widely known. A new release can trigger it even when it is properly signed.
- Make sure you downloaded it from the official link on sakutility.com or the project's GitHub releases.
- In the blue window, click More info.
- Check the publisher shown. It should read Randy Northrup.
- Click Run anyway.
To check a file yourself, right-click sak_utility.exe, choose Properties, and open Digital Signatures. Each release also lists its file fingerprints in SHA256SUMS.txt beside the download.
If the publisher is missing or is someone else, or the file came from anywhere but the official links, do not run it. Delete it and download a fresh copy.
If there is no Run anyway button, an administrator or company policy has blocked the program on this PC. Ask whoever manages it.
The "data folder" error
The window is titled S.A.K. Utility: data folder, and says the folder is not writable. The app keeps its settings, logs, and temporary files in a data folder beside the program, and it will not start without one it can write to. It does not fall back to another location, so it never scatters files around the PC without telling you.
- Read the path in the message.
- Move the whole S.A.K. Utility folder somewhere you can write, such as your Documents folder or a USB drive.
- Do not keep it in
C:\Program Files, on a write-protected USB drive, on a read-only disc, or in a folder your account cannot change. - Start it again.
If you must keep it where it is, give your account permission to write to that folder, or run it with an account that has permission.
A missing DLL, or an error about Qt
Errors such as "Qt6Core.dll was not found" or "no Qt platform plugin could be initialized" usually mean the program is separated from its files.
- Do not run it from inside the ZIP window. Right-click the ZIP and choose Extract All, then open the new folder.
- Keep everything together. Do not move
sak_utility.exeout of its folder on its own, or make a copy of it alone. Make a shortcut instead. - If files may be missing, delete the folder, and extract a fresh download.
Security software can also move a file into quarantine, with the same result. Check its history, and restore the file only if you got it from the official links.
Nothing happens when you double-click
Only one copy runs at a time from each folder. If one is already running, a second launch brings the first window forward and then closes. No error appears.
- Look for S.A.K. Utility on the taskbar, or behind other windows.
- If you cannot find it, open Task Manager, find
sak_utility.exe, and end it. Then start the app again.
Startup can also take several seconds on a slow PC, or a PC with thousands of fonts. Wait a moment before you try again.
"Did not close" after Run as Admin
The message says the window that started the administrator copy did not close in time. Run as Admin restarts the app, and the new copy waits for the old one to close first.
- Close the open S.A.K. Utility window.
- Finish or cancel anything it is doing.
- Start the app and use Run as Admin again.
A "Fatal Error" or "Initialization Error" window
S.A.K. Utility -- Fatal Error means the app hit a problem it could not recover from. Initialization Error with "Failed to initialize logger" means it could not set up its log files, usually because of the same write problem as the data folder error.
- Fix any write problem first, as above.
- Try a fresh copy in a new folder.
- If it still fails, report it. See the help guide below, and include the files listed there.
How it works
At each start, S.A.K. Utility creates data beside the program and tests that it can write a file there. It then checks that no other copy is using that folder, sets up its logs, and opens the window. A separate copy in a different folder counts as a separate app, with its own settings.
If the app crashes, it tries to save a crash record in data\crashes. Logs are in data\logs.
Good to know
- Running as administrator is not the usual fix. The app runs as a standard user, and asks for more only when a tool needs it.
- Moving the folder keeps your settings, because they live inside it. Your saved OpenAI key will still work on the same Windows account, but not on another.