Update-Invoke-WPFSystemRepair.ps1#4043
Merged
ChrisTitusTech merged 5 commits intoChrisTitusTech:mainfrom Feb 17, 2026
Merged
Conversation
ChrisTitusTech
approved these changes
Feb 17, 2026
|
Is this version already public or not? I tested the link with the stable and dev branches, but nothing changes. Can we get screenshots of the new changes with these messages displayed? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type of Change
Description
This PR modifies the SFC and DISM execution method to use
cmd.exeviaStart-Processso the user can see the full live output in the same console window.Previously, output was not fully visible when executed directly through
Start-Process. Running the commands throughcmd.exe /censures complete real-time console output while still maintaining the required process invocation method.Removed chkdsk.
Removed the second SFC scan.
Running SFC after DISM already prompts for a restart if repairs require it.
A second SFC scan does not provide additional value in this workflow.
chkdsk is not necessary in this context, as SFC and DISM sufficiently handle system file integrity issues.
Issue related to PR