Windows 10 averaging over 50GB of writes/day to SSD over 9months
Rise to the top 3% as a developer or hire one of them at Toptal: https://topt.al/25cXVn
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Sunrise at the Stream
--
Chapters
00:00 Windows 10 Averaging Over 50gb Of Writes/Day To Ssd Over 9months
04:15 Answer 1 Score 0
04:36 Accepted Answer Score 4
05:54 Answer 3 Score 1
06:58 Thank you
--
Full question
https://superuser.com/questions/1229362/...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#windows10 #ssd #resourceusage
#avk47
ACCEPTED ANSWER
Score 4
You can use Task Manager to see what processes are writing the most data to disk.
Open Task Manager, select the Details tab, right-click on the table header, and click Select columns. Then check I/O read bytes, I/O write bytes, and I/O other bytes and click OK.
That said, I think File History is to blame here.
In my experience, the File History databases (Catalog1.edb
and Catalog2.edb
) can grow very large over time. To make matters worse, they are rewritten in their entirety every time the history is updated (every 10 minutes as configured on your system), and Windows will decompress them if you use NTFS compression. This can cause large amounts of writes to the disk over time.
Regardless of which drives are covered by File History, these databases are stored in your user profile at C:\Users\<username>\AppData\Local\Microsoft\Windows\FileHistory\Configuration
. With a pair of 100 MB databases, nearly 30 GB a day will be written to the system volume at 10 minutes per update, assuming it writes both files every time.
My solution was to use a junction point. Stop the File History service, move the Configuration folder to another location where write endurance is not an issue, create a junction point that points to the new location in place of the original location of the folder, and restart the File History service. That should fix the problem.
ANSWER 2
Score 1
You can potentially save a few more GB per day by disabling/redirecting WFP and NetCore logs :
(Info was found here: How to disable Windows 10 system log)
1. C:\Windows\System32\LogFiles\WMI\NetCore.etl
get constantly written, especially when multiple apps are open. You can redirect it to another drive with the following command:
logman update trace NetCore -ets -o X:\Some_dir\NetCore.etl
If you reboot you will need to launch the command again. So i created a (elevated) scheduled task on session start.
2. C:\ProgramData\Microsoft\Windows\wfp\wfpdiag.etl
get constant writes too.
You can simply disable the log :
netsh wfp set options netevents = off
3. I also disabled the NFTS last access (disabled in Vista/7 and reintroduced in 10) but i think it is negligible :
fsutil behavior set disablelastaccess 3
(default is 2)