Before anything else, one line from Microsoft’s documentation for computer manufacturers, about the reset option called "Remove everything":
The Windows volume is never formatted, as the files needed to rebuild the OS are on it. Instead, user data files are deleted individually.
The operation almost everyone means when they say they formatted the computer does not format the drive. That is checkable, it is in Microsoft’s own words, and it is the least of the reasons a format so often changes nothing.
Every Polish guide on this subject explains how to do it. Almost none of them ask whether it will help. That is the question this article is about.
What "formatting" actually means
Five different operations share the word, and they do different things.
When someone says they formatted the computer, they could mean any of these, and the difference decides whether it was ever going to help:
Reset this PC, keeping your files. Windows is rebuilt and your documents stay. Your installed programs do not.
Reset this PC, removing everything. The one people mean by "format". It is also the one that does not do what its name suggests - see below.
Reinstall from Settings. Windows reinstalls the same version over itself and keeps your apps, files and settings. The least destructive repair Microsoft ships, and the only one that keeps installed programs.
A clean install from a USB stick. The only route where you decide what happens to the partitions.
The manufacturer’s factory recovery. Puts the machine back to how it shipped, including the old Windows build and every piece of preinstalled software.
Two things in Microsoft’s own documentation are worth knowing before you pick one. The first is that "Remove everything" does not format your C: drive:
The Windows volume is never formatted, as the files needed to rebuild the OS are on it. Instead, user data files are deleted individually.
The second is that a reset does not take you back to the factory version. Microsoft: it "restores Windows to an updated state rather than to the factory-preinstalled state". Your other drives are not touched at all unless you specifically choose to include them.
Will it fix what is wrong?
Only if the fault lives in the part that gets replaced.
A reinstall replaces one layer of the machine: Windows itself, the programs on it, and the configuration that built up around them. If the fault is in that layer, a reinstall is a good and fast answer.
It cannot reach the layers either side of it. Not the hardware, not your other drives, not the firmware on the motherboard. And there is a fourth one that catches more people than the rest combined: the settings you sign back into.
Windows Backup restores, on setup with the same Microsoft account, your accounts, your Wi-Fi networks and their passwords, your personalisation, your accessibility options and your language settings. Microsoft puts it plainly: "We’ll see that you have backups and ask you if you would like to restore one."
Which means a problem that lives in a setting is back within a minute of signing in. The machine was genuinely clean, for about as long as it took to accept the restore.
Why it did not work last time
Because it was almost certainly pointed at the wrong layer.
We went through Polish forum threads from people who had formatted and come back to report that nothing changed. Of the cases that reached a resolution, four out of five had been aimed somewhere a format could never have helped:
A dying drive. Reinstalling onto a disk with failing sectors does not repair the disk. The tell is timing: if a format fixed it and it broke again within weeks, stop suspecting software.
Malware that was never on C:. Twice. Only the Windows drive was wiped, the infection was sitting on the second one, and it came back.
A factory reset mistaken for a clean install. The machine was restored to its shipped state, which is not the same thing and did not remove the problem.
There is a fifth pattern that does not appear as a single thread so much as a habit: people who format every few months, watch the machine slow down again, and format again. Nothing in that loop is a diagnosis. If the cause is a background program you reinstall every time, or a fan that stopped spinning, the cycle can run for years.
What survives a wipe
More than you would expect, and some of it by design.
Everything on your other drives. This is documented rather than incidental: keeping your files explicitly bypasses "all files and folders on non-OS partitions". Anything on D: outlives every reset you are likely to run.
The EFI system partition. This is the sharpest example we found. Microsoft’s own guidance for a machine infected with the BlackLotus bootkit is that it should be "reformatted (both the OS partition and EFI partition)". Reset this PC formats neither. Microsoft’s remediation for that class of infection is a thing Microsoft’s own reset feature does not do.
Firmware. Implants like MoonBounce and CosmicStrand live in flash memory on the motherboard, outside any disk. Kaspersky’s researchers describe the result directly: such a rootkit keeps a computer infected "even if the operating system is reinstalled or the user replaces the machine’s hard drive entirely". This is rare. It is also the reason "I reinstalled Windows" is not the same sentence as "the machine is clean".
And one correction to something repeated everywhere, including by us until we checked: it is said that installing Windows never touches your UEFI. It does. BCDBoot writes a firmware entry into the board’s memory and places it first in the boot order. What a reinstall genuinely leaves alone is your BIOS setup - memory profiles, Resizable BAR, fan curves. Those live in the board, not on the disk, and Windows Setup has no way to write them.
Reset or clean install?
A reset keeps your drivers. That is the difference nobody mentions.
Microsoft is explicit that "the drivers that are installed on the PC at the time it’s reset are restored as part of Push-button Reset". A clean install from a USB stick starts from the drivers Microsoft ships and nothing else. If you have ever spent an evening after a reinstall hunting for a network driver, that is the difference you were feeling.
Two more things that are widely misdescribed. A local reinstall does not come from your recovery partition - modern Windows rebuilds itself from the component store inside the running installation, and the recovery partition holds repair tools rather than a copy of Windows. And before it starts, a reset checks those system files for corruption and repairs them through Windows Update if it can.
So: cloud download when you want a fresh copy from Microsoft, local when your connection is poor and the machine is otherwise healthy. And note that booting from recovery media removes both reset options - from a USB stick, the only thing on offer is a full reinstall.
What it actually costs you
Your programs and settings, always. Access to your accounts, sometimes.
"Keep my files" is a fair description of your documents and a poor one of everything else. It wipes the Windows folder, both Program Files folders, ProgramData and all three of your AppData folders. Your applications go, and so does the configuration inside them.
There is a documented detail people find genuinely annoying: preinstalled manufacturer software "will be restored to their factory condition, even if users have previously uninstalled them". The bloatware you removed on day one comes back.
The one that actually locks people out is two-factor. We found a thread from someone who reinstalled Windows and then could not get into their Google account, because the recovery phone number on it was years out of date. That mailbox was the recovery address for their other accounts, so the problem multiplied. They did not get it back.
Three more things are commonly listed as losses and we want to be accurate about them: passwords saved in a browser without sync, game saves that are not in cloud saves, and Office needing to be reactivated. We could not find first-hand accounts of these in the threads we read, so treat them as risks worth ten minutes of checking, not as things that reliably happen.
If you are selling or giving the machine away
Windows’ own "clean the drive" is not a secure erase, and Microsoft says so.
The option that says it removes files and cleans the drive carries this line in Microsoft’s documentation for manufacturers:
The data erasure functionality is targeted at consumers and does not meet government and industry data erasure standards.
The consumer-facing wording is hedged to match. It says the option makes it "harder" for other people to recover your files. Harder, not impossible, and that is Microsoft’s own choice of word.
For an SSD, overwriting is the wrong tool entirely. Micron’s engineers put it plainly: writing zeroes over the data is legitimate on a mechanical drive but "is not an effective method for an SSD", because the controller spreads writes across the memory and keeps spare capacity your computer cannot address. The reliable routes are the drive manufacturer’s own secure-erase tool, or full-disk encryption from day one so that discarding the key destroys the data.
If you want to read the standard on this, note that the version everyone cites, NIST SP 800-88 Revision 1, was withdrawn in September 2025 and replaced by a revision that covers flash storage and cryptographic erase properly.
If you are going to do it anyway
Four things beforehand, in this order.
Link your Microsoft account to the licence first. Windows ties the licence to your hardware. Linking an account is what lets you reactivate after a significant hardware change. Do it before the wipe: afterwards, on a changed motherboard, with no linked account and no retail key, there is no self-service path left. And ignore the advice that you must deactivate the licence before reinstalling - no Microsoft source supports it, and a reinstall on the same hardware reactivates itself.
Put the network driver on the USB stick. Windows does not ship a driver for every current Wi-Fi module or network chip, and when it lacks one the machine cannot get online to download it. That is the loop that turns an hour into an evening.
Check your two-factor recovery before, not after. The phone number on the account, and the backup codes. This is the step that the story above turns on.
Then drivers, in order. Dell documents the only part of the order that matters: "Only BIOS and chipset drivers should be installed first. After that, the order doesn’t matter."
You will need an empty USB stick of at least 8 GB, and everything on it will be erased. One more thing worth saying in 2026: Windows 10 stopped being supported in October 2025, so reinstalling it puts you on a version that no longer receives fixes.
How we approach it
The format is the easy part. What decides the result is what happens either side of it.
We should say the uncomfortable thing directly: a session with us starts with a format. Everything above says a format on its own frequently changes nothing. Both of those are true, and the gap between them is the whole point.
When a format does not help, it is usually not because it was done badly. It is because nothing happened afterwards. The machine came back to a clean Windows, restored the same settings from the same account, reinstalled the same background programs, and kept the same drive, the same thermal problem and the same driver. A clean Windows is a starting point, not a result.
So we look first and wipe second. If the cause is a failing drive, a fan that has stopped, or a machine throttling itself under load, we say so, and a format is not the answer to any of them.
And the honest limit, because this section is worth nothing without one: we can tell you a drive is failing. We cannot replace it over a remote connection. Hardware faults need hardware, and when that is what we find, what you get from us is the diagnosis and an explanation - not a repair.