Skip to content

Commit f788dae

Browse files
Merge pull request #10164 from MicrosoftDocs/main
Auto Publish – main to live - 2025-11-11 02:00 UTC
2 parents 7000ca5 + 9144f2c commit f788dae

5 files changed

Lines changed: 131 additions & 3 deletions

File tree

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

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,9 @@ items:
9393
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
9494
- name: Error Code 0x800f0831
9595
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
96-
96+
- name: Error code 0x80072f8f
97+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80072f8f.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
98+
9799
- name: Uploading a VHD to Azure
98100
items:
99101
- name: Uploading a VHD to Azure
@@ -272,6 +274,28 @@ items:
272274

273275
- name: Instant Metadata Service (IMDS)
274276
items:
277+
- name: In-place system upgrade for Windows Server Azure VMs
278+
href: /azure/virtual-machines/windows-in-place-upgrade?context=/troubleshoot/azure/virtual-machines/windows/context/context
279+
- name: In-place system upgrade for Windows-based Azure VMs
280+
href: in-place-system-upgrade.md
281+
- name: Upgrade VM to contain more than 64 vCPUs
282+
href: vm-cannot-upgrade-64-vcpu.md
283+
- name: Windows Update errors that require in-place upgrades
284+
href: windows-update-errors-requiring-in-place-upgrade.md
285+
- name: Known errors and issues
286+
items:
287+
- name: Error code 0x80070002
288+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070002.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
289+
- name: Error code 0x8024002E
290+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-code-0x8024002e.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
291+
- name: Error code 0x80070490
292+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
293+
- name: Error 0x8007000d after installing Windows updates
294+
href: ../../../windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
295+
- name: Error Code 0x800f0831
296+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-installation-error-corruption.md
297+
- name: Error Code 0x8007045b
298+
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md
275299
- name: Overview
276300
href: /azure/virtual-machines/instance-metadata-service?context=/troubleshoot/azure/virtual-machines/windows/context/context
277301
- name: Certificate Issues

support/mem/intune/app-management/troubleshoot-google-apps.md

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Managed Google Play apps on Intune-managed devices
33
description: Troubleshoot common issues with Managed Google Play for Android Enterprise devices enrolled in Microsoft Intune.
4-
ms.date: 02/11/2025
4+
ms.date: 11/07/2025
55
search.appverid: MET150
66
ms.reviewer: kaushika, v-six, esalter
77
ms.custom: sap:AppDeployment - Android\ManagedGooglePlay
@@ -36,8 +36,32 @@ This is expected behavior. Only system apps installed in the Work Profile are in
3636

3737
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.
3838

39-
### I want to stay updated on any Google service issues that may cause impact
39+
## I want to stay updated on any Google service issues that may cause impact
4040

4141
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.
4242

