From f1b6c2e40c087b7843ab9718c359219af7b1e8f2 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Mar 2025 08:36:41 -0700 Subject: [PATCH 1/8] dep-map-plat-9853566 --- windows/whats-new/deprecated-features-resources.md | 3 +++ windows/whats-new/deprecated-features.md | 1 + 2 files changed, 4 insertions(+) diff --git a/windows/whats-new/deprecated-features-resources.md b/windows/whats-new/deprecated-features-resources.md index a276519e51..4d5155934e 100644 --- a/windows/whats-new/deprecated-features-resources.md +++ b/windows/whats-new/deprecated-features-resources.md @@ -21,6 +21,9 @@ appliesto: This article provides additional resources about [deprecated features for Windows client](deprecated-features.md) that may be needed by IT professionals. The following information is provided to help IT professionals plan for the removal of deprecated features: +## Windows UWP Map control and Windows Maps platform APIs + + ## Paint 3D Paint 3D is deprecated and will be removed from the Microsoft Store on November 4, 2024. Existing installations of Paint 3D will continue to work, but the app will no longer be available for download from the Microsoft Store. If you remove the app, you can reinstall it from the Microsoft Store until November 4, 2024. After that date, Paint 3D will no longer be available for download. Paint 3D was preinstalled on some Windows 10 devices, but wasn't preinstalled on Windows 11 devices. Some alternatives to Paint 3D include: diff --git a/windows/whats-new/deprecated-features.md b/windows/whats-new/deprecated-features.md index 88573222b7..407195c666 100644 --- a/windows/whats-new/deprecated-features.md +++ b/windows/whats-new/deprecated-features.md @@ -47,6 +47,7 @@ The features in this article are no longer being actively developed, and might b | Feature | Details and mitigation | Deprecation announced | |---|---|---| +| Windows UWP Map control and Windows Maps platform APIs | [Windows UWP Map control](/uwp/api/windows.ui.xaml.controls.maps) and [Windows Maps platform APIs](/uwp/api/windows.services.maps) are deprecated. Once the Maps app for Windows is removed on **[APP Date TBD]**, the UWP Bing Maps platform support within Windows will also be removed on **[PLAT Date TBD]**. Once the UWP Bing Maps platform support is removed, it won't be available to your UWP apps that use the Map control. For more information, see [Resources for deprecated features](deprecated-features-resources.md#windows-uwp-map-control-and-windows-maps-platform-apis). | April 2025 | | Line printer daemon (LPR/LPD) | Deprecation reminder: [The line printer daemon protocol (LPR/LPD) was deprecated](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) starting in Windows Server 2012. As removal of the line printer daemon protocol nears, we'd like to remind customers to ensure their environments are prepared for removal. When these features are eventually removed, clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the [Windows Standard Port Monitor](/troubleshoot/windows-server/printing/standard-port-monitor-for-tcpip). | [Original announcement: Windows Server 2012](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing)

