Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Author: Learn Build Service GitHub App

support/azure/virtual-machines/windows/toc.yml

@@ -93,9 +93,13 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error Code 0x800f0831
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error code 0x80244007
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80244007.md?context=/troubleshoot/azure/virtual-machines/windows/context/context   
     - name: Error code 0x80072f8f
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80072f8f.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
-  
+    - name: Error code 0x8000ffff
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x8000ffff.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+      
 - name: Uploading a VHD to Azure
   items:
   - name: Uploading a VHD to Azure
@@ -295,7 +299,7 @@ items:
     - name: Error Code 0x800f0831
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-installation-error-corruption.md
     - name: Error Code 0x8007045b
-      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md 
+      href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md
   - name: Overview
     href: /azure/virtual-machines/instance-metadata-service?context=/troubleshoot/azure/virtual-machines/windows/context/context
   - name: Certificate Issues

support/azure/virtual-machines/windows/windows-activation-troubleshoot-tools.md

@@ -27,7 +27,7 @@ Validates the activation status of your Windows VM and checks for common issues
   - Detects misconfigurations.
   - Provides actionable guidance.
 
-For more information, see [Windows activation validation](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/WindowsActivationValidation/README.md).
+For more information, see [Windows activation validation](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_Activation_Validation).
 
 ### 2. Azure Instance Metadata Service certificate check
 
@@ -44,7 +44,7 @@ Verifies the integrity and availability of certificates that are required for ac
 For more information, see: 
 
 - [Cause: Azure Instance Metadata Service connection issue](activation-watermark-appears.md#cause-1-azure-instance-metadata-service-connection-issue).
-- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck/README.md).
+- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_IMDSValidation).
 
 ## How to run these tools
 

support/azure/virtual-machines/windows/windows-vm-ghostednic-tool.md

@@ -28,8 +28,8 @@ When an Azure Virtual Machine running Windows Server or Windows Client with **Ac
 **Purpose**  
 There two scripts that can be used to detect if there are 'ghosted nics' inside of the VM. A VM that has one ore more could experience issues.This script detects ghosted (disconnected) network interface cards (NICs) and remove them from the registry.
 
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 
 
@@ -41,8 +41,8 @@ There two scripts that can be used to detect if there are 'ghosted nics' inside
 For more information, see: 
 
 - [Troubleshooting: Multiple Mellanox Ethernet Adapters After VM Deallocation (Ghost NICs)](./windows-vm-ghostednic-troubleshooting.md)
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 ## How to run the tools
 
@@ -63,7 +63,7 @@ Download the scripts from GitHub, and then run them manually. To access the scri
 - Navigate to your VM in the Azure portal: > **Operations** > **Run Command**.
 - Select the script from the list (see the following screenshot).
 
-**Only the [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning) is available in this method. The other script can be run via the Run Command prepackeged method.**
+**Only the [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection) is available in this method. The other script can be run via the Run Command prepackeged method.**
 
 :::image type="content" source="media/windows-vm-ghostednic-tool/windows-vm-ghostednicvalidationtool-portal-runcmd.png" alt-text="Azure portal view Run Command example." lightbox="media/windows-vm-ghostednic-tool/windows-vm-ghostednicvalidationtool-portal-runcmd.png":::   
 
@@ -76,14 +76,14 @@ For more information, see [Run scripts in your Windows VM by using action Run Co
 
 ## Recommended workflow
 
-1. Run **[Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)** to verify activation status and detect common issues.
-2. If ghost-nics are detected, run [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time) to remove them.
+1. Run **[Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)** to verify activation status and detect common issues.
+2. If ghost-nics are detected, run [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal) to remove them.
 
 ### **Additional resources**
 
 - [Troubleshooting: Multiple Mellanox Ethernet Adapters After VM Deallocation (Ghost NICs)](./windows-vm-ghostednic-troubleshooting.md)
-- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+- [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+- [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 [!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
 

support/azure/virtual-machines/windows/windows-vm-ghostednic-troubleshooting.md

@@ -75,7 +75,7 @@ This behavior is **by design** due to the architecture of Accelerated Networking
 
 ### **1. Detect the Scenario**
 Use **RunCommand** to check for ghosted NICs:  
-[Ghosted NIC Check Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
+[Ghosted NIC Check Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows_GhostedNIC_Detection)
 
 ### **2. Clean Up Ghosted NICs**
 
@@ -84,8 +84,8 @@ Use **RunCommand** to check for ghosted NICs:
 
 **Option B: Force Removal via RunCommand**
 - Use RunCommands to check then remove ghosted NICs:  
-  - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/GhostedNIC_Check_Time_warning)
-  - [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal_time)
+  - [Azure VM - Windows Ghosted NIC Check Warning Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Detection)
+  - [Azure VM - Windows Ghosted NIC Check Removal Script](https://github.com/Azure/azure-support-scripts/tree/master/RunCommand/Windows/Windows_GhostedNIC_Removal)
 
 
 ### **3. Plan for Design Behavior**

support/azure/virtual-machines/windows/windows-vm-imds-tool.md

@@ -37,7 +37,7 @@ Certificate not found: 'CN=Microsoft Azure XXXX, ...'
 For more information, see: 
 
 - [Cause: Azure Instance Metadata Service connection issue](activation-watermark-appears.md#cause-1-azure-instance-metadata-service-connection-issue).
-- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/IMDSCertCheck/README.md).
+- [Azure VM Attested Metadata Verification Script](https://github.com/Azure/azure-support-scripts/blob/master/RunCommand/Windows/Windows_IMDSValidation).
 
 ## How to run the tool
 

support/developer/visualstudio/installation/toc.yml

@@ -58,6 +58,8 @@
     href: ./version-visual-studio-requires-april-2014-update.md
   - name: Wait for setup to finish before trying again
     href: ./another-setup-already-running-wait-finish.md
+  - name: Workarounds for Visual Studio on unsupported operating systems
+    href: ./visual-studio-unsupported-operating-systems.md
   - name: Workarounds for Visual Studio 2022 on unsupported operating systems
     href: ./visual-studio-2022-unsupported-operating-systems.md
   - name: Windows Program Compatibility mode is on

support/developer/visualstudio/installation/visual-studio-unsupported-operating-systems.md

@@ -0,0 +1,76 @@
+---
+title: Workarounds for Visual Studio on Unsupported Operating Systems
+description: This article describes known issues and workarounds for Visual Studio if it's installed on unsupported operating systems.
+ms.date: 11/11/2025
+ms.reviewer: pchapman, jagbal, v-shaywood
+ms.custom: sap:Installation\Setup, maintenance, or uninstall
+---
+# Workarounds and operating system requirements for Visual Studio
+
+_Applies to:_   Visual Studio  
+
+## Summary
+
+Microsoft Visual Studio is supported on only 64-bit editions of [Windows 11](/lifecycle/products/?terms=windows%2011), [Windows 10](/lifecycle/products/?terms=windows%2010), and Windows Server 2019 and later versions that are still within their support lifecycle. We recommend that you don't run Visual Studio on earlier or unsupported versions of Windows and Windows Server. For more information, see [full system requirements](/visualstudio/releases/vs18/vs-system-requirements). To enable organizations to schedule their operating system upgrades, this article provides known issues and potential workarounds when you use Visual Studio on an unsupported operating system.
+
+> [!NOTE]
+> Microsoft can't provide support or fixes for issues that occur if you use Visual Studio on an unsupported operating system. For feedback on supported configurations, see [Developer Community](https://developercommunity.visualstudio.com/).
+
+## Arm-based operating systems
+
+Arm64 Visual Studio is supported on only Windows 11 on Arm. 64-bit Visual Studio isn't supported on ARM operating systems. Therefore, the performance of that setup might not meet your expectations.
+
+The following workloads and components aren't supported by Arm64 Visual Studio running on ARM64 operating systems:
+
+- Azure development (except for the Container development tools that are supported)
+- Data storage and processing (except for the SQL Server Data Tools that are supported)
+- Data science and analytical applications
+- Python development
+- Mobile development with C++
+- Office/SharePoint development
+- Microsoft Blend
+- XAML Designer (runs in an x86 process on ARM64)
+
+## Windows LTSC
+
+The Windows Long-term Servicing channel (LTSC) isn't intended for deployment on most devices in an organization. Use it only for special-purpose devices. Visual Studio isn't intended to run on [the Windows Long-term Servicing Channel (LTSC)](/windows/deployment/update/waas-overview#long-term-servicing-channel). However, building apps that run on Windows LTSC is supported.
+
+## Application Virtualization
+
+Visual Studio doesn't support Application Virtualization (App-V) solutions. For example, Microsoft App-V for Windows or third-party app virtualization technologies isn't supported by Visual Studio.
+
+## Azure Virtual Desktops
+
+Running Visual Studio in a virtual machine (VM) environment requires a full Windows operating system. Visual Studio doesn't support multiple simultaneous users using the software on the same computer, including shared virtual desktop infrastructure computers or a pooled Windows Virtual Desktop host pool.
+
+## Windows containers
+
+Running Visual Studio Community, Professional, Enterprise, or Team Explorer editions in Windows containers isn't supported. The Build Tools edition is supported.
+
+## 32-bit operating systems
+
+Visual Studio doesn't install on 32-bit operating systems.
+
+## Windows 7 and Windows Server 2008 R2
+
+Visual Studio doesn't install on Windows 7 and Windows Server 2008 R2.
+
+## Windows 8 and Windows Server 2012
+
+Visual Studio doesn't install on Windows 8 and Windows Server 2012.
+
+## Windows 8.1 and Windows Server 2012 R2
+
+Visual Studio doesn't install on Windows 8.1 and Windows Server 2012 R2.
+
+## Windows 10, versions 1507 and 1511
+
+Visual Studio doesn't install on Windows 10, versions 1507 or 1511.
+
+## Windows 10, versions 1607 through 1903
+
+.NET 4.8.1 doesn't install and isn't supported on Windows 10, versions 1607 through 1903.
+
+## Windows 10, versions 1909 through 2004
+
+.NET 4.8.1 doesn't install and isn't supported on Windows 10, versions 1909 through 2004.

support/power-platform/power-automate/desktop-flows/ui-automation/element-picker-cant-see-elements.md

@@ -0,0 +1,67 @@
+---
+title: Troubleshoot UI Element Visibility Issues in Power Automate for Desktop
+description: Troubleshoot Power Automate for desktop when it can't interact with specific UI elements. Explore solutions like OCR, image actions, and more.
+ms.date: 11/05/2025
+ms.custom: sap:Desktop flows\UI or browser automation
+ms.reviewer: iomimtso, nimoutzo, v-shaywood
+---
+
+# UI element picker or recorder can't view UI elements in desktop applications
+
+This article provides troubleshooting guidance for an issue where Power Automate for desktop can't view or interact with specific UI elements in a desktop application.
+
+## Symptoms
+
+When using Power Automate for desktop, the element picker tool can't detect or "see" certain UI elements within desktop applications. This issue prevents you from selecting elements for automation tasks.
+
+## Cause
+
+Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with the standard accessibility APIs that Power Automate for desktop relies on. This incompatibility can make certain elements invisible to the element picker.
+
+> [!IMPORTANT]
+> For coordinate-based solutions (Solutions [3](#solution-3-use-the-recorder-with-coordinates) and [4](#solution-4-use-move-mouse-and-send-mouse-click-actions)) to work reliably:
+>
+> - The screen configuration (resolution, DPI settings, scaling) must remain static at runtime and match the configuration used during development.
+> - Changes to the application's user interface structure might affect the effectiveness of these workarounds.
+> - Test your flows thoroughly when deploying to different machines or environments.
+
+## Solution 1: Use Move mouse to image action
+
+1. Add a **Move mouse to image** action to your flow.
+1. Capture an image of the UI element you want to interact with.
+1. Enable the **Send a click after moving mouse** option.
+1. Configure any additional settings as needed.
+
+This action moves the mouse to the first occurrence of the specified image and sends a left click.
+
+## Solution 2: Use Move mouse to text on screen (OCR) action
+
+1. Add a **Move mouse to text on screen (OCR)** action to your flow.
+1. Specify the text that appears on or near the UI element you want to interact with.
+1. Enable the **Send a click after moving mouse** option.
+1. Configure OCR settings and click options as needed.
+
+This action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
+
+## Solution 3: Use the recorder with coordinates
+
+1. Open Power Automate for desktop and create a new flow.
+1. Select **Recorder** from the toolbar.
+1. Start recording and perform the click action on the desired UI element in your desktop application.
+1. Stop the recording.
+
+The recorder creates a **Click UI element in window** action with coordinate-based input parameters populated by using the respective values from your click action.
+
+## Solution 4: Use Move mouse and Send mouse click actions
+
+1. Add a **Move mouse** action to your flow.
+1. Configure the action to move the mouse to the specific coordinates of the target element.
+1. Add a **Send mouse click** action immediately after the Move mouse action.
+1. Configure the Send mouse click action to perform the desired click (left, right, or double-click).
+
+## Related content
+
+- [UI automation in Power Automate for desktop](/power-automate/desktop-flows/ui-elements)
+- [Use the recorder in Power Automate for desktop](/power-automate/desktop-flows/recording-flow)
+- [Mouse and keyboard actions](/power-automate/desktop-flows/actions-reference/mouseandkeyboard)
+- [OCR actions in Power Automate for desktop](/power-automate/desktop-flows/actions-reference/ocr)

support/power-platform/power-automate/toc.yml

@@ -108,6 +108,8 @@
           href: desktop-flows/ui-automation/ui-rdp-automation/rdp-no-highlight.md
         - name: '"The remote desktop was not found" error'
           href: desktop-flows/ui-automation/ui-rdp-automation/error-remote-desktop-not-found.md
+        - name: UI element picker or recorder can't view UI elements in desktop applications
+          href: desktop-flows/ui-automation/element-picker-cant-see-elements.md
         - name: UIPI issues with UI and web automation actions
           href: desktop-flows/ui-automation/uipi-issues.md
     - name: '"Could not read the application certificate" error when creating a connection'