Blog

The number I keep coming back to is 40 gigabytes. That was the amount of orphaned junk I cleared off a colleague’s laptop last spring, and not one byte of it showed up in Settings > Apps. It was all in AppData, ProgramData, and a handful of registry keys that the original installer had written and the built-in uninstaller had quietly forgotten. Windows removes what the developer told it to remove. When the developer’s uninstall script is lazy, the leftovers stay.

So people go looking for a free uninstaller. The category is crowded with tools that promise to scrub every trace, and most of them do roughly the same thing: they watch what an installer writes, then delete it later. The difference is in how much they actually catch, whether they nag you to buy something, and whether they leave your system in a state you can still boot. Here is what I’ve settled on after installing and testing these on real machines, including a couple I’d rather you skip.

What a leftover actually is

Before picking a tool, it helps to know what you’re hunting. When you run a normal setup program, it scatters files in at least four places: the install folder under Program Files, a per-user folder in AppData, a machine-wide folder in ProgramData, and registry branches under HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. A good uninstaller records all of that during installation and sweeps it on removal. A bad one only knows about Program Files.

The ones worth your time work by monitoring. You launch the installer through the uninstaller, it logs every file and key written, and later it offers to remove exactly those. That’s a different job from a cleanup tool that guesses at leftovers after the fact. If a program advertises “deep scanning for leftover files” but never watched the install happen, treat its findings with suspicion. It’s pattern matching, not memory.

The ones I keep on my own machines

BCUninstaller (Bulk Crap Uninstaller) is the one I reach for first, and it’s open source and free with no upsell. It lists everything Windows knows about, sorts by size, and can run several uninstallers in sequence while you step away. The quiet uninstall feature is genuinely useful for clearing a batch of bloatware off a new PC without clicking through fifteen wizards. It also detects leftover files and registry entries, though I let it show me the list rather than auto-delete. Its detection is good, not perfect, and blind deletion is how people break things.

Revo Uninstaller Free is the one I recommend to non-technical staff because the interface doesn’t scare them. It launches the program’s built-in removal tool before sweeping for leftovers, then shows you what remains so you can tick off each item. The free version handles the core job fine. The paid tier adds forced removal and some monitoring features, but the free one does the scan-and-clean that most people actually want. The nag screen on launch is mildly annoying. Tolerable.

Geek Uninstaller is a single portable executable, which matters when you’re working on someone else’s locked-down machine and can’t install anything. It’s tiny, fast, and has a force-remove option for programs that refuse to leave. It does less than Revo, but it does the essential part without drama. I keep a copy on a USB stick.

IObit Uninstaller Free works, and its leftover scan is decent, but it bundles offers during installation if you’re not careful with the checkboxes. Read every screen. If you click through on autopilot you’ll end up with a browser toolbar you didn’t ask for, which is a strange thing for an uninstaller to give you.

Two I’d steer you away from: anything that requires an account to remove software, and anything whose “free” tier caps how many programs you can uninstall per day. That last one is a business model, not a tool.

The registry question

People worry about registry leftovers more than they should. A stray key for a program you removed is mostly harmless. It sits there, costs nothing, and Windows ignores it. The real space hogs are the AppData folders and the leftover install directories, which can run to gigabytes for something like a game or a creative suite.

That said, if you’re the person who gets called when a machine misbehaves, leaving broken registry entries around eventually causes confusion, not crashes. My rule: let the uninstaller clean registry entries it actually recorded, and skip the ones it merely guessed at. If a tool shows you a list of “suspicious” keys it found by scanning, and you don’t recognize them, don’t delete them. That caution has saved me more reinstall calls than any aggressive cleaner ever did.

When you don’t need a fancy uninstaller at all

For everyday removals, the built-in Settings > Apps list is fine. Most mainstream installers clean up after themselves reasonably well. The third-party tools earn their keep in three situations: clearing bloatware off a fresh PC in one pass, removing something that crashed halfway through its own uninstall, and tracking down the folders a sloppy installer left behind.

