From ecfb8109f1c1190af681f7f6630ab3555432e05b Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Sun, 6 Jul 2025 18:58:29 -0600 Subject: [PATCH] Delete Scripts/Batch/VSS/Delete Shadow Copies.md --- Scripts/Batch/VSS/Delete Shadow Copies.md | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 Scripts/Batch/VSS/Delete Shadow Copies.md diff --git a/Scripts/Batch/VSS/Delete Shadow Copies.md b/Scripts/Batch/VSS/Delete Shadow Copies.md deleted file mode 100644 index 3bd73ec..0000000 --- a/Scripts/Batch/VSS/Delete Shadow Copies.md +++ /dev/null @@ -1,20 +0,0 @@ -## Purpose -You may find that you need to delete shadow copies on a disk for any number of reasons such as freeing up space. Sometimes the shadow copies simply don't want to be deleted gracefully. In those circumstances, you can use the two methods seen below to delete the shadows. - -!!! warning - These commands will delete **all** shadow copies for the associated drive letter. In these examples, the drive letter will be `D:\`. - -### Delete Shadows Via `vssadmin` -Vssadmin is generally the de-facto method of deleting shadows, as it is pretty graceful with the process, but sometimes antivirus might not let you run it thinking you are doing something ransomware-ish. If that happens, defer to the `diskshadow` method seen further below. -```batch -vssadmin delete shadows /for=D: /all /quiet -``` - -### Delete Shadows via `diskshadow` -This method is a little more aggressive than `vssadmin` and should be only used as a *Plan B* if `vssadmin` doesn't work. -```batch -diskshadow -set context persistent nowriters -delete shadows volume D: -exit -``` \ No newline at end of file