Image processing can occasionally need to be stopped before completion. You might discover that the wrong photographs were selected, realize that a profile is unsuitable, or encounter a problem with storage or decoding during a batch.
PhotoSanitize provides cancellation for supported running operations. Because processing takes place image by image, an interrupted batch may contain completed outputs alongside files that were not finished.
Canceling processing
When an operation is running, choose Cancel from the progress display. PhotoSanitize stops the operation as the cancellation request takes effect.
Cancellation does not necessarily undo work that had already completed. If several photographs were successfully sanitized before the request was handled, their output files may remain available.
Likewise, an image that was being processed when cancellation occurred should not be assumed to have completed successfully.
Checking the queue after cancellation
When the operation stops, inspect the Photo Queue and the status of each included file. An image that completed sanitization and verification may be usable, while another may still be unprocessed or have an incomplete result.
The distinction is particularly important when cancellation occurs during verification. A sanitized file may exist on disk without having completed the applicable checks.
Open Verification for each relevant image and confirm its result. Do not distribute an output simply because its filename exists in the destination folder.
Recovering from a processing failure
When an individual image fails, start by examining the displayed error and the operation it relates to. A source-access problem is different from an unsupported image conversion or incomplete visual review.
If the error concerns reading the file, confirm that the original still exists, can be opened, and is accessible to your Windows account. Files stored on removable media or network shares may become unavailable during processing if the device or connection is interrupted.
If the problem occurs while creating the output, check that the destination directory can be written to and has sufficient free space. A custom output folder may have permissions different from those of the source directory, particularly on an organization-managed computer.
Format-related failures require a different response. An image may be suitable for metadata inspection but lack the decoding or encoding support needed for reconstruction. A specialized TIFF may require more restrictive settings to preserve its sample characteristics. In these cases, review the selected profile and output format rather than repeatedly running the same unsupported operation.
When PhotoSanitize reports that visual review is incomplete, return to Visual Privacy, complete the required detection and redaction review, and choose Mark Reviewed before sanitizing again.
Recovering after an application or system interruption
If Windows shuts down, PhotoSanitize closes unexpectedly, or the storage connection fails, reopen the application once the environment is stable. Add the source files again and repeat the relevant analysis and sanitization steps.
Because the originals are retained, you can create a fresh output without depending on an interrupted processing state. Confirm the active profile, output directory, and any required visual redactions before restarting.
If previous output files remain in the destination, PhotoSanitize uses collision-safe naming rather than simply overwriting them. Check the new filename carefully so that you do not mistake an earlier incomplete result for the latest processed image.
Recovering a batch
For a large collection, it is usually unnecessary to repeat every successful file. Identify which photographs completed sanitization and verification, then prepare a separate selection containing the unsuccessful or interrupted files.
Use their individual statuses and any exported processing records to track what remains to be done.
For organizational work, keep incomplete outputs outside the approved distribution folder. Only move a file into the final collection after its sanitization and verification results have been reviewed.
An interrupted operation is not necessarily a problem with the entire collection, but its results must be checked individually before the files are used.