Concrete fixes for installer warnings, token validation issues, missing zones, thin scan coverage, export problems, and platform-specific runtime failures.
- Platform warning handling
- Workspace and token diagnosis
- Scan coverage interpretation
- Export and runtime recovery
Applies to
WindowsmacOSLinux
Covers
TroubleshootingSetupScansSupport
Troubleshooting
Windows shows SmartScreen or Unknown publisher
If Windows shows a warning on an unsigned beta build:
- Confirm the installer came from the official release path.
- Verify the version matches the public download page.
- Follow the documented Windows install flow before assuming the build is compromised.
macOS blocks the app
Beta builds are not notarized.
If macOS blocks launch, run:
xattr -cr "/path/to/CF Guard Desk.app"
Then try launching again.
Linux install choice is unclear
Choose the package that matches your distro.
- prefer
.debon Debian or Ubuntu - prefer
.rpmon Fedora or RHEL-derived systems - use AppImage as the portable fallback
I validated the token but expected zones are missing
Check, in order:
- the token is tied to the intended account
- the token scope actually allows zone discovery
- the connection is saved in the workspace you think it is
The scan completed but coverage looks thin
That usually means one of these is true:
- the token lacks access to some Cloudflare surfaces
- analytics coverage is partial
- the selected scan profile was intentionally lighter
- the zone genuinely has little signal for that category
Visibility gaps are correct behavior when the app cannot inspect a desired surface confidently.
Exports failed or look incomplete
Confirm:
- the scan completed successfully
- the active workspace is unlocked
- the destination path is writable
- the export reflects the selected scan snapshot and not an earlier run