Friendly button, serious machinery. Here is exactly which Microsoft repair tool each 1-click fix launches, what the switches mean, and how to read the result text like a technician.
It is reasonable to be suspicious of any button that promises to fix a computer in one click. So let us open the bonnet. In a GUI WinPE like the one in this video, the buttons are launchers - each one starts a standard, documented Windows repair tool with the correct options, aimed at the correct drive. Once you know what each button runs, the whole environment stops being magic and becomes what it really is: a well-organised toolbox.
Every 1-click fix button in a GUI WinPE does three honest things: it detects which drive holds Windows, it launches a standard Windows repair tool with the correct switches, and it shows you the output in a friendly window. Nothing inside the button is a private invention. The system-file button runs SFC. The deep-repair button runs DISM. The boot button runs the boot-file rebuild tools (bcdboot / bootrec). The update button restarts services and renames cache folders.
Why does this matter to you? Because when a button reports a failure, the failure message comes from the underlying Microsoft tool - and that message is searchable, documented and fixable. A button that fails with a DISM error code is not a dead end; it is DISM asking for something, usually a clean source of replacement files.
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. SFC compares every protected Windows file against the known-good copies in the component store and replaces the damaged ones. The two "off" switches simply tell it which offline Windows to repair.dism /image:C:\ /cleanup-image /restorehealth. This repairs the store itself - the warehouse SFC takes its spare parts from. If the warehouse is damaged, SFC keeps failing until DISM has been run.bcdboot C:\Windows /s Z: /f UEFI (letters vary). This writes fresh boot files for the installed Windows. It is the fix behind "no bootable device" and many boot-loop repairs.chkdsk C: /f scans the file system structure and fixes logical errors like cross-linked files and bad directory entries.netsh resets - covered in their own guides in this series.The result text after a run is the whole value of the tool - read it before clicking anything else:
Buttons cover the standard cases. Real benches meet non-standard ones: a Windows installed on a drive that WinPE letters as E:, a PC with two Windows installs where the button picks the wrong one, a DISM repair that needs a specific ISO as its source. In those moments the technician drops to the command prompt inside the same WinPE and types the same command the button would have run - with the letters and source corrected. The GUI is the fast path, not a locked door: anything the button can do, the command underneath can do with more control.
That is also the honest way to judge any repair toolkit, including the one in this video. If a tool hides what it runs and shows only "Fixed!" with no log and no output, you cannot verify the repair - or undo it. A trustworthy environment shows the command, the progress and the result text, exactly like this one does.
The complete repair session, live - which button was clicked, what ran underneath, and what the result said.
▶️ Watch Full VideoYou can - the command prompt is right there in the same WinPE, and the commands are listed in this guide. The buttons earn their keep in three places: they detect the correct Windows drive letter automatically, they never mistype a long switch, and they run multi-step sequences (like the update reset) in the right order. For one PC once a year, typing is fine. For a bench repairing PCs daily, the buttons remove the most common human errors.
No. If SFC finishes with "successfully repaired", the job is done - restart and test. DISM is the next step only when SFC reports it could not fix some files, because that message usually means the component store SFC takes parts from is itself damaged.
Almost never. The code comes from the underlying Microsoft tool and it names a specific obstacle - a wrong drive letter, a damaged component store, a missing repair source. Note the exact code and message, correct that one thing, and run the tool again. A named error is progress, not a verdict.