I have a little idea. I know Windows does a lot of useless disk access¹, but I never thought it was localized before I tried a VM. I always assumed it was random, but it looks like it's kinda random, but all over the same small area, and Windows can't optimize it for some reason.
Anyway, if you do that, you better keep those ~3GB free. If you don't have enough cache things break down really fast.
1 - It is for cortana, file indexing, telemetry, and etc. If you take the time to disable them, your computer will get much faster... for about a week, until it updates again.
While we're spitballing, from my recollection, it seems to do a lot of small writes; probably different write cache policies, possibly including the VM not passing through fsync/write barriers.
And, you know, organizational failure to have this issue lingering.
Anyway, if you do that, you better keep those ~3GB free. If you don't have enough cache things break down really fast.
1 - It is for cortana, file indexing, telemetry, and etc. If you take the time to disable them, your computer will get much faster... for about a week, until it updates again.