For that last job, pair your uninstaller with a disk space viewer. WizTree scans a drive in seconds and shows you, as a visual map, exactly which folders are eating space, and you can manage files from inside it. I’ve used it to spot a forgotten 8GB video file and, more relevantly here, the leftover AppData folder of a program whose uninstaller claimed it was gone. Windows’ own Storage settings give you a rough overview. WizTree gives you the actual folders. Between a monitored uninstaller and a fast space viewer, you can account for every byte without guesswork.

How I actually run a clean removal

• Install the program through the uninstaller if you can, so it gets watched from the start. If it’s already installed, skip to the next step.
• Run the uninstaller’s removal, and let the program’s own uninstaller finish first. Don’t interrupt it.
• Review the leftover list it presents. Delete the install folder, the AppData folder, and any shortcuts it found. Leave registry items you don’t recognize.
• Open WizTree or a similar viewer and check the ProgramData and AppData folders by size. If a folder for the removed program is still there and large, delete it manually.
• Reboot, then confirm the app is gone from Settings > Apps and that nothing you rely on broke.

The reboot matters. Some files stay locked until the process that holds them exits, and a program that “won’t delete” often just needs the machine restarted before you try again.

What none of these will do

No free uninstaller will recover space from a program that installed a background service or a driver and left it running, unless you stop the service first. They also won’t clean up leftovers from software that was already uninstalled months ago unless you point them at the folders manually. And they won’t fix a machine whose problems come from something other than leftover files, which is most of the time.

My honest setup after years of this: BCUninstaller for bulk work, Revo Free for the machines I hand to other people, Geek Uninstaller on a stick for emergencies, and WizTree to verify the job is done. That combination has never failed to find the gigabytes, and it has never once required me to buy anything.

Four calls in the first week. That is roughly my average after handing a freshly set up Windows 11 machine to someone who doesn’t work in IT. Not because the hardware is bad or Windows 11 is broken, but because the out-of-box experience is built for a version of your relative or coworker who reads settings menus for fun. They don’t. So the setup job is really about removing decisions before they get a chance to make them badly.

Here is how I prep a machine now, in the order I actually do it, with the reasoning behind each step so you can skip the ones that don’t apply to your person.

Start with the account, not the desktop

Create a local administrator account for yourself and a standard user account for them. This one decision saves more support calls than anything else on this page. When they click something they shouldn’t, and they will, the damage is contained to their profile. When you need to install something or change a system setting, you sign in with your own account and do it cleanly.

Set the machine to sign in automatically if they live alone. Password fatigue is real, and a sticky note with a password on the monitor is worse security than no password prompt at all. If they share the machine or take it out of the house, skip this.

Cut the background noise before it becomes a complaint

A slow PC complaint is almost always a background process complaint. Windows 11 ships with a crowd of startup apps and background permissions that the average user never asked for. Microsoft’s own performance guidance points at three fixes that are genuinely worth doing on day one.

• Uninstall the junk. Settings > Apps > Installed apps. Game launchers, trial antivirus, the manufacturer’s “assistant” software. If you didn’t put it there and they won’t use it, it goes.
• Trim startup apps. Ctrl + Shift + Esc, then Startup apps. Disable anything they don’t recognise. That includes the vendor updater that pops a window every boot.
• Kill background permissions for the apps that don’t need them. Settings > Apps > Installed apps, then Advanced options on each one, and set the background permission to Never for anything that isn’t a mail client or a sync tool.

While you’re in there, set the power mode to Best performance unless battery life matters more than speed. On a desktop this costs nothing. On a laptop, think it through.

One more: the visual effects. Open the performance options in Windows and either set it to adjust for best performance or, if you want it to still look like Windows 11, leave animations on and turn off the transparency effects. On older hardware the difference is noticeable. On a modern machine it’s cosmetic, so use your judgement.

