Windows 10: Deleting files does not free space after "Volume Shadow Copy" MS malware removed.

Is Windows actually counting free space, or just guessing? How can I delete 2.5GB from the recycle bin and have only 20MB free space afterwards? Why does deleting files not free space, I have already disabled the malware "System Volume Shadow Copy" which does nothing but eat all free space available, yet I still run out of space without adding anything to the system. I can delete 1GB file, reboot, and have only 100MB remaining before I have had the chance to do anything. It's bad enough that win10 takes an average of 45 hours to finish booting every single time (when disk activity finally dips below 100%), now deleting files does not free space? Win 10 installation has ballooned to over 280GB in size with only 90GB of applications installed, for no discernible reason.


But I'm guessing I won't get a response, because I called Microsoft out on their innumerable lies about win10, like the F8 menu disappearing

(MS tech support, 14 different occasions: "Win10 boots too fast to see F8 Key"...Me: Discovers registry key [fastboot = 1) disabling F8 menu and it always works now)

or how MS has removed Intel Drivers for the Radeon 3650 PCI in windows 10 river database that would allow me to use OpenGL 3.1 that it was designed for and working on Win7 and blamed it on Intel. Or how MS tech support said something wasn't possible on Windows XP Sp3 some time ago after I just did it while on the phone with them. Maybe it's because I have had to write apps to force registry keys to stay in place so that Update doesn't destroy them, if not force Update through a VM and install the files manually so that it doesn't corrupt the OS like it does every single time with thousands of illegitimate and corrupt registry entries and overturning my settings like disabling useless and wasteful services like Print Spooler and Cortana (have to delete the exe AND dll's to remove Cortana)?


Maybe I should ask "How do I get a refund for my Windows license, so I can buy a functional operating system to replace it before it destroys my hardware?"

:)

 

Removing errant files in the "System Volume Information" folder under Windows 10.

Hi,

Thank you for posting your response.

I suggest you to first stop Volume Shadow Copy service and try to remove the files and check. Follow the steps provided below:

Step 1: Stop Volume Shadow Copy service

• 
  Press Windows logo Key + R key.
  
• 
  Type services.msc.
  
• 
  Search for Volume Shadow Copy service.
  
• 
  Right click on it and select
  Stop.
  

Now, take ownership of the System volume Information folder and then try to delete its contents.

Step 2: File permissions.

• Right click on System volume Information folder.
• Select Properties.
• Go to Security tab.
• Select the user name.
• Click on Edit button.
• Under permission to Authenticated user, check on full control.
• Click on Apply and OK button.

Hope it helps. Do let us know the status of the issue. If you need further assistance, get back to us. We will be glad to assist you.

 

Shadow copies are deleted automatically

Hi all,

I am using Windows 2008 R2 for file server function, and already configured shadow copy.

Issues: When size of shadow copy reach to maximum size (100GB in my case), all my previous shadow copies are deleted.

My understanding is it will delete oldest shadow copy first, until enough space to create new shadow copy.

Can anyone explain to me why all my shadow copies are deleted? (about 10 days)

Thank you,

 

Shadow Copy With Storage Spaces?

1 Create shadow storage

1.1 The System protection tab in System Properties

• this GUI only lists NTFS volumes, so you can't create shadow storage for ReFS volume there
  
• instead try one of:
  
  • vssadmin add shadowstorage /for=D: /on=D: /maxsize=100GB (Windows Server only)
    
    • alternatively for non-server Windows editions try vssadmin resize shadowstorage /for=D: /on=D: /maxsize=10% that will add shadow storage if it does not exist and thus is comparable to vssadmin add
      
  • wmic shadowstorage call create Volume=D:\ DiffVolume=D:\ MaxSpace=20
    
    • if this command returns ReturnValue = 10 (which is Unknown error) workaround follows
      
  • wmic shadowcopy call create Volume=D:\
    
    • creating shadow copy on disk without shadow storage will create one automatically
      
    • you can resize the shadow storage with vssadmin resize shadowstorage /for=D: /on=D: /maxsize=10%
      

1.2 List shadow storages

• make sure the shadow storage is there and configured using one of:
  
  • vssadmin list shadowstorage
    
  • wmic shadowstorage list
    

2 Create shadow copy

2.1 Create shadow copy

• you want to use scheduled system protection feature, but for now just take a snapshot manually:
  
  • wmic shadowcopy call create Volume=D:\
    

2.2 List shadow copies

• verify the snapshot was created:
  
  • vssadmin list shadows /for=D:
    

3 Mount shadow copy

• since you are using Storage Spaces, you won't see snapshots in Previous versions tab in disk/file properties
  
• but the snapshots exists and can be mounted as a folder
  
• this shortage apply for both NTFS and ReFS Storage Spaces
  
• to mount a snapshot you will need shadow ID, shadow path and temporary folder
  

3.1 Get shadow copy ID

• vssadmin list shadows /for=D:
  
  • look for something like this Shadow Copy ID: {5cc29315-0379-415e-8496-69923618e3de}
    

3.2 Get shadow copy path

• wmic shadowcopy where "ID='{5cc29315-0379-415e-8496-69923618e3de}'" get DeviceObject
  
• or vssadmin list shadows /for=D:
  
  • look for Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy624
    

3.3 Mount shadow copy as folder

• mklink /j %tmp%\shadow \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy624\
  
  • note the extra \ at the end
    
  • the shadow copy is now available in %tmp%\shadow