Format before
recovering?

A "quick" format doesn't erase the data: it erases the table that tells the operating system where each file is and marks all that space as available for writing. As long as nothing is written over it, specialist tools can still locate the files by their content, although without the original table it's harder to recover the file names and folder structure. A "full" format, on the other hand, does overwrite the whole drive, which greatly reduces the chances. The real difference lies less in which type of format was chosen than in what has happened since: every installation, every photo saved, every update downloaded from that moment on takes up part of the space your files used to occupy. That's why "quick" doesn't mean harmless: it's only the first step in a process that becomes irreversible through normal use of the computer from then on, not through the format itself.

Yes, and the "keep my files" option the installer offers isn't as safe as it sounds: it needs free space to work with, it moves and reorganises data during the process, and if something goes wrong halfway through the result can be worse than a clean install. What determines the real damage is whether the system and your data share the same drive and the same partition. If your documents were on a different drive or partition from the one Windows lives on, reinstalling the system may not touch them. If everything is on the same drive, which is usual on a laptop that hasn't been set up otherwise, the new installation writes system files, drivers and updates exactly into the space your documents used to occupy. Before launching any "reset this PC", it's worth checking how many partitions there are and which one the files that matter were really on, rather than assuming they're safe because you ticked the right box.

That depends on the type of failure, not on how good the program is. In a logical failure — the drive spins normally and the computer detects it, but the file system is damaged or deleted — some free tools manage to locate and copy files, provided they're run from a bootable USB stick or from another computer, never installed on the drive you're trying to recover. In a mechanical failure — noises, won't start, keeps disconnecting — any program that keeps the drive reading for hours accelerates the wear on parts that are already failing, increasing the risk that it stops responding altogether before it finishes. The problem is that telling a logical failure from a mechanical one by eye, without opening the drive or analysing it with the right equipment, isn't always reliable: a drive with an early-stage mechanical fault sometimes still gets detected and appears to work. That's why it's worth confirming the type of failure before leaving any program scanning for hours.

No. A repeated click or tick is a mechanical symptom, almost always from the head that reads the drive's platters, and formatting is a purely logical operation: it doesn't touch or repair any physical part. All it achieves is forcing the drive to carry out more read and write operations while it's already failing, which increases the risk of the head scratching the surface of the platter and turning a recoverable mechanical fault into one that no longer is. Every attempt to boot, every "let's see if formatting fixes it", is another power cycle on a damaged part. The right response to a mechanical noise is to switch the computer off as soon as you notice the symptom, not to turn it back on "to see if it's still doing it", and to take it to be opened under controlled conditions if the platters need to be accessed. The time between the first noise and switching off is, in these cases, the factor that weighs most on the final outcome.

Yes, and it's the right way to work on a failing drive without risking the original, but it isn't the same as copying folders with the file explorer. A true clone is a sector-by-sector image, which also copies the space marked as free and any file remnants that may still be there, not just what the operating system sees as active files. The original is put away and not touched again, and all the recovery work, software tests included, is done on the copy. Consumer cloning tools tend to fail precisely on the drives that need it most: when they hit a damaged sector, many stop or skip it without warning, leaving an incomplete image. A setup with the right hardware can retry those sectors in other ways and get more out than a standard copy manages. That's why cloning at home with a free tool gives a false sense of security if the drive is already failing.

Sometimes, yes, and what matters most is what has happened in that hour, not the time itself. If you haven't installed anything, haven't saved new files and haven't let the system run automatic updates, much of the content may still be physically on the drive waiting to be found. There's an important difference depending on the type of drive: on a traditional mechanical hard drive, formatted data can stay intact for quite a while if nothing is written over it. On a solid-state drive, many systems automatically run an operation called TRIM that physically erases the blocks marked as free shortly after formatting, which reduces what's left far more quickly, sometimes within minutes. Switch the computer off now, don't turn it on yourself "to check whether anything's left", and bring it in as it is: every extra boot is one more chance for the system to write over it without you noticing.

Don't run it if your priority is recovering data. CHKDSK and Windows' "repair drive" tools are designed to get the disk working again as a system drive, not to preserve what's on it: they rewrite the file tables, relocate or mark as bad any sectors they can't read, and in the process they can overwrite exactly the remnants of the files you wanted back. It's a maintenance tool, not a recovery tool, and the two pursue opposite goals when the drive already holds important data. If Windows offers to repair it automatically at startup, decline until you know whether anything needs recovering from that drive. The only situation in which it makes sense to let a drive repair itself is when you've already established there was nothing valuable to lose, or when a complete, verified copy already exists elsewhere.

First, listen to the drive for a few seconds before pressing any key: if it clicks, ticks or spins up and stops in a loop, it's a mechanical problem and no repair screen will fix it; switch it off and don't persist. If the drive sounds normal and Windows simply won't load, a logical failure of the file system is more likely, which can often be diagnosed and in some cases recovered without writing anything to the drive, by examining it from another computer. The blue or black screen offering "repair", "reset" or "reinstall" doesn't distinguish between these two cases and doesn't know whether there's uncopied data behind it: it simply runs whichever option you pick. Before pressing any of those buttons, a short call describing the exact symptom — whether it makes noise or not, at what point the startup stops — is usually enough to know which path you won't be able to undo afterwards.