There’s nothing the sysadmin should have to worry about here. This is entirely on Windows. No other system in existence just fills up the space of the drive it’s on like this. This isn’t configured poorly. It’s just a bad OS.
My Windows 10 installation is on a 120GB partition on a 256GB NVMe SSD with hibernate off and I don’t have these issues. I have applied these changes since the first laptop I bought, 2012 Windows 7.
You shouldn’t have to do this to avoid the massive bloat and new users shouldn’t be expected to have to learn how to “fix” their brand-new operating system.
Sure, but this doesn’t change the fact that it’s the fault of the OS and that the user shouldn’t have to take these steps. I totally believe Windows does this, but not that it has any legitimate reason to happen.
The reason Windows works like this is because there are loads of people who try to run Windows 10 on super old weak Intel Celerons so they try all kinds of caching steps to make it manageable.
It would be better if Microsoft made some sort of lite edition, or immediately give you the option to turn this stuff off when configuring it. Problem is, Windows is used by a lot of people and most people have no clue how to configure an OS.
You have two options: either spend a lot on a computer that can run the OS it comes with without issue (Apple), or try your luck with a GNU/Linux distro, for which you might need to develop some knowledge about what you’re doing.
There’s nothing the sysadmin should have to worry about here. This is entirely on Windows. No other system in existence just fills up the space of the drive it’s on like this. This isn’t configured poorly. It’s just a bad OS.
My Windows 10 installation is on a 120GB partition on a 256GB NVMe SSD with hibernate off and I don’t have these issues. I have applied these changes since the first laptop I bought, 2012 Windows 7.
You shouldn’t have to do this to avoid the massive bloat and new users shouldn’t be expected to have to learn how to “fix” their brand-new operating system.
Sure, but this doesn’t change the fact that it’s the fault of the OS and that the user shouldn’t have to take these steps. I totally believe Windows does this, but not that it has any legitimate reason to happen.
The reason Windows works like this is because there are loads of people who try to run Windows 10 on super old weak Intel Celerons so they try all kinds of caching steps to make it manageable.
It would be better if Microsoft made some sort of lite edition, or immediately give you the option to turn this stuff off when configuring it. Problem is, Windows is used by a lot of people and most people have no clue how to configure an OS.
You have two options: either spend a lot on a computer that can run the OS it comes with without issue (Apple), or try your luck with a GNU/Linux distro, for which you might need to develop some knowledge about what you’re doing.
Or put up with Windows’s shit.
Windows S mode?
\s