Courtesy reminder: February 2025 | | Location History | We are deprecating and removing the Location History feature, an [API](/uwp/api/windows.devices.geolocation.geolocator.getgeopositionhistoryasync) that allowed Cortana to access 24 hours of device history when location was enabled. With the removal of the Location History feature, location data will no longer be saved locally and the corresponding settings will also be removed from the **Privacy & Security** > **Location** page in **Settings**. | February 2025 | | Suggested actions | Suggested actions that appear when you copy a phone number or future date in Windows 11 are deprecated and will be removed in a future Windows 11 update. | December 2024 | From b426d36fdbafd79bf3e03f73cc452356c4e56455 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 27 Mar 2025 10:56:09 -0700 Subject: [PATCH 2/8] dep-map-plat-9853566 --- windows/whats-new/deprecated-features-resources.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/windows/whats-new/deprecated-features-resources.md b/windows/whats-new/deprecated-features-resources.md index 4d5155934e..7aa2acecc7 100644 --- a/windows/whats-new/deprecated-features-resources.md +++ b/windows/whats-new/deprecated-features-resources.md @@ -23,6 +23,11 @@ This article provides additional resources about [deprecated features for Window ## Windows UWP Map control and Windows Maps platform APIs +In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). This means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement before **[PLAT Date TBD]** rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: +- [Migrate from Bing Maps to Azure Maps](/azure/azure-maps/migrate-bing-maps-overview) +- [Use the Azure Maps map control](/azure/azure-maps/how-to-use-map-control) +- [Azure Maps code samples](https://samples.azuremaps.com/) + ## Paint 3D From 342135a4b88960aa68d9bca8e80935bf908d318e Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Tue, 8 Apr 2025 13:43:25 -0400 Subject: [PATCH 3/8] Update various Windows Upgrade articles --- windows/deployment/upgrade/log-files.md | 514 +++++++++--------- windows/deployment/upgrade/setupdiag.md | 18 +- windows/deployment/upgrade/submit-errors.md | 12 +- .../upgrade/windows-error-reporting.md | 28 +- ...ws-upgrade-and-migration-considerations.md | 7 +- 5 files changed, 290 insertions(+), 289 deletions(-) diff --git a/windows/deployment/upgrade/log-files.md b/windows/deployment/upgrade/log-files.md index 78f9f1690b..34fd512807 100644 --- a/windows/deployment/upgrade/log-files.md +++ b/windows/deployment/upgrade/log-files.md @@ -1,257 +1,257 @@ ---- -title: Log files and resolving upgrade errors -description: Learn how to interpret and analyze the log files that are generated during the Windows upgrade process. -ms.service: windows-client -author: frankroj -manager: aaroncz -ms.author: frankroj -ms.localizationpriority: medium -ms.topic: troubleshooting -ms.collection: - - highpri - - tier2 -ms.subservice: itpro-deploy -ms.date: 01/29/2025 -appliesto: - - ✅ Windows 11 - - ✅ Windows 10 ---- - -# Windows upgrade log files - -> [!NOTE] -> -> This article is a 400-level article (advanced). -> -> See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of articles in this section. - -Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is **setupact.log**. The log files are located in a different folder depending on the Windows Setup phase. Recall that the phase can be determined from the extend code. - -> [!NOTE] -> -> Also see the [Windows Error Reporting](windows-error-reporting.md) article in this section for help with locating error codes and log files. - -The following table describes some log files and how to use them for troubleshooting purposes: - -|Log file |Phase: Location |Description |When to use| -|---|---|---|---| -|**setupact.log**|Down-Level:
$Windows.~BT\Sources\Panther|Contains information about setup actions during the downlevel phase. |All down-level failures and starting point for rollback investigations.
Setup.act is the most important log for diagnosing setup issues.| -|**setupact.log**|OOBE:
$Windows.~BT\Sources\Panther\UnattendGC|Contains information about actions during the OOBE phase.|Investigating rollbacks that failed during OOBE phase and operations - 0x4001C, 0x4001D, 0x4001E, 0x4001F.| -|**setupact.log**|Rollback:
$Windows.~BT\Sources\Rollback|Contains information about actions during rollback.|Investigating generic rollbacks - 0xC1900101.| -|**setupact.log**|Pre-initialization (prior to downlevel):
Windows|Contains information about initializing setup.|If setup fails to launch.| -|**setupact.log**|Post-upgrade (after OOBE):
Windows\Panther|Contains information about setup actions during the installation.|Investigate post-upgrade related issues.| -|**setuperr.log**|Same as setupact.log|Contains information about setup errors during the installation.|Review all errors encountered during the installation phase.| -|**miglog.xml**|Post-upgrade (after OOBE):
Windows\Panther|Contains information about what was migrated during the installation.|Identify post upgrade data migration issues.| -|**BlueBox.log**|Down-Level:
Windows\Logs\Mosetup|Contains information communication between `setup.exe` and Windows Update.|Use during WSUS and Windows Update down-level failures or for 0xC1900107.| -|Supplemental rollback logs:
**Setupmem.dmp**
**setupapi.dev.log**
Event logs (*.evtx)|$Windows.~BT\Sources\Rollback|Additional logs collected during rollback.|Setupmem.dmp: If OS bug checks during upgrade, setup attempts to extract a mini-dump.
Setupapi: Device install issues - 0x30018
Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.| - -## Log entry structure - -A `setupact.log` or `setuperr.log` entry includes the following elements: - -1. **The date and time** - 2023-09-08 09:20:05 - -2. **The log level** - Info, Warning, Error, Fatal Error - -3. **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS - - The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are useful for troubleshooting Windows Setup errors. - -4. **The message** - Operation completed successfully. - -See the following example: - -| Date/Time | Log level | Component | Message | -|------|------------|------------|------------| -|2023-09-08 09:23:50,| Warning | MIG | Couldn't replace object C:\Users\name\Cookies. Target Object can't be removed.| - -## Analyze log files - -The following instructions are meant for IT professionals. Also see the [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json) section in this guide to become familiar with [result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) and [extend codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes). - -To analyze Windows Setup log files: - -1. Determine the Windows Setup error code. Windows Setup should return an error code if it isn't successful with the upgrade process. - -1. Based on the [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes) portion of the error code, determine the type and location of a log file to investigate. - -1. Open the log file in a text editor, such as notepad. - -1. Using the [result code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below. - -1. To find the last occurrence of the result code: - - 1. Scroll to the bottom of the file and select after the last character. - 1. Select **Edit**. - 1. Select **Find**. - 1. Type the result code. - 1. Under **Direction** select **Up**. - 1. Select **Find Next**. - -1. When the last occurrence of the result code is located, scroll up a few lines from this location in the file and review the processes that failed prior to generating the result code. - -1. Search for the following important text strings: - - - `Shell application requested abort` - - `Abandoning apply due to error for object` - -1. Decode Win32 errors that appear in this section. - -1. Write down the timestamp for the observed errors in this section. - -1. Search other log files for additional information matching these timestamps or errors. - -For example, assume that the error code for an error is **0x8007042B - 0x2000D**. Searching for **8007042B** reveals the following content from the `setuperr.log` file: - -> [!NOTE] -> -> Some lines in the following text are shortened to enhance readability. For example -> -> - The date and time at the start of each line (ex: 2023-10-05 15:27:08) is shortened to minutes and seconds -> - The certificate file name, which is a long text string, is shortened to just "CN." - -**setuperr.log** content: - -```console -27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] -27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] -27:08, Error Gather failed. Last error: 0x00000000 -27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C -27:09, Error SP CMigrateFramework: Gather framework failed. Status: 44 -27:09, Error SP Operation failed: Migrate framework (Full). Error: 0x8007042B[gle=0x000000b7] -27:09, Error SP Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7] -27:09, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007042B[gle=0x000000b7] -``` - -The first line indicates there was an error **0x00000570** with the file **C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]**: - -```console -27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] -``` - -The error **0x00000570** is a [Win32 error code](/openspecs/windows_protocols/ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d) corresponding to: **ERROR_FILE_CORRUPT: The file or directory is corrupted and unreadable**. - -Therefore, Windows Setup failed because it wasn't able to migrate the corrupt file **C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\[CN]**. This file is a local system certificate and can be safely deleted. After the `setupact.log` file is searched for more details, the phrase **Shell application requested abort** is found in a location with the same timestamp as the lines in `setuperr.log`. This analysis confirms the suspicion that this file is the cause of the upgrade failure: - -**setupact.log** content: - -```console -27:00, Info Gather started at 10/5/2023 23:27:00 -27:00, Info [0x080489] MIG Setting system object filter context (System) -27:00, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped -27:00, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped -27:00, Info SP ExecuteProgress: Elapsed events:1 of 4, Percent: 12 -27:00, Info [0x0802c6] MIG Processing GATHER for migration unit: <System>\UpgradeFramework (CMXEAgent) -27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] -27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] -27:08, Info SP ExecuteProgress: Elapsed events:2 of 4, Percent: 25 -27:08, Info SP ExecuteProgress: Elapsed events:3 of 4, Percent: 37 -27:08, Info [0x080489] MIG Setting system object filter context (System) -27:08, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped -27:08, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped -27:08, Info MIG COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress. -27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost::CommandLine: -shortened- -27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost: Successfully launched host and got control object. -27:08, Error Gather failed. Last error: 0x00000000 -27:08, Info Gather ended at 10/5/2023 23:27:08 with result 44 -27:08, Info Leaving MigGather method -27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C -``` - -**setupapi.dev.log** content: - -```console ->>> [Device Install (UpdateDriverForPlugAndPlayDevices) - PCI\VEN_8086&DEV_8C4F] ->>> Section start 2023/09/26 20:13:01.623 - cmd: rundll32.exe "C:\WINDOWS\Installer\MSI6E4C.tmp",zzzzInvokeManagedCustomActionOutOfProc SfxCA_95972906 484 ChipsetWiX.CustomAction!Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers - ndv: INF path: C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf - ndv: Install flags: 0x00000000 - ndv: {Update Device Driver - PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8} - ndv: Search options: 0x00000081 - ndv: Searching single INF 'C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf' - dvi: {Build Driver List} 20:13:01.643 - dvi: Searching for hardware ID(s): - dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 - dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 - dvi: pci\ven_8086&dev_8c4f&cc_060100 - dvi: pci\ven_8086&dev_8c4f&cc_0601 - dvi: Searching for compatible ID(s): - dvi: pci\ven_8086&dev_8c4f&rev_04 - dvi: pci\ven_8086&dev_8c4f - dvi: pci\ven_8086&cc_060100 - dvi: pci\ven_8086&cc_0601 - dvi: pci\ven_8086 - dvi: pci\cc_060100 - dvi: pci\cc_0601 - sig: {_VERIFY_FILE_SIGNATURE} 20:13:01.667 - sig: Key = lynxpointsystem.inf - sig: FilePath = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf - sig: Catalog = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\LynxPoint.cat - sig: Success: File is signed in catalog. - sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 20:13:01.683 - dvi: Created Driver Node: - dvi: HardwareID - PCI\VEN_8086&DEV_8C4F - dvi: InfName - c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf - dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F - dvi: Section - Needs_ISAPNP_DRV - dvi: Rank - 0x00ff2001 - dvi: Signer Score - WHQL - dvi: DrvDate - 04/04/2016 - dvi: Version - 10.1.1.18 - dvi: {Build Driver List - exit(0x00000000)} 20:13:01.699 - ndv: Searching currently installed INF - dvi: {Build Driver List} 20:13:01.699 - dvi: Searching for hardware ID(s): - dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 - dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 - dvi: pci\ven_8086&dev_8c4f&cc_060100 - dvi: pci\ven_8086&dev_8c4f&cc_0601 - dvi: Searching for compatible ID(s): - dvi: pci\ven_8086&dev_8c4f&rev_04 - dvi: pci\ven_8086&dev_8c4f - dvi: pci\ven_8086&cc_060100 - dvi: pci\ven_8086&cc_0601 - dvi: pci\ven_8086 - dvi: pci\cc_060100 - dvi: pci\cc_0601 - dvi: Created Driver Node: - dvi: HardwareID - PCI\VEN_8086&DEV_8C4F - dvi: InfName - C:\WINDOWS\System32\DriverStore\FileRepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf - dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F - dvi: Section - Needs_ISAPNP_DRV - dvi: Rank - 0x00ff2001 - dvi: Signer Score - WHQL - dvi: DrvDate - 10/03/2016 - dvi: Version - 10.1.1.38 - dvi: {Build Driver List - exit(0x00000000)} 20:13:01.731 - dvi: {DIF_SELECTBESTCOMPATDRV} 20:13:01.731 - dvi: Default installer: Enter 20:13:01.735 - dvi: {Select Best Driver} - dvi: Class GUID of device changed to: {4d36e97d-e325-11ce-bfc1-08002be10318}. - dvi: Selected Driver: - dvi: Description - Intel(R) QM87 LPC Controller - 8C4F - dvi: InfFile - c:\windows\system32\driverstore\filerepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf - dvi: Section - Needs_ISAPNP_DRV - dvi: {Select Best Driver - exit(0x00000000)} - dvi: Default installer: Exit - dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 20:13:01.743 - ndv: Currently Installed Driver: - ndv: Inf Name - oem1.inf - ndv: Driver Date - 10/03/2016 - ndv: Driver Version - 10.1.1.38 - ndv: {Update Device Driver - exit(00000103)} -! ndv: No better matching drivers found for device 'PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8'. -! ndv: No devices were updated. -<<< Section end 2019/09/26 20:13:01.759 -<<< [Exit status: FAILURE(0xC1900101)] -``` - -This analysis indicates that the Windows upgrade error can be resolved by deleting the `C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\[CN]` file. - -> [!NOTE] -> -> In this example, the full file name is `C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f`. - -## Related articles - -- [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors). +--- +title: Log files and resolving upgrade errors +description: Learn how to interpret and analyze the log files that are generated during the Windows upgrade process. +ms.service: windows-client +author: frankroj +manager: aaroncz +ms.author: frankroj +ms.localizationpriority: medium +ms.topic: troubleshooting +ms.collection: + - highpri + - tier2 +ms.subservice: itpro-deploy +ms.date: 04/08/2025 +appliesto: + - ✅ Windows 11 + - ✅ Windows 10 +--- + +# Windows upgrade log files + +> [!NOTE] +> +> This article is a 400-level article (advanced). +> +> See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of articles in this section. + +Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is **setupact.log**. The log files are located in a different folder depending on the Windows Setup phase. Recall that the phase can be determined from the [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes). + +> [!NOTE] +> +> Also see the [Windows Error Reporting](windows-error-reporting.md) article in this section for help with locating error codes and log files. + +The following table describes some log files and how to use them for troubleshooting purposes: + +|Log file |Phase: Location |Description |When to use| +|---|---|---|---| +|**setupact.log**|Down-Level:
$Windows.~BT\Sources\Panther|Contains information about setup actions during the downlevel phase. |All downlevel failures and starting point for rollback investigations.
Setup.act is the most important log for diagnosing setup issues.| +|**setupact.log**|Out of box experience (OOBE):
$Windows.~BT\Sources\Panther\UnattendGC|Contains information about actions during the OOBE phase.|Investigating rollbacks that failed during OOBE phase and operations - 0x4001C, 0x4001D, 0x4001E, 0x4001F.| +|**setupact.log**|Rollback:
$Windows.~BT\Sources\Rollback|Contains information about actions during rollback.|Investigating generic rollbacks - 0xC1900101.| +|**setupact.log**|Pre-initialization (before downlevel):
Windows|Contains information about initializing setup.|If setup fails to launch.| +|**setupact.log**|Post-upgrade (after OOBE):
Windows\Panther|Contains information about setup actions during the installation.|Investigate post-upgrade related issues.| +|**setuperr.log**|Same as setupact.log|Contains information about setup errors during the installation.|Review all errors encountered during the installation phase.| +|**miglog.xml**|Post-upgrade (after OOBE):
Windows\Panther|Contains information about what was migrated during the installation.|Identify post upgrade data migration issues.| +|**BlueBox.log**|Down-Level:
Windows\Logs\Mosetup|Contains information communication between `setup.exe` and Windows Update.|Use during WSUS and Windows Update downlevel failures or for 0xC1900107.| +|Supplemental rollback logs:
**Setupmem.dmp**
**setupapi.dev.log**
Event logs (*.evtx)|$Windows.~BT\Sources\Rollback|Additional logs collected during rollback.|Setupmem.dmp: If OS bug checks during upgrade, setup attempts to extract a mini-dump.
Setupapi: Device install issues - 0x30018
Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.| + +## Log entry structure + +A `setupact.log` or `setuperr.log` entry includes the following elements: + +1. **The date and time** - 2023-09-08 09:20:05 + +1. **The log level** - Info, Warning, Error, Fatal Error + +1. **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS + + The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are useful for troubleshooting Windows Setup errors. + +1. **The message** - Operation completed successfully. + +See the following example: + +| Date/Time | Log level | Component | Message | +|------|------------|------------|------------| +|2023-09-08 09:23:50,| Warning | MIG | Couldn't replace object C:\Users\name\Cookies. Target Object can't be removed.| + +## Analyze log files + +The following instructions are meant for IT professionals. To become more familiar with [result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) and [extend codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes), see the article [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json). + +To analyze Windows Setup log files: + +1. Determine the Windows Setup error code. Windows Setup should return an error code if it isn't successful with the upgrade process. + +1. Based on the [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes) portion of the error code, determine the type and location of a log file to investigate. + +1. Open the log file in a text editor, such as Notepad. + +1. Using the [result code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below. + +1. To find the last occurrence of the result code: + + 1. Scroll to the bottom of the file and select after the last character. + 1. Select **Edit**. + 1. Select **Find**. + 1. Type the result code. + 1. Under **Direction** select **Up**. + 1. Select **Find Next**. + +1. When the last occurrence of the result code is located, scroll up a few lines from this location in the file and review the processes that failed before generating the result code. + +1. Search for the following important text strings: + + - `Shell application requested abort` + - `Abandoning apply due to error for object` + +1. Decode Win32 errors that appear in this section. + +1. Write down the timestamp for the observed errors in this section. + +1. Search other log files for additional information matching these timestamps or errors. + +For example, assume that the error code for an error is **0x8007042B - 0x2000D**. Searching for **8007042B** reveals the following content from the `setuperr.log` file: + +> [!NOTE] +> +> Some lines in the following text are shortened to enhance readability. For example +> +> - The date and time at the start of each line (ex: 2023-10-05 15:27:08) is shortened to minutes and seconds +> - The certificate file name, which is a long text string, is shortened to just "CN." + +**setuperr.log** content: + +```console +27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] +27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] +27:08, Error Gather failed. Last error: 0x00000000 +27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C +27:09, Error SP CMigrateFramework: Gather framework failed. Status: 44 +27:09, Error SP Operation failed: Migrate framework (Full). Error: 0x8007042B[gle=0x000000b7] +27:09, Error SP Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7] +27:09, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007042B[gle=0x000000b7] +``` + +The first line indicates there was an error **0x00000570** with the file **C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]**: + +```console +27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] +``` + +The error **0x00000570** is a [Win32 error code](/openspecs/windows_protocols/ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d) corresponding to: **ERROR_FILE_CORRUPT: The file or directory is corrupted and unreadable**. + +Therefore, Windows Setup failed because it wasn't able to migrate the corrupt file **C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\[CN]**. This file is a local system certificate and can be safely deleted. After the `setupact.log` file is searched for more details, the phrase **Shell application requested abort** is found in a location with the same timestamp as the lines in `setuperr.log`. This analysis confirms the suspicion that this file is the cause of the upgrade failure: + +**setupact.log** content: + +```console +27:00, Info Gather started at 10/5/2023 23:27:00 +27:00, Info [0x080489] MIG Setting system object filter context (System) +27:00, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped +27:00, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped +27:00, Info SP ExecuteProgress: Elapsed events:1 of 4, Percent: 12 +27:00, Info [0x0802c6] MIG Processing GATHER for migration unit: <System>\UpgradeFramework (CMXEAgent) +27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570] +27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570] +27:08, Info SP ExecuteProgress: Elapsed events:2 of 4, Percent: 25 +27:08, Info SP ExecuteProgress: Elapsed events:3 of 4, Percent: 37 +27:08, Info [0x080489] MIG Setting system object filter context (System) +27:08, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped +27:08, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped +27:08, Info MIG COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress. +27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost::CommandLine: -shortened- +27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost: Successfully launched host and got control object. +27:08, Error Gather failed. Last error: 0x00000000 +27:08, Info Gather ended at 10/5/2023 23:27:08 with result 44 +27:08, Info Leaving MigGather method +27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C +``` + +**setupapi.dev.log** content: + +```console +>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - PCI\VEN_8086&DEV_8C4F] +>>> Section start 2023/09/26 20:13:01.623 + cmd: rundll32.exe "C:\WINDOWS\Installer\MSI6E4C.tmp",zzzzInvokeManagedCustomActionOutOfProc SfxCA_95972906 484 ChipsetWiX.CustomAction!Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers + ndv: INF path: C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf + ndv: Install flags: 0x00000000 + ndv: {Update Device Driver - PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8} + ndv: Search options: 0x00000081 + ndv: Searching single INF 'C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf' + dvi: {Build Driver List} 20:13:01.643 + dvi: Searching for hardware ID(s): + dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 + dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 + dvi: pci\ven_8086&dev_8c4f&cc_060100 + dvi: pci\ven_8086&dev_8c4f&cc_0601 + dvi: Searching for compatible ID(s): + dvi: pci\ven_8086&dev_8c4f&rev_04 + dvi: pci\ven_8086&dev_8c4f + dvi: pci\ven_8086&cc_060100 + dvi: pci\ven_8086&cc_0601 + dvi: pci\ven_8086 + dvi: pci\cc_060100 + dvi: pci\cc_0601 + sig: {_VERIFY_FILE_SIGNATURE} 20:13:01.667 + sig: Key = lynxpointsystem.inf + sig: FilePath = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf + sig: Catalog = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\LynxPoint.cat + sig: Success: File is signed in catalog. + sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 20:13:01.683 + dvi: Created Driver Node: + dvi: HardwareID - PCI\VEN_8086&DEV_8C4F + dvi: InfName - c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf + dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F + dvi: Section - Needs_ISAPNP_DRV + dvi: Rank - 0x00ff2001 + dvi: Signer Score - WHQL + dvi: DrvDate - 04/04/2016 + dvi: Version - 10.1.1.18 + dvi: {Build Driver List - exit(0x00000000)} 20:13:01.699 + ndv: Searching currently installed INF + dvi: {Build Driver List} 20:13:01.699 + dvi: Searching for hardware ID(s): + dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 + dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 + dvi: pci\ven_8086&dev_8c4f&cc_060100 + dvi: pci\ven_8086&dev_8c4f&cc_0601 + dvi: Searching for compatible ID(s): + dvi: pci\ven_8086&dev_8c4f&rev_04 + dvi: pci\ven_8086&dev_8c4f + dvi: pci\ven_8086&cc_060100 + dvi: pci\ven_8086&cc_0601 + dvi: pci\ven_8086 + dvi: pci\cc_060100 + dvi: pci\cc_0601 + dvi: Created Driver Node: + dvi: HardwareID - PCI\VEN_8086&DEV_8C4F + dvi: InfName - C:\WINDOWS\System32\DriverStore\FileRepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf + dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F + dvi: Section - Needs_ISAPNP_DRV + dvi: Rank - 0x00ff2001 + dvi: Signer Score - WHQL + dvi: DrvDate - 10/03/2016 + dvi: Version - 10.1.1.38 + dvi: {Build Driver List - exit(0x00000000)} 20:13:01.731 + dvi: {DIF_SELECTBESTCOMPATDRV} 20:13:01.731 + dvi: Default installer: Enter 20:13:01.735 + dvi: {Select Best Driver} + dvi: Class GUID of device changed to: {4d36e97d-e325-11ce-bfc1-08002be10318}. + dvi: Selected Driver: + dvi: Description - Intel(R) QM87 LPC Controller - 8C4F + dvi: InfFile - c:\windows\system32\driverstore\filerepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf + dvi: Section - Needs_ISAPNP_DRV + dvi: {Select Best Driver - exit(0x00000000)} + dvi: Default installer: Exit + dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 20:13:01.743 + ndv: Currently Installed Driver: + ndv: Inf Name - oem1.inf + ndv: Driver Date - 10/03/2016 + ndv: Driver Version - 10.1.1.38 + ndv: {Update Device Driver - exit(00000103)} +! ndv: No better matching drivers found for device 'PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8'. +! ndv: No devices were updated. +<<< Section end 2019/09/26 20:13:01.759 +<<< [Exit status: FAILURE(0xC1900101)] +``` + +This analysis indicates that the Windows upgrade error can be resolved by deleting the `C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\[CN]` file. + +> [!NOTE] +> +> In this example, the full file name is `C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f`. + +## Related articles + +- [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors). diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index c945c7d666..b082524620 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -12,7 +12,7 @@ ms.topic: troubleshooting ms.collection: - highpri - tier2 -ms.date: 04/08/2024 +ms.date: 04/08/2025 appliesto: - ✅ Windows 11 - ✅ Windows 10 @@ -264,7 +264,7 @@ Logs ZipFile created at: c:\setupdiag\Logs_14.zip When SetupDiag searches log files, it uses a set of rules to match known issues. These rules are contained in an xml file. The xml file might be updated with new and updated rules as new versions of SetupDiag are made available. -Each rule name and its associated unique rule identifier are listed with a description of the known upgrade-blocking issue. In the rule descriptions, the term **down-level** refers to the first phase of the upgrade process, which runs under the original OS. +Each rule name and its associated unique rule identifier are listed with a description of the known upgrade-blocking issue. In the rule descriptions, the term **downlevel** refers to the first phase of the upgrade process, which runs under the original OS. | Rule Name | GUID | Description | | --- | --- | @@ -285,7 +285,7 @@ Each rule name and its associated unique rule identifier are listed with a descr | **HardblockDeviceOrDriver** | ED3AEFA1-F3E2-4F33-8A21-184ADF215B1B | This error indicates a device driver that is loaded on the host OS isn't compatible with the newer OS version. The device driver needs to be removed before the upgrade. | | **HardblockMismatchedLanguage** | 60BA8449-CF23-4D92-A108-D6FCEFB95B45 | This rule indicates the host OS and the target OS language editions don't match. | | **HardblockFlightSigning** | 598F2802-3E7F-4697-BD18-7A6371C8B2F8 | This rule indicates the target OS is a pre-release, Windows Insider build, and the target machine has Secure Boot enabled. This rule blocks the pre-release signed build from booting if installed on the machine. | -| **DiskSpaceBlockInDownLevel** | 6080AFAC-892E-4903-94EA-7A17E69E549E | This failure indicates the system ran out of disk space during the down-level operations of upgrade. | +| **DiskSpaceBlockInDownLevel** | 6080AFAC-892E-4903-94EA-7A17E69E549E | This failure indicates the system ran out of disk space during the downlevel operations of upgrade. | | **DiskSpaceFailure** | 981DCBA5-B8D0-4BA7-A8AB-4030F7A10191 | This failure indicates the system drive ran out of available disk space at some point after the first reboot into the upgrade. | | **PreReleaseWimMountDriverFound** | 31EC76CC-27EC-4ADC-9869-66AABEDB56F0 | Captures failures due to having an unrecognized `wimmount.sys` driver registered on the system. | | **DebugSetupMemoryDump** | C7C63D8A-C5F6-4255-8031-74597773C3C6 | This offline only rule indicates a bug check occurred during setup. If the debugger tools are available on the system, SetupDiag debugs the memory dump and provide details. | @@ -305,7 +305,7 @@ Each rule name and its associated unique rule identifier are listed with a descr | **FindMigGatherApplyFailure** | A9964E6C-A2A8-45FF-B6B5-25E0BD71428E | Shows errors when the migration Engine fails out on a gather or apply operation. Indicates the Migration Object (file or registry path), the Migration | | **OptionalComponentFailedToGetOCsFromPackage** | D012E2A2-99D8-4A8C-BBB2-088B92083D78 | This rule matches a specific Optional Component failure when attempting to enumerate components in a package. Indicates the optional component (OC) migration operation failed to enumerate optional components from an OC Package. It outputs the package name and error code. This rule replaces the OptionalComponentInstallFailure rule present. | | **OptionalComponentOpenPackageFailed** | 22952520-EC89-4FBD-94E0-B67DF88347F6 | Matches a specific Optional Component failure when attempting to open an OC package. It outputs the package name and error code. Indicates the optional component migration operation failed to open an optional component Package. Outputs the package name and error code. | -| **OptionalComponentInitCBSSessionFailed** | 63340812-9252-45F3-A0F2-B2A4CA5E9317 | Matches a specific failure where the advanced installer service or components aren't operating or started on the system. Indicates corruption in the servicing stack on the down-level system. Outputs the error code encountered while trying to initialize the servicing component on the existing OS. | +| **OptionalComponentInitCBSSessionFailed** | 63340812-9252-45F3-A0F2-B2A4CA5E9317 | Matches a specific failure where the advanced installer service or components aren't operating or started on the system. Indicates corruption in the servicing stack on the downlevel system. Outputs the error code encountered while trying to initialize the servicing component on the existing OS. | | **CriticalSafeOSDUFailure** | 73566DF2-CA26-4073-B34C-C9BC70DBF043 | This rule indicates a failure occurred while updating the SafeOS image with a critical dynamic update. It indicates the phase and error code that occurred while attempting to update the SafeOS image for diagnostic purposes. | | **UserProfileCreationFailureDuringOnlineApply** | 678117CE-F6A9-40C5-BC9F-A22575C78B14 | Indicates there was a critical failure while creating or modifying a User Profile during the online apply phase of the update. It indicates the operation and error code associated with the failure for diagnostic purposes. | | **UserProfileCreationFailureDuringFinalize** | C6677BA6-2E53-4A88-B528-336D15ED1A64 | Matches a specific User Profile creation error during the finalize phase of setup. It outputs the failure code. | @@ -314,7 +314,7 @@ Each rule name and its associated unique rule identifier are listed with a descr | **WimMountFailure** | BE6DF2F1-19A6-48C6-AEF8-D3B0CE3D4549 | This rule indicates the update failed to mount a WIM file. It shows the name of the WIM file and the error message and error code associated with the failure for diagnostic purposes. | | **WimMountDriverIssue** | 565B60DD-5403-4797-AE3E-BC5CB972FBAE | Detects failures in `WimMount.sys` registration on the system. | | **WimApplyExtractFailure** | 746879E9-C9C5-488C-8D4B-0C811FF3A9A8 | Matches a WIM apply failure during WIM extraction phases of setup. It outputs the extension, path, and error code. | -| **UpdateAgentExpanderFailure** | 66E496B3-7D19-47FA-B19B-4040B9FD17E2 | Matches DPX expander failures in the down-level phase of update from Windows Update. It outputs the package name, function, expression, and error code. | +| **UpdateAgentExpanderFailure** | 66E496B3-7D19-47FA-B19B-4040B9FD17E2 | Matches DPX expander failures in the downlevel phase of update from Windows Update. It outputs the package name, function, expression, and error code. | | **FindFatalPluginFailure** | E48E3F1C-26F6-4AFB-859B-BF637DA49636 | Matches any plug-in failure that setupplatform decides is fatal to setup. It outputs the plugin name, operation, and error code. | | **MigrationAbortedDueToPluginFailure** | D07A24F6-5B25-474E-B516-A730085940C9 | Indicates a critical failure in a migration plugin that causes setup to abort the migration. Provides the setup operation, plug-in name, plug-in action and error code. | | **DISMAddPackageFailed** | 6196FF5B-E69E-4117-9EC6-9C1EAB20A3B9 | Indicates a critical failure during a DISM add package operation. Specifies the Package Name, DISM error and add package error code. | @@ -327,9 +327,9 @@ Each rule name and its associated unique rule identifier are listed with a descr | | | | **FindSuccessfulUpgrade** | 8A0824C8-A56D-4C55-95A0-22751AB62F3E | Determines if the given setup was a success or not based off the logs. | | **FindSetupHostReportedFailure** | 6253C04F-2E4E-4F7A-B88E-95A69702F7EC | Gives information about failures surfaced early in the upgrade process by `setuphost.exe` | -| **FindDownlevelFailure** | 716334B7-F46A-4BAA-94F2-3E31BC9EFA55 | Gives failure information surfaced by SetupPlatform, later in the down-level phase. | -| **FindAbruptDownlevelFailure** | 55882B1A-DA3E-408A-9076-23B22A0472BD | Gives last operation failure information when the system fails in the down-level, but the log just ends abruptly. | -| **FindEarlyDownlevelError** | A4CE4FC9-5E10-4BB1-8ECE-3B29EB9D7C52 | Detects failures in down-level phase before setup platform is invoked. | +| **FindDownlevelFailure** | 716334B7-F46A-4BAA-94F2-3E31BC9EFA55 | Gives failure information surfaced by SetupPlatform, later in the downlevel phase. | +| **FindAbruptDownlevelFailure** | 55882B1A-DA3E-408A-9076-23B22A0472BD | Gives last operation failure information when the system fails in the downlevel, but the log just ends abruptly. | +| **FindEarlyDownlevelError** | A4CE4FC9-5E10-4BB1-8ECE-3B29EB9D7C52 | Detects failures in downlevel phase before setup platform is invoked. | | **FindSPFatalError** | A4028172-1B09-48F8-AD3B-86CDD7D55852 | Captures failure information when setup platform encounters a fatal error. | | **FindSetupPlatformFailedOperationInfo** | 307A0133-F06B-4B75-AEA8-116C3B53C2D1 | Gives last phase and error information when SetupPlatform indicates a critical failure. This rule indicates the operation and error associated with the failure for diagnostic purposes. | | **FindRollbackFailure** | 3A43C9B5-05B3-4F7C-A955-88F991BB5A48 | Gives last operation, failure phase, and error information when a rollback occurs. | @@ -363,7 +363,7 @@ System Information: Error: SetupDiag reports Optional Component installation failed to open OC Package. Package Name: Foundation, Error: 0x8007001F Recommend you check the "Windows Modules Installer" service (Trusted Installer) is started on the system and set to automatic start, reboot and try the update again. Optionally, you can check the status of optional components on the system (search for Windows Features), uninstall any unneeded optional components, reboot and try the update again. -Error: SetupDiag reports down-level failure, Operation: Finalize, Error: 0x8007001F - 0x50015 +Error: SetupDiag reports downlevel failure, Operation: Finalize, Error: 0x8007001F - 0x50015 Refer to https://learn.microsoft.com/windows/deployment/upgrade/upgrade-error-codes for error information. ``` diff --git a/windows/deployment/upgrade/submit-errors.md b/windows/deployment/upgrade/submit-errors.md index fd90fdc246..f1fc97e892 100644 --- a/windows/deployment/upgrade/submit-errors.md +++ b/windows/deployment/upgrade/submit-errors.md @@ -2,13 +2,13 @@ title: Submit Windows upgrade errors using Feedback Hub manager: aaroncz ms.author: frankroj -description: Download the Feedback Hub app, and then submit Windows upgrade errors for diagnosis using feedback hub. +description: Download the Feedback Hub app, and then submit Windows upgrade errors for diagnosis using Feedback Hub. ms.service: windows-client author: frankroj ms.localizationpriority: medium ms.topic: troubleshooting-general ms.subservice: itpro-deploy -ms.date: 01/29/2025 +ms.date: 04/08/2025 appliesto: - ✅ Windows 11 - ✅ Windows 10 @@ -28,17 +28,17 @@ This article describes how to submit problems with a Windows upgrade to Microsof The Feedback Hub app allows reporting to Microsoft of any problems encountered while using Windows. It also allows sending suggestions to Microsoft on how to improve the Windows experience. Previously, the Feedback Hub could only be used through the Windows Insider Program. Now anyone can use this tool. The Feedback Hub app can be downloaded from the [Microsoft Store](https://www.microsoft.com/store/p/feedback-hub/9nblggh4r32n?SilentAuth=1&wa=wsignin1.0). -The Feedback Hub requires a currently supported version of Windows. The Feedback Hub can be used to submit information to Microsoft if problems are encountered while upgrading Windows. If upgrading to a currently supported version of Windows from a previous version that's Windows 10 or newer, the Feedback Hub automatically collects log files. For operating systems prior to Windows 10 that don't support the Feedback Hub, the log files must be manually collected. The log files can then be attached to the feedback item using a device that is running a currently supported version of Windows that supports the Feedback Hub. +The Feedback Hub requires a [currently supported version of Windows](/windows/release-health/supported-versions-windows-client). The Feedback Hub can be used to submit information to Microsoft if problems are encountered while upgrading Windows. If upgrading between [currently supported version of Windows](/windows/release-health/supported-versions-windows-client), the Feedback Hub automatically collects log files. For out of support operating systems before Windows 10 that don't support the Feedback Hub, the log files must be manually collected. The log files can then be attached to the feedback item using a device that is running a [currently supported version of Windows](/windows/release-health/supported-versions-windows-client) that supports the Feedback Hub. ## Submit feedback To submit feedback about a failed Windows upgrade, open the [Feedback Hub](feedback-hub://?referrer=resolveUpgradeErrorsPage&tabid=2&contextid=81&newFeedback=true&feedbackType=2&topic=submit-errors.md). -In the Feedback Hub, fill out all four sections with as much detail as possible: +In the Feedback Hub, fill out all of the sections with as much detail as possible: 1. **Enter your feedback** 1. **Choose a category** -1. **Find similar feedback** +1. **Find similar feedback** - this section doesn't have anything to fill out, but it is important to check for similar feedback items. If a similar feedback item is found, select it and then select the **Next** button. This allows Microsoft to see how many people are affected by the same issue. 1. **Add more details** Recommended information that can be included under the **Add more details** section include: @@ -71,5 +71,3 @@ After the feedback is submitted, additional information and items can be added t 1. Copy and then use the short link that is displayed. :::image type="content" alt-text="Share example." source="../images/share.jpg"::: - -## Related articles diff --git a/windows/deployment/upgrade/windows-error-reporting.md b/windows/deployment/upgrade/windows-error-reporting.md index 958dbd15ef..d78577edfb 100644 --- a/windows/deployment/upgrade/windows-error-reporting.md +++ b/windows/deployment/upgrade/windows-error-reporting.md @@ -8,7 +8,7 @@ author: frankroj ms.localizationpriority: medium ms.topic: article ms.subservice: itpro-deploy -ms.date: 01/29/2025 +ms.date: 04/08/2025 appliesto: - ✅ Windows 11 - ✅ Windows 10 @@ -22,7 +22,7 @@ appliesto: > > See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of articles in this section. -When Windows Setup fails, the result and extend code are recorded as an informational event in the Application log by Windows Error Reporting as event 1001. The event name is **WinSetupDiag02**. Event Viewer or Windows PowerShell can be used to review this event. +When Windows Setup fails, the [result code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) and [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes) are recorded as an informational event in the Application log by Windows Error Reporting as event 1001. The event name is **WinSetupDiag02**. Event Viewer or Windows PowerShell can be used to review this event. To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt: @@ -48,18 +48,18 @@ To use Event Viewer: Ten parameters are listed in the event: -| Parameters | -| ------------- | -| P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) | -| P2: Setup Mode (x=default,1=Downlevel,5=Rollback) | -| P3: New OS Architecture (x=default,0=X86,9=AMD64) | -| P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) | -| **P5: Result Error Code** (Ex: 0xc1900101) | -| **P6: Extend Error Code** (Ex: 0x20017) | -| P7: Source OS build (Ex: 9600) | -| P8: Source OS branch (not typically available) | -| P9: New OS build (Ex: 16299) | -| P10: New OS branch (Ex: rs3_release) | +| Parameters | Description| Example | +| ------------- | --- | --- | +| P1 | The Setup Scenario | 1=Media, 5=WindowsUpdate, 7=Media Creation Tool | +| P2 | Setup Mode | x=default, 1=Downlevel, 5=Rollback | +| P3 | New OS Architecture | x=default, 0=X86, 9=AMD64 | +| P4 | Install Result | x=default, 0=Success, 1=Failure,2=Cancel, 3=Blocked | +| **P5** | Result Error Code | 0xc1900101 | +| **P6** | Extend Error Code | 0x20017 | +| P7 | Source OS build | 9600 | +| P8 | Source OS branch | Not typically available | +| P9 | New OS build | 16299 | +| P10 | New OS branch | rs3_release) | The event also contains links to log files that can be used to perform a detailed diagnosis of the error. The following example is an example of this event from a successful upgrade: diff --git a/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md b/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md index ca0f26473f..e1d51e9ebd 100644 --- a/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md +++ b/windows/deployment/upgrade/windows-upgrade-and-migration-considerations.md @@ -7,7 +7,10 @@ ms.service: windows-client author: frankroj ms.topic: upgrade-and-migration-article ms.subservice: itpro-deploy -ms.date: 08/30/2024 +ms.date: 04/08/2025 +appliesto: + - ✅ Windows 11 + - ✅ Windows 10 --- # Windows upgrade and migration considerations @@ -61,7 +64,7 @@ If a single-language Windows image that matches the system default UI language o ### Errorhandler.cmd -If using **Errorhandler.cmd** when upgrading from an earlier version of Windows, copy **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows. Copying **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows makes sure that if there are errors during the down-level phase of Windows Setup, the commands in **Errorhandler.cmd** run. For more information, see [Run a script if Windows Setup encounters a fatal error (ErrorHandler.cmd)](/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup#run-a-script-if-windowssetup-encounters-a-fatal-error-errorhandlercmd). +If using **Errorhandler.cmd** when upgrading from an earlier version of Windows, copy **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows. Copying **Errorhandler.cmd** into the `%WINDIR%\Setup\Scripts` directory on the original installation of Windows makes sure that if there are errors during the downlevel phase of Windows Setup, the commands in **Errorhandler.cmd** run. For more information, see [Run a script if Windows Setup encounters a fatal error (ErrorHandler.cmd)](/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup#run-a-script-if-windowssetup-encounters-a-fatal-error-errorhandlercmd). ## Related content From 8e6fde221700faed3a8295ea81b19abf54d35bf1 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Tue, 8 Apr 2025 13:48:52 -0400 Subject: [PATCH 4/8] Update various Windows Upgrade articles 2 --- .../upgrade/resolve-windows-upgrade-errors.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/windows/deployment/upgrade/resolve-windows-upgrade-errors.md b/windows/deployment/upgrade/resolve-windows-upgrade-errors.md index 9ab18bdcfd..8b9ff49ed1 100644 --- a/windows/deployment/upgrade/resolve-windows-upgrade-errors.md +++ b/windows/deployment/upgrade/resolve-windows-upgrade-errors.md @@ -8,7 +8,7 @@ ms.localizationpriority: medium ms.topic: troubleshooting-general ms.service: windows-client ms.subservice: itpro-deploy -ms.date: 01/29/2025 +ms.date: 04/08/2025 appliesto: - ✅ Windows 11 - ✅ Windows 10 @@ -35,22 +35,22 @@ The following four levels are assigned: See the following articles in this section: -- [Quick fixes](/troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): \Level 100\ Steps to take to eliminate many Windows upgrade errors. -- [SetupDiag](setupdiag.md): \Level 300\ SetupDiag is a new tool to help isolate the root cause of an upgrade failure. -- [Troubleshooting upgrade errors](/troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): \Level 300\ General advice and techniques for troubleshooting Windows upgrade errors, and an explanation of phases used during the upgrade process. -- [Windows Error Reporting](windows-error-reporting.md): \Level 300\ How to use Event Viewer to review details about a Windows upgrade. -- [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): \Level 400\ The components of an error code are explained. +- [Quick fixes](/troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): (Level 100) Steps to take to eliminate many Windows upgrade errors. +- [SetupDiag](setupdiag.md): (Level 300) SetupDiag is a new tool to help isolate the root cause of an upgrade failure. +- [Troubleshooting upgrade errors](/troubleshoot/windows-client/deployment/windows-10-upgrade-issues-troubleshooting?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): (Level 300) General advice and techniques for troubleshooting Windows upgrade errors, and an explanation of phases used during the upgrade process. +- [Windows Error Reporting](windows-error-reporting.md): (Level 300) How to use Event Viewer to review details about a Windows upgrade. +- [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): (Level 400) The components of an error code are explained. - [Result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes): Information about result codes. - [Extend codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes): Information about extend codes. -- [Log files](log-files.md): \Level 400\ A list and description of log files useful for troubleshooting. +- [Log files](log-files.md): (Level 400) A list and description of log files useful for troubleshooting. - [Log entry structure](log-files.md#log-entry-structure): The format of a log entry is described. - [Analyze log files](log-files.md#analyze-log-files): General procedures for log file analysis, and an example. -- [Resolution procedures](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): \Level 200\ Causes and mitigation procedures associated with specific error codes. +- [Resolution procedures](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json): (Level 200) Causes and mitigation procedures associated with specific error codes. - [0xC1900101](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#0xc1900101): Information about the 0xC1900101 result code. - [0x800xxxxx](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#0x800xxxxx): Information about result codes that start with 0x800. - [Other result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#other-result-codes): Additional causes and mitigation procedures are provided for some result codes. - [Other error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#other-error-codes): Additional causes and mitigation procedures are provided for some error codes. -- [Submit Windows upgrade errors](submit-errors.md): \Level 100\ Submit upgrade errors to Microsoft for analysis. +- [Submit Windows upgrade errors](submit-errors.md): (Level 100) Submit upgrade errors to Microsoft for analysis. ## Related articles From cbb15ff160d4c81a13c54d0a5723f57c2b56a668 Mon Sep 17 00:00:00 2001 From: Frank Rojas <45807133+frankroj@users.noreply.github.com> Date: Tue, 8 Apr 2025 14:00:58 -0400 Subject: [PATCH 5/8] Update various Windows Upgrade articles 3 --- windows/deployment/upgrade/windows-error-reporting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/windows-error-reporting.md b/windows/deployment/upgrade/windows-error-reporting.md index d78577edfb..d2da8a5c3d 100644 --- a/windows/deployment/upgrade/windows-error-reporting.md +++ b/windows/deployment/upgrade/windows-error-reporting.md @@ -59,7 +59,7 @@ Ten parameters are listed in the event: | P7 | Source OS build | 9600 | | P8 | Source OS branch | Not typically available | | P9 | New OS build | 16299 | -| P10 | New OS branch | rs3_release) | +| P10 | New OS branch | rs3_release | The event also contains links to log files that can be used to perform a detailed diagnosis of the error. The following example is an example of this event from a successful upgrade: From 972f6b60b35e22ed2c88cc21096001e72031652f Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 8 Apr 2025 13:41:56 -0700 Subject: [PATCH 6/8] edits --- windows/whats-new/deprecated-features-resources.md | 7 ++++--- windows/whats-new/deprecated-features.md | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/windows/whats-new/deprecated-features-resources.md b/windows/whats-new/deprecated-features-resources.md index 7aa2acecc7..299258715a 100644 --- a/windows/whats-new/deprecated-features-resources.md +++ b/windows/whats-new/deprecated-features-resources.md @@ -1,7 +1,7 @@ --- title: Resources for deprecated features in the Windows client description: Resources and details for deprecated features in the Windows client. -ms.date: 08/14/2024 +ms.date: 04/08/2025 ms.service: windows-client ms.subservice: itpro-fundamentals ms.localizationpriority: medium @@ -23,11 +23,12 @@ This article provides additional resources about [deprecated features for Window ## Windows UWP Map control and Windows Maps platform APIs -In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). This means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement before **[PLAT Date TBD]** rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: +In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). TThis means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement within one year of this deprecation notice rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: - [Migrate from Bing Maps to Azure Maps](/azure/azure-maps/migrate-bing-maps-overview) - [Use the Azure Maps map control](/azure/azure-maps/how-to-use-map-control) - [Azure Maps code samples](https://samples.azuremaps.com/) - +- [Bing Maps Blog](https://blogs.bing.com/maps) +- [Azure Maps Blog](https://techcommunity.microsoft.com/category/azure/blog/azuremapsblog) ## Paint 3D diff --git a/windows/whats-new/deprecated-features.md b/windows/whats-new/deprecated-features.md index 407195c666..227c3532f5 100644 --- a/windows/whats-new/deprecated-features.md +++ b/windows/whats-new/deprecated-features.md @@ -1,7 +1,7 @@ --- title: Deprecated features in the Windows client description: Review the list of features that Microsoft is no longer actively developing in Windows 10 and Windows 11. -ms.date: 02/19/2025 +ms.date: 04/08/2025 ms.service: windows-client ms.subservice: itpro-fundamentals ms.localizationpriority: medium @@ -47,7 +47,7 @@ The features in this article are no longer being actively developed, and might b | Feature | Details and mitigation | Deprecation announced | |---|---|---| -| Windows UWP Map control and Windows Maps platform APIs | [Windows UWP Map control](/uwp/api/windows.ui.xaml.controls.maps) and [Windows Maps platform APIs](/uwp/api/windows.services.maps) are deprecated. Once the Maps app for Windows is removed on **[APP Date TBD]**, the UWP Bing Maps platform support within Windows will also be removed on **[PLAT Date TBD]**. Once the UWP Bing Maps platform support is removed, it won't be available to your UWP apps that use the Map control. For more information, see [Resources for deprecated features](deprecated-features-resources.md#windows-uwp-map-control-and-windows-maps-platform-apis). | April 2025 | +| Windows UWP Map control and Windows Maps platform APIs | The [Windows UWP Map control](/uwp/api/windows.ui.xaml.controls.maps) and [Windows Maps platform APIs](/uwp/api/windows.services.maps) within Windows have been deprecated as of April 8, 2025. The Maps UWP Control and Maps platform support within Windows will continue to function but will not be updated. For more information, see [Resources for deprecated features](deprecated-features-resources.md#windows-uwp-map-control-and-windows-maps-platform-apis). | April 8, 2025 | | Line printer daemon (LPR/LPD) | Deprecation reminder: [The line printer daemon protocol (LPR/LPD) was deprecated](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing) starting in Windows Server 2012. As removal of the line printer daemon protocol nears, we'd like to remind customers to ensure their environments are prepared for removal. When these features are eventually removed, clients that print to a server using this protocol, such as UNIX clients, will not be able to connect or print. Instead, UNIX clients should use IPP. Windows clients can connect to UNIX shared printers using the [Windows Standard Port Monitor](/troubleshoot/windows-server/printing/standard-port-monitor-for-tcpip). | [Original announcement: Windows Server 2012](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831568(v=ws.11)#printing)

Courtesy reminder: February 2025 | | Location History | We are deprecating and removing the Location History feature, an [API](/uwp/api/windows.devices.geolocation.geolocator.getgeopositionhistoryasync) that allowed Cortana to access 24 hours of device history when location was enabled. With the removal of the Location History feature, location data will no longer be saved locally and the corresponding settings will also be removed from the **Privacy & Security** > **Location** page in **Settings**. | February 2025 | | Suggested actions | Suggested actions that appear when you copy a phone number or future date in Windows 11 are deprecated and will be removed in a future Windows 11 update. | December 2024 | From dc081551db1769a0b2e33a319ba5d1efa2bcb0c3 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 8 Apr 2025 13:50:09 -0700 Subject: [PATCH 7/8] edits --- windows/whats-new/deprecated-features-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/deprecated-features-resources.md b/windows/whats-new/deprecated-features-resources.md index 299258715a..25f3146597 100644 --- a/windows/whats-new/deprecated-features-resources.md +++ b/windows/whats-new/deprecated-features-resources.md @@ -23,7 +23,7 @@ This article provides additional resources about [deprecated features for Window ## Windows UWP Map control and Windows Maps platform APIs -In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). TThis means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement within one year of this deprecation notice rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: +In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). This means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement within one year of this deprecation notice rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: - [Migrate from Bing Maps to Azure Maps](/azure/azure-maps/migrate-bing-maps-overview) - [Use the Azure Maps map control](/azure/azure-maps/how-to-use-map-control) - [Azure Maps code samples](https://samples.azuremaps.com/) From 8e5ce4f53a94fb68a8855468d638a3c8210871ab Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Tue, 8 Apr 2025 14:28:58 -0700 Subject: [PATCH 8/8] edits --- windows/whats-new/deprecated-features-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/deprecated-features-resources.md b/windows/whats-new/deprecated-features-resources.md index 25f3146597..e17e62955c 100644 --- a/windows/whats-new/deprecated-features-resources.md +++ b/windows/whats-new/deprecated-features-resources.md @@ -23,7 +23,7 @@ This article provides additional resources about [deprecated features for Window ## Windows UWP Map control and Windows Maps platform APIs -In May 2024, we announced the unification of [Bing Maps for Enterprise](https://www.microsoft.com/maps/bing-maps/discontinued-services) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). This means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement within one year of this deprecation notice rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: +In May 2024, we announced the unification of [Bing Maps for Enterprise](https://blogs.bing.com/maps/2024-05/Microsoft-Announces-Vision-for-Next-Generation-of-Enterprise-Maps) with [Azure Maps](https://azure.microsoft.com/products/azure-maps). This means that going forward, Azure Maps will combine the best of Bing Maps for Enterprise and Azure Maps. If your solution uses the Windows UWP Map control, look to move to an Azure Maps based replacement within one year of this deprecation notice rather than the end date for the entire Bing Maps for Enterprise platform. The following resources can help you with this transition: - [Migrate from Bing Maps to Azure Maps](/azure/azure-maps/migrate-bing-maps-overview) - [Use the Azure Maps map control](/azure/azure-maps/how-to-use-map-control) - [Azure Maps code samples](https://samples.azuremaps.com/)