There are exactly three honest sources for a Windows driver, and one of them is a good way to break your machine. Here is the order that works, and the safety net to set up before you start.
Every driver Windows offers you has been through Microsoft certification. That is not a marketing badge: it means the driver was tested against the operating system and cryptographically signed, and that Windows knows how to roll it back if it misbehaves.
The catch is that the visible list in Settings shows only what Microsoft pushes to everyone. There is a second, larger catalogue — Microsoft Update — which carries the optional driver updates for your specific hardware. Rain Cleaner queries that larger catalogue directly, which is why it often finds updates that Settings does not show.
Graphics cards are the honest exception. NVIDIA, AMD and Intel publish new graphics drivers on their own sites weeks before those drivers reach Microsoft certification, and for a new game that difference is real.
For everything else — chipset, network, audio, storage — the manufacturer version is rarely worth the risk. Go to nvidia.com, amd.com or intel.com directly, or to the support page for your laptop model. Some manufacturers publish their own updater through winget, which is Microsoft's package tool, and that is a reasonable way to install it.
A driver pack is an archive of thousands of drivers from an unnamed source, installed by matching hardware IDs. It is the single most common way a working machine gets a broken network card or a black screen after reboot.
The drivers inside are collected, repackaged and sometimes modified by people with no relationship to the hardware vendor. When one of them is wrong, nothing tells you which one — you get a machine that no longer boots properly and a folder of 4000 candidates. Rain Cleaner hosts no driver files of its own for exactly this reason.
Two things, in this order, and both take under a minute. First, a system restore point, so Windows can put the previous driver back even if the new one stops the machine from starting normally. Second, an export of the current DriverStore — that is the folder where Windows keeps every driver package it has ever installed — so you can reinstall the old version from a file if you need to.
Rain Cleaner refuses to start a driver installation unless at least one of those two succeeded, and it says which one failed and why. That is a deliberate design choice: a driver update that cannot be undone is not an update, it is a bet.
This is the loop that catches people: the driver you need is for the adapter you would download it with. Windows carries a set of generic drivers inside itself, and a scan for hardware changes will often bring an adapter back to life without any download at all.
If it does not, the way out is another working machine: export just the network drivers to a USB stick, carry it over, and install from the folder. Rain Cleaner has a screen that does exactly this — it prepares the USB set on the working machine and installs from the folder on the broken one.
Last updated: 2026-08-28
No, and this is where most driver tools are dishonest. A stable driver from 2019 on a chipset from 2019 is the correct driver. Update when something is actually wrong, when a game needs a newer graphics driver, or when a security fix says so.
Graphics, network, audio, storage, USB and Bluetooth. Those are the classes where fixes keep arriving. A printer driver from four years ago is usually just fine.
It is safe if the program takes the drivers from Microsoft's catalogue, makes a restore point first, and can put the old one back. It is not safe if it downloads from its own servers and cannot tell you where the file came from.
Category by category — what you get back, and what you quietly give up.
What “free” should mean, and how to check a cleaner before installing it.
The signs that come before the ransom note — and what to do in the first minute.
Free, no account, no subscription. Windows 10 and 11.