43+
## Newly approved Managed Google Play apps don't appear in the Play Store
44+
45+
<!-- 33632857 -->
46+
47+
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.
48+
49+
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.
50+
51+
To resolve the issue, use one of the following options:
52+
53+
- **Add the app to a collection:** In the Managed Google Play iFrame, add the app to an existing or new collection.
54+
- **Reset the Play Store layout to Basic:**
55+
1. In the Intune admin center, go to **Apps** > **All apps** > **Create Managed Google Play app**.
56+
2. Select **Reset to Basic**.
57+
3. Confirm the action.
58+
59+
> [!IMPORTANT]
60+
> 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.
61+
62+
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.
63+
64+
For more information, see [Add Managed Google Play apps to Android Enterprise devices with Intune](/mem/intune/apps/apps-add-android-for-work).
65+
66+
4367
[!INCLUDE [Third-party disclaimer](../../../includes/third-party-contact-disclaimer.md)]
Loading
Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
---
2+
title: Troubleshoot Windows Update Error 0x80072f8f
3+
description: Learn how to resolve Windows Update error 0x80072f8f on Windows.
4+
manager: dcscontentpm
5+
audience: itpro
6+
ms.date: 11/6/2025
7+
ms.topic: troubleshooting
8+
ms.reviewer: scotro, mwesley, jarretr, v-ryanberg, v-gsitser
9+
ms.custom:
10+
- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
11+
- pcy:WinComm Devices Deploy
12+
appliesto:
13+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
14+
---
15+
16+
# Troubleshoot Windows Update error 0x80072f8f
17+
18+
## Summary
19+
20+
When you try to connect to Windows Update, you encounter error 0x80072f8f. This error typically indicates issues that affect SSL negotiation because of out-of-sync clock settings or untrusted SSL certificates.
21+
22+
:::image type="content" source="./media/troubleshoot-windows-update-error-0x80072f8f/updateerror0x80072f8f-wusaerror.png" alt-text="Windows Update error 0x80072f8f" lightbox="media/troubleshoot-windows-update-error-0x80072f8f/updateerror0x80072f8f-wusaerror.png":::
23+
24+
## Prerequisites
25+
26+
For virtual machines (VMs) running Windows in Azure, make sure that you back up the OS disk. For more information, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
27+
28+
## How to identify the issue
29+
30+
### Symptom 1
31+
32+
Windows Update fails and returns error 0x80072f8f. Check the `WindowsUpdate.log` located at *C:\Windows\Logs\WindowsUpdate* for entries that resemble the following entry:
33+
34+
```output
35+
03E4 1668 SLS Making request with URL HTTPS://sls.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.14393.0/0?CH=531&L=en-US&P=&PT=0x7&WUA=10.0.14393.1794
36+
03E4 1668 Misc Send request failed, hr:0x80072f8f
37+
03E4 1668 Misc WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f; retrying with default proxy.
38+
03E4 1668 Misc Send request failed, hr:0x80072f8f
39+
03E4 1668 Misc Library download error. Error 0x80072f8f. Will retry. Retry Counter:0
40+
```
41+
42+
### Symptom 2
43+
44+
When you try to download updates from Windows Update, you see no progress. The `WindowsUpdate.log` shows failures on WinHTTP requests to `SLS.Update.Microsoft.com`:
45+
46+
```output
47+
2032 2248 ComApi * START * Federated Search ClientId = Device Driver Retrieval Client (cV: xXbBtDYuUUOnH3AK.1.0)
48+
4744 4120 Misc *FAILED* [80072F8F] Send request
49+
4744 4120 Misc *FAILED* [80072F8F] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
50+
4744 4120 Misc *FAILED* [80072F8F] Library download error. Will retry. Retry Counter:0
51+
```
52+
53+
### Symptom 3
54+
55+
When you check for updates from Windows Update, you see no progress. The `WindowsUpdate.log` indicates `HTTP Send Request failed with 0x80072f8f (WININET_E_DECODING_FAILED)`:
56+
57+
```output
58+
7452 3228 Misc *FAILED* [80072F8F] Send request
59+
7452 3228 Misc *FAILED* [80072F8F] WinHttp: SendRequestToServerForFileInformation (retrying with default proxy)
60+
7452 3228 Misc *FAILED* [80072F8F] Library download error. Will retry. Retry Counter:0
61+
```
62+
63+
## Cause
64+
65+
This error is usually caused by one of the following issues:
66+
67+
- **Out-of-sync clock**: If the clock settings on the computer are incorrect, SSL negotiation fails. You can quickly verify clock accuracy from `WindowsUpdate.log` that always prints traces in local time.
68+
- **Untrusted SSL certificate**: This issue occurs in the following managed scenarios:
69+
- For Windows Server Update Services (WSUS).
70+
- For Configuration Manager that's configured over SSL and includes self-generated or signed SSL certificates.
71+
72+
In these scenarios, the scan fails if the client doesn't trust the certificate chain.
73+
74+
## Resolution
75+
76+
For Windows-based computers, perform an [in-place upgrade](/windows-server/get-started/perform-in-place-upgrade#perform-the-in-place-upgrade).
77+
78+
For VMs running Windows in Azure, see [in-place upgrade on the Windows virtual machine](/azure/virtual-machines/windows-in-place-upgrade).

support/windows-server/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3224,6 +3224,8 @@ items:
32243224
href: installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md
32253225
- name: Troubleshoot "Shutdown in Progress" Windows error 0x8007045b
32263226
href: installing-updates-features-roles/troubleshoot-error-shutdown-in-process.md
3227+
- name: Troubleshoot Windows Update error 0x80072f8f
3228+
href: ./installing-updates-features-roles/troubleshoot-windows-update-error-0x80072f8f.md
32273229
- name: Troubleshoot Windows Update error 0x8024002E
32283230
href: installing-updates-features-roles/troubleshoot-windows-update-error-code-0x8024002e.md
32293231
- name: WUSA returns 0x5 ERROR_ACCESS_DENIED

0 commit comments

Comments
 (0)