DriveErase can work with several storage technologies and Windows environments, but hardware configuration can affect which devices are visible and which sanitization methods are available. A drive connected directly to a motherboard may expose different capabilities from the same drive installed behind a USB adapter, RAID controller, or enterprise storage enclosure.
Standard and Pro are intended for eligible physical, non-server Windows installations. Enterprise and Audit also support compatible Windows Server and virtual-machine environments, where storage configuration and operational planning often require additional attention.
The active Windows system disk is protected from selection, and DriveErase performs destructive operations outside the normal Windows session. These protections help prevent unsuitable operations, but they do not replace the need to identify the correct target and confirm that the chosen method can provide the required result.
This section explains the practical considerations for servers, virtual machines, removable storage, RAID controllers, and system disks. It also provides troubleshooting guidance for situations where a drive is not detected, a firmware command fails, the Privileged Execution Environment cannot start, or licensing and reporting functions are unavailable.
When investigating a problem, keep the storage device’s physical identity and any available operation results. An unsuccessful sanitization should not be treated as successful simply because the drive appears empty or Windows can no longer recognize its previous partitions.
-
Use DriveErase on Windows Server
-
Use DriveErase in Virtual Machines
-
Sanitize USB and Removable Media
-
Work with RAID Controllers, HBAs, and Storage Bridges
-
Sanitize an Active System Disk
-
Troubleshoot Device Detection and Selection
-
Troubleshoot the Privileged Execution Environment
-
Troubleshoot SMART, Firmware, and Overwrite Operations
-
Troubleshoot Licensing and Report Export
-
Collect Diagnostic Information and Contact Support
