| Previous | Next |
| E_IMAPI_ERASE_TOOK_LONGER_THAN_ONE_HOUR | E_IMAPI_ERASE_DRIVE_FAILED_SPINUP_COMMAND |
E_IMAPI_ERASE_UNEXPECTED_DRIVE_RESPONSE_DURING_ERASE
E_IMAPI_ERASE_UNEXPECTED_DRIVE_RESPONSE_DURING_ERASE is deliberately ambiguous about the final physical state: Microsoft notes that the medium may be unusable, erase may actually be complete, or the drive may still be erasing. The response cannot safely be treated as a clean rollback.
Re-discover state before any new media operation
- Stop issuing follow-up write or erase commands until the recorder becomes responsive.
- Re-query media type/support and, when possible, examine whether the medium is blank or still busy.
- Preserve the last erase progress event and recorder identity for device/firmware diagnosis.
The safest application behavior is to invalidate cached media assumptions. Do not continue with a burn merely because the original erase call returned; the physical device may still be processing the disc. Likewise, do not claim the disc is definitely destroyed solely from this HRESULT. Report the uncertain state, allow device recovery, and perform fresh capability/media checks before presenting the next operation.
EraseMedia · Erase progress events · IDiscRecorder2
Looking for a different code? Search another status or error code.