Release Notes – Tool Fixes: Network Tools, Fix Filesystem Issues, Check for App Crashes and More

Hi folks –

We’ve updated six tools and all of the network tools to fix reports that gave misleading answers. There’s nothing to install. TechSuite picks up the new versions automatically.

Fix Filesystem Issues

No more false “WMI repository is inconsistent.” This warning showed up on most machines, along with advice to run winmgmt /resetrepository, even when SFC and DISM came back clean. It only appears now when the repository is actually damaged. Resetting WMI is disruptive, so please don’t do it on a machine that was only flagged by the old version.
The headline matches the findings. A report no longer says “CLEAN – No issues found” when WMI is corrupt or a disk check couldn’t be scheduled.
Pending reboots are detected. If Windows Update is waiting on a restart, the tool now sees it and skips the scan, as intended.

If you alert on exit codes: the tool now exits with code 2 where it used to exit 0 when WMI is corrupt or a requested chkdsk couldn’t be scheduled. Exit code 5 means the scan was skipped for a pending reboot.

Network tools

All 11 network tools share one program, so they were updated together: Network Diagnostics, Reset Network Adapter, Reset Proxy Settings, Repair DNS, Reset Internet Protocol, Repair Winsock, Renew Internet Connections, Flush DNS Resolver Cache, Reset Windows Firewall Configuration, Restore Default HOSTS File and Sync System Time.

Network Diagnostics works on non-English Windows. On a French machine it reported “0 adapters connected” with blank IP, gateway and DNS fields, even though the internet worked. It now reads that information directly from Windows instead of parsing English text.
Reset Internet Protocol reports failures. If any step failed, the report said it succeeded. It now shows the failure, and tells you when a restart is needed to finish.

Check for App Crashes

Only real crashes and hangs are counted. Windows Store and Windows Update errors were being counted as application crashes, which pushed machines to a Critical stability rating and a “possible hardware issue” warning. Those reports are now left out and noted in the log as ignored.
The Trend card is readable. It now says Worsening, Improving or Stable, or N/A when there isn’t enough data. It used to show an internal label.

ProcessHawk

Protected processes are left alone. Some antivirus and Windows helper processes can’t have their file path read, so ProcessHawk called them unsigned, tried to kill them and reported a failure. They’re now listed as “signature unknown” and never targeted.
Dry Run reports say what they mean. A dry run now shows “Would Kill” instead of “Killed”, and no longer says all target processes were terminated.

Windows Defender

Update Signatures says “Already up to date” when the version didn’t change, instead of reporting a successful update.
Defender Available now agrees with the service state. It could show “No” while Defender was running.

HijackThis

When HiJackThis+ doesn’t produce a log, the report now shows a red “scan did not complete” message. Before, it showed zero findings, which looked like a clean scan.

Clean Windows Update Cache

Last Successful Update now shows a proper date on machines where it couldn’t be read before, including ones with non-US regional settings.

Questions or feedback? Email us at [email protected].

Ian & Garrett