Testing and Verification Methodology

Documentation review, practical checks and honest limits.

Current verification status

For this edition, the developer documentation and Microsoft storage guidance were reviewed on 2026-10-05. No Windows installation, malware scan, digital-signature check, package hash verification or performance benchmark was performed. The download payload was not independently audited. These limits apply to the published guides.

Protocol for future hands-on tests

  1. Record Windows edition, build, CPU, memory, storage type, filesystem and WizTree version.
  2. Record the package source, signature and hash. Use an isolated test environment and approved data.
  3. Repeat identical scopes with and without authorized elevation; document filters and active workloads.
  4. Check representative file paths and compare the intended measurement with Windows.
  5. For cleanup tests, use disposable files and measure free space before and after.
  6. Publish raw observations, dates, limitations and failures. Mark tests as completed only after they occur.

Do not call this protocol a completed test or claim speed, safety or compatibility based solely on its existence.