Browser-only tools for endpoint and server ops
The log never
leaves your machine.
Production logs are full of device names, user names, and internal paths, which is why you cannot paste one into a hosted AI tool and should not want to. These tools have no server to send anything to. They read the file in your browser, and you can watch the network stay silent while they do it.
Start with the log analyzer, or look up a single error code.
The tools
Free, no accounts, no upload. Each one does a job you would otherwise do by hand.
Log analyzer
Drop a log, read the verdict
CBS, DISM, MSI, Configuration Manager, syslog, journald, dmesg, nginx, Event Log exports, and a generic parser for everything else. Finds the lines that actually failed, shows the lines around them, and explains the codes. An 11MB CBS.log parses in about a fifth of a second.
Error code decoder
Paste a code, get the cause
60 Windows Installer, Windows Update, and servicing codes, each checked against Microsoft documentation. Codes it does not know still get broken down structurally rather than guessed at.
Field notes
Problems from real endpoint work, written up so the next person can skip the diagnosis.
How to read a CBS log
The format, why the error line almost never names the real problem, and the search that finds it in eighty thousand lines.
How to read an MSI verbose log
Return value 3, what the line above it means, and why the properties dump answers most of the questions people ask about a failed install.
Repairing WMI on Windows endpoints without reimaging
When WMI breaks, every management tool that depends on it goes quiet at the same time. How to tell real corruption from a stuck service, and repair it at scale.
0x80070643 is not a Windows Update error
It is Windows Installer error 1603 in a different coat. Once you know that, the troubleshooting path changes completely.