Applies to: All editions
Preparation fails in Windows
If preparation fails in DriveErase, check if:
- DriveErase is running with administrative rights;
- The system volume has sufficient free space;
- Boot-configuration changes are permitted by endpoint policy;
- The installation is complete and not missing required environment files;
- Security software has not quarantined or blocked required files;
- The Windows boot configuration is healthy;
- No previous restart or update is pending.
Restart Windows, validate the license, refresh the targets, and create a new job after resolving the cause.
Computer returns directly to Windows
The temporary boot entry may not have been applied or may have been overridden by firmware, boot manager, endpoint control, or system recovery. Review the displayed preparation result and Windows event or security logs where appropriate.
Do not repeatedly confirm the same stale job. Create a new job after the boot issue is corrected.
Job is rejected
The privileged environment can reject a job when:
- The signature is invalid;
- The job format or license policy is invalid;
- The job has expired;
- The computer clock is inconsistent;
- A method is not permitted by the encoded edition;
- The target list is missing, duplicated, or malformed;
- The target identity no longer matches;
- A target is the protected boot disk.
A rejected job performs no approved destructive operation. Return to Windows and create a new job.
Storage device is missing after restart
The privileged environment may lack a required storage-controller driver or may see a different controller mode. Use a supported direct path or deploy the approved driver through the supported product process. Do not change controller mode casually on an installed Windows system, as doing so can prevent Windows from starting.
Unexpected shutdown
Treat every affected device as incomplete. Restore stable power, identify the device, and repeat the approved process or move it to destruction according to the recorded state.