1k_scanner is not a document scanner. It is a Rust+egui based multi-market, multi-timeframe trading scanning app.

When installation fails, most people lose time in random trial-and-error. The better approach is simple: short, reproducible checks in a fixed order. This guide helps you recover installation first, then move directly into a real first-scan workflow.

1) Most install failures fall into 4 buckets

Check these in order:

1. Execution permission/security warning (macOS Gatekeeper, Windows SmartScreen)
2. Download file condition (corrupt, partial, outdated)
3. Network/time sync (license verification loops)
4. Missing post-install validation (installed, but no workflow verification)

Do not change everything at once. Test one bucket at a time.

2) macOS fastest path

1. App icon right-click → Open
2. If blocked: System Settings → Privacy & Security → Open Anyway
3. If “damaged app” keeps appearing, run:

1

xattr -dr com.apple.quarantine /Applications/1K_Scanner.app

Then relaunch.

If download integrity is uncertain, re-download and verify SHA-256 before retrying.

3) Windows minimal path

• SmartScreen warning: More info → Run anyway
• Admin privilege is usually unnecessary.
• If login/license repeatedly fails after install, verify VPN/proxy/firewall and system time first.

The goal is not over-granting permissions; it is restoring a clean network path.

4) 3-minute post-install validation: run → scan → focus → record

After installation, confirm real usability with this sequence:

1. Run: load template (Cmd/Ctrl + L)
2. Scan: dense grid for broad pass (Cmd/Ctrl + 7)
3. Focus: expanded/single chart (Cmd/Ctrl + 8, Space)
4. Record: save evidence in Check Note (V, N)

Completing these steps moves you from “installed” to “operational.”

5) Validate the visual model first: rows and columns

In 1k_scanner, read the grid as:

• Rows = timeframes
• Columns = symbols

One column gives one symbol’s MTF story from top to bottom. If this structure is clear, your scanning mindset—compressing candidates from the whole market—starts working immediately.

6) Keep indicator interpretation simple: EMA/NRZ + consensus

Right after installation, focus on “is it working as expected?”

• EMA: persistence of trend flow
• NRZ(Narrow Range Zone): hold vs break reference
• when multiple signals align, chart frames show green/red emphasis.

Use consensus emphasis as candidate compression, not as a one-click execution command.

7) Close with repeatability: Check Note + template routine

A successful setup means you can reproduce the same workspace next session.

1. choose Grid Size, Timeframes per row, Exchange, then run Generate Grid Template
2. save before session end with F12
3. reload next session with Cmd/Ctrl + L
4. add evidence with V, batch-review via N

With this routine, install success naturally becomes execution readiness.

8) Final one-page checklist

If all items below pass, onboarding is complete:

• Open Anyway (macOS) or Run anyway (Windows)
• network/time sync checked
• Cmd/Ctrl + 7, Cmd/Ctrl + 8, Space toggles verified
• grid model verified (rows=timeframes, columns=symbols)
• EMA/NRZ observation + consensus frame color (green/red) verified
• Check Note flow verified with V, N
• template generated, saved with F12, loaded by Cmd/Ctrl + L

The goal of install troubleshooting is not “the app opens.” It is reaching a state where you can start candidate compression and observation routines immediately.