Merge branch 'main' into CI-8139

Author: ryanberg-aquent

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

@@ -95,10 +95,13 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Errors associated with error code 8024A000
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-download-error-codes-associated-with-error-8024a000.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
@@ -298,7 +301,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/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/mem/intune/app-management/troubleshoot-google-apps.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot Managed Google Play apps on Intune-managed devices
 description: Troubleshoot common issues with Managed Google Play for Android Enterprise devices enrolled in Microsoft Intune.
-ms.date: 02/11/2025
+ms.date: 11/07/2025
 search.appverid: MET150
 ms.reviewer: kaushika, v-six, esalter
 ms.custom: sap:AppDeployment - Android\ManagedGooglePlay
@@ -36,8 +36,32 @@ This is expected behavior. Only system apps installed in the Work Profile are in
 
 See the blog post [Best practices for updating your Android Enterprise apps](https://techcommunity.microsoft.com/t5/intune-customer-success/best-practices-for-updating-your-android-enterprise-apps/ba-p/3038520) to learn about best practices and options for configuring app updates for your corporate-owned devices. This includes using network preferences, maintenance windows, and high-priority update mode Which bypasses all regular constraints so you can apply and update as fast as possible.
 
-### I want to stay updated on any Google service issues that may cause impact
+## I want to stay updated on any Google service issues that may cause impact
 
 Google releases [service announcements](https://www.androidenterprise.community/t5/service-announcements/tkb-p/Announcements) containing details about issues that may impact Android Enterprise management. Follow the [instructions to subscribe](https://www.androidenterprise.community/t5/news-info/new-community-board-subscribe-to-the-new-service-announcements/ba-p/1044) and receive notifications for new posts.
 
+## Newly approved Managed Google Play apps don't appear in the Play Store
+
+<!-- 33632857 -->
+
+When you approve a Managed Google Play app, it might not appear in the Play Store for users. This behavior occurs when your tenant is in Custom mode.
+
+Custom mode is enabled automatically when you edit collections in the Managed Google Play iFrame. In this mode, newly approved apps remain hidden until you manually add them to a collection.
+
+To resolve the issue, use one of the following options:
+
+- **Add the app to a collection:** In the Managed Google Play iFrame, add the app to an existing or new collection.
+- **Reset the Play Store layout to Basic:**  
+  1. In the Intune admin center, go to **Apps** > **All apps** > **Create Managed Google Play app**.  
+  2. Select **Reset to Basic**.  
+  3. Confirm the action.
+
+> [!IMPORTANT]
+> Resetting to Basic deletes all existing collections. After the reset, all approved apps become visible in the Play Store automatically. Any future changes to collections switch the store back to Custom mode.
+
+Allow a few minutes for the change to propagate. If the reset fails, retry and confirm that you have the correct permissions. If the issue continues, capture the error details and contact Microsoft Support.
+
+For more information, see [Add Managed Google Play apps to Android Enterprise devices with Intune](/mem/intune/apps/apps-add-android-for-work).
+
+
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-contact-disclaimer.md)]

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'

support/windows-server/installing-updates-features-roles/media/troubleshoot-windows-update-error-0x8000ffff/0x8000ffff-1.png

@@ -0,0 +1,44 @@
+---
+title: Troubleshoot Windows Update Error 0x8000FFFF
+description: Learn how to resolve Windows Update installation error 0x8000FFFF on Windows.
+manager: dcscontentpm
+audience: itpro
+ms.date: 11/6/2025
+ms.topic: troubleshooting
+ms.reviewer: scotro, mwesley, jarretr, v-ryanberg, v-gsitser
+ms.custom:
+- sap:windows servicing,updates and features on demand\windows update fails - Install errors starting with 0x800F (CBS E)
+- pcy:WinComm Devices Deploy
+appliesto:
+  - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+---
+
+#  Troubleshoot Windows Update error 0x8000FFFF
+
+**Applies to:** :heavy_check_mark: Windows VMs
+
+## Summary
+
+During a Windows Update installation, you receive error code 0x8000FFFF. This error is usually related to the`CryptCATAdminAddCatalog` function.
+
+## Prerequisites
+
+For Microsoft Azure virtual machines (VMs) that are running Windows, make sure that you back up the OS disk. For more information, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
+
+## How to identify the issue
+
+ This error is visible in the `Event Setup` and `CBS` logs after a failed update occurs.
+
+:::image type="content" source="./media/troubleshoot-windows-update-error-0x8000ffff/0x8000ffff-1.png" alt-text="Example of Windows Update error 0x8000FFFF in the Event Setup log" lightbox="media/troubleshoot-windows-update-error-0x8000ffff/0x8000ffff-1.png":::
+
+Although this error occurs without store corruption, it usually indicates corruption in *C:\Windows\System32\catroot2*.
+
+## Cause 
+
+This error is generally unexpected, and is usually considered to indicate a catastrophic failure. The `CryptCATAdminAddCatalog` process can be affected by corruption in the system files or folders, such as the *catroot2* folder.
+
+## Resolution
+
+For Windows-based computers, perform an [in-place upgrade](/windows-server/get-started/perform-in-place-upgrade#perform-the-in-place-upgrade). 
+
+For VMs that are running Windows in Azure, see [in-place upgrade on the Windows virtual machine](/azure/virtual-machines/windows-in-place-upgrade).