Lock down the settings that generate confusing prompts later

This is the part most people skip, and it’s the part that produces the “a window popped up and I clicked yes” phone call.

Open Settings > Privacy & security and work through it methodically. Diagnostic & feedback: turn off Send optional diagnostic data. That optional data includes app activity and browsing history, which nobody needs to share to keep their PC working.

While you’re on that page, turn off Improve inking and typing. It’s another feedback channel, and turning it off breaks nothing.

Then go to General and turn off the advertising ID. I explain it to people this way: Windows stamps a unique number on your profile and apps can use it to build a picture of what you do. Turning it off doesn’t remove ads from Windows, but it stops the personalised tracking behind them. Fewer surprises, fewer targeted pop-ups that look like system warnings.

Under Speech, turn off online speech recognition if they won’t dictate. It sends audio to Microsoft for processing. Leave it on only if they actually use voice typing.

Finally, App permissions. Go through camera, microphone, location, and the rest one category at a time. A note-taking app has no business touching the microphone. This is the most tedious part of the setup and the one I consider non-negotiable. If you do one privacy pass, do this one.

Updates: turn them on and set the window

Windows Update stays enabled. Fighting it is a losing battle, and unpatched machines are how people end up with the problems they call you about. But you can stop updates from rebooting the machine mid-afternoon.

Set active hours in Windows Update so it won’t restart while they’re working. Then check Optional updates occasionally, because drivers and firmware sometimes land there rather than in the main feed. I check it right after setup and leave it alone after that, since chasing every optional driver is how you end up rolling things back.

Set up a backup before you hand it over, not after

Data loss is the support call you cannot fix over the phone. ZDNET’s roundup of backup tools makes the same point in its opening: it always happens when you least expect it. OneDrive is already on most Windows 11 installs and it’s fine for documents and photos if they’re signed in. If they have photos or work files that would hurt to lose, get a real backup running, either OneDrive with enough storage or a dedicated tool that copies to an external drive. Set it up, confirm the first backup finishes, then explain in one sentence where their files live.

Leave a short written note

Not a manual. Three or four lines taped inside a drawer or saved as a text file on the desktop: how to sign in, where their files are, and which number to call. People don’t remember screen tours, but they will find a note.

The machine itself is the easy part. What you’re really configuring is a support relationship, and every decision above exists to make that relationship less frequent. Uninstall the noise, tighten the permissions, set the update window, confirm the backup, and then leave it alone. The next call you get should be about something they actually did, not something Windows did to them.

Two machines this month. Both with the same complaint: the printer stopped working after a Tuesday morning update, and neither user had any idea what changed. That is the pattern with driver updates in Windows. They arrive quietly, they install at the worst possible moment, and when the device misbehaves you are left staring at hardware that worked fine yesterday. The fix is usually simpler than people fear.

Here is what actually happens when you roll a driver back, how to do it without making things worse, and where Windows hides the tools so you can get your machine running again.

Why a driver update breaks things in the first place

Windows Update treats drivers like any other patch. It checks a catalogue, matches your hardware IDs, and installs whatever version Microsoft’s testing pipeline signed off on. That process is convenient. It is also blunt.

The driver Redmond ships may fall behind the one your manufacturer released. Or it may be newer, built against a different revision of your motherboard, and tuned for a chip revision you do not have. Audio devices, network cards, and chipset components are the usual suspects because they sit close to the hardware and depend on specific firmware behaviour.

Microsoft itself acknowledges the risk at the operating system level. The company confirmed this year that September 2026 security updates for Windows 11 can break Always On VPN connections, which is not a driver problem in origin but shows how regularly a routine monthly rollout collides with working configurations. Drivers are the same story wrapped in smaller files.

There is also a quieter trap. Windows installs some drivers as “optional updates,” which you approve manually under Settings > Windows Update > Advanced options > Optional updates. People click through those without reading. Then the machine changes underneath them and the blame lands on the printer.

