Scan text exports from CBS.log, DISM.log, Windows Update and Event Viewer for recognizable error codes, repair failures, missing-source clues, permission errors and useful excerpts. Findings are evidence to review, not a guaranteed diagnosis.
Private by design — no API key is required
Files are not uploaded, and no AI API key is used. Text parsing and the rule-based scan happen in this browser. This tool will not run repair commands or change your computer.
For performance and safety, selected files must be under 10 MB; scans examine up to the most recent 350,000 characters.
1. Add a supported log export
Supported: CBS.log, DISM.log, exported WindowsUpdate.log, Event Viewer XML/CSV/TXT. Binary .evtx and .etl are not supported.
0 / 350,000 characters
Where to get useful Windows logs
CBS servicing log: find CBS.log in the Windows servicing logs and copy only the lines around the timestamp of the failure.
DISM log: check the DISM log for the same repair attempt and compare the code and time rather than treating one line as a final result.
Windows Update: export a text WindowsUpdate.log or select the relevant update event as XML/CSV from Event Viewer.
Event Viewer: export selected events as XML or CSV. This tool does not read the binary .evtx container directly.
Privacy reminder
Logs may contain account names, file paths, device information or internal network details. Review the text before sharing it with anyone. Although this analyzer does not upload it, remove private information before copying a report elsewhere.
Frequently asked questions
Are my Windows logs uploaded?
No. The selected text file is read and analyzed in your browser. The log contents, file name and extracted lines are not sent to Tech World Window. No AI API key is required.
Which files are supported?
Use text-based CBS.log, DISM.log, exported WindowsUpdate.log, or Event Viewer XML/CSV/TXT exports. Binary .evtx and .etl traces, ZIP archives and memory dumps are not parsed by this first version.
Does this tool repair Windows automatically?
No. It only identifies known text patterns and shows nearby evidence. It does not run commands, change Windows settings, modify files or prove the root cause.
Why might a log contain no findings?
The relevant error may be outside the scanned text window, use a pattern not yet recognized, or be stored in a binary trace. A quiet result is not proof that Windows is healthy or that a repair succeeded.
What should I do before trying a repair?
Keep important files backed up, note the exact error code and Windows version, and prefer reversible checks. For repair-source errors, confirm that any Windows installation media matches the installed edition, language and release before using it.
