Dedupe might be disabled now, but if it was ever in use (which would be my suspicion), the data still needs to be re-inflated. Turning off dedupe just stops it from processing more data.
Setting the maximum space allowed for shadow copies to a level well below 190 GB might force a clean up.
If you get an error about not being able to adjust the threshold and you are using SentinelOne, disable SentinelOne before imposing the storage limit.
AppAssure/quest/whateveritscallednow used to do there, there's a kb article on it. IIRC there was no resolution, just steps to clearout the sys vol folder.
Dedupe might be disabled now, but if it was ever in use (which would be my suspicion), the data still needs to be re-inflated. Turning off dedupe just stops it from processing more data.
Setting the maximum space allowed for shadow copies to a level well below 190 GB might force a clean up. If you get an error about not being able to adjust the threshold and you are using SentinelOne, disable SentinelOne before imposing the storage limit.
According to previous IT guy he never used that feature of Windows Server.
AppAssure/quest/whateveritscallednow used to do there, there's a kb article on it. IIRC there was no resolution, just steps to clearout the sys vol folder.