Differences

This shows you the differences between two versions of the page.

--- solved_windows_10_settings_app_not_opening_working [2023/12/29 04:19] – wikiadmin
+++ solved_windows_10_settings_app_not_opening_working [2023/12/29 05:33] (current) – wikiadmin
@@ Line 7: / Line 7: @@
 To do this, follow these steps:
-Open an elevated command prompt. next to Windows start button, perform a  search for cmd.exe and press enter key.
+Open an elevated command prompt. To do this, go to the search box next to Windows start button, and perform a search for cmd.exe and press enter key.
-The top search result should be Command Prompt.
+The top search result should be "Command Prompt."
-Right click on the "Command Prompt" result and then Left click on "Run As Administrator" from the drop down list.
+Right click on the "Command Prompt" result and then Left click to select "Run As Administrator" from the drop down list.
 When asked for further run permissions, click YES. The black command prompt window should then open with administrative privileges. This is known as an elevated command prompt.
@@ Line 23: / Line 23: @@
 </code>
-It may take several minutes for the command operation to be completed.
+It may take about half and hour for the command operation to be completed.
-Now, after DISM has been run, in the same elevated black Command Prompt window, next run the system file checker (sfc.exe) to scan for and repair corrupted or missing system files, as follows.
+During this process you should see something like the following echo onscreen inside the command window:
+<code>
+Deployment Image Servicing and Management tool
+Version: 10.0.19041.3636
+Image Version: 10.0.19045.3803
+[===== 1% etc, 12.8% etc, up to 100% complete  ] - The progress indicator.
+[==========================100.0%==========================] The restore operation completed successfully.
+The operation completed successfully.
+C:\Windows\system32>
+</code>
+Now, after DISM has been run, and within the same elevated black Command Prompt window, next run the system file checker (sfc.exe) to scan for and repair corrupted or missing system files, as follows.
 ►CMD Command
@@ Line 33: / Line 50: @@
 </code>
-Check to see if this corrected the problem. If not, then move on to the next possible fix.
+While this scan is being performed you should see something like the following:
+<code>
+Beginning system scan.  This process will take some time.
+Beginning verification phase of system scan.
+Verification 6% complete.
+</code
+When the scan is completed, you should see something like the following message:
+<code>
+Verification 100% complete.
+Windows Resource Protection found corrupt files and successfully repaired them.
+For online repairs, details are included in the CBS log file located at
+windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
+repairs, details are included in the log file provided by the /OFFLOGFILE flag.
+C:\Windows\system32>
+</code>
+After the scan is completed, then RESTART Windows After Restarting Windows, try opening "Settings" or otherwise check to see if this corrected the problem. If it did, stop here.  If not, then move on to the next possible fix.
+This fixed the problem for me.
-You must first open an elevated Powershell blue window.
+**You must first open an elevated Powershell blue window.**
 Next to the Windows start button, search for Powershell.  Open the top level result with administrative privileges in the same manner that you opened an elevated command prompt with Administrative privileges.  See above.