Differences

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

--- software:microsoft:windows:windows7 [2019/11/02 22:52] – superwizard
+++ software:microsoft:windows:windows7 [2021/11/24 16:08] – superwizard
@@ Line 1: / Line 1: @@
-====== DSIM - The restorehealth option is not recognized in this context ======
+====== Windows 7 TLS 1.2 and TLS 1.1 ======
-From: http://www.geekstogo.com/forum/topic/370758-error-87-the-restorehealth-option-is-not-recognized-in-this-context/
+<WRAP center round box >
+-11-23
-<copy>
-Hi Ansal,
-If you have Windows 7 the DISM command doesn't have the repair functionality that's why you get the error, only Windows 8 and above supports that.
+Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows
+From <https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392>
+</WRAP>
+====== Restore Registry from RegBackup ======
+From: https://pureinfotech.com/restore-registry-backup-windows-10/
+<WRAP center round box >
+Type the following command to move inside the RegBack, which contains a backup of the Registry, and press Enter:
+    cd c:\windows\system32config\RegBack
+</WRAP>
+====== DSIM - The restorehealth option is not recognized in this context ======
+From: http://www.geekstogo.com/forum/topic/370758-error-87-the-restorehealth-option-is-not-recognized-in-this-context/
+<code>
+Hi Ansal,
+If you have Windows 7 the DISM command doesn't have the repair functionality
+that's why you get the error, only Windows 8 and above supports that.
 You need to download the System Update Readiness Tool (SUR)
@@ Line 16: / Line 43: @@
 http://support.microsoft.com/kb/947821
 Save it to some place, its a big download and eventually you
@@ Line 23: / Line 48: @@
 Run the tool. Its like an Update but it can take a long time to do
 the work. You will get an Installation Complete screen when it's done running.
 After running SUR restart the computer and run SFC /scannow again to see
 if it continues to report errors or not.
-</copy>
+</code>