Updates for stale version information

Author: v-lianna

support/windows-client/performance/application-error-explorer-shut-down.md

@@ -14,7 +14,7 @@ ms.custom:
 
 ## Symptoms
 
-You receive the following error message when Windows 8.1 or Windows Server 2012 R2 is shutting down:
+You receive the following error message when Windows is shutting down:
 
 > explorer.exe - Application Error  
 The instruction at \<memory address\> referenced memory at \<memory address\>. The memory could not be "\<read or write\>".  
@@ -23,12 +23,12 @@ The instruction at \<memory address\> referenced memory at \<memory address\>. T
 > [!NOTE]
 > The shutdown process continues after the error message is displayed. The error doesn't harm the computer, and it can be safely ignored.
 
-This issue occurs when you right-click the Start tip or press the Windows key+X keyboard shortcut, and then you use the **Shut down or sign out** option to shut down or restart Windows.
-
-## Workaround
-
-To work around this issue, use the Settings charm to shut down or restart Windows.
+This issue occurs when you right-click the Start tip or press the Windows key+<kbd>X</kbd> keyboard shortcut, and then you use the **Shut down or sign out** option to shut down or restart Windows.
 
 ## Cause
 
 This error occurs because the **Explorer.exe** process accesses memory that has already been freed during the shutdown process.
+
+## Workaround
+
+To work around this issue, use the Settings charm to shut down or restart Windows.

support/windows-client/setup-upgrade-and-drivers/prevent-users-connect-usb.md

@@ -14,7 +14,7 @@ ms.custom:
 
 ## Problem description
 
-Assume that you want to prevent users from connecting to a USB storage device that is connected to a computer that is running Windows XP, Windows Server 2003, or Windows 2000. This article discusses two methods that you can use to do this.
+Assume that you want to prevent users from connecting to a USB storage device that is connected to a computer that is running Windows. This article discusses two methods that you can use to do this.
 
 ## Resolution
 

support/windows-client/windows-security/unified-extensible-firmware-interface-not-boot.md

@@ -32,4 +32,4 @@ To reduce the effect of this issue, use one of the following options:
 
 ## More information
 
-By policy, Windows 8 and Windows 8.1 require UEFI firmware to boot the operating system. UEFI provides basic services such as access to the boot device in the preboot environment. Windows Server and earlier versions of Windows client don't require UEFI mode and can boot either from traditional BIOS or from UEFI if this is supported by firmware. To enable booting these operating systems on a computer that uses UEFI, Compatibility Support Module (CSM) in UEFI provides compatibility support for traditional BIOS. Windows 7 and earlier versions of Windows require INT 10H support for boot graphics. This is provided by CSM in UEFI mode. The CSM can also be used to fully support traditional BIOS mode on a system that has UEFI firmware. These modes are known as Class 2 UEFI mode and Class 2 BIOS mode.
+By policy, Windows requires UEFI firmware to boot the operating system. UEFI provides basic services such as access to the boot device in the preboot environment. Windows Server and earlier versions of Windows client don't require UEFI mode and can boot either from traditional BIOS or from UEFI if this is supported by firmware. To enable booting these operating systems on a computer that uses UEFI, Compatibility Support Module (CSM) in UEFI provides compatibility support for traditional BIOS. Earlier versions of Windows require INT 10H support for boot graphics. This is provided by CSM in UEFI mode. The CSM can also be used to fully support traditional BIOS mode on a system that has UEFI firmware. These modes are known as Class 2 UEFI mode and Class 2 BIOS mode.

support/windows-server/networking/modify-tcp-ip-maximum-retransmission-time-out.md

@@ -26,7 +26,7 @@ By default, after the retransmission timer hits 240 seconds, it uses that value
 
 The `TcpMaxDataRetransmissions` registry value controls the number of times that TCP retransmits an individual data segment before it aborts the connection. This value isn't configured by default, but it can be entered to change the default number of retries.
 
-Change the following subkey in Windows 7, Windows 2008 R2, Windows 2008, Windows 2000, Windows Vista, Windows 2003, and Windows XP:
+Change the following subkey in Windows:
 
 `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters`
 
@@ -39,7 +39,7 @@ Description: This parameter controls the number of times TCP retransmits an indi
 
 Windows provides a mechanism to control the initial retransmit time, and the retransmit time is then dynamically self-tuned. To change the initial retransmit time, modify the following registry values.
 
-Change the following subkey in Windows 2003, Windows XP, and Windows 2000:
+Change the following subkey in Windows:
 
 `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ID for Adapter`
 
@@ -53,7 +53,7 @@ Description: This parameter controls the initial retransmission time-out that is
 > [!NOTE]
 > You can increase the value only for the initial time-out. Decreasing the value isn't supported.
 
-Change the following key in Windows NT 4.0:
+Change the following key in Windows:
 
 `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters`
 
@@ -66,7 +66,7 @@ Description: This parameter controls the initial retransmission time-out used by
 
 For example, the value data of "5000 decimal" sets the initial retransmit time to five seconds.
 
