From 2fb7046837a90721997f135cb081b7fb9b3bed21 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sun, 6 Jul 2025 19:09:02 -0600 Subject: [PATCH] Update Workflows/Windows/VSS/Delete Shadow Copies.md --- Workflows/Windows/VSS/Delete Shadow Copies.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Workflows/Windows/VSS/Delete Shadow Copies.md b/Workflows/Windows/VSS/Delete Shadow Copies.md index db267e0..88155fd 100644 --- a/Workflows/Windows/VSS/Delete Shadow Copies.md +++ b/Workflows/Windows/VSS/Delete Shadow Copies.md @@ -9,7 +9,7 @@ The `vssadmin` utility is the standard tool for managing shadow copies. It is ty However, some antivirus or endpoint protection software may block its execution due to its similarity to behavior used by ransomware. If `vssadmin` fails, use the `diskshadow` method described below. -```batch +```cmd vssadmin delete shadows /for=D: /all /quiet ``` @@ -20,7 +20,7 @@ vssadmin delete shadows /for=D: /all /quiet ## Method 2: Delete Shadow Copies Using `diskshadow` `diskshadow` is a more direct and lower-level tool than `vssadmin`. It should be used as a fallback option if `vssadmin` fails or is blocked. -```batch +```cmd diskshadow set context persistent nowriters delete shadows volume D: