Read-only PowerShell diagnostics for domain-joined laptops that slow down or crash File Explorer when they leave the corporate network.
On domain-joined PCs, mapped network drives (Z:, S:, ...) are the most common cause of this exact symptom. When the PC leaves the network, Explorer tries to reconnect every mapped drive and waits for a long network timeout on each one before giving up. Several dead drives = Explorer hangs, and a long hang looks like a crash (Explorer restarts itself).
This toolkit collects the evidence needed to confirm or rule out that story, plus the common adjacent causes: DNS, VPN, EDR agents, search indexing, NFS mounts, and third-party shell extensions.
| Script | Focus |
|---|---|
| OffNet-Diag.ps1 | Baseline sweep: system and domain state, network profile and DNS servers (flags internal DNS), mapped drives and network location history, Explorer crash/hang history (Events 1000/1002/1001) with faulting modules, top CPU processes, EDR service state, VPN/tunnel adapters, per-server connectivity probes with a hard 5s timeout, GPO drive-map section, SMB client timeout settings, key service states. Ends with a printed "fixes to try" list |
| OffNet-Diag2.ps1 | Explorer hang deep dive: WER report contents for every explorer.exe AppHang, system log context around each hang, NLA service state, sleep/wake history (Kernel-Power), SearchIndexer health, third-party DLLs loaded in explorer.exe right now, shell extension inventory from the registry |
| OffNet-Diag3.ps1 | NFS and search follow-up: NFS client presence (nfsclnt.exe, NfsClnt service), NFS/network mounts, Windows Search indexed locations, Event 10024 counts (filter-host storms), connectivity probes to every file server found, regression comparison of Explorer hang count and SearchIndexer CPU since v1 |
All three scripts are read-only. They collect information only. They do not change, disable, or remove anything on the computer, and they are safe to run as a normal user (admin is not required). The only files they create are their own timestamped reports (report.txt, console transcript) in the script folder.
Double-click the matching run.bat, or from PowerShell:
powershell -NoProfile -ExecutionPolicy Bypass -File OffNet-Diag.ps1Run all three for a complete picture. v1 first, v2 if Explorer hangs are the complaint, v3 if file servers or search indexing are suspected.
MIT.