5 Outdated Windows Maintenance Habits: When Reinstalls, Defrag and Pagefile Tuning Still Help

The useful distinction is between routine rituals and targeted troubleshooting. Here are the five habits, checked against Microsoft's own documentation.

1. Reinstalling Windows on a schedule​

The case against annual reinstalls is solid. The wrinkle is the claim that DISM and SFC have "effectively eliminated" the need to reinstall. Microsoft doesn't frame it that way. Reinstalling is still part of its recovery ladder, but it now sits near the bottom and comes in several levels of severity.

Microsoft's Windows 11 guidance describes a "Fix problems using Windows Update" option that is the gentlest option. It reinstalls the same Windows version, repairs system files and components, and preserves your apps, files and settings. Wait, that is from Microsoft's support page, so I'm describing it from the evidence rather than from the search results above.

To use it, follow these steps:

1. Go to Settings > System > Recovery.
2. Under Fix problems using Windows Update, select Reinstall now.
3. Choose whether the PC may restart automatically 15 minutes after the install completes.
4. Select OK, and keep the PC on power and online throughout.

It won't appear on every machine. Microsoft says it may be missing on work- or school-managed PCs. It may also be missing on builds older than Windows 11 with the 2022 annual update. You also need the February 2024 optional update or later. For IT admins, devices with managed update policies, such as WSUS location settings or deferral and target-version policies, won't offer it.

Microsoft's recovery page ranks the other options by how disruptive they are:

• Reset this PC reinstalls Windows and lets you keep or remove personal files.
• Cloud rebuild on Windows 11 removes personal files, apps and settings.
• Clean install from installation media is Microsoft's suggestion if you suspect malware or nothing else works. It says to run a Windows Security scan first.

Back up your files before any of these. If BitLocker is on, make sure you know your recovery key.

Verdict: Don't reinstall on a calendar. Do keep reinstall options in mind for real faults, starting with the least destructive one.

2. Manually defragmenting and optimizing drives​

The article says to stop doing this "every month." That doesn't match Windows. Microsoft says Windows optimizes your drives once a week by default. Microsoft also says Windows automatically optimizes data drives "for the most part."

The tool treats the two drive types differently. Microsoft explains that hard drives are defragmented, while SSDs are "trimmed". Trimming tells the drive where it can safely clean up when it isn't busy. Third-party guides say the same: Windows detects solid-state media and changes what the Optimize button does. One caveat from a Windows-focused outlet is that Windows can still run a traditional defrag on SSDs about once a month. That claim comes from a single source and I haven't verified it against Microsoft documentation. Treat it as an open question, not settled fact.

The real mistake here isn't running the tool by hand. It's switching the schedule off. Microsoft lets you do that, but there's no benefit in doing so. Commentary from the SSD-tweak world makes the same point: turning the schedule off disables maintenance your SSD relies on.

To check that it's working:

1. Search for defrag and open Defragment and Optimize Drives.
2. Select a drive. On a hard drive, Analyze shows whether it needs work.
3. Under Scheduled optimization, select Change settings to confirm the schedule is on.

Verdict: You don't need to run it by hand. Leave the weekly schedule enabled.

3. RAM cleaners​

The article's practical advice is sound: don't judge health by the "memory used" percentage alone. Microsoft's performance documentation explains why. Available memory includes both free and standby memory. Standby memory holds cached data and files that are in memory but not actively in use, and it becomes available when an application needs it.

That means a "full" RAM graph often reflects useful caching, not waste. A cleaner that dumps the cache can make the free number look better while forcing Windows to reload data from disk.

Two caveats apply:

• Microsoft's material explains memory categories. It doesn't prove that every high-usage case is harmless.
• The article's line that persistent RAM exhaustion simply means you need more RAM is a rule of thumb, not Microsoft guidance.

If you suspect a real problem, look for symptoms such as sluggishness, hard-paging storms or a single process growing without limit. Microsoft's Sysinternals RAMMap is an advanced tool for this. It breaks down physical memory by use counts, process working sets, standby priorities and file data cached in RAM.

Verdict: Skip the cleaner. Investigate sustained pressure rather than chasing a high free-memory figure.

4. Registry cleaners​

The article says registry cleaners don't deliver measurable gains and can cause harm. The strongest evidence I have is indirect. Microsoft's formal documentation doesn't quantify cleaner benefits. A Microsoft Q&A answer from an MVP says Windows has no built-in cleaner. It says residual entries are usually harmless and don't slow the system, and that automated cleaning can break apps if the wrong key goes. That's a community answer, not official policy, so weigh it accordingly.

The practical rule is simple. Edit the registry to fix a specific, understood problem. Don't run a cleaner in hope of a faster PC. If you're worried about corruption rather than leftovers, the Q&A answer points to sfc /scannow and DISM, which repair system files rather than orphaned app entries.

Verdict: The performance claim is unproven and the downside is real. Skip it.

5. Manually setting or disabling the pagefile​

This is the one where "never touch it" needs the most nuance. Microsoft's guidance says page files are system-managed by default. They grow and shrink based on installed RAM, commit charge and crash-dump needs. Microsoft also says sizing is unique to each system and can't be generalized.

Some of the documented specifics:

• The system-managed maximum is three times RAM or 4 GB, whichever is larger. That's a ceiling, not a typical size.
• The minimum varies with usage history, RAM and crash-dump settings.
• If you want a crash dump, a page file or a dedicated dump file must exist and be large enough. Disabling it outright can therefore cost you diagnostics, not just virtual memory headroom.

So the old "1.5 to 2 times RAM" formula isn't a modern universal recommendation. But there are exceptions. Microsoft documents a Windows 10 problem involving memory-allocation errors tied to slow page-file growth. Its workaround is a manual size, starting at 1.5 times RAM. That is why "don't tweak by habit" is better advice than "never configure it."

Verdict: Leave consumer PCs on system-managed. Change it only for a documented issue, a specific workload or admin guidance.

What's still worth doing​

Windows maintenance isn't fully hands-off. The article ends by pointing to apps and graphics drivers, and that's reasonable. Updates, backups and a recovery plan matter more than any of the five rituals above. Microsoft's own recovery guidance suggests enabling Windows Backup, keeping your BitLocker key handy and creating a recovery drive while the PC still works.

Bottom line: The article is right about the direction. Windows has absorbed most of these chores. Where it oversimplifies, it overstates how final the verdict is. Reinstalling, pagefile tuning and manual optimization all remain legitimate tools when something is actually wrong.