Applies to: All editions; edition restrictions apply to server and virtual environments
Windows and hardware requirements
DriveErase requires a supported 64-bit Windows installation and x64-compatible hardware. Consult the release information supplied with the current installer for the supported Windows versions for that release.
The Windows account running DriveErase must have local administrative rights. The application needs permission to inspect physical storage devices, prepare a one-time boot entry, write temporary operating files to the system volume, and restart the computer.
The computer must provide:
- Sufficient free space on the Windows system volume for the Privileged Execution Environment and job data;
- A working system boot configuration that permits a temporary one-time boot entry;
- Stable power for the complete sanitization and health-assessment period;
- Compatible storage-controller access in both Windows and the Privileged Execution Environment;
- A keyboard and display, or an equivalent supported console, for reviewing execution status and completion prompts.
Supported device classes
DriveErase can detect and process compatible physical storage devices exposed through Windows, including:
- Rotational hard disk drives;
- SATA solid-state drives;
- NVMe storage devices;
- SAS hard disk and solid-state drives;
- USB-attached fixed storage;
- Removable flash media.
Detection does not guarantee that every method is available. Firmware methods require a compatible device and a controller path that passes the required commands. USB bridges, RAID controllers, HBAs, docking stations, storage enclosures, and virtual storage stacks can limit this access.
Active system disk
The disk containing the running Windows installation is marked as the system disk and cannot be selected in a normal DriveErase session. The disk used to start the Privileged Execution Environment is also protected from erasure.
To sanitize a system disk, connect it as a non-system device to another supported computer and run DriveErase from that host.
Edition restrictions
- Standard and Pro: supported on eligible physical, non-server Windows installations.
- Enterprise and Audit: additionally permit supported use on Windows Server and in virtual-machine environments.
A virtual machine can expose only the storage visible to the guest. Hypervisor snapshots, backup copies, replication targets, storage-array copies, and the physical media beneath a virtual disk remain outside the guest’s sanitization scope.
Network requirements
Internet access is required for initial activation and periodic license validation. After successful validation, protected local license data permits temporary offline use for up to 14 days. Audit report validation and management requires access to the applicable Probativa service.
Deployment validation
Before production use, complete a controlled test with representative hardware. Confirm:
- Device identity is reported accurately;
- The intended controller exposes the required method;
- The Privileged Execution Environment starts correctly;
- A test job completes and returns usable results;
- Report export works in the selected edition;
- Organizational monitoring or endpoint controls do not interrupt preparation or reporting.