This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
DISM can repair the component store. SFC compares protected system files. The builder drafts the commands. The wizard explains a result you type. Neither tool connects to a PC and neither tool disables antivirus.
Run them, later, on a host you administer, from an account that is allowed to repair that host. Do not download a repair program from a search ad. Do not disable Defender or another control because a scan was slow.
One host. If the same command fails twice, stop and record the line. A second tool from the internet is not the next step.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Confirm the hostname.
- Draft the commands.
- Do not run them during the reading.
- Do not disable a security control.
- Record the result line later.
- Stop after one host.
Mistakes that outlive the command
Repairing Windows with DISM and SFC goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- A repair tool downloaded from an ad.
- Defender disabled.
- A host you do not administer.
- The commands run during the reading.
- A second random tool added after one failure.
Decisions to write down
One decision for Repairing Windows with DISM and SFC: The host is yours. The commands are the drafted ones. No security control was disabled. No third-party repair tool was added. And nothing was run yet.
Checks before you call it done
Confirm this before you call the change done: The hostname is written. The draft is the known repair commands. No control was disabled. Nothing was run during the reading. And a failure will be recorded rather than hidden. If one of those fails, stop.
# Host you administer.
# Do not disable Defender to hurry a scan.
# Do not download a repair tool from an ad.Before you leave the host
Repairing Windows with DISM and SFC ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.