# Glow: a single-portable-binary Windows system analysis tool > Glow is a Windows system analysis tool that answers the question you end up asking when something is wrong with a machine: what exactly is this thing made of. It inventories the hardware down to memory slot part numbers and battery cycle counts, lists drivers, services and installed applications including hidden ones, adds benchmark and repair utilities, and exports the whole picture as text, HTML, Markdown or JSON. It runs from a ZIP with no installer and no external dependencies. **turkaysoft/glow** — Advanced System Analysis Software - Repository: https://github.com/turkaysoft/glow - Website: https://turkaysoft.com - Stars: 542 · Forks: 34 - Language: C# - License: MIT - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/turkaysoft-glow ## One executable that replaces a shelf of utilities Glow is advanced system analysis software developed by Eray Turkay, and its stated purpose is to uncover technical details that are difficult to access with standard tools or that typically remain completely hidden. That is the pitch, and the scale of it is stated in the README: with over 500 advanced features and broad analysis capabilities, Glow examines system components from multiple angles. The aim is to make critical data that would normally go unnoticed visible, and to present it in a way that even users with limited computer knowledge can read. The two implementation constraints are interesting, because they explain a lot about the shape of the application. It is developed exclusively in C# and .NET Framework with no external libraries or dependencies. And it is portable: no installation required, just download it, extract all the files from the ZIP, select the appropriate architecture and run it. The no-dependency claim is the unusual one. A system analysis tool normally leans on whatever the platform offers, and a modern .NET application would pull in packages for the UI, for JSON and for the HTTP calls. Writing it without them means the application ships as a self-contained executable and does not care what is installed on the machine it inspects, which matters when the machine in question is the one misbehaving. The licence is MIT, the primary language is C#, the project home is turkaysoft.com, and the platform badge in the README says Windows. The releases are v26.12.1 in August 2026, v26.13 in September and v26.14 on 2026-10-16, with the last push to the repository on the same day. The version numbering is a year and month, so a build tells you its age without a changelog. ## The hardware inventory, slot by slot The technical insights section is organised by component, and the level of detail is what distinguishes it from a system information panel. For the operating system it reports detailed Windows build numbers, the installation timestamp, the current uptime, and active security settings. The motherboard section gives chipset details, the BIOS manufacturer, its release date and specific board revision numbers, which is the information you need when a board is behaving oddly and the vendor support page asks for the revision. The processor section covers the microcode version, physical and logical core counts, the L1, L2 and L3 cache hierarchies, and the real-time virtualization status. The memory section is described as a slot-by-slot breakdown including part numbers, manufacturer, bank labels, voltage levels and the true operating frequency, which is the memory module information that a warranty claim needs and that a vendor utility often does not show. The graphics section gives the full adapter string, VRAM capacity, driver date and version, and the active monitor refresh rates and resolutions. The storage section reports real-time health monitoring, partition styles as GPT or MBR, interface types as NVMe or SATA, and precise capacity reports. Then the peripherals: dynamic monitoring of MAC addresses, internal IP addresses, network adapter speeds and active connection status for the network section; all connected USB controllers and devices with detailed hardware IDs; audio controllers, driver versions and active output and input devices; and a battery report with design capacity against full charge capacity, cycle count and a wear level percentage. That last one is the most useful to most people and the hardest to get elsewhere without a third party utility. ## Software inventory, and four ways to take it away The software side is the other half, and it follows the same idea of completeness. Installed Drivers gives a full listing of kernel and system drivers with provider and version details. Installed Services shows all background services, their current status as running or stopped, and their startup types. Installed Applications gives a complete list of the software installed on the system, including hidden components, which is the part that matters when you are looking for something that installed itself quietly. Then the feature that makes the tool useful as documentation rather than as a curiosity: the ability to save all features offered in the interface as a Text Document, an HTML Document, a Markdown Document and a JSON Document, if desired. Four formats is a deliberate spread. Text is for pasting into a support ticket, HTML is for attaching, Markdown is for a wiki or an issue, and JSON is for a script or a record you keep elsewhere. The export is described as an advanced reporting tool that saves your entire system analysis as a clean, structured document. There is also a system identity feature: unique device ID generation for hardware verification, with the shortcut CTRL + 6. That is the piece you would use when you need to prove that two machines are the same machine, without collecting anything that identifies the user. The privacy position is stated as a headline feature. Your data stays on your machine, and no information is transferred to external servers. That claim is consistent with the rest of the design, since a portable executable with no dependencies and no update service phoning home is easy to verify. ## The tools menu: benchmarks, repair and diagnostics Beyond the inventory there is a suite of system maintenance tools, and it is the part of the application that does things rather than reports. The repair tool is an automated DISM and SFC system file repair and image health management module, which is the operation every Windows user has run at the command prompt and every support article has recommended. The benchmarks are three separate modules, one each for CPU, RAM and disk performance testing, which is the quickest way to see whether a machine is slower than it was. Then the cache cleanup tool, which clears system and temporary junk files, the system ID analysis tool for unique system identifiers, and a hardware security audit module for auditing the security of the system's hardware. The connectivity group covers Bluetooth information, a DNS test for analysing and testing DNS performance, and a network troubleshooting suite for resolving connectivity issues. There is a tool that displays saved Wi-Fi networks and their security keys, which is the information Windows already stores for the machine you are sitting at. The port scanner analyses TCP and UDP ports and network listeners, shows the connected processes and risk levels, and can scan local or remote hosts. That is a genuinely useful diagnostic: the question it answers is which process is holding that port, which is a regular cause of a service that will not start. The monitor tools are the closing group: a dead pixel test that identifies faulty pixels across various colour ranges, a dynamic colour range test for the monitor's colour depth and accuracy, and a stuck pixel repair tool designed to revive unresponsive pixels. The pattern across the menu is that each item replaces a small utility you would otherwise download, run and then delete. ## The interface, the languages and the updater The presentation details are the ones a developer notices first, and the README does not undersell them. The interface is described as clean and intuitive, compatible with the Windows 11 design language, with light, dark and system themes. There is a screenshot in the README showing the application window. The application supports 16 different languages, primarily English, with the list of supported languages in a discussion on the repository, and the localisation is community driven through an official translation guide. For a tool whose audience is not only developers, that matters: a Windows internals utility that only speaks English reaches a smaller audience than the one that ships sixteen languages, and the translation work is done by people who use it. The build and release process is not public, but the release badge points at the releases page and the CODE_SIGNING.md file at the repository root suggests the binaries are signed, which is the thing that determines whether Windows SmartScreen treats a download as suspicious. The SECURITY.md file is there too, so the project has a policy for reporting a vulnerability in it. And there is a built-in update mechanism, described as a smart update mechanism developed specifically by Turkaysoft. That is the one feature that touches the network, and it sits awkwardly beside the privacy claim, so it is worth knowing that it exists. The project is funded by donations through a Buy Me a Coffee link, with a note that supporting it helps ensure its sustainability and the development of new features. ## Getting it running, and the one step people skip The getting started section is five steps, and the third one is the one people get wrong. Navigate to the releases page and download the latest ZIP file. Extract all files from the ZIP, and the README marks this as important, saying the application requires all folder contents to run correctly. Then launch the executable matching your architecture. ```bash Glow_x64.exe ``` is for standard 64-bit Intel and AMD systems, and there is a separate arm64 build for ARM-based devices like the Surface Pro. The README lists both names, and the reason to extract everything rather than the executable alone is that a portable application of this kind keeps its resources, and possibly its data files, beside the binary. The architecture choice is worth a moment's thought, because Surface devices and the ARM-based Windows machines that have become common are not the same as an x64 desktop, and running the wrong build is a launch failure rather than a degraded experience. There is no installer, no configuration file to edit and no service to register, which means Glow leaves nothing behind on the machine. For a system analysis tool that is arguably the right default: it does not modify the system it is describing, and removing it is deleting a folder. ## Where Glow is the wrong choice There are cases where a single large analysis tool is the wrong answer, and they come from what it is designed to be. It is a Windows application. The badge says so, the executables are Windows PE binaries, and the inventory is built on Windows specific interfaces, so on Linux or macOS there is nothing to run. It is also a graphical application rather than a command line tool with a documented output contract. The JSON export is close to that, but there is no documented schema for it in the README, so if you want to inventory hundreds of machines on a schedule, a script driving the PowerShell CIM cmdlets or the Windows Management Instrumentation interfaces will give you something more reliable than scraping an export file. And the tool menu has a shadow. A port scanner, a disk benchmark and a monitor test all exist as focused utilities that other people maintain, and the ones in Glow are conveniences inside a bigger package rather than the best tool for the job. If the benchmark is going into a review, a dedicated benchmarking tool with published methodology is the one to use. The alternative approach is the operating system's own tooling: the system information panel, the device manager, PowerShell queries against WMI, and one focused utility per component. The difference in approach is that those tools answer one question each and give you nothing else, while Glow gives you the whole inventory in one window and one export, which is exactly what you want when you are documenting a machine rather than debugging one setting. There is one security consideration to name rather than avoid. Several of the menu items, the port scanner and the saved network key display among them, need elevated rights and reveal information about the machine and the network it sits on. On your own machine that is fine. On a machine you do not administer, it is a different activity. ## Conclusion Glow suits somebody documenting a machine, checking whether a warranty claim matches the hardware, or trying to work out why a system behaves oddly, because one export gives you the whole inventory in a form you can attach to a ticket. It does not suit a non-Windows machine, since the release badge says Windows and the executables are architecture specific, and it does not suit somebody who wants a reproducible inventory from a script, since the tool is a graphical application rather than a command line with a stable output format. Check three things before you rely on it: that you extract the whole ZIP, because the README says the application requires all folder contents to run correctly, which architecture your machine is, with the x64 build for standard Intel and AMD systems and the arm64 build for devices like the Surface Pro, and whether you want the whole report or just one section, because the port scanner and the audit utilities need elevated rights and are a different kind of tool from the inventory pages. The last push to the repository was on 2026-10-16 and the newest release is v26.14. ## FAQ ### What is Glow? It is advanced system analysis software for Windows developed by Eray Turkay, built in C# and .NET Framework with no external libraries or dependencies, and designed to surface technical details that standard tools leave hidden. It is MIT licensed and distributed as a portable ZIP with no installation. ### What does Glow report about the hardware? Detailed Windows build numbers and uptime, motherboard and BIOS revision details, CPU microcode and cache hierarchy, slot by slot memory part numbers and voltage, GPU and monitor refresh rate information, storage health with partition style and interface type, network addresses and adapter speeds, USB device identifiers, audio devices, and battery design capacity against full charge capacity with cycle count and wear percentage. ### Can I export the Glow results? Yes. You can save all the features offered in the interface as a Text Document, an HTML Document, a Markdown Document or a JSON Document. There is also a unique device ID generation feature for hardware verification, reachable with the shortcut CTRL + 6. ### How do I run Glow on my machine? Download the latest ZIP from the releases page and extract all of its files, since the application requires all folder contents to run correctly. Then run Glow_x64.exe for a standard 64-bit Intel or AMD system, or the arm64 build for ARM-based devices such as the Surface Pro. ### Does Glow send my data anywhere? The README lists privacy first as a key feature, stating that your data stays on your machine and no information is transferred to external servers. The application does include a built-in update mechanism developed by Turkaysoft, which is the one component that reaches out. ## Sources - [License: MIT](https://github.com/turkaysoft/glow/blob/main/LICENSE) - [Project website](https://turkaysoft.com) - [README](https://github.com/turkaysoft/glow/blob/main/README.md) - [Releases](https://github.com/turkaysoft/glow/releases) - [turkaysoft/glow on GitHub](https://github.com/turkaysoft/glow) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/turkaysoft-glow