Merge pull request #9434 from v-lianna/CI_6767

AB#6767 Migrate Windows Server articles from SMC

Author: v-lianna

support/windows-client/networking/clear-register-addresses-not-remove-dns-records.md

@@ -0,0 +1,80 @@
+---
+title: Clearing the "Register This Connection's Addresses in DNS" Option Doesn't Remove DNS Records
+description: Provides a resolution to an issue in which a client doesn't remove its Domain Name System (DNS) records from the server after you clear the Register this connection's addresses in DNS checkbox on the client computer.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:network connectivity and file sharing\dns
+- pcy:WinComm Networking
+---
+# Clearing the "Register this connection's addresses in DNS" option doesn't remove DNS records for Windows clients using static IP addresses
+
+## Symptoms
+
+After you clear the **Register this connection's addresses in DNS** checkbox on a client computer, the client doesn't remove its Domain Name System (DNS) records from the server. For more information about the setting, see the following screenshot:
+
+:::image type="content" source="media/clear-register-addresses-not-remove-dns-records/register-connection-address-dns.png" alt-text="Screenshot of the Advanced TCP/IP Settings window with the Register this connection's addresses in DNS unchecked.":::
+
+## Resolution
+
+To resolve the issue, follow these steps according to the client computer's configuration.
+
+### For client computers that are configured to use a static IP address
+
+If the client computer is using a static IP address, follow these steps on the client computer to remove the record from the DNS server:
+
+1. Clear the **Register this connection's addresses in DNS** checkbox.
+2. Trigger the registration of the DNS record. To do this, use one of the following steps, which are listed in the order of preference:
+
+    - Restart the DNS Client service.
+    - Restart the Windows-based computer.
+    - Open a command prompt window as administrator, and then run the `ipconfig /registerdns` command.
+
+> [!NOTE]
+> If one or more adapters on a multi-homed client or server are configured by using a Dynamic Host Configuration Protocol (DHCP) address, see the last note in the "For client computers that are configured to use a dynamic IP address" section.
+
+### For client computers that are configured to use a dynamic IP address
+
+If you configure the client computer to obtain anIP address by using DHCP, the client or DHCP server will try to remove dynamically registered records after you clear the **Register this connection's addresses in DNS** checkbox.
+
+> [!NOTE]
+> After you clear the **Register this connection's addresses in DNS** checkbox on the DNS tab of the **Advanced TCP/IP Settings** property window of either TCP/IPv4 or TCP/IPv6, the following node is deleted from that computer's local registry:
+>
+> `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DNSRegisteredAdapters\{<36 character GUID corresponding to the network adapter that TCPIP was bound to>}`
+>
+> This applies to both clients that use static IP addresses and clients that use dynamic IP addresses.
+
+> [!NOTE]
+> If an adapter is configured to use dynamic IP addressing (DHCP) on the computer, don't run the `ipconfig /registerdns` command. Dynamic IP addressing uses a DHCP server to register "PTR" records and optionally Host "A" and "AAAA" records on behalf of DHCP clients. DHCP server configuration determines how "A" and "AAAA" registrations are added. After you run the `ipconfig /registerdns` command, the DNS records are registered by using the local machine's security descriptor. This prevents the DHCP server from updating those records until the record is manually removed. Restated, if the DHCP server doesn't have the permission to update the DNS record, the DHCP registration silently fails.
+
+For DHCP clients, we recommend that you follow these steps:
+
+1. Restart the "DNS Client" service. To do this, run the following commands:
+
+    ```console
+    net stop DNSCACHE
+    net start DNSCACHE
+    ```
+
+2. Run the following commands to update DNS registrations for DHCP clients:
+
+    ```console
+    ipconfig /release
+    ipconfig /renew
+    ```
+
+For more information, see:
+
+- [DNS Processes and Interactions](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd197552(v=ws.10)).
+- [General information about IPv4 and IPv6 advanced DNS tab](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754143(v=ws.11)).
+
+## More Information
+
+To determine whether a network adapter is using static an IP address or a dynamic IP address, follow these steps:
+
+1. Open a command prompt window.
+2. Run the `ipconfig /all` command.
+3. In the returned result, if the **DHCP Enabled** field under the network adapter is displayed as **Yes**, the network adapter is using a dynamic IP address. If it's displayed as **No**, the network adapter is using a static IP address.

support/windows-client/networking/media/clear-register-addresses-not-remove-dns-records/register-connection-address-dns.png