-The Initial RTO in Windows Server 2008 R2 and Windows 7 can be controlled by using the `netsh` command by initialRTO.
+The Initial RTO in Windows can be controlled by using the `netsh` command by initialRTO.
 
 For prerequisites and more information, see [You can't customize some TCP configurations by using the netsh command in Windows Server 2008 R2](https://support.microsoft.com/topic/you-cannot-customize-some-tcp-configurations-by-using-the-netsh-command-in-windows-server-2008-r2-c1feebea-82a8-cb05-83c7-46ffb5fd9cec).
 

support/windows-server/networking/reset-tcp-ip-net-shell.md

@@ -18,10 +18,6 @@ You can try to reset TCP/IP if you have Internet connection issues. This article
 
 To reset TCP/IP automatically, select the **Download** button. In the **File Download** dialog box, select **Run** or **Open**, and then follow the steps in the easy fix wizard.
 
-Windows 8.1, Windows 8, Windows RT, Windows 7, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2
-
-Windows Vista, Windows XP, Windows Server 2008, or Windows Server 2003
-
 > [!NOTE]
 >
 > - This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
@@ -31,48 +27,17 @@ Windows Vista, Windows XP, Windows Server 2008, or Windows Server 2003
 
 To manually reset TCP/IP, follow these steps:
 
-### Windows 8 and Windows 8.1
-
-1. On the **Start** screen, type **CMD**. In the search results, right-click **Command Prompt**, and then select **Run as administrator**.
+1. On the **Start** screen, type **cmd**. In the search results, right-click **Command Prompt**, and then select **Run as administrator**.
 2. At the command prompt, enter the following command, and then press <kbd>Enter</kbd>:
 
     ```console
     netsh int ip reset c:\resetlog.txt
     ```
 
-    > [!NOTE]
-    > If you don't want to specify a directory path for the log file, run the following command instead: `netsh int ip reset`.
-
-3. Restart the computer.
-
-### Windows 7 and Windows Vista
-
-1. To open a command prompt, select **Start** and then type **cmd** in the **Search programs and files** box.
-2. Under **Programs**, right-click the **CMD.exe** icon, and then select **Run as administrator**.
-3. When the **User Account Control** box appears, select **Yes**.
-4. At the command prompt, enter the following command, and then press <kbd>Enter</kbd>:
-
-    ```console
-    netsh int ip reset c:\resetlog.txt
-    ```
-
-    > [!NOTE]
-    > If you don't want to specify a directory path for the log file, run the following command instead: `netsh int ip reset resetlog.txt`.
-
-5. Restart the computer.
-
-### Windows XP
-
-1. To open a command prompt, select **Start** > **Run**. In the **Open** box, enter the following command, and then press <kbd>Enter</kbd>:
-
-    ```console
-    netsh int ip reset c:\resetlog.txt
-    ```
-
     > [!NOTE]
     > If you don't want to specify a directory path for the log file, run the following command instead: `netsh int ip reset resetlog.txt`.
 
-2. Restart the computer.
+3. Restart the computer.
 
 When you run the reset command, it overwrites the following registry keys, both of which are used by TCP/IP:
 
@@ -203,10 +168,10 @@ deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
 deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
-<completed> Note In Windows Server 2003 Service Pack 1, you can use the netsh winsock reset command to repair Winsock.
+<completed>
 ```
 
 For more information, see:
 
 - [Chapter 16 – Troubleshooting TCP/IP](/previous-versions/tn-archive/bb727023(v=technet.10)?redirectedfrom=MSDN)
-- [TCP/IP and NBT configuration parameters for Windows XP](/troubleshoot/windows-client/networking/tcpip-and-nbt-configuration-parameters)
+- [TCP/IP and NBT configuration parameters for Windows](/troubleshoot/windows-client/networking/tcpip-and-nbt-configuration-parameters)

support/windows-server/networking/windows-activation-validation-fails.md

@@ -38,16 +38,9 @@ If you experience other errors than those mentioned above when you try to activa
 
 Use the Windows Activation Wizard to activate Windows through the automated telephone system. To do this, follow these steps for your version of the operating system.  
 
-Windows 8 and later versions:
-
 1. Swipe in from the right edge of the screen, and then tap **Search**. Or, if you're using a mouse, point to the lower-right corner of the screen, and then select **Search**.
 2. Type **SLUI 04**, and then tap or select the displayed icon to open the wizard.
 
-Windows Vista and Windows 7:
-
-1. Select **Start**, and then select **Run**.
-2. Type **SLUI 04**, and then select **OK** to open the wizard.
-
 ### Method 2: Configure the proxy server to disable Basic authentication
 
 Configure the proxy server to disable Basic authentication. For information about how to use this method, see the documentation that is included with the proxy software.
@@ -78,8 +71,9 @@ For information about how to use this method, see the documentation that is incl
 
 ## More information
 
-For more information about Windows Vista Volume Activation 2.0, see [Volume activation for Windows](/windows/deployment/volume-activation/volume-activation-windows).
+For more information, see:
 
-For more information how to troubleshoot Volume Activation error codes, see [Troubleshoot Windows activation error codes](/troubleshoot/windows-server/licensing-and-activation/troubleshoot-activation-error-codes).
+- [Volume activation for Windows](/windows/deployment/volume-activation/volume-activation-windows).
+- [Troubleshoot Windows activation error codes](/troubleshoot/windows-server/licensing-and-activation/troubleshoot-activation-error-codes).
 
 If these articles don't help you resolve the problem, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, go to [Microsoft Support](https://support.microsoft.com). Type the text of the error message that you receive, or type a description of the problem.