Over the past few months, I’ve uncovered how the default settings Windows 11 decides are usually not in the best interest of users, whether it’s about user experience, accessibility, resource allocation, or even power plans. Most of these are very obviously tuned in a way that’s not optimal for most users, and for those with multiple drives, this aspect applies to storage as well.
The past few weeks have got me rethinking how I manage my PC’s combined 1.2 terabytes of storage, which pinches just past the 1TB mark most users work with in 2026, but a little lower than optimal capacity on a dedicated workstation. This is exactly why reclaiming control over my storage from Windows’ grasp became so important, especially since its defaults insisted everything belonged on the boot drive.
OneDrive was turning my second drive into a spectator
Moving the sync folder can reclaim a decent chunk of space
The first thing I looked at was OneDrive, primarily because it was creating a rather paradoxical situation on my PC with a PCIe Gen 4 NVMe and a SATA SSD. I had a perfectly good second storage solution sitting mostly unoccupied, while Microsoft’s cloud storage was ballooning up in my boot drive, because I like to keep the files always on the device.
If you use OneDrive, its local folder naturally gets assigned a spot on your boot drive. That can become expensive once you start keeping portions of cloud library available offline. Worse still, if you’ve enabled OneDrive’s backup for Desktop, Documents, or Pictures, those Windows folders can become a part of the OneDrive ecosystem as well.
Fortunately, there is an option to move OneDrive itself rather than struggle with individual folders. From OneDrive’s settings, you can unlink the PC. Before signing back in, manually move the existing OneDrive folder to the secondary drive so that when you select that folder during setup, OneDrive can index and merge local files instead of re-downloading everything. OneDrive will then proceed to sync against that location instead of ballooning up on the boot drive.
Clearing this space is pointless if it keeps refilling
That’s why my new files needed a new destination
If I simply just moved the bulk of my C: drive to the D: drive, it’d quickly become a repetitive chore that I’d have to go through month after month, or week after week to save my Crucial T500 from the constant write cycles that Windows puts it through. As such, I needed to stop the leak before I bothered to mop the floor.
What most people don’t know is that there’s a simple fix to this exact predicament that Windows makes available through the settings, and to Microsoft’s credit, the option is quite accessible. All you have to do to find it is go to Settings, then System, followed by Storage, then go into Advanced Storage Settings below it. This will unveil an option that most users will not have seen before, which is “Where new content is saved”.
The dropdowns here on this menu allow you to specify the destination for new file downloads. I could just change the dropdowns to D:, which gives the system a place to put new content instead of continually adding to the drive that would fill itself to critical levels over a period of a few months. Embarrassingly enough, even I discovered it by going through a couple of posts on Microsoft Tech Community forums.
One file refused to leave C:, so I got rid of it instead
hiberfil.sys has to be on the boot drive, but my desktop doesn’t need it at all
Most of the storage strain Windows was putting on my boot drive could simply be migrated elsewhere, but then I found one particularly stubborn exception by the name of hiberfil.sys. If you’ve been following my coverage, you’d know that I stumbled upon the 12.5-gigabyte file while going through my NVMe SSD and found that the reason it exists is because of a Windows feature called Fast Startup.
The file sits on your C: drive, holding the contents of your system memory, and it does so to hold the contents of RAM, which allows the machine to hibernate. Unlike the page file, it must always stay on the boot drive, and there’s no supported way to move it to another.
How big the file gets depends on your system memory, because it can grow up to 40% of its size. On my machine with 32GB of DDR5 memory, it grew up to 12.5GB, which is exactly 39%. I’d argue that hibernation is a useful feature on mobile devices like laptops where there’s actually a use case for preserving a session and resuming later, but on a desktop backed by a PCIe Gen 4 SSD that can be up and running in no time, the extra storage matters more.
To make the hiberfil.sys file go away, you too, can use the following command on an elevated CMD or PowerShell. Bear in mind, this also does away with Fast Startup functionality.
powercfg /hibernate off
The boot drive doesn’t have to be the default location for everything
It’s widely acknowledged that Windows defaults don’t really serve the users all that well, and the same logic applies to how storage is managed on the drives as well. However, it’s also true that the OS is flexible enough for the savvy user to take back control, redirect (or eliminate) the biggest offenders and manage their storage better themselves.
For more details and an in-depth look at managing Windows storage settings, visit Here.
“`