@@ -0,0 +1,34 @@
+---
+title: Application Error in Explorer.exe When You Shut Down or Restart Windows
+description: Provides a workaround to an application error in Explorer.exe when you shut down or restart Windows.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:system performance\shutdown performance (slow,unresponsive)
+- pcy:WinComm Performance
+---
+# Application error in Explorer.exe when you shut down or restart Windows
+
+## Symptoms
+
+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\>".  
+> Click on OK to terminate the program.
+
+> [!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+<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/performance/application-error-explorer-shut-down.md

@@ -0,0 +1,49 @@
+---
+title: Can't Scan From a Scanning Device Connected Through USB
+description: Provides a workaround to an issue in which you can't scan from a scanning device connected through USB to a USB-zero-client-connected station.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:system performance\system reliability (crash,errors,bug check or blue screen,unexpected reboot)
+- pcy:WinComm Performance
+---
+# Can't scan from a scanning device connected through USB to a USB-zero-client-connected station
+
+## Symptoms
+
+Consider the following scenario:
+
+- You have a server that is running Windows Multipoint Server 2011.
+- A scanning device is connected through USB to a USB-zero-client-connected station.
+- You select **Scan from device or camera** from a scan application such as Microsoft Paint.
+
+In this scenario, you receive an error message that resembles the following:
+
+> Unable to retrieve picture from device. Verify the device is properly connected and try again.
+
+Additionally, Windows Multipoint Server might restart unexpectedly from a Stop 0x3B error if the scanning device is connected directly to a USB port on the server. In this case, an event similar to the following is logged in Event Viewer under **Windows Logs** > **System**:
+
+```output
+Event ID: 1001
+Level: Error
+Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8800247e447, 0xfffff88004385cc0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030614-19375-01..
+```
+
+## Workaround
+
+[!INCLUDE [Registry important alert](../../includes/registry-important-alert.md)]
+
+To have us fix this problem for you, go to the "Fix it for me" section. If you prefer to fix this problem yourself, go to the "Let me fix it myself" section.
+
+To work around this problem, use Registry Editor to remove `WmsImageFilter` from the `UpperFilters` registry key. To do this, follow these steps:
+
+1. Open Registry Editor.
+2. Locate and select the following registry subkey
+
+    `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}`
+3. In the right pane, right-click the multi-string value named `UpperFilters`, and then select **Modify…**.
+4. Locate `WmsImageFilter` in the box under **Value Data**, and then remove it from the list.
+5. Select **OK** to save the changes, and then close Registry Editor.

support/windows-client/performance/cannot-scan-device-connected-usb.md

@@ -0,0 +1,79 @@
+---
+title: Prevent Users From Connecting to a USB Storage Device
+description: Provides a resolution to prevent users from connecting to a USB storage device.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:windows device and driver management\peripherals driver installation or update
+- pcy:WinComm Devices Deploy
+---
+# How can I prevent users from connecting to a USB storage device?
+
+## 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. This article discusses two methods that you can use to do this.
+
+## Resolution
+
+To prevent users from connecting to USB storage devices, use one or more of the following procedures, as appropriate for your situation.
+
+### If a USB storage device isn't already installed on the computer
+
+If a USB storage device isn't already installed on the computer, assign the user or the group and the local SYSTEM account **Deny** permissions to the following files:
+
+- **%SystemRoot%\Inf\Usbstor.pnf**
+- **%SystemRoot%\Inf\Usbstor.inf**
+
+When you do this, users can't install a USB storage device on the computer. To assign a user or group **Deny** permissions to the **Usbstor.pnf** and **Usbstor.inf** files, follow these steps:
+
+1. Start Windows Explorer, and then locate the **%SystemRoot%\Inf** folder.
+2. Right-click the **Usbstor.pnf** file, and then select **Properties**.
+3. Select the **Security** tab.
+4. In the **Group or user names** list, add the user or group that you want to set **Deny** permissions for.
+5. In the **Permissions for UserName or GroupNamel** list, select the **Deny** checkbox next to **Full Control**.
+
+    > [!NOTE]
+    > Also add the SYSTEM account to the **Deny** list.
+
+6. In the **Group or user names** list, select the SYSTEM account.
+7. In the **Permissions for UserName or GroupNamel** list, select the **Deny** checkbox next to **Full Control**, and then select **OK**.
+8. Right-click the **Usbstor.inf** file, and then select **Properties**.
+9. Select the **Security** tab.
+10. In the **Group or user names** list, add the user or group that you want to set **Deny** permissions for.
+11. In the **Permissions for UserName or GroupNamel** list, select the **Deny** checkbox next to **Full Control**.
+12. In the **Group or user names** list, select the SYSTEM account.
+13. In the **Permissions for UserName or GroupNamel** list, select the **Deny** checkbox next to **Full Control**, and then select **OK**.
+
+### If a USB storage device is already installed on the computer
+
+If a USB storage device is already installed on the computer, you can change the registry to make sure that the device doesn't work when the user connects to the computer.
+
+[!INCLUDE [Registry important alert](../../includes/registry-important-alert.md)]
+
+If a USB storage device is already installed on the computer, set the `Start` value in the following registry key to `4`:
+
+`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor`
+
+When you do this, the USB storage device doesn't work when the user connects the device to the computer. To set the `Start` value, follow these steps:
+
+1. Select **Start**, and then select **Run**.
+2. In the **Open** box, type **regedit**, and then select **OK**.
+3. Locate and then select the following registry key:
+
+    `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor`
+4. In the details pane, double-click `Start`.
+5. In the **Value data** box, type **4**, select **Hexadecimal** (if it isn't already selected), and then select **OK**.
+6. Exit Registry Editor.
+
+Did this fix the problem?
+
+Check whether the problem is fixed. If the problem is fixed, you're finished with this article. If the problem isn't fixed, you can [contact support](https://support.microsoft.com/contactus).
+
+## More information
+
+Contact the vendor of your USB device to ask about a newer driver.
+
+Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft doesn't guarantee the accuracy of this third-party contact information.

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

@@ -0,0 +1,67 @@
+---
+title: Operation to Change a Personal Folder Location Fails
+description: Provides a workaround to an issue in which you fail the operation to change the location of a personal folder.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:windows desktop and shell experience\desktop (shell,explorer.exe init,themes,colors,icons,recycle bin)
+- pcy:WinComm User Experience
+---
+# Operation to change a personal folder location fails in Windows
+
+## Symptoms
+
+Assume that you changed the location of a personal folder in Windows, such as **Documents** or **Downloads**, and mapped the folder to another personal folder. When you try to change the location of the folder again, the operation fails.
+
+For example:
+
+If the personal folder was mapped to a personal folder in the OneDrive folder on the computer, the following error message is received:
+
+> Can't move the folder because there is a folder in the same location that can't be redirected. Access is denied.
+
+If the personal folder was mapped to a local personal folder, for example, **Documents** was mapped to **Videos**, no error message is displayed. However, after the operation, the two folders' locations aren't separated.
+
+For more information about how to change the location of a personal folder and map it to another folder, see the [More Information](#more-information) section.
+
+## Workaround
+
+> [!IMPORTANT]
+> Essential information required for user success: Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, [back up the registry for restoration](https://support.microsoft.com/en-us/topic/how-to-back-up-and-restore-the-registry-in-windows-855140ad-e318-2a13-2829-d428a2ab0692) in case problems occur.
+
+To work around this issue, follow these steps:
+
+1. Right-click the Windows logo at the lower-left corner of the screen, and then select **Run**.
+2. Type **regedit.exe** and press <kbd>Enter</kbd>. If **User Account Control** window pops up, select **Yes**.
+3. In Registry Editor, browse to the following path:
+
+    `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders`
+
+4. Refer to the following table to find the registry key for the folder that encounters this issue, and change it to the default value.
+
+    |Folder  |Registry key  |Default value  |
+    |---------|---------|---------|
+    |**Downloads**     |`{374DE290-123F-4565-9164-39C4925E467B}`         |`%USERPROFILE%\Downloads`         |
+    |**Desktop**     |`Desktop`         |`%USERPROFILE%\Desktop`         |
+    |**Favorites**     |`Favorites`         |`%USERPROFILE%\Favorites`         |
+    |**Music**     |`My Music`         |`%USERPROFILE%\Music`         |
+    |**Pictures**     |`My Pictures`         |`%USERPROFILE%\Pictures`         |
+    |**Videos**     |`My Video`         |`%USERPROFILE%\Videos`         |
+    |**Documents**     |`Personal`         |`%USERPROFILE%\Documents`         |
+
+5. Restart the **Explorer.exe** process to make the changes take effect. To do this, you can use either of the following steps:
+
+    - Restart the process in Task Manager.
+    - Sign out, and then sign in.
+    - Restart the computer.
+
+## More Information
+
+To change the location of a personal folder, follow these steps:
+
+1. Right-click the personal folder, and then select **Properties**.
+2. Switch to the **Location** tab in the dialog box.
+3. Select **Move...**.
+4. Select the destination folder path and then select **OK**.

support/windows-client/shell-experience/change-personal-folder-location-fails.md

@@ -0,0 +1,34 @@
+---
+title: Scheduled Task Can't Run an Exe File on a Share Folder
+description: Provides a workaround to an issue in which scheduled task can't run an .exe file on a share folder in Windows.
+ms.date: 08/06/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, v-lianna
+ms.custom:
+- sap:system management components\task scheduler
+- pcy:WinComm User Experience
+---
+# Scheduled task can't run an .exe file on a share folder in Windows
+
+## Summary
+
+Consider the following scenario:
+
+- You set up a share folder in a domain environment.
+- You configure the share or New Technology File System (NTFS) level permission settings on the share folder.
+- You set up a task schedule on a client computer. The task runs an .exe file on the share folder.
+- Only the user account that is used to run the task has the access permission to the share folder.
+
+In this scenario, the task can't run. You receive an access denied or a not found error.
+
+## More Information
+
+To work around this issue, use one of the following steps:
+
+1. Assign the access permission for the share folder to the client computer.
+2. Configure the task to run `cmd /c \\share\name.exe` instead of `\\share\name.exe`.
+
+> [!NOTE]
+> `\\share\name.exe` is the placeholder of the path of the share folder.