WinPool is a Windows desktop application for viewing storage topology, editing simulated systems, monitoring devices, and performing supported local storage operations through a controlled workflow.
WinPool V0.63, the first public test release, is now available. Everyone is welcome to try it and share feedback. Download it from the V0.63 release page, and report a problem or suggestion.
Implementation and authorized local acceptance for V0.62 are complete and archived. Initial manual testing has been reassuring, but testing on other systems and hardware, continuous 20 Hz monitoring, and 150%/200% display scaling are still in progress. These checks remain on the plan; the developer has chosen to proceed with public testing while they continue. See Quality for the actual coverage and package identity; Directory.Build.props is the version source.
- Manage shows pools, tiers, physical and virtual disks, partitions, and their relationships. Developer mode in Settings exposes the hardware report, testing roadmap, and current-run messages.
- Storage structure previews a draft before the Agent executes the confirmed structural job. Disk/partition submits individual actions. New pools generate virtual disk and partition goals by default; existing RAW virtual disks are not automatically partitioned. Drafts survive page navigation during the current App lifetime, and simulation documents load on demand.
- Valid simulation Apply/Enter actions show a local candidate and save merged edits in the background. Save failures retain the local work and report its state. JSON import/export and simulation do not modify real disks; complete canonical document envelopes support up to 64 MiB. Simulation results do not prove that Windows can execute the same configuration.
- Real editing starts off and uses exact targets and the current controlled confirmation. An accepted job may continue after the App closes while the Agent remains alive; an Agent restart performs read-only recovery without continuing writes. Unknown outcomes block further writes. Capabilities depend on Windows/provider support. Real MBR-to-GPT conversion, extending existing VDs/tiers to MAX, and direct pool-member migration remain unsupported; see Product.
- Monitoring supports 0.2–20 Hz and pushes batches to a shared chart/alert cache, reseeding its window after connection or sequence gaps. Recording uses a separate database, rotates at 1 GiB, and archives with bundled 7-Zip. Historical archives are not automatically deleted. CSV export covers the active database only; there is no monitoring-history browser.
- English, Simplified Chinese, themes, and keyboard controls are available. Hardware fields retain their original values; review their contents before sharing exports.
Implementation does not establish coverage across every environment or performance scenario. Quality records actual ordinary-privilege startup, hardware-operation, and candidate results; historical reviews and speed measurements do not replace current verification.
The support target starts at Windows 10 22H2 x64, with Windows 11 24H2/25H2 x64 as primary platforms. Coverage across environments remains external testing work; these targets are not a completed verification matrix.
Use the complete x64 portable runtime directory with matching App and Agent files. Run WinPool.App.exe; the Agent appears in the user tray. Exit both before replacing files. Data defaults to %LocalAppData%\WinPool, with an explicitly selected writable Data directory beside the program also supported. No formal MSIX or Store release is available.
The runtime uses the system Windows PowerShell 5.1; PowerShell 7 and development SDKs are unnecessary for running the portable package. Project compatibility testing is separate from upstream .NET support; Windows 10 Pro 22H2 is not listed in the .NET 10 support matrix.
The public test package provides a ZIP containing TESTING.md and a separate SHA-256 checksum file on the release page. Extract the complete folder before running. If something goes wrong or could work better, please let us know, including the version, Windows/device environment, reproduction steps, and relevant errors.
On Windows with PowerShell and the SDK specified by global.json:
dotnet restore WinPool.slnx
dotnet build WinPool.slnx -c Release --no-restore -m:1
.\artifacts\Release\WinPool.App.exeContributor rules are in AGENTS; build and data ownership are in Development. Internal development documents are maintained in Chinese.
64K interleave + 64K NTFS cluster = current tested recommendation.
Windows 11 has not yet received equivalent testing because current storage hardware prices and the author's practical budget do not allow a second full test platform.
The research findings cover their recorded samples. Software platform testing and storage reliability research have different scopes.
No license is granted for WinPool's own code by this repository. All rights are reserved. Third-party components retain their respective licenses; see the runtime license index and the bundled 7-Zip license and source notice.