Wondering what the heck Rimuru is so lethargic at I/O, to the point that programs take minutes to launch from the start menu and Explorer instances minutes to refresh.
Task Manager reports that my NVMe drive is at locked on 100% but only registers tens of MB/s in I/O. That's kind of silly in more ways than one.
Running perfmon /res from PowerShell, imagine my greater surprise when the Resource Monitor paints the finger at PID 4, SYSTEM and shows executable files from the new XBox advanced management feature.
Now here's the real kicker! Of the top three entries two are for a file that no longer exists on disk because I uninstalled the game a few weeks ago. Both marked at roughly 10~11 MB/s reads if you translate the B/s into reality. The third is installed but is registering ~4.5 MB/s reads for a file that is 600 something KB in size.
But I suspect that this non-sense is also a red herring, as system performance has leveled off despite the silly entries in the monitor. Whatever really sledgehammered the drive at startup is likely long since gone by the time I could get the monitors up and running.
That said, I kind of have to wonder what kind of I/O pattern could possibly register tens of megabytes of reads on a file that does not exist for thirty plus minutes and going, and if it did exist, would probably fit on a floppy diskette with plenty of room to spare.