Applies to: All editions; advanced stages require Pro, Enterprise or Audit
Processing sequence
For each selected file, CertErase follows a staged process. Optional stages run only when their controls are enabled and permitted by the licence edition.
Stage 1 — Access preparation
CertErase attempts to remove the read-only attribute so that the file can be modified. A file can still fail at this stage because of access-control permissions, locks, unavailable storage, or other operating-system restrictions.
Stage 2 — File identity modification
When enabled, CertErase renames the file repeatedly before deletion. It can also replace the extension with a randomized three-character value. This reduces the persistence of the original name in normal directory views, but it is not a guarantee that every historical metadata copy has been removed.
Stage 3 — Timestamp and basic metadata handling
When enabled, CertErase attempts to set creation, last-access, and last-write times to a fixed early timestamp and reset basic file attributes. This is a best-effort Windows file-system operation. Journals, indexes, backups, snapshots, endpoint telemetry, and external systems may retain prior metadata.
Stage 4 — Alternate data stream processing
When enabled, CertErase enumerates accessible NTFS alternate data streams, overwrites them with random data, and requests deletion of each stream. The default unnamed data stream—the normal file content—is processed separately by the selected overwrite profile.
Stage 5 — Content overwrite
CertErase opens the file for write-through, sequential processing and writes the selected pass pattern in blocks. Patterns can be fixed values or cryptographically generated random data, depending on the selected software profile.
Stage 6 — Verification
When verification is enabled, CertErase reads the overwritten data back and compares it with the expected pass data. A failed verification receives one retry. Some profiles will carry out verification of the final pass even when full per-pass verification is not selected.
Stage 7 — File deletion
CertErase requests deletion only after the overwrite stage reports success. If overwrite or required verification fails, the file should be treated as not successfully erased even if part of its content was modified.
Stage 8 — Folder cleanup
After files are processed, CertErase attempts to remove selected folders. When configured, folder names and timestamps can be modified before removal. A remaining child item, lock, or permission issue can prevent folder removal.
Stage 9 — Post-deletion cleanup
When enabled, CertErase can fill addressable free space with temporary data and then remove the temporary files. This targets currently unallocated logical space; it does not sanitize controller-inaccessible regions, backups, snapshots, or remote copies. For that purpose, Probativa DriveErase complete device sanitization should be used.
Success definition
A successful operation means that CertErase completed its configured stages for the recorded targets without a reported fatal error. It does not independently prove physical media sanitization or elimination of copies outside the processed file system.