deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Freshnes 2024-01 4

Browse Source
This commit is contained in:
Frank Rojas 2024-01-12 18:46:59 -05:00
parent 8a7c649634
commit 61d178294c
10 changed files with 140 additions and 144 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
.openpublishing.redirection.json
View File

@ -12734,6 +12734,11 @@
"source_path": "windows/deployment/windows-10-media.md", "source_path": "windows/deployment/windows-10-media.md",
"redirect_url": "/licensing/", "redirect_url": "/licensing/",
"redirect_document_id": false "redirect_document_id": false
},
{
"source_path": "windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md",
"redirect_url": "/windows/deployment/upgrade/resolve-windows-upgrade-errors",
"redirect_document_id": false
} }
] ]
} }

4
windows/deployment/TOC.yml
View File

@ -335,8 +335,8 @@
items: items:
- name: Resolve upgrade errors - name: Resolve upgrade errors
items: items:
- name: Resolve Windows client upgrade errors - name: Resolve Windows upgrade errors
href: upgrade/resolve-windows-10-upgrade-errors.md href: upgrade/resolve-windows-upgrade-errors.md
- name: Quick fixes - name: Quick fixes
href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json href: /troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json
- name: SetupDiag - name: SetupDiag

12
windows/deployment/deploy-whats-new.md
View File

