You download a small tool, double-click it, and the operating system stops you. Windows says it "protected your PC". macOS says the app "cannot be opened because Apple cannot check it for malicious software". Neither message says the app is harmful, and neither says it is safe. They are telling you something narrower, and it helps to know what.
We have a direct interest in this subject. Some of our own desktop builds are not code-signed yet, and our product pages say so. This article explains what that means for anyone deciding whether to run them, or any other unsigned software.
What the warnings check
Both systems mark files that arrive from the internet. Windows attaches a hidden tag often called the Mark of the Web. macOS attaches a quarantine attribute. The first time you open a marked file, the system runs a check before the app starts.
Windows SmartScreen works largely on reputation. It looks at whether the file is signed, who signed it, and how many people have already run that publisher's software without trouble. A brand-new build from a small publisher has no reputation yet, so SmartScreen can warn about it even when nothing is wrong with it.
macOS Gatekeeper checks two things. The app should be signed with a Developer ID certificate that Apple issued to an identified developer, and it should be notarised, which means the developer submitted it to Apple for an automated malware scan before release. An app that lacks either is blocked on first launch.
What code signing proves, and what it does not
Signing a build does two useful things:
- It ties the file to a verified publisher identity, so you know who released it.
- It lets the system detect whether the file was changed after it was signed.
It does not prove the software is well behaved. Signed software can still be buggy, intrusive or malicious, and certificates are occasionally stolen or misused. The reverse is also true: a great deal of legitimate software from small teams and open-source projects is unsigned, because certificates cost money every year and involve an identity verification process.
So a warning means "the system cannot vouch for this file". It does not mean "this file is dangerous". The decision is left to you, which is why it is worth having a way to make it.
How to decide whether to open it
Ask the same few questions each time:
- Did you go looking for it? Software you chose and downloaded deliberately is a very different case from an attachment or a link that arrived unprompted. Never override a warning for something you did not seek out.
- Did it come from the publisher's own site? Check the address bar. Download from the official page over HTTPS, not from an aggregator or a search advertisement.
- Does the publisher say what to expect? A careful publisher states on the download page that the build is unsigned and that the warning will appear. A warning that nobody mentioned deserves more suspicion.
- Can you verify the file? If the page publishes a SHA-256 checksum, check it. A match confirms your copy is the file the publisher released.
- What does it need? A small utility that asks for administrator rights, or for access it has no obvious use for, should make you stop.
- What machine is this? On a work computer, follow your organisation's policy and ask IT. On a show or production machine, test on something else first.
If the answers are unclear, do not open it. Nothing is lost by waiting and asking the publisher.
Opening a flagged app on Windows
When SmartScreen shows "Windows protected your PC":
- Select More info.
- Read the app name and the publisher line. An unsigned build shows the publisher as unknown.
- If you have decided to proceed, select Run anyway.
This approves that one file. It does not switch SmartScreen off, and you should leave it on.
Opening a flagged app on macOS
On recent versions of macOS:
- Try to open the app once and dismiss the warning.
- Open System Settings, then Privacy & Security.
- Scroll to the Security section, where the blocked app is listed, and select Open Anyway.
- Confirm with your password or Touch ID.
The button is only offered for a short period after the blocked attempt, so do this straight away. On older versions of macOS you could hold Control, click the app and choose Open instead. Apple removed that shortcut in macOS 15, so Settings is now the route.
As on Windows, this approves one app. Do not disable Gatekeeper as a whole to get one tool running.
Advice that makes things worse
Some instructions you will find online trade one prompt for a much larger risk:
- Turning off SmartScreen or Gatekeeper entirely. This removes the check for every future download, including the ones you did not mean to open.
- Running terminal commands you do not understand to strip the quarantine attribute from a file. If you cannot say what a command does, do not paste it.
- Running everything as administrator to make a warning go away. Most tools do not need it.
Where our own builds stand
Several of our free desktop tools are not code-signed at present, and their product pages state that Windows SmartScreen and macOS Gatekeeper may ask you to confirm the first launch. Where we publish a checksum, you can use it to confirm the file is ours before you approve it. If you would rather wait for signed builds, that is a reasonable choice.
The warning is doing its job when it makes you pause. The useful response is neither to click through automatically nor to refuse everything, but to spend a minute on the questions above.