PDF Insight for Windows: A Signed Installer, and How to Check It Yourself

Short answer: PDF Insight 0.4.2 ships a signed Windows installer — PDF-Insight-Setup-0.4.2.exe, about 186 MB, for 64-bit Windows 10 and 11. Before you run it, you can confirm who published it without trusting this page: right-click the file → Properties → Digital Signatures, or run Get-AuthenticodeSignature in PowerShell and check that the status is Valid, the chain reaches a Microsoft ID Verified Code Signing certificate authority, and the signature is timestamped. The exact commands are below.

For a few weeks the Windows download on this site was a "email us" link rather than a button. This page explains what was wrong, what changed, and — more usefully than either — how to verify any installer that is about to touch your clients' tax files.

Why Windows is the platform that matters here

A Canadian tax practice runs on Windows, not by preference but by dependency. The desktop preparation suites simply do not ship anything else. TaxCycle's own system requirements list Windows 11, 64-bit, Windows Server 2022 and Windows Server 2019, with no macOS entry anywhere on the page (TaxCycle — System Requirements). Intuit's ProFile is blunter still:

"ProFile requires operating system Windows 11 (recommended), Windows 10 (version 1607 or later), Windows Server 2016 and 2019 … Apple™ products are not supported."

— Intuit ProFile, System requirements

So the machine where a T1 actually gets prepared is a Windows machine. A tool that organizes the documents feeding that return has to live on the same desk. Shipping Mac-first was our decision, not the market's.

What was wrong: the right kind of signature, the wrong ecosystem

The earlier Windows build was signed. It was signed with an Apple Developer ID certificate — the identity that makes a Mac app open without a warning. Applied to a Windows .exe, that signature is technically well-formed and completely meaningless: Windows does not trust Apple's code-signing roots for Authenticode. The result on a real machine was a Microsoft Defender SmartScreen block.

Microsoft describes the mechanism plainly:

"It also provides reputation checks for apps, checking downloaded programs and the digital signature used to sign a file. If a URL, a file, an app, or a certificate has an established reputation, users don't see any warnings. If there's no reputation, the item is marked as a higher risk and presents a warning to the user."

— Microsoft, Microsoft Defender SmartScreen overview

We took the download offline instead of leaving it up with instructions to click past the warning. Teaching an accountant to override a security prompt in order to install a document tool is a bad trade for everyone: the habit outlives the install.

What changed in 0.4.2

The Windows installer is now signed in our build pipeline through Microsoft's managed signing service, which Microsoft describes as "a Microsoft fully managed, end-to-end signing solution that simplifies the certificate signing process and helps partner developers more easily build and distribute applications" (Microsoft — What is Artifact Signing?). Three properties matter to you rather than to us:

• The chain ends somewhere Windows trusts. The certificate chains to a Microsoft ID Verified Code Signing certificate authority, not to an Apple root.
• The signature is timestamped. It stays verifiable after the signing certificate itself expires.
• No human holds the key. Signing happens inside the release pipeline against a hardware-backed key; there is no certificate file on a laptop to be copied or lost.

How to verify the installer yourself

Do this before running it. It takes about fifteen seconds and it is the same check worth running on any installer you let near client data.

Option 1 — File properties

1. Right-click PDF-Insight-Setup-0.4.2.exe → Properties.
2. Open the Digital Signatures tab. If the tab is missing, the file is unsigned — stop there.
3. Select the signature → Details → View Certificate → Certification Path, and confirm the chain reaches a Microsoft ID Verified Code Signing authority.

Option 2 — PowerShell

In the folder where you saved the file:

Get-AuthenticodeSignature .\PDF-Insight-Setup-0.4.2.exe | Format-List Status, StatusMessage, SignerCertificate, TimeStamperCertificate

What you want to see: Status : Valid, a signer certificate issued by a Microsoft ID Verified Code Signing CA, and a non-empty timestamper certificate. Anything reporting NotSigned, HashMismatch or UnknownError means the file you have is not the file we published — delete it and download again from pdf-insight.com.

What you get once it is installed

PDF Insight takes the pile a client sends you — T4s, RL-1s, an RL-31 photographed at an angle, RRSP receipts, the PDF that is actually three documents in one — and produces a single ordered, bookmarked, review-ready PDF per client. Classification, OCR and merging all run on your machine. In the default local tier nothing is uploaded; once the local AI engine is installed the app works with the network switched off.

The point is narrow. The return is already electronic: in the 2025 tax-filing season the CRA processed 33,839,390 individual returns, 93% of them filed electronically — 60% through EFILE by preparers, 33% through NETFILE, and only 7% on paper (CRA — individual income tax return statistics). The filing takes minutes. The documents that justify it still arrive as email attachments and phone photos, and assembling them is the part still done by hand.

First run, in order

1. Download and install the signed .exe (verify it first, per above).
2. Install the free local AI engine when the app prompts — the link is in the app. This is the one step that needs the internet.
3. Point PDF Insight at a client folder, say in plain language how you want it ordered, and export one merged PDF.

The trial is 14 days with no card. If it does not save you time on the first real client folder you try, it will not save you time on the hundredth.

Current versions, stated plainly

macOS is deliberately one version behind: the 0.4.2 Mac build is waiting on an Apple Developer agreement renewal before it can be notarized, and an un-notarized Mac build would be the same mistake in the opposite direction. 0.4.1 is signed, notarized and current for macOS users until that clears.