If Windows has just shown you a blue box reading “Windows protected your PC” after downloading one of our tools, nothing is wrong with your computer and nothing is wrong with the file. This page explains exactly what that warning means, why our downloads trigger it, and how to verify for yourself that the file you have is the file we published.
What the warning actually says
Microsoft Defender SmartScreen checks every executable you download against a reputation database. If it has not seen that exact file, from that exact publisher, enough times before, it shows the warning. It is not telling you the file is malicious. It is telling you the file is unfamiliar.
That distinction matters, because reputation is earned by download volume and by a paid code-signing certificate. A free utility from a small independent publisher starts at zero on both counts, and a brand-new release resets part of it again.
Why our builds are unsigned
We will be straight about this: our Windows applications are not code-signed. A certificate that meaningfully improves SmartScreen reputation is an ongoing annual cost, and for software we give away for free with no advertising and no bundled installers, we decided that money is better not spent. That is a deliberate choice, not an oversight.
The trade-off is that you see a warning, and you have to take our word for it — or, better, not take our word for it and check instead. The rest of this page is how you check.
Verify the file yourself in about ten seconds
Every file we publish has a SHA-256 hash — a fingerprint that changes completely if even one byte of the file changes. Compare the hash of your downloaded file against the list below. If they match, you have exactly the file we built. If they do not match, delete it and download again from the official link.
Open PowerShell, and run:
Get-FileHash -Algorithm SHA256 "$env:USERPROFILE\Downloads\PDFGeekSetup.exe"Change the filename to whichever file you downloaded. Compare the Hash value it prints with the matching row below. Case does not matter.
Current release hashes
| File | Version | SHA-256 |
|---|---|---|
| AppGeekSetup.exe | 1.1.3 | b6060e5c1a7cb230ba0f5d3dda70edee54d69f31d6a45259636c12953f799806 |
| AppGeek.exe (portable) | 1.1.3 | 1c4a04c7551e72e751719a01db41900b13f7eaea15a96fffd59118688d1243ba |
| AppGeek-light.exe | 1.1.3 | a689d135869eb00c8148d73c90f5de64a2d64887a0148766d999b09f707c49db |
| CleanGeekSetup.exe | 1.0.4 | 3dd2917f6e5b9a98f3f581f6e46741e0f15212ef914fa6917502621045d567eb |
| CleanGeek-portable.exe | 1.0.4 | 274c45caecc3e4b767da737d0efe3336619adac9de058e21c175ea2a6c1f5295 |
| DiskGeekSetup.exe | 1.1.0 | ef605542940caa201cfb0f0c52c1cdc206d379fdbbe933f2dac2f82edca859ea |
| DriverGeekSetup.exe | 1.1.1 | f2add8e1e5278e1c14f175fe0e916a5cc7f624881405e8bc08eeaa5db63bb0bd |
| DriverGeek-portable.exe | 1.1.1 | b4de7c59cae7629feaf125e452b0d0392c09e82cf5b67fe888d8bcd458df51f0 |
| PDFGeekSetup.exe | 1.1.1 | 97d137d53ef00625e2135db09909686863aa1306a1078e83fb6c54a97229a521 |
| PDFGeek.exe (portable) | 1.1.1 | 00baac7e3832f42a46697a593c0d999ece84c491365ca79e9f561d54b899eac6 |
| Ultimate-Settings-Panel.zip | 8.0.4 | 20f59d823894710d8e59f6927bd0b2b5ea955b8ecf52f9c532d7523709fa2f65 |
You can also cross-check any of these against the SHA256SUMS.txt file attached to the matching GitHub release, and against the file’s digest shown by GitHub itself.
Second opinion: scan it
Upload the file to VirusTotal and it will be checked by around seventy antivirus engines at once. Do not be alarmed by one or two engines flagging an unsigned installer — heuristic engines routinely flag any unsigned self-extracting binary. What you are looking for is the overall pattern, and the ability to compare the hash VirusTotal reports with the table above.
What we do instead of buying a certificate
- The source is public. Every application on this site has its full source on our GitHub organisation. You can read what it does before you run it.
- The builds are produced by public CI. Releases are compiled by GitHub Actions from the tagged commit, not uploaded by hand from someone’s laptop, and the workflow file is in the repository alongside the code.
- We publish hashes with every release, in a
SHA256SUMS.txtfile attached to the release itself. - We report false positives. Each new release is submitted to Microsoft’s security intelligence portal so that incorrect detections get corrected at source.
- No bundling, no adware, nothing running in the background. Our installers install one application and nothing else.
What we will never ask you to do
We will never tell you to turn off SmartScreen, disable Windows Defender, or add an exclusion for our folder. Any site that tells you to disable your security software in order to install its free utility is telling you something about itself. Leave your protections on. Verify the hash instead — it is a stronger check than the warning you are bypassing, and it costs you ten seconds.
If you are ever unsure about a file that claims to come from us, the safest thing to do is delete it and download again from the product page on this site or from our GitHub releases. If something still looks wrong, get in touch and we will look at it.