Desktop utility for offline Windows audit: collecting inventory, checking security policies and exporting a report

Initial situation
The company has about 150 workstations running Windows 10-11 Pro. Some computers are periodically without access to the network and domain, so it is not possible to collect a single snapshot of the state and check basic security requirements through cloud/server agents. You need a ready-made desktop application that runs locally (without installation or with an MSI of your choice), collects data and generates a report for transmission to the information security department.

Technical environment and subject area
- OS: Windows 10-11 x64
- Language and stack: C# .NET 8 (WPF) or .NET 8 + WinUI 3 (WPF preferred due to compatibility)
- Data access: WMI/CIM, Windows Registry, Event Log, netsh, auditpol, PowerShell via runspace (no external dependencies)
- Limitations: Run without admin rights where possible, and clearly show which checks require elevated rights

What should happen
A ready-made program with GUI and CLI mode that performs a local audit according to a check profile, shows progress, saves the results in JSON and generates a readable report (PDF or DOCX) with the final status and inconsistencies found.

Functional Requirements
- The check profile is specified by a configuration file (YAML or JSON) and supports enabling/disabling modules
- Inventory collection: OS version, PC name, domain/workgroup, CPU/RAM/disks, list of installed updates (KB), list of installed programs (Uninstall keys), active network interfaces and IP, BitLocker status by volume
- Security checks (minimum set): built-in firewall status by profile, Defender status (if available), UAC status, password policy (via local security policy where possible), RDP presence and its settings (enabled/disabled, NLA), autorun status for key points (Run/RunOnce), list of local administrators
- Logs: selectively download the last N events from Security and System according to specified filters (level/ID/period), with protection against freezes
- Export:
- JSON with complete data structure
- PDF or DOCX report with sections: summary, inventory, checks, logs, list of problems
- Report signature: calculating the SHA-256 hash of all exported files and recording it in a separate manifest.txt
- CLI: launch without GUI with parameters: profile path, output directory, report format, timeouts

Non-functional requirements and restrictions
- Execution time on a typical PC: up to 3 minutes with default profile
- Do not use third-party commercial libraries, only free NuGet packages with a permissive license are allowed (MIT/Apache/BSD)
- The application should work correctly when the Internet is turned off
- Localization: interface and report in RU

Measurable acceptance criteria
1) On 3 test machines (Win10, Win11, Win11 without admin rights), the program starts and completes the audit without crashes, displays clear messages about unavailable checks
2) JSON is validated according to the provided schema (the schema must be developed and attached to the project)
3) The report contains a summary table: number of checks, number passed, number of warnings, number of errors
4) When restarted on the same machine with the same profile, the JSON structure is stable, and the differences are only in the time/log dependent fields
5) CLI mode returns a non-zero exit code if there are errors at the error level (configurable in the profile)

Execution steps
- Design of data structure and JSON schema, prototype of collection modules
- Implementation of a modular system of checks and UI/CLI
- JSON export and report generation, manifest with hashes
- Testing on different rights and fixing timeouts/error handling, release build

Results to be conveyed
- Sources in the repository (Git), assembly instructions
- Ready release: portable zip and optional MSI
- Example of a check profile and example output files