Gutcheck

0.5.2

Gutcheck - an honest look inside a slow or unstable Windows PC. Performance and stability diagnostics for Windows clients, driven by data-defined Checks. A technician runs one command at a customer site and reads the report on the spot.

Minimum PowerShell version

5.1

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name Gutcheck -RequiredVersion 0.5.2

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name Gutcheck -Version 0.5.2

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

(c) 2026 MERLIN. Licensed under the MIT License.

Package Details

Author(s)

  • MERLIN

Tags

Windows Diagnostics Performance Support Troubleshooting Helpdesk Hardware Reporting

Functions

Invoke-Gutcheck

PSEditions

Desktop Core

Dependencies

This module has no dependencies.

Release Notes

0.5.2 - Which Check Definitions did this Run use?

- Every Report shows a Kennung beside the version of its Check Definitions: eight
 characters worked out from the document the Run read. Two Reports with the same Kennung
 used the same Checks, whether or not anybody updated the version.
- A document that carries a time says when today it was created.

0.5.1 - A click no longer freezes a Run.

- A click in the admin window, or in the window Gutcheck was started from, started a text
 selection, and Windows then held the Run still until somebody pressed Enter. Gutcheck
 switches that behaviour off for its windows while a Run lasts, and puts the Technician's
 own window back as it was afterwards.

0.5 - Did the application crash because its server dropped?

- A Run finds out which programs depend on which Servers, with no Check Definition per
 application: running programs and the DLLs they load, services, scheduled tasks,
 startup entries, shortcuts, redirected folders, offline files, printers, ODBC sources
 and the configuration files beside a program. Each Server is measured. A program
 running from a share is a warning before the first crash.
- Crashes are counted as incidents - the events of one crash are one row - and every
 program that crashes repeatedly gets a Finding of its own: where it runs from, what
 the exceptions were, how many incidents coincided with a network disruption, and a
 verdict drawn from that evidence. Where the evidence does not reach, it says so.
- What Windows logged about the network going away is read with admin rights: SMB
 disconnects and timeouts, adapter and Wi-Fi drops, standby and resume.
- Network adapters: whether the machine is on a USB adapter, and its power saving.
- Installed .NET versions, held against the version a crash happened on.
- The admin part runs again. In 0.4 it ended within a second on every machine, without
 results and without saying why.
- No more false alarms from healthy-volume messages counted as disk errors, old driver
 hangs reported again and again, or one antivirus registered several times.

0.4 - Progress while a Check waits.

- A Run shows a bar for the Run - which Check, of how many - and one beneath it while a
 Check waits: sampling, pings and connections, the disk write test, the stress test and
 the admin part. A Run no longer looks hung.
- The banner says "Trust your gut. Check everything."

0.3 - Outlook connectivity.

- Outlook connectivity, for Microsoft 365 and on-premises Exchange, without anybody's
 password:
 - Autodiscover: per mail domain, whether its DNS and endpoints answer the way Outlook
   needs, whether the mailbox is in Exchange Online, registry overrides that bend the
   lookup, and an Active Directory pointer still aiming on-premises after a migration.
 - HttpsEndpoint: whether an HTTPS service is reachable end to end - not blocked, not
   held by a proxy, not intercepted - with a valid certificate. Ships for Exchange Online
   and the Microsoft sign-in service; usable for any application's endpoint.
 - OutlookAuth: modern authentication, the Windows sign-in broker, MAPI over HTTP,
   client TLS 1.2, sign-in errors, the Entra device and its sign-in token, and for
   on-premises Exchange the NTLM level and stale saved Office credentials.
 - Mail files on a network drive, sizes against the limit Outlook actually enforces,
   lost connections to Exchange; whether the Office build is still supported for its
   channel and the product for Microsoft 365; the proxy Outlook's background requests
   use, against the user's.
- The application list shows in two columns when the window allows.
- Mail files are found the same way on Windows PowerShell 5.1 as on PowerShell 7; 5.1
 listed every file in the Outlook folder as one.

0.2 - Services, printing and Group Policy.

- Service: whether the Windows services an application depends on are installed, running
 and set to start the way they should, and how often they crashed. Configured per
 application in the Check Definitions; shipped for DATEV, Lexware, Sage, FortiClient and
 GlobalProtect.
- Printing: the print spooler, whether the default printer can be reached - Office waits
 on it whenever a document opens - offline printers, stuck jobs and print service errors.
- GroupPolicy: how long Group Policy holds up boot and logon, the slowest and failing
 extensions, slow-link detection, and a domain controller that could not be reached.
 Needs the admin prompt.
- Applications a Run now offers: Lexware, Sage, ADDISON, StarMoney, SFirm, DocuWare,
 ELO Java Client and ELOoffice; SwyxIt!, estos ProCall and STARFACE; Citrix Workspace,
 FortiClient, GlobalProtect and Securepoint VPN; pcvisit; Securepoint Antivirus, ESET,
 G DATA and Sophos; Server-Eye. Identifiers are sourced in docs/research.
- A Service Check can name OptionalServices: reported with their state, never judged for
 being stopped or disabled - the Server-Eye OCC Connector runs on one machine per site.
- An application whose installer records no install path is no longer merged with another
 one that does not either, so an old and a new VPN client side by side both appear.

0.1 - Gutcheck is a module.

The single-file script is retired. Everything it examined is now a Check described by
data: a Check Definition names a Kind the module implements and supplies that Kind's
parameters, and every threshold is one of those parameters rather than a literal.

- One command, one Report, as before. Technicians install once and update with the same
 command they installed with.
- The privileged half of a Run happens behind one UAC prompt, so an admin colleague can
 enter their own credentials while the rest of the Run stays in the technician's session.
- Every Finding states the Privilege it was gathered with, and Checks that could not run
 appear in the Report rather than being absent from it.
- Every Report states where its Check Definitions came from, which version they were and
 how old.

Upgrading from the script: see the project page. There is no compatibility shim.

FileList

Version History

Version Downloads Last updated
0.11.1 8 10/10/2026
0.11 5 10/10/2026
0.10 5 10/10/2026
0.9.1 10 10/10/2026
0.9 8 10/10/2026
0.8.3 5 10/9/2026
0.8.2 4 10/9/2026
0.8.1 3 10/9/2026
0.8 3 10/9/2026
0.7.2 4 10/9/2026
0.7.1 5 10/9/2026
0.6.2 6 10/8/2026
0.6.1 5 10/8/2026
0.6 4 10/8/2026
0.5.2 (current version) 6 10/7/2026
0.5.1 8 10/7/2026
0.5 5 10/7/2026
0.4 19 9/25/2026
0.3 7 9/25/2026
0.2 7 9/24/2026
Show less