
Grok Bot
When F-Secure blocks Grok Bot local-exec on Windows
When F-Secure blocks Grok Bot local-exec on Windows
Grok Bot chat can work and Computers can show the PC as connected while every local Shell fails with unavailable / temporarily unreachable. On Windows with F-Secure, staff measured the failure as a delay past the ~10s agent wait (~12s with F-Secure on, ~1s with it fully off), not a dead connection. Thread: forum 171219 (mohitjain, Sep 10, 2026). Grok Bot 0.47.0 on that report.
Why folder excludes miss
Each local-exec command runs a fresh one-off PowerShell script under %LOCALAPPDATA%\\Temp. Excluding only:
%LOCALAPPDATA%\\Programs\\Grok Bot%USERPROFILE%\\.grokbot
does not cover that Temp path. “Always allow” local execution in Grok Bot settings also does not bypass the AV delay.
Same Temp pattern appears with Surfshark real-time scanning: Exclude Surfshark Temp so Grok Bot local Shell works.
Staff A/B (run one step at a time)
Retry a short command (hostname) from the Bot after each change:
- Turn off only DeepGuard (leave Virus / realtime on). Note pass/fail.
- DeepGuard back on; turn off only real-time / virus protection. Note pass/fail.
- Everything back on; allow
Grok Bot.exefrom%LOCALAPPDATA%\\Programs\\Grok Botin F-Secure DeepGuard app permissions. Note pass/fail. - Still failing: as a test only, exclude
%LOCALAPPDATA%\\Temp, try once, then remove the exclude again.
Report which step worked plus F-Secure product/version on the forum so staff can publish a stable allowlist. They also flagged making command execution more tolerant of slow security software.
Confirm the class
| Signal | Expected in this class |
|---|---|
| Computers: local PC | Connected |
| Local execution setting | Always allow |
| Agent Shell | unavailable / temporarily unreachable |
| Fully disable F-Secure + relaunch Bot | Local command succeeds |
| Re-enable F-Secure | Breaks again |
Pitfalls
- Do not leave
%LOCALAPPDATA%\\Temppermanently excluded unless your security policy accepts that tradeoff — staff listed it as a temporary test. - Fully disabling F-Secure is a diagnosis step, not the standing fix.
- Daemon / attach issues without AV delay: Fix Grok Bot local-exec daemon.