Hello!This time, I would like to introduce three commands to repair Windows system.
Windows is used normally and the system is rarely broken.Unfortunately, there are two main cases, one is "Hard disk is corrupted and system files are corruptedThis is the case.the other one is"OS and software updates fail and system files get corruptedIs the case.
Both are very annoying things that can happen if you don't use them incorrectly, but you can't just leave them alone.Especially because I left the error aloneVulnerability is left unattended and develops into a security accidentYou should be most afraid to do it.
It is often discovered when the OS update patch cannot be applied, so if you try to repair it with these 3 commands for the time being, it will work better than you think!
* Unfortunately, not all events can be resolved by this method.I would like to provide it as a means.
Let's introduce it now!
Try using sfc / scannow
First, I will introduce the sfc command.
sfc isSystem file checkerAs the name implies, it is a tool for checking system files with a Windows program called.
Of course, it not only checks, but also tries to repair any inconsistencies (corruptions or errors) in the file.
To execute it, use the following commandCommand prompt started by administrator or PowershellIt is OK if you execute it with.
sfc / scannow
This command comes in handy because you can easily repair system-protected files that normally do not change, or system files that you accidentally delete.
In some cases, this can cover damage caused by malicious software such as viruses (although it is necessary to run virus removal software separately ...).
In addition, the log file is saved in the following, and it may be good to refer to it in case of failure.
% windir% \ Logs \ CBS \ CBS.log * If it is in the initial state, it is saved in c: \ Windows \ Logs \ CBS \ CBS.log.
In addition to Scannow, sfc offers various options.
If you are interested, I have linked to the related page of Microsoft, so I think you should refer to this.
Try using DISM
Next is DISM.
DISM seems to be an abbreviation for Deployment Image Servicing and Management. It seems to mean a tool for "service and management of deployment images", but it's a bit difficult to say.
Originally it is a tool for customizing for distribution in companies etc., but for thisRepair compared to normal WindowsThere is a function to do it.
It's a tool that has a lot of features, but in terms of repair, here are two typical options that you often use.BothConsole running as administratorPlease note that is required.
DISM / Online / Cleanup-image / RestoreHealth
First of allRestore Health.
When you execute this command, it will check the currently running Windows for damage or errors, and if you find any problems, it will repair them.
It is a command with a role similar to sfc, but both seem to have different areas to repair,If you can't fix it with sfc, you can fix it hereYou may.
In addition, More powerful repair by specifying the Windows installation disk and imagecan.How to specifyInstall.wimWith the Source option.
DISM / Online / Cleanup-image / RestoreHealth / Source:wim: wim:E: \ Sources \ Install.wim:1 / LimitAccess ■E: \ Sources \ Install.wimIs the location of the Install.wim on the installation disk or mount image before the file path if you specify Wimwim: wim:Please note that is required.
The ISO image file can be obtained by using the Media Creation Tool.
For details, please see the reference article below.
I think it's worth doing if the update fails or if there are KBs that just can't be applied.Also, if the update cannot be applied, you should also try the following command.
DISM / Online / Cleanup-image / StartComponentCleanup
This isComponent storeThere is a function to store important Windows files, but this isWill be damagedAnd updatesCannot be appliedIt will be.Also, to store successive updates,Squeezing disk capacitySometimes.
By eliminating themApproaching normal operationI think you can.
The DISM log is stored below.Please refer to it as it will be a hint for improvement in case of failure.
% Windir% / Logs \ DISM \ dism.log * By default, it is stored in "C: \ Windows \ Logs \ DISM \ dism.log".
There is also a Microsoft article here, so I will link to it.Please refer to it!
Try using CHKDSK
The endCheck disk.
This command is for the hard diskRepair file system to improve operationIt will be something to do.
In addition, Detects defectsAnd avoid that partMove dataYou can let it.This allows you to use the hard disk normally temporarily.
Rather than repairing the OSFix hard disk malfunctionAlthough it is a command, it can be repaired by executing it when the above command does not fix it, and then executing the above two commands again, so it cannot be underestimated.
The command is as follows.me tooRun as administratorplease.
"/fThe option isFile system repair onlyto hold.I personally have the impression that this is often used at the restoration stage.
"/rThe option is also often used,Includes bad sector moving workBecause veryIt takes time.. In terms of OS repair, "/fLet's try from the option.
Because this command operates the hard disk,Cannot be executed while runningIt may be.In that case, you will be asked on the console if you want to schedule it to run at startup.If there is no problemSchedule and runLet's let it.
* CHKDSKHeavy burden on the hard diskTo apply.When running on an old hard diskNotesplease.
This time, I introduced three Windows repair commands.
There is no doubt that all of them are very useful commands, but they change important parts of the computer and should be handled with care.It is highly recommended to back up before execution if possible.
It also simply takes time.
Nowadays, with the spread of SSDs, it has become possible to process at a much higher speed, but it cannot be said that it can be repaired instantly.Please do it with plenty of time.
Windows 10 is updated by frequently issuing quality updates (QU: QualityUpdate) and feature updates (FU: FeatureUpdate), but it is rare that it can be applied to all machines smoothly at the actual corporate site.
It is not easy to investigate the cause, so I think that there is no man-hour reduction measure of repairing by "backup → command" as a primary measure. * If it is repaired without knowing the cause, it may not be possible to reproduce it, but ...
Not only this command but also overwriting update of OS is effective for repair, so I hope you can read this as well.
I hope it helps you.