Multi-Item Moves Stay Sequential, Visible, And Recoverable.
DiskFreeVault does not shotgun changes across your disk. Batch mode builds a queue, evaluates each item, skips unsafe running apps, and reports moved, failed, blocked, and skipped results clearly.
How batch mode behaves
The queue is built once, then each item is evaluated and executed in a deterministic order so the results stay readable and the filesystem stays safer.
Select
Use multi-selection to choose multiple items from one side before you start the move.
Preview
The dry-run plan lists every item with its own status, compatibility level, and privilege expectation.
Execute
Items run one by one instead of in parallel, which keeps rollback and progress reporting understandable.
Summarize
The app reports moved, failed, blocked, skipped, and needs-closure states instead of flattening everything into one message.
Running Apps In Batch
Batch mode does not force-close app bundles automatically. If a selected app is currently running, the plan marks it as skipped so the rest of the queue can continue safely.
- ✓Single-item app moves can ask you to close or force-close the app.
- ✓Batch mode prefers predictable skipping over surprise termination.
Privileges In Batch
If protected filesystem steps need admin access, DiskFreeVault applies the selected privilege strategy and tries to minimize repeated prompts within the same operation session.
- ✓SMAppService Preferred can use the helper and fall back when needed.
- ✓Admin Prompt Only uses direct privileged command execution.
- ✓SMAppService Required refuses to continue if the helper path is unavailable.
Every queue entry tells you what happened
That matters when a batch mixes safe items, blocked items, running apps, and paths that may need elevated access.
Ready
The item passed preview checks and can execute immediately when you continue the plan.
Needs Closure
Single running app bundles can proceed only after you explicitly close or force-close the app.
Skipped
Batch mode leaves running app bundles alone and marks them as skipped so the rest of the queue can continue.
Blocked
The move is refused because the path, destination, privilege, or compatibility rules say it should not continue.
Next: see how Safety Status decides those outcomes
The queue is only as trustworthy as the safety rules behind it. The Safety Status page explains those rules in detail.