@ -11,7 +11,7 @@ ms.topic: conceptual
ms.collection: ms.collection:
- highpri - highpri
- tier2 - tier2
ms.date: 11/17/2023 ms.date: 01/12/2024
appliesto: appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
@ -21,7 +21,7 @@ appliesto:
This article provides an overview of new solutions and online content related to deploying Windows client in your organization. This article provides an overview of new solutions and online content related to deploying Windows client in your organization.
- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](/windows/whats-new/index). - For an all-up overview of new features in Windows, see [What's new in Windows](/windows/whats-new/).
## [Preview] Windows Autopilot diagnostics page ## [Preview] Windows Autopilot diagnostics page
@ -88,7 +88,7 @@ The following Delivery Optimization policies are removed in the Windows 10, vers
- **Intune console updates**: target version is now available allowing you to specify which supported version of Windows you want devices to move to. Additionally, this capability enables you to keep devices on their current version until they reach end of service. Check it out in Intune, also available as a Group Policy and Configuration Service Provider (CSP) policy. - **Intune console updates**: target version is now available allowing you to specify which supported version of Windows you want devices to move to. Additionally, this capability enables you to keep devices on their current version until they reach end of service. Check it out in Intune, also available as a Group Policy and Configuration Service Provider (CSP) policy.
- **Validation improvements**: To ensure devices and end users stay productive and protected, Microsoft blocks devices from updating when there are known issues that would impact that device. Also, to better enable IT administrators to validate on the latest release, a new policy is available that enables admins to opt devices out of the built-in safeguard holds. - **Validation improvements**: To ensure devices and end users stay productive and protected, Microsoft blocks devices from updating when there are known issues affect that device. Also, to better enable IT administrators to validate on the latest release, a new policy is available that enables admins to opt devices out of the built-in safeguard holds.
- [**Automatic Restart Sign-on (ARSO)**](/windows-server/identity/ad-ds/manage/component-updates/winlogon-automatic-restart-sign-on--arso-): Windows automatically signs in as the user and locks their device in order to complete the update. This automatic sign-on ensures that when the user returns and unlocks the device, the update is completed. - [**Automatic Restart Sign-on (ARSO)**](/windows-server/identity/ad-ds/manage/component-updates/winlogon-automatic-restart-sign-on--arso-): Windows automatically signs in as the user and locks their device in order to complete the update. This automatic sign-on ensures that when the user returns and unlocks the device, the update is completed.
@ -158,8 +158,8 @@ Input from the community heavily influenced the development of Upgrade Readiness
For more information about Upgrade Readiness, see the following articles: For more information about Upgrade Readiness, see the following articles:
- [Windows Analytics blog](https://aka.ms/blog/WindowsAnalytics/) - [Windows Analytics blog](https://aka.ms/blog/WindowsAnalytics/).
- [Manage Windows upgrades with Upgrade Readiness](/mem/configmgr/desktop-analytics/overview) - [Manage Windows upgrades with Upgrade Readiness](/mem/configmgr/desktop-analytics/overview).
### Update Compliance ### Update Compliance
@ -215,7 +215,7 @@ For more information, see the following guides:
## Troubleshooting guidance ## Troubleshooting guidance
[Resolve Windows 10 upgrade errors](upgrade/resolve-windows-10-upgrade-errors.md) was published in October of 2016 and continues to be updated with new fixes. The article provides a detailed explanation of the Windows upgrade process and instructions on how to locate, interpret, and resolve specific errors that can be encountered during the upgrade process. [Resolve Windows upgrade errors](upgrade/resolve-windows-upgrade-errors.md) was published in October of 2016 and continues to be updated with new fixes. The article provides a detailed explanation of the Windows upgrade process and instructions on how to locate, interpret, and resolve specific errors that can be encountered during the upgrade process.
## Related articles ## Related articles

2
windows/deployment/index.yml
View File

@ -129,7 +129,7 @@ additionalContent:
- text: Convert a disk from MBR to GPT - text: Convert a disk from MBR to GPT
url: mbr-to-gpt.md url: mbr-to-gpt.md
- text: Resolve Windows upgrade errors - text: Resolve Windows upgrade errors
url: upgrade/resolve-windows-10-upgrade-errors.md url: upgrade/resolve-windows-upgrade-errors.md
- title: Licensing and activation - title: Licensing and activation
links: links:

77
windows/deployment/upgrade/log-files.md
View File

@ -1,6 +1,6 @@
--- ---
title: Log files and resolving upgrade errors title: Log files and resolving upgrade errors
description: Learn how to interpret and analyze the log files that are generated during the Windows 10 upgrade process. description: Learn how to interpret and analyze the log files that are generated during the Windows upgrade process.
ms.prod: windows-client ms.prod: windows-client
author: frankroj author: frankroj
manager: aaroncz manager: aaroncz
@ -11,29 +11,28 @@ ms.collection:
- highpri - highpri
- tier2 - tier2
ms.technology: itpro-deploy ms.technology: itpro-deploy
ms.date: 10/28/2022 ms.date: 01/12/2024
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
--- ---
# Windows upgrade log files # Windows upgrade log files
**Applies to**
- Windows 10
> [!NOTE] > [!NOTE]
>
> This is a 400-level topic (advanced).<br> > This is a 400-level topic (advanced).<br>
>
> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article. > See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of topics in this article.
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 you can determine the phase from the extend code. 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 you can determine the phase from the extend code.
> [!NOTE] > [!NOTE]
>
> Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files. > Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files.
The following table describes some log files and how to use them for troubleshooting purposes: The following table describes some log files and how to use them for troubleshooting purposes:
|Log file |Phase: Location |Description |When to use| |Log file |Phase: Location |Description |When to use|
|---|---|---|---| |---|---|---|---|
|setupact.log|Down-Level:<br>$Windows.~BT\Sources\Panther|Contains information about setup actions during the downlevel phase. |All down-level failures and starting point for rollback investigations.<br> Setup.act is the most important log for diagnosing setup issues.| |setupact.log|Down-Level:<br>$Windows.~BT\Sources\Panther|Contains information about setup actions during the downlevel phase. |All down-level failures and starting point for rollback investigations.<br> Setup.act is the most important log for diagnosing setup issues.|
@ -48,21 +47,17 @@ The following table describes some log files and how to use them for troubleshoo
## Log entry structure ## Log entry structure
A setupact.log or setuperr.log entry (files are located at C:\Windows) includes the following elements: A `setupact.log` or `setuperr.log` entry (files are located at C:\Windows) includes the following elements:
1. **The date and time** - 2016-09-08 09:20:05 1. **The date and time** - 2016-09-08 09:20:05
1. **The log level** - Info, Warning, Error, Fatal Error
2. **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.
3. **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS 1. **The message** - Operation completed successfully.
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: See the following example:
@ -78,37 +73,38 @@ To analyze Windows Setup log files:
1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it isn't successful with the upgrade process. 1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it isn't successful with the upgrade process.
2. 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. 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.
3. Open the log file in a text editor, such as notepad. 1. Open the log file in a text editor, such as notepad.
4. 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. 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.
5. To find the last occurrence of the result code: 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. Scroll to the bottom of the file and select after the last character.
2. Select **Edit**. 1. Select **Edit**.
3. Select **Find**. 1. Select **Find**.
4. Type the result code. 1. Type the result code.
5. Under **Direction** select **Up**. 1. Under **Direction** select **Up**.
6. Select **Find Next**. 1. Select **Find Next**.
6. When you've located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed prior to generating the result code. 1. When you've located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed prior to generating the result code.
7. Search for the following important text strings: 1. Search for the following important text strings:
- `Shell application requested abort` - `Shell application requested abort`
- `Abandoning apply due to error for object` - `Abandoning apply due to error for object`
8. Decode Win32 errors that appear in this section. 1. Decode Win32 errors that appear in this section.
9. Write down the timestamp for the observed errors in this section. 1. Write down the timestamp for the observed errors in this section.
10. Search other log files for additional information matching these timestamps or errors. 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: 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] > [!NOTE]
>
> Some lines in the text below are shortened to enhance readability. For example > Some lines in the text below are shortened to enhance readability. For example
> >
> - The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds > - The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds
@ -250,15 +246,16 @@ Therefore, Windows Setup failed because it wasn't able to migrate the corrupt fi
<<< [Exit status: FAILURE(0xC1900101)] <<< [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. 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] > [!NOTE]
> In this example, the full, unshortened file name is C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f. >
> In this example, the full, unshortened file name is `C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f`.
## Related articles ## Related articles
[Windows 10 FAQ for IT professionals](../planning/windows-10-enterprise-faq-itpro.yml) - [Windows 10 FAQ for IT professionals](../planning/windows-10-enterprise-faq-itpro.yml).
<br>[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx) - [Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx).
<br>[Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications) - [Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications).
<br>[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro) - [Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro).
<br>[Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors) - [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors).

24
windows/deployment/upgrade/resolve-windows-10-upgrade-errors.md → windows/deployment/upgrade/resolve-windows-upgrade-errors.md
View File

@ -6,9 +6,9 @@ description: Resolve Windows upgrade errors for ITPros. Technical information fo
author: frankroj author: frankroj
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article ms.topic: article
ms.service: windows-client ms.prod: windows-client
ms.subservice: itpro-deploy ms.technology: itpro-deploy
ms.date: 01/10/2024 ms.date: 01/11/2024
appliesto: appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
@ -16,13 +16,13 @@ appliesto:
# Resolve Windows upgrade errors: Technical information for IT Pros # Resolve Windows upgrade errors: Technical information for IT Pros
>[!IMPORTANT] > [!IMPORTANT]
> >
>This article contains technical instructions for IT administrators. If you are not an IT administrator, try some of the [quick fixes](/troubleshoot/windows-client/deployment/windows-10-upgrade-quick-fixes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json) described in this article then contact [Microsoft Support](https://support.microsoft.com/contactus/) starting with the Virtual Agent. To talk to a person about your issue, click **Get started** to interact with the Virtual Agent, then enter "Talk to a person" two times. The Virtual Agent can also help you to resolve many Windows upgrade issues. Also see: [Get help with Windows 10 upgrade and installation errors](https://support.microsoft.com/help/10587/windows-10-get-help-with-upgrade-installation-errors) and [Submit Windows 10 upgrade errors using Feedback Hub](submit-errors.md). > This article contains technical instructions for IT administrators. The article isn't intended for non-IT administrators such as home or consumer users.
This article contains a brief introduction to the Windows installation processes, and provides resolution procedures that IT administrators can use to resolve issues with a Windows upgrade. This article contains a brief introduction to the Windows installation processes, and provides resolution procedures that IT administrators can use to resolve issues with a Windows upgrade.
The article has been divided into subtopics of different technical levels. Basic level provides common procedures that can resolve several types of upgrade errors. Advanced level requires some experience with detailed troubleshooting methods. The article is divided into subtopics of different technical levels. Basic level provides common procedures that can resolve several types of upgrade errors. Advanced level requires some experience with detailed troubleshooting methods.
The following four levels are assigned: The following four levels are assigned:
@ -33,12 +33,12 @@ The following four levels are assigned:
## In this guide ## In this guide
See the following topics in this article: 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 you can take to eliminate many Windows upgrade errors.<br> - [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 you can take to eliminate many Windows upgrade errors.<br>
- [SetupDiag](setupdiag.md): \Level 300\ SetupDiag is a new tool to help you isolate the root cause of an upgrade failure. - [SetupDiag](setupdiag.md): \Level 300\ SetupDiag is a new tool to help you 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 10 upgrade errors, and an explanation of phases used during the upgrade process.<br> - [Troubleshooting upgrade errors](/troubleshoot/windows-client/deployment/windows-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.<br>
- [Windows Error Reporting](windows-error-reporting.md): \Level 300\ How to use Event Viewer to review details about a Windows 10 upgrade. - [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. - [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. - [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. - [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.
@ -50,12 +50,8 @@ See the following topics in this article:
- [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. - [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 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. - [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 10 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 ## Related articles
- [Windows 10 FAQ for IT professionals](../planning/windows-10-enterprise-faq-itpro.yml).
- [Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx).
- [Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications).
- [Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro).
- [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors). - [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors).

22
windows/deployment/upgrade/setupdiag.md
View File

@ -11,7 +11,7 @@ ms.topic: troubleshooting
ms.collection: ms.collection:
- highpri - highpri
- tier2 - tier2
ms.date: 01/10/2024 ms.date: 01/12/2024
appliesto: appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a> - ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
@ -21,7 +21,7 @@ appliesto:
> [!NOTE] > [!NOTE]
> >
> This is a 300 level topic (moderate advanced). See [Resolve Windows upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article. > This is a 300 level article (moderate advanced). See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of articles in this section.
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
> [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142) > [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142)
@ -30,7 +30,7 @@ appliesto:
> [!IMPORTANT] > [!IMPORTANT]
> >
> Always be sure to run the most recent version of SetupDiag. This ensures the latest functionality and fixes to known issues. > Microsoft recommends running the latest version of SetupDiag when running it manually. The latest version is available via the following [download link](https://go.microsoft.com/fwlink/?linkid=870142). Running the latest version ensures the latest functionality and fixes known issues.
SetupDiag is a diagnostic tool that can be used to obtain details about why a Windows upgrade was unsuccessful. SetupDiag is a diagnostic tool that can be used to obtain details about why a Windows upgrade was unsuccessful.
@ -38,7 +38,7 @@ SetupDiag works by examining Windows Setup log files. It attempts to parse these
SetupDiag is included with [Windows Setup](/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files#windows-setup-scenario) in all currently supported versions of Windows. SetupDiag is included with [Windows Setup](/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files#windows-setup-scenario) in all currently supported versions of Windows.
During the upgrade process, Windows Setup will extract all its sources files, including **SetupDiag.exe**, to the **%SystemDrive%\$Windows.~bt\Sources** directory. If there's an issue with the upgrade, SetupDiag will automatically run to determine the cause of the failure. During the upgrade process, Windows Setup extracts all its sources files, including **SetupDiag.exe**, to the **%SystemDrive%\$Windows.~bt\Sources** directory. If there's an issue with the upgrade, SetupDiag automatically runs to determine the cause of the failure.
When run by Windows Setup, the following [parameters](#parameters) are used: When run by Windows Setup, the following [parameters](#parameters) are used:
@ -47,29 +47,29 @@ When run by Windows Setup, the following [parameters](#parameters) are used:
- /Output:%windir%\logs\SetupDiag\SetupDiagResults.xml - /Output:%windir%\logs\SetupDiag\SetupDiagResults.xml
- /RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results - /RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results
The resulting SetupDiag analysis can be found at `%WinDir%\Logs\SetupDiag\SetupDiagResults.xml` and in the registry under `HKLM\SYSTEM\Setup\SetupDiag\Results`. Note that the registry path isn't the same as the default registry path when SetupDiag is run manually. When SetupDiag is run manually, and the `/RegPath` parameter isn't specified, data is stored in the registry at `HKLM\SYSTEM\Setup\MoSetup\Volatile\SetupDiag`. The resulting SetupDiag analysis can be found at `%WinDir%\Logs\SetupDiag\SetupDiagResults.xml` and in the registry under `HKLM\SYSTEM\Setup\SetupDiag\Results`. Note that the registry path isn't the same as the default registry path when SetupDiag is run manually. When SetupDiag is run manually, and the `/RegPath` parameter isn't specified, data is stored in the registry at `HKLM\SYSTEM\Setup\MoSetup\Volatile\SetupDiag`.
> [!IMPORTANT] > [!IMPORTANT]
> >
> When SetupDiag indicates that there were multiple failures, the last failure in the log file is typically the fatal error, not the first one. > When SetupDiag indicates that there were multiple failures, the last failure in the log file is typically the fatal error, not the first one.
If the upgrade process proceeds normally, the **Sources** directory including **SetupDiag.exe** is moved under **%SystemDrive%\Windows.Old** for cleanup. If the **Windows.old** directory is deleted later, **SetupDiag.exe** will also be removed. If the upgrade process proceeds normally, the **Sources** directory including **SetupDiag.exe** is moved under **%SystemDrive%\Windows.Old** for cleanup. If the **Windows.old** directory is deleted later, **SetupDiag.exe** is also removed.
## Using SetupDiag ## Using SetupDiag
To quickly use SetupDiag on your current computer: To quickly use SetupDiag on your current computer:
1. Verify that your system meets the [requirements](#requirements) described below. If needed, install [.NET framework 4.6](https://www.microsoft.com/download/details.aspx?id=48137). 1. Verify that your system meets the [requirements](#requirements). If needed, install [.NET framework 4.6](https://www.microsoft.com/download/details.aspx?id=48137).
1. [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). 1. [Download SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142).
1. If your web browser asks what to do with the file, choose **Save**. By default, the file will be saved to your **Downloads** folder. IF desired, you can also save it to a different location by using **Save As**. 1. If your web browser asks what to do with the file, choose **Save**. By default, the file is saved to the **Downloads** folder. If desired, you can also save it to a different location by using **Save As**.
1. When SetupDiag has finished downloading, open the folder where you downloaded the file. By default, this folder is the **Downloads** folder, which is displayed in File Explorer under **Quick access** in the left navigation pane. 1. When SetupDiag finishes downloading, open the folder where you downloaded the file. By default, this folder is the **Downloads** folder, which is displayed in File Explorer under **Quick access** in the left navigation pane.
1. Double-click the **SetupDiag** file to run it. Select **Yes** if you're asked to approve running the program. 1. Double-click the **SetupDiag** file to run it. Select **Yes** if you're asked to approve running the program.
Double-clicking the file to run it will automatically close the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing **SetupDiag** at the command prompt instead of double-clicking it. You'll need to change directories to the location of SetupDiag to run it this way. Double-clicking the file to run it automatically closes the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing **SetupDiag** at the command prompt instead of double-clicking it. You'll need to change directories to the location of SetupDiag to run it this way.
1. A command window will open while SetupDiag diagnoses your computer. Wait for this process to finish. 1. A command window will open while SetupDiag diagnoses your computer. Wait for this process to finish.
@ -673,4 +673,4 @@ Refer to "https://learn.microsoft.com/windows/desktop/Debug/system-error-codes"
## Related articles ## Related articles
- [Resolve Windows upgrade errors: Technical information for IT Pros](./resolve-windows-10-upgrade-errors.md). - [Resolve Windows upgrade errors: Technical information for IT Pros](./resolve-windows-upgrade-errors.md).

66
windows/deployment/upgrade/submit-errors.md
View File

@ -1,57 +1,57 @@
--- ---
title: Submit Windows 10 upgrade errors using Feedback Hub title: Submit Windows upgrade errors using Feedback Hub
manager: aaroncz manager: aaroncz
ms.author: frankroj ms.author: frankroj
description: Download the Feedback Hub app, and then submit Windows 10 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.prod: windows-client ms.prod: windows-client
author: frankroj author: frankroj
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article ms.topic: article
ms.technology: itpro-deploy ms.technology: itpro-deploy
ms.date: 10/28/2022 ms.date: 01/12/2024
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
--- ---
# Submit Windows 10 upgrade errors using Feedback Hub # Submit Windows upgrade errors using Feedback Hub
**Applies to** > [!NOTE]
- Windows 10 >
> This article is a 100 level article (basic).
>
> See [Resolve Windows upgrade errors](resolve-windows-upgrade-errors.md) for a full list of articles in this section.
>[!NOTE] This article describes how to submit problems with a Windows upgrade to Microsoft using the Windows Feedback Hub.
>This is a 100 level topic (basic).<br>
>See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
## In this topic
This topic describes how to submit problems with a Windows 10 upgrade to Microsoft using the Windows 10 Feedback Hub.
## About the Feedback Hub ## About the Feedback Hub
The Feedback Hub app lets you tell Microsoft about any problems you run in to while using Windows 10 and send suggestions to help us improve your Windows experience. Previously, you could only use the Feedback Hub if you were in the Windows Insider Program. Now anyone can use this tool. You can download the Feedback Hub app from the Microsoft Store [here](https://www.microsoft.com/store/p/feedback-hub/9nblggh4r32n?SilentAuth=1&wa=wsignin1.0). The Feedback Hub app lets you tell Microsoft about any problems you run in to while using Windows and send suggestions to help us improve your Windows experience. Previously, you could only use the Feedback Hub if you were in the Windows Insider Program. Now anyone can use this tool. You can download the Feedback Hub app from the [Microsoft Store](https://www.microsoft.com/store/p/feedback-hub/9nblggh4r32n?SilentAuth=1&wa=wsignin1.0).
The Feedback Hub requires Windows 10. If you're having problems upgrading from an older version of Windows to Windows 10, you can use the Feedback Hub to submit this information. However, you must collect the log files from the legacy operating system and then attach these files to your feedback using a device that is running Windows 10. If you're upgrading to Windows 10 from a previous version of Windows 10, the Feedback Hub will collect log files automatically. The Feedback Hub requires a currently supported version of Windows. If you're having problems upgrading from an older version of Windows to currently supported versions of Windows, you can use the Feedback Hub to submit this information. However, for operating systems prior to Windows 10 that don't support the Feedback Hub, the log files must be collected and then attached to the feedback using a device that is running a currently supported version of Windows. If you're upgrading to a currently supported version of Windows from a previous version that's Windows 10 or newer, the Feedback Hub collects log files automatically.
## Submit feedback ## Submit feedback
To submit feedback about a failed Windows 10 upgrade, select the following link: [Feedback Hub](feedback-hub://?referrer=resolveUpgradeErrorsPage&tabid=2&contextid=81&newFeedback=true&feedbackType=2&topic=submit-errors.md) To submit feedback about a failed Windows upgrade, select the following link: [Feedback Hub](feedback-hub://?referrer=resolveUpgradeErrorsPage&tabid=2&contextid=81&newFeedback=true&feedbackType=2&topic=submit-errors.md)
The Feedback Hub will open. The Feedback Hub opens:
- Under **Tell us about it**, and then under **Summarize your issue**, type **Upgrade failing**. - Under **Tell us about it**, and then under **Summarize your issue**, type **Upgrade failing**.
- Under **Give us more detail**, provide additional information about the failed upgrade, such as: - Under **Give us more detail**, provide additional information about the failed upgrade, such as:
- When did the failure occur? - When did the failure occur?
- Were there any reboots? - Were there any reboots?
- How many times did the system reboot? - How many times did the system reboot?
- How did the upgrade fail? - How did the upgrade fail?
- Were any error codes visible? - Were any error codes visible?
- Did the computer fail to a blue screen? - Did the computer fail to a blue screen?
- Did the computer automatically rollback or did it hang, requiring you to power cycle it before it rolled back? - Did the computer automatically rollback or did it hang, requiring you to power cycle it before it rolled back?
- Additional details - Additional details
- What type of security software is installed? - What type of security software is installed?
- Is the computer up to date with latest drivers and firmware? - Is the computer up to date with latest drivers and firmware?
- Are there any external devices connected? - Are there any external devices connected?
- If you used the link above, the category and subcategory will be automatically selected. If it isn't selected, choose **Install and Update** and **Windows Installation**. - If the link was used, the category and subcategory are automatically selected. If it isn't selected, choose **Install and Update** and **Windows Installation**.
You can attach a screenshot or file if desired. This is optional, but can be helpful when diagnosing your upgrade issue. The location of these files is described here: [Windows Setup log files and event logs](/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs). You can attach a screenshot or file if desired. Attachments are optional, but can be helpful when diagnosing your upgrade issue. The location of these files is described here: [Windows Setup log files and event logs](/windows-hardware/manufacture/desktop/windows-setup-log-files-and-event-logs).
Select **Submit** to send your feedback. Select **Submit** to send your feedback.
@ -59,14 +59,12 @@ See the following example:
![feedback example.](../images/feedback.png) ![feedback example.](../images/feedback.png)
After you select Submit, that's all you need to do. Microsoft will receive your feedback and begin analyzing the issue. You can check on your feedback periodically to see what solutions have been provided. After you select Submit, that's all that needs to be done. Microsoft receives your feedback and begins analyzing the issue. The submitted feedback can be checked on periodically to see what solutions are provided.
## Link to your feedback ## Link to the feedback
After your feedback is submitted, you can email or post links to it by opening the Feedback Hub, clicking My feedback at the top, clicking the feedback item you submitted, clicking **Share**, then copying the short link that is displayed. After the feedback is submitted, you can email or post links to it by opening the Feedback Hub, clicking My feedback at the top, clicking the feedback item you submitted, clicking **Share**, then copying the short link that is displayed.
![share.](../images/share.jpg) ![share.](../images/share.jpg)
## Related articles ## Related articles
[Windows 10 release information](https://technet.microsoft.com/windows/release-info.aspx)

52
windows/deployment/upgrade/windows-error-reporting.md
View File

@ -8,25 +8,27 @@ author: frankroj
ms.localizationpriority: medium ms.localizationpriority: medium
ms.topic: article ms.topic: article
ms.technology: itpro-deploy ms.technology: itpro-deploy
ms.date: 10/28/2022 ms.date: 01/12/2024
appliesto:
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
- ✅ <a href="https://learn.microsoft.com/windows/release-health/supported-versions-windows-client" target="_blank">Windows 10</a>
--- ---
# Windows Error Reporting # Windows Error Reporting
**Applies to**
- Windows 10
> [!NOTE] > [!NOTE]
> This is a 300 level topic (moderately advanced). >
> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article. > This article is a 300 level article (moderately advanced).
>
> 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**. You can use Event Viewer to review this event, or you can use Windows PowerShell. 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**. You can use Event Viewer to review this event, or you can use Windows PowerShell.
To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt: To use Windows PowerShell, type the following commands from an elevated Windows PowerShell prompt:
> [!IMPORTANT] > [!IMPORTANT]
> The following source will be available only if you have updated from a previous version of Windows 10 to a new version. If you installed the current version and have not updated, the source named **WinSetupDiag02** will be unavailable. >
> The following Event logs are only available if Windows was updated from a previous version of Windows to a new version of Windows.
```powershell ```powershell
$events = Get-WinEvent -FilterHashtable @{LogName="Application";ID="1001";Data="WinSetupDiag02"} $events = Get-WinEvent -FilterHashtable @{LogName="Application";ID="1001";Data="WinSetupDiag02"}
@ -35,36 +37,34 @@ $event.Event.EventData.Data
``` ```
To use Event Viewer: To use Event Viewer:
1. Open Event Viewer and navigate to **Windows Logs\Application**. 1. Open Event Viewer and navigate to **Windows Logs\Application**.
2. Select **Find**, and then search for **winsetupdiag02**. 1. Select **Find**, and then search for **winsetupdiag02**.
3. Double-click the event that is highlighted. 1. Double-click the event that is highlighted.
> [!NOTE] > [!NOTE]
>
> For legacy operating systems, the Event Name was WinSetupDiag01. > For legacy operating systems, the Event Name was WinSetupDiag01.
Ten parameters are listed in the event: Ten parameters are listed in the event:
| Parameters | | Parameters |
| ------------- | | ------------- |
|P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) | | P1: The Setup Scenario (1=Media,5=WindowsUpdate,7=Media Creation Tool) |
|P2: Setup Mode (x=default,1=Downlevel,5=Rollback) | | P2: Setup Mode (x=default,1=Downlevel,5=Rollback) |
|P3: New OS Architecture (x=default,0=X86,9=AMD64) | | P3: New OS Architecture (x=default,0=X86,9=AMD64) |
|P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) | | P4: Install Result (x=default,0=Success,1=Failure,2=Cancel,3=Blocked) |
|**P5: Result Error Code** (Ex: 0xc1900101) | | **P5: Result Error Code** (Ex: 0xc1900101) |
|**P6: Extend Error Code** (Ex: 0x20017) | | **P6: Extend Error Code** (Ex: 0x20017) |
|P7: Source OS build (Ex: 9600) | | P7: Source OS build (Ex: 9600) |
|P8: Source OS branch (not typically available) | | P8: Source OS branch (not typically available) |
|P9: New OS build (Ex: 16299} | | P9: New OS build (Ex: 16299) |
|P10: New OS branch (Ex: rs3_release} | | P10: New OS branch (Ex: rs3_release) |
The event will also contain links to log files that can be used to perform a detailed diagnosis of the error. An example of this event from a successful upgrade is shown below. 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:
:::image type="content" alt-text="Windows Error Reporting." source="../images/event.png" lightbox="../images/event.png"::: :::image type="content" alt-text="Windows Error Reporting." source="../images/event.png" lightbox="../images/event.png":::
## Related articles ## Related articles
[Windows 10 FAQ for IT professionals](../planning/windows-10-enterprise-faq-itpro.yml) - [Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors).
[Windows 10 Enterprise system requirements](https://technet.microsoft.com/windows/dn798752.aspx)
[Windows 10 Specifications](https://www.microsoft.com/windows/Windows-10-specifications)
[Windows 10 IT pro forums](https://social.technet.microsoft.com/Forums/en-US/home?category=Windows10ITPro)
[Fix Windows Update errors by using the DISM or System Update Readiness tool](/troubleshoot/windows-server/deployment/fix-windows-update-errors)

2
windows/deployment/windows-10-poc-mdt.md
View File

@ -659,7 +659,7 @@ Deployment logs are available on the client computer in the following locations:
You can review WDS events in Event Viewer at: **Applications and Services Logs > Microsoft > Windows > Deployment-Services-Diagnostics**. By default, only the **Admin** and **Operational** logs are enabled. To enable other logs, right-click the log and then select **Enable Log**. You can review WDS events in Event Viewer at: **Applications and Services Logs > Microsoft > Windows > Deployment-Services-Diagnostics**. By default, only the **Admin** and **Operational** logs are enabled. To enable other logs, right-click the log and then select **Enable Log**.
Also see [Resolve Windows 10 upgrade errors](upgrade/resolve-windows-10-upgrade-errors.md) for detailed troubleshooting information. Also see [Resolve Windows upgrade errors](upgrade/resolve-windows-upgrade-errors.md) for detailed troubleshooting information.
## Related articles ## Related articles