The documented RivoShield 2.0 build is a development evaluation. The current driver requires an x64 test machine or VM, a recovery snapshot, Secure Boot off, Test Mode on and a restart. That setup is not suitable for normal production deployment.
Before installation
- Use disposable test data and retain an independent backup.
- Close Word, Excel, CorelDRAW and other applications using the test folder.
- Record the intended build version and hash.
- Never begin with the only copy of business data.
Runtime health
After installation or restart, the Dashboard should show both the Protection Service and File-system Protection as healthy. Confirm the expected protected locations remain visible and any archived folders retain their state.
Functional acceptance
- Normal create, open, edit, repeated save and reopen succeeds.
- Delete attempts from Explorer, Command Prompt and PowerShell are blocked and the file remains.
- Nested file and folder delete attempts are blocked.
- Archive allows read and copy-out while blocking all mutations.
- Audit fields, search, CSV/JSONL export and controlled clearing are verified.
Stop conditions
Stop relying on the product if the service or filter is unavailable, protected locations disappear after restart, deletion succeeds, or data integrity is in doubt. Preserve diagnostics and exact reproduction details.
Production release gate
A production-ready claim requires a Microsoft-trusted signing route and complete clean-install, upgrade, restart, reboot and application-regression acceptance on each target Windows version.