Posted 03 June 2017 - 02:17 PM
"Usually takes about 4 or 5 minutes" if nothing (or nothing significant) is wrong.
Either of these commands can take longer, significantly longer, to run if there's something substantial to fix. I put this out there only so the entire range of possibilities is mentioned. I have had an SFC, for instance, take a very long time when it had to repair a lot of issues. Also so the original poster doesn't panic if SFC were to run for anywhere between 30 minutes to several hours (which is unusual, but does happen on occasion).
DISM has been more like 15 to 20 minutes on average for me when there's nothing it really has to do or it has very little to do. SFC has done the heavy lifting.
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134
. . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it. The willing suspension of disbelief has its limits, or should.
~ Ruth Marcus, November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story