About Security Software False Positives

Problem Description

After downloading WSL Dashboard's .exe installer or .zip archive, Windows Defender or other antivirus software may pop up a security warning, flag the file as risky, or even block and delete it.

Why Does This Happen?

This is a false positive — the file does not actually carry a virus.

The root cause: this project has not purchased an EV (Extended Validation) code signing certificate.

What Is a Code Signing Certificate?

A code signing certificate is used to digitally sign executables, proving that the file comes from a trusted publisher and has not been tampered with. Windows applies stricter security checks to programs that are unsigned or signed with an ordinary certificate.

Differences Between Certificate Types

Certificate type	Price	SmartScreen policy
No signature	Free	Blocked outright, marked as "Unknown publisher"
Regular OV certificate	Hundreds of RMB/year	Still shows a warning; reputation must be built up
EV certificate	Thousands of RMB/year	Passes immediately, no warning

Programs not signed with an EV certificate are marked as unsafe by Windows SmartScreen by default, and antivirus software is more likely to treat them as potential threats.

About File Safety

Rest assured, this project's build process is completely transparent and auditable:

1. Open source code: All source code is hosted on GitHub; anyone can review it
2. Automated builds: The exe files are built automatically by GitHub Actions workflows on GitHub's servers, with no human intervention throughout the process
3. Traceable builds: Every build has a complete log record, viewable on the GitHub Actions page
4. Zero-touch release: Developers cannot insert any malicious code during the build; files are fully automated from build completion to release download

In short: the exe files have never passed through the developer's hands, so there is no possibility of "poisoning".

Solutions

Solution 1: Add a trust exception (recommended for regular users)

When Windows Defender blocks the file:

1. Open "Windows Security" → "Virus & threat protection"
2. Click "Protection history"
3. Find the blocked item, click "Actions" → "Allow"

Or add an exclusion before downloading:

1. Open "Windows Security" → "Virus & threat protection" → "Manage settings"
2. Scroll down to "Exclusions", click "Add or remove exclusions"
3. Add your download directory as an exclusion

Third-party antivirus software: add the downloaded file or directory to the trust list in the respective software.

Solution 2: Build from source (recommended for developers)

If you still have concerns about the prebuilt binaries, you can clone the source and compile it locally:

# Clone the repository
git clone https://github.com/owu/wsl-dashboard.git
cd wsl-dashboard

# Build the Release version
cargo build --release

# The build output is in the target/release/ directory

This way you can be fully confident in the code that runs.

Solution 3: Purchase an EV certificate (note for developers)

Purchasing an EV code signing certificate can solve the false positive problem at the root, but it faces the following practical difficulties:

• High cost: an EV certificate costs thousands of RMB per year
• Ongoing cost: the certificate must be renewed annually — a long-term burden
• Project nature: WSL Dashboard is a non-profit open-source project and can hardly afford this expense

If you'd like to support the project's development, you can donate through the sponsorship channel on the project homepage to help the developer cover operational costs such as certificates.

Summary

• The file is blocked because of the missing EV code signing certificate — it is not a virus
• All build artifacts are generated automatically by GitHub Actions — the process is transparent and auditable
• Users can solve the problem by adding a whitelist exception or compiling it themselves
• Purchasing an EV certificate solves it at the root, but creates financial pressure for a non-profit project

Thank you for your understanding and support!