Check your office computer in 3 steps DRAFT

Free and read-only. It looks at security settings on one Windows computer. It changes nothing, and your results stay on that computer.

Want to start without downloading anything? Try the domain check first. It runs in your browser and reads the public email settings of your office domain (mail provider, SPF, DMARC, and DKIM for common selectors). The domain you type is looked up through Cloudflare's public DNS service; it is not sent to WispBinder. It does not look at your computers: for that, use the 3 steps below.

1Download

Download the free Windows check

The file is called WispBinder-Check.cmd. It goes to your Downloads folder.

Your browser may warn that the file "could harm your device". Click Keep (in some browsers it is under … or See more). The warning appears because the file is a script that is not code-signed yet, not because something was found in it.

Edge Downloads panel: WispBinder-Check.cmd could harm your device. Do you want to keep it anyway? Buttons Keep and Delete. — Edge asks whether to keep the file: click Keep.

2Open it and click "Yes"

Double-click WispBinder-Check.cmd in your Downloads folder (or click Open file in the browser's download list).

Windows shows "Open File – Security Warning" with Publisher: Unknown Publisher, because the file is not code-signed yet. Click Run.

Windows dialog Open File - Security Warning: The publisher could not be verified. Name WispBinder-Check.cmd in Downloads, Publisher Unknown Publisher, buttons Run and Cancel. — Security warning: click Run.

Then Windows asks "Do you want to allow this app to make changes to your device?" for Windows Command Processor. Click Yes, then wait one or two minutes.

Two black windows are now open for a short time: the first one shows how long it has been waiting (it stops waiting after 6 minutes), and a second one, marked Administrator, runs the check and closes by itself. Both are expected; you do not need to type anything in them.

User Account Control window: Do you want to allow this app to make changes to your device? Windows Command Processor, Verified publisher Microsoft Windows, buttons Yes and No. — Windows permission window: click Yes.

On some computers a blue window "Windows protected your PC" appears instead. Click More info, then Run anyway. To read or verify the file first, see "For IT staff" below.

If your antivirus stops the check: some antivirus programs (for example Bitdefender) may stop it, because it is a script that asks for administrator permission. If that happens, your antivirus is doing its job: the check did not change any settings on your computer, and your antivirus may have removed the downloaded file, which is fine. Please do not turn your antivirus off, and do not add an exception for this file. Contact us and we will help you with the next step.

3Drag your result file onto the page

When the check is done, two windows open by themselves: the WispBinder results page in your browser, and your WispBinder-Results folder with the result file highlighted.

The first WispBinder window after the check: the line Waiting for the check: 0:10 so far. This window stops waiting in 5:50, then Done. Two windows are now open, and Press any key to close this window. — When the check is done, the first window says Done.

Drag the highlighted file onto the results page. You will see what was found and what to do next. The file is read inside your browser and is not uploaded.

The WispBinder-Results folder with one result file highlighted, open in front of the WispBinder results page in Edge. The file name is hidden in this picture. — The results folder opens in front of the results page.

If dragging is awkward, click Choose the file on the results page instead, open the WispBinder-Results folder on your Desktop and pick the file.

The Open dialog from the results page, in the WispBinder-Results folder, with the result file selected and the Open button. — Or click Choose the file and open it.

The results page: script fingerprint matches published version 0.2.2-draft, and three boxes: 2 Need your action, 3 Need written confirmation, 11 Detected. The computer name is hidden. — Your summary, with the fingerprint check of the script.

The action list: two items not detected, W02 full-disk encryption (BitLocker) and W09 daily user works without administrator rights, each with what to do. Account names are hidden. — The action list tells you what to do first.

What the check does: reads settings such as disk encryption, antivirus, updates, screen lock, accounts, backups and remote-access software. What it does not do: it does not change settings, read your documents or client files, or send your results anywhere.

Tested so far: earlier launcher versions on Windows (v1 on 1 computer with Windows 11 Home; v3 on 1 Windows computer, 2 Nov 2026; v6 on 1 Windows 11 test computer, a virtual machine with Microsoft Edge, 3 Nov 2026, where the check completed, the waiting line showed the time, the time-limit message was confirmed with a test copy that stops waiting after 1 minute, and the security warning appeared twice). This version (v7): on the same Windows 11 test computer, 3–4 Nov 2026, with the file marked as downloaded from the internet, the security warning appeared once, the check completed after Yes, and clicking No stopped it cleanly. v7 changes only how the check asks for administrator permission; its waiting and time-limit steps are the same as v6. Pictures on this page are from the v6 test (the windows look the same in v7); account and computer names hidden.

For IT staff: read and verify the file

The launcher is a plain text file: open it in Notepad to read all of it. The check script inside it is identical to wisp-check.ps1; its SHA-256 is listed in releases.json and SHA256SUMS.txt. Before running the script, the launcher compares the script's SHA-256 with the value written in the launcher.

These hashes show whether a file was damaged or changed after it was published (an integrity check). They do not prove who made the file. The file is not code-signed yet.

Launcher v7, SHA-256: BFAB2CB0170AE8FA380196370BDC60EF73077B0218235BBA5FF88C5C888B4884

Prefer to run the script yourself? See verifying the script.

Questions, or prefer that we guide you on a call? Contact us.

Describes settings detected at the time of the check. Not an audit, not a certification, not legal advice.