First-launch warnings
The v2026.9.27 installers are not code-signed or notarized yet, so macOS and Windows each block the first launch until you allow the app once. This is expected for these builds — verify the SHA-256 first, then follow the steps for your OS.
1. Verify the download first
Compare the SHA-256 of the file you downloaded with the value shown on the download page:
# macOS
shasum -a 256 ~/Downloads/UsingOpen-Desktop-MacOS.dmg
# Linux
sha256sum ~/Downloads/UsingOpen-Desktop-Linux.AppImage# Windows PowerShell
Get-FileHash $HOME\Downloads\UsingOpen-Desktop-Windows.exe -Algorithm SHA256Only allow the app if the hash matches. If it doesn't, stop and email [email protected] — don't click through the warning.
2. macOS
macOS 15 (Sequoia) and later
- Drag UsingOpen Studio into Applications, then try to open it once. Dismiss the warning.
- Open System Settings → Privacy & Security and scroll to the Security section.
- Next to the message about UsingOpen Studio, click Open Anyway and authenticate with your password or Touch ID.
- Click Open in the final dialog. macOS remembers the choice.
macOS 14 and earlier
- In Finder, Control-click (or right-click) UsingOpen Studio and choose Open.
- Click Open in the confirmation dialog.


If macOS says the app “is damaged and can’t be opened”, the quarantine flag is set on an unsigned build. After confirming the SHA-256, clear it once in Terminal:
xattr -d com.apple.quarantine "/Applications/UsingOpen Studio.app"Apple's own guides: Safely open apps on your Mac and Open a Mac app from an unknown developer.
3. Windows
- Run
UsingOpen-Desktop-Windows.exe. - If “Windows protected your PC” appears, click More info, then Run anyway.
- If that button is missing, close the dialog, right-click the .exe → Properties → General → tick Unblock → Apply, then run it again.
- If Microsoft Defender shows a notification, open Windows Security → Virus & threat protection → Protection history, select the item, and choose Allow.
Smart App Control (Windows 11) can block the app without offering “Run anyway”. If your PC has it on, turn it off under Windows Security → App & browser control → Smart App Control. Microsoft notes that re-enabling it may require resetting Windows, so only do this after verifying the SHA-256.


Microsoft's docs: App & browser control, SmartScreen overview, Smart App Control FAQ.
Why this happens
Code signing and notarization need certificates that these builds don't have yet. Until the signed pipeline ships, Gatekeeper and SmartScreen will warn once per file. Don't disable either protection system-wide — verifying the SHA-256 and allowing the single app is the safe middle ground.
The one-line installers download the same unsigned builds, so the same warnings apply.