You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noticed C: free space getting to low because of cached videos stored into it ,so I changed it to D:
After letting the screensaver run for a bit I noticed the space on th C: drive dropping low again. Checked the new cache folder on D: for videos, all ok new videos have been added. Performed a restart on the computer, C: free space gone back to normal(this solution doesn't apply on shutdown due to fast Startup option on Windows 10).
I let the screensaver run again, checked th C: drive again, space has decreased by ~1.2Gb. Checked new caching location on D: also gets larger alongside. Decided to run the Windows Disk Cleanup Tool, free space returned to normal. Also performed a check with some disk space analyzer tools, can't find anything related to .mov files.
This problem only occurs when I run the screensaver, so no other app appears to be responsible for this issue.
The text was updated successfully, but these errors were encountered:
Noticed C: free space getting to low because of cached videos stored into it ,so I changed it to D:
After letting the screensaver run for a bit I noticed the space on th C: drive dropping low again. Checked the new cache folder on D: for videos, all ok new videos have been added. Performed a restart on the computer, C: free space gone back to normal(this solution doesn't apply on shutdown due to fast Startup option on Windows 10).
I let the screensaver run again, checked th C: drive again, space has decreased by ~1.2Gb. Checked new caching location on D: also gets larger alongside. Decided to run the Windows Disk Cleanup Tool, free space returned to normal. Also performed a check with some disk space analyzer tools, can't find anything related to .mov files.
This problem only occurs when I run the screensaver, so no other app appears to be responsible for this issue.
The text was updated successfully, but these errors were encountered: