Please note that our forum is a public platform, and we will modify your question to hide private, identifiable information in the description. Kindly ensure that you hide such details the next time you post to protect personal data.
For the 1) question, I was referring to the relationship between backup/System Restore operations and Volume Shadow Copy Service (VSS). Microsoft's VSS documentation confirms that VSS is used by System Restore and backup scenarios, including backups archived to another hard drive
To clarify my point, "Windows thinks there is already a system image backup associated with that drive" - "that drive" here is the one being backed up. For example, if you're backing up C:, it doesn't matter where (a second HDD in your case), Windows saw "C: has a backup". That's what I meant.
- Now for the yellow triangle, like I previously said, it was just a warning that restore points could be deleted sooner because System Restore and system-image backup operations both use the Volume Shadow Copy Service. It was not, by itself, evidence of corruption or anything wrong.
- Your screenshots show that
C:currently has one shadow copy, created on September 13, 2026. So it seems like System Protection is currently creating snapshots again. However, older restore points are no longer listed, so those were truly removed, and unfortunately, the reasons for it cannot be identified.
For the 2) question, if it's D:, based on what you posted, VSS/shadow copies do not appear to account for that loss of space. It actually shows 0 bytes of used Shadow Copy Storage right now. Either way, for the secondary HDD issue, I suggest checking what is actually consuming the space:
- Go to Settings > System > Storage > Advanced storage settings > Storage used on other drives.
- Select the secondary internal HDD and check which category is using the additional space.
- Also check the Recycle Bin, because files deleted from drive can continue taking space.
So, although it was reasonable to wonder whether the two symptoms were connected, the vssadmin results currently point toward two separate issues rather than VSS being responsible for the unexplained loss of free space.