DriveErase requires a supported 64-bit Windows installation running on x64-compatible hardware. The computer must also be capable of starting the dedicated Privileged Execution Environment used for sanitization. Because supported Windows versions can change between product releases, consult the release information accompanying your installer for the operating systems supported by that version.
You must run DriveErase with local administrator privileges. The application requires access to physical storage information and must be able to prepare a temporary boot configuration, use space on the Windows system volume, and restart the computer. A standard Windows account without sufficient permissions may be able to open parts of the interface but cannot be relied upon to prepare a sanitization job.
Computer and storage requirements
Your Windows installation must have enough free space on the system volume for the temporary execution environment and job information. The Windows boot configuration must also support the required one-time startup, and the storage controller must provide access to the selected devices both in Windows and after restart.
DriveErase supports compatible HDDs, SATA SSDs, NVMe devices, SAS storage, USB-attached drives, and removable flash media. The available sanitization methods depend on how the device is connected and which commands are exposed by its controller. A disk that appears in the Device List may support ordinary overwriting without supporting any firmware-based method.
Specialized RAID controllers, HBAs, storage bridges, and external enclosures can affect device visibility and identification. Some present a logical disk instead of the underlying physical drives, while others restrict SMART information or firmware commands. If you are working with unfamiliar hardware, test the intended method before relying on it for equipment disposal.
Windows Server and virtual machines
DriveErase Standard and Pro are intended for eligible physical, non-server Windows installations. Windows Server and virtual-machine environments require Enterprise or Audit.
When DriveErase runs inside a virtual machine, it can process only the storage presented to that guest. An overwrite of a virtual disk does not automatically remove hypervisor snapshots, clones, host backups, replicated copies, or data retained by the physical storage system. Those storage locations must be handled separately when complete removal is required.
On Windows Server, take account of maintenance windows, active services, RAID configurations, shared storage, and remote-console availability. Since the DriveErase workflow requires restarting the computer, workloads must be stopped or moved before proceeding.
Active system disk and boot protection
The disk containing the active Windows installation is protected from selection. The Privileged Execution Environment also protects the device from which it is running, preventing that device from being used as a sanitization target.
To erase the Windows system disk from an old computer, connect it to another compatible computer as a secondary drive. The computer running DriveErase must boot from a different disk.
On computers using BitLocker or other boot-protection technologies, the temporary restart may require special handling. Make sure authorized recovery information is available before proceeding, particularly on computers managed by an organization’s IT department.
Internet access and licensing
An internet connection is required for initial license activation and periodic validation. After a successful online validation, DriveErase can operate temporarily without internet access for up to 14 days. Once that period expires, another successful online validation is required before protected operations can continue.
DriveErase Audit also requires access to the applicable online service when using its report validation and management capabilities.
Preparing a reliable working environment
Sanitization should be performed using stable power and dependable storage connections. A laptop should remain connected to AC power, while a workstation or server used for lengthy operations can benefit from an uninterruptible power supply.
For external drives, avoid unreliable USB hubs, damaged cables, and enclosures that disconnect under sustained activity. If a controller, enclosure, or storage driver behaves differently after restart, DriveErase may be unable to access the intended target.
Before processing valuable or sensitive equipment for the first time, perform a representative test using a disposable non-system drive. This allows you to verify device detection, method availability, startup of the Privileged Execution Environment, and successful completion of the intended workflow.