Roll back the driver first, before you touch anything else

This is the cleanest move and it takes about ninety seconds. Open Device Manager (click the Start button with your right mouse button and choose it from the list). Find the device that is misbehaving, right-click it, and choose Properties. Go to the Driver tab.

If you see a Roll Back Driver button that isn’t greyed out, that’s the one to use. Windows keeps the previous package cached precisely for moments like this. Press it, confirm, reboot, and test.

A few things worth knowing before you click:

• The button is only available if Windows recorded a prior driver for that device. Fresh installs and recently rebuilt machines often have nothing to go back to.
• A successful rollback does not stop Windows Update from reinstalling the newer package later. You will need to block that separately.
• If the rollback makes the device disappear entirely, that is a sign the older package is incompatible with the current OS build, not a reason to panic. Move to the next section.

When there is no rollback option

You have two realistic routes. The first is the manufacturer’s older driver installer. Go to the support page for the precise model you have, not the general download hub, and pull the previous version deliberately. Laptops are the common case here, and vendor pages usually keep two or three revisions. Install, reboot, and check Device Manager to confirm the version changed.

The second route is Windows’ own driver store. It keeps copies of every package it has installed, even after you update. Open Command Prompt as administrator and type:

pnputil /enum-drivers

You get a list of published names, original names, provider, and version. Find the entry for the problem device, note the published name (it looks like oem12.inf), then remove the newer package with pnputil /delete-driver oem12.inf /uninstall /force, and reinstall the previous INF. This is the method I use when a vendor installer refuses to downgrade over a newer signed package. It is not scary, but read the list carefully. Deleting the wrong INF can take out an unrelated device.

Stop the same update from coming back

Rolling back once solves today. Without a block, the next scheduled pass reinstalls the driver and you are back on the phone explaining the same fix.

For a single device, use Group Policy or the registry to set the driver update exclusion. The cleanest approach on a machine you control is Settings > System > About > Advanced system settings > Hardware tab > Device Installation Settings, where you can tell Windows not to fetch manufacturer apps and drivers automatically. That is broad, so treat it as a blunt instrument rather than a per-device solution.

For a more surgical block, Microsoft publishes the “ExcludeWUDriversInQualityUpdate” policy. Enabling it stops Windows Update from offering driver packages in quality updates while leaving security patches flowing. Setup takes a minute through the Local Group Policy Editor under Computer Configuration > Administrative Templates > Windows Components > Windows Update. It is the right setting for a machine that needs to stay stable, such as a control station or a laptop attached to a piece of lab equipment.

Have a recovery plan that does not rely on rollback

Rollback depends on Windows having kept what you need. Sometimes it has not. That is when a full image of the system drive saves the day, and it is why I keep backup software on every machine I service.

Windows’ built-in tools are a patchwork. Restore Points and File History are serviceable for documents, but the imaging side still leans on holdover utilities from the Windows 7 era, and the System Repair Disc and Recovery Drive have become unreliable enough that PCWorld’s roundup of backup software is blunt about it. A proper third-party imaging tool lets you capture the entire disk state before you install anything new and restore it in twenty minutes if the driver turns out to be a dead end. That is a stronger guarantee than any rollback button.

If you have not built that safety net yet, start with a full image right now, before the next Patch Tuesday, while the machine still works.

Keep the driver list short

Most Windows installs converge on a handful of drivers that matter: chipset, graphics, network, audio, and the storage controller. Everything else is a convenience package you rarely need to update manually. When you let Windows grab optional driver updates on every pass, you multiply the surfaces where something can go wrong.

One habit worth building: before installing any driver update on a machine you depend on, note the current version in Device Manager. It takes ten seconds. If the new package misbehaves, you have both the version number and a rollback target, and the fix conversation stays short.

Driver updates are not the enemy. Uncontrolled ones are. Roll back first, restore only when rollback fails, and block the package that already bit you.