mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Merged PR 13451: SetupDiag 1.4 update
Update for new release
This commit is contained in:
Greg Lindsay
parent
24beb6c91a
commit
00f038facb
@ -7,7 +7,7 @@ ms.localizationpriority: medium
|
||||
ms.prod: w10
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
ms.date: 12/07/2018
|
||||
ms.date: 12/18/2018
|
||||
author: greg-lindsay
|
||||
---
|
||||
|
||||
@ -23,6 +23,10 @@ This topic provides an overview of new solutions and online content related to d
|
||||
- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](https://technet.microsoft.com/itpro/windows/whats-new/index).
|
||||
- For a detailed list of changes to Windows 10 ITPro TechNet library content, see [Online content change history](#online-content-change-history).
|
||||
|
||||
## Recent additions to this page
|
||||
|
||||
[SetupDiag](#setupdiag) 1.4 is released.
|
||||
|
||||
## The Modern Desktop Deployment Center
|
||||
|
||||
The [Modern Desktop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home) has launched with tons of content to help you with large-scale deployment of Windows 10 and Office 365 ProPlus.
|
||||
@ -56,6 +60,12 @@ Windows Autopilot streamlines and automates the process of setting up and config
|
||||
|
||||
Windows Autopilot joins devices to Azure Active Directory (Azure AD), optionally enrolls into MDM services, configures security policies, and sets a custom out-of-box-experience (OOBE) for the end user. For more information, see [Overview of Windows Autopilot](windows-autopilot/windows-autopilot.md).
|
||||
|
||||
### SetupDiag
|
||||
|
||||
[SetupDiag](upgrade/setupdiag.md) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
|
||||
SetupDiag version 1.4 was released on 12/18/2018.
|
||||
|
||||
### Upgrade Readiness
|
||||
|
||||
The Upgrade Readiness tool moved from public preview to general availability on March 2, 2017.
|
||||
|
||||
@ -7,7 +7,7 @@ ms.mktglfcycl: deploy
|
||||
ms.sitesec: library
|
||||
ms.pagetype: deploy
|
||||
author: greg-lindsay
|
||||
ms.date: 08/16/2018
|
||||
ms.date: 12/18/2018
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -24,7 +24,7 @@ ms.localizationpriority: medium
|
||||
|
||||
## About SetupDiag
|
||||
|
||||
<I>Current version of SetupDiag: 1.3.1.0</I>
|
||||
<I>Current version of SetupDiag: 1.4.0.0</I>
|
||||
|
||||
SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful.
|
||||
|
||||
@ -61,11 +61,14 @@ The [Release notes](#release-notes) section at the bottom of this topic has info
|
||||
| --- | --- |
|
||||
| /? | <ul><li>Displays interactive help</ul> |
|
||||
| /Output:\<path to results file\> | <ul><li>This optional parameter enables you to specify the output file for results. This is where you will find what SetupDiag was able to determine. Only text format output is supported. UNC paths will work, provided the context under which SetupDiag runs has access to the UNC path. If the path has a space in it, you must enclose the entire path in double quotes (see the example section below). <li>Default: If not specified, SetupDiag will create the file **SetupDiagResults.log** in the same directory where SetupDiag.exe is run.</ul> |
|
||||
| /Mode:\<Offline \| Online\> | <ul><li>This optional parameter allows you to specify the mode in which SetupDiag will operate: Offline or Online.<li>Offline: tells SetupDiag to run against a set of log files already captured from a failed system. In this mode you can run anywhere you have access to the log files. This mode does not require SetupDiag to be run on the computer that failed to update. When you specify offline mode, you must also specify the /LogsPath: parameter.<li>Online: tells SetupDiag that it is being run on the computer that failed to update. SetupDiag will attempt find log files and resources in standard Windows locations, such as the **%SystemDrive%\$Windows.~bt** directory for setup log files.<li>Log file search paths are configurable in the SetupDiag.exe.config file, under the SearchPath key. Search paths are comma separated. Note: A large number of search paths will extend the time required for SetupDiag to return results.<li>Default: If not specified, SetupDiag will run in Online mode.</ul> |
|
||||
| /LogsPath:\<Path to logs\> | <ul><li>This optional parameter is required only when **/Mode:Offline** is specified. This tells SetupDiag.exe where to find the log files. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories. This parameter should be omitted when the **/Mode:Online** is specified.</ul> |
|
||||
| /LogsPath:\<Path to logs\> | <ul><li>This optional parameter tells SetupDiag.exe where to find the log files for an offline analysis. These log files can be in a flat folder format, or containing multiple subdirectories. SetupDiag will recursively search all child directories.</ul> |
|
||||
| /ZipLogs:\<True \| False\> | <ul><li>This optional parameter tells SetupDiag.exe to create a zip file containing the results and all the log files it parsed. The zip file is created in the same directory where SetupDiag.exe is run.<li>Default: If not specified, a value of 'true' is used.</ul> |
|
||||
| /Verbose | <ul><li>This optional parameter will output much more data to the log file produced by SetupDiag.exe. By default SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce a log file with debugging details, which can be useful when reporting a problem with SetupDiag.</ul> |
|
||||
| /Verbose | <ul><li>This optional parameter will output much more data to a log file. By default, SetupDiag will only produce a log file entry for serious errors. Using **/Verbose** will cause SetupDiag to always produce an additional log file with debugging details. These details can be useful when reporting a problem with SetupDiag.</ul> |
|
||||
| /Format:\<xml \| json\> | <ul><li>This optional parameter can be used to output log files in xml or JSON format. If this parameter is not specified, text format is used by default.</ul> |
|
||||
| /NoTel | <ul><li>This optional parameter tells SetupDiag.exe not to send diagnostic telemetry to Microsoft.</ul> |
|
||||
|
||||
Note: The **/Mode** parameter is deprecated in version 1.4.0.0 of SetupDiag.
|
||||
- In previous versions, this command was used with the LogsPath parameter to specify that SetupDiag should run in an offline manner to analyze a set of log files that were captured from a different computer. In version 1.4.0.0 when you specify /LogsPath then SetupDiag will automatically run in offline mode, therefore the /Mode parameter is not needed.
|
||||
|
||||
### Examples:
|
||||
|
||||
@ -75,10 +78,10 @@ In the following example, SetupDiag is run with default parameters (online mode,
|
||||
SetupDiag.exe
|
||||
```
|
||||
|
||||
In the following example, SetupDiag is specified to run in Online mode (this is the default). It will know where to look for logs on the current (failing) system, so there is no need to gather logs ahead of time. A custom location for results is specified.
|
||||
In the following example, SetupDiag is run in online mode (this is the default). It will know where to look for logs on the current (failing) system, so there is no need to gather logs ahead of time. A custom location for results is specified.
|
||||
|
||||
```
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Online
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Results.log
|
||||
```
|
||||
|
||||
The following example uses the /Output parameter to save results to a path name that contains a space:
|
||||
@ -90,7 +93,7 @@ SetupDiag /Output:"C:\Tools\SetupDiag\SetupDiag Results\Results.log"
|
||||
The following example specifies that SetupDiag is to run in offline mode, and to process the log files found in **D:\Temp\Logs\LogSet1**.
|
||||
|
||||
```
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Offline /LogsPath:D:\Temp\Logs\LogSet1
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:D:\Temp\Logs\LogSet1
|
||||
```
|
||||
|
||||
## Log files
|
||||
@ -111,7 +114,7 @@ When Microsoft Windows encounters a condition that compromises safe system opera
|
||||
If crash dumps [are enabled](https://docs.microsoft.com/windows-hardware/drivers/debugger/enabling-a-kernel-mode-dump-file) on the system, a crash dump file is created. If the bug check occurs during an upgrade, Windows Setup will extract a minidump (setupmem.dmp) file. SetupDiag can also debug these setup related minidumps.
|
||||
|
||||
To debug a setup related bug check, you must:
|
||||
- Specify the **/Mode:Offline** and **/LogsPath** parameters. You cannot debug memory dumps in online mode.
|
||||
- Specify the **/LogsPath** parameter. You cannot debug memory dumps in online mode.
|
||||
- Gather the setup memory dump file (setupmem.dmp) from the failing system.
|
||||
- Setupmem.dmp will be created in either **%SystemDrive%\$Windows.~bt\Sources\Rollback**, or in **%WinDir%\Panther\NewOS\Rollback** depending on when the bug check occurs.
|
||||
- Install the [Windows Debugging Tools](https://docs.microsoft.com/windows-hardware/drivers/debugger/debugger-download-tools) on the computer that runs SetupDiag.
|
||||
@ -119,7 +122,7 @@ To debug a setup related bug check, you must:
|
||||
In the following example, the **setupmem.dmp** file is copied to the **D:\Dump** directory and the Windows Debugging Tools are installed prior to running SetupDiag:
|
||||
|
||||
```
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /Mode:Offline /LogsPath:D:\Dump
|
||||
SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /LogsPath:D:\Dump
|
||||
```
|
||||
|
||||
## Known issues
|
||||
@ -135,10 +138,10 @@ The following is an example where SetupDiag is run in offline mode. In this exam
|
||||
The output also provides an error code 0xC1900208 - 0x4000C which corresponds to a compatibility issue as documented in the [Upgrade error codes](upgrade-error-codes.md#result-codes) and [Resolution procedures](resolution-procedures.md#modern-setup-errors) topics in this article.
|
||||
|
||||
```
|
||||
C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /Mode:Offline /LogsPath:C:\Temp\BobMacNeill
|
||||
C:\SetupDiag>SetupDiag.exe /Output:C:\SetupDiag\Results.log /LogsPath:C:\Temp\BobMacNeill
|
||||
|
||||
SetupDiag v1.01
|
||||
Copyright (c) Microsoft Corporation. All rights reserved
|
||||
SetupDiag v1.4.0.0
|
||||
Copyright (c) Microsoft Corporation. All rights reserved.
|
||||
|
||||
Searching for setup logs, this can take a minute or more depending on the number and size of the logs...please wait.
|
||||
Found 4 setupact.logs.
|
||||
@ -365,16 +368,42 @@ Each rule name and its associated unique rule identifier are listed with a descr
|
||||
40. UpdateAgentExpanderFailure – 66E496B3-7D19-47FA-B19B-4040B9FD17E2
|
||||
- Matches DPX expander failures in the down-level phase of update from WU. Will output the package name, function, expression and error code.
|
||||
41. FindFatalPluginFailure – E48E3F1C-26F6-4AFB-859B-BF637DA49636
|
||||
- Matches any plug in failure that setupplatform decides is fatal to setup. Will output the plugin name, operation and error code.
|
||||
- Matches any plug-in failure that setupplatform decides is fatal to setup. Will output the plugin name, operation and error code.
|
||||
42. AdvancedInstallerFailed - 77D36C96-32BE-42A2-BB9C-AAFFE64FCADC
|
||||
- Indicates critical failure in the AdvancedInstaller while running an installer package, includes the .exe being called, the phase, mode, component and error codes.
|
||||
43. MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
|
||||
- Indicates a critical failure in a migration plugin that causes setup to abort the migration. Will provide the setup operation, plug in name, plug in action and error code.
|
||||
- Indicates a critical failure in a migration plugin that causes setup to abort the migration. Will provide the setup operation, plug-in name, plug-in action and error code.
|
||||
44. DISMAddPackageFailed - 6196FF5B-E69E-4117-9EC6-9C1EAB20A3B9
|
||||
- Indicates a critical failure during a DISM add package operation. Will specify the Package Name, DISM error and add package error code.
|
||||
45. PlugInComplianceBlock - D912150B-1302-4860-91B5-527907D08960
|
||||
- Detects all compat blocks from Server compliance plug-ins. Outputs the block information and remediation.
|
||||
46. AdvancedInstallerGenericFailure - 4019550D-4CAA-45B0-A222-349C48E86F71
|
||||
- Triggers on advanced installer failures in a generic sense, outputting the application called, phase, mode, component and error code.
|
||||
47. 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
|
||||
48. OptionalComponentFailedToGetOCsFromPackage - D012E2A2-99D8-4A8C-BBB2-088B92083D78
|
||||
- Indicates the optional component (OC) migration operation failed to enumerate optional components from an OC Package. Outputs the package name and error code.
|
||||
49. OptionalComponentOpenPackageFailed - 22952520-EC89-4FBD-94E0-B67DF88347F6
|
||||
- Indicates the optional component migration operation failed to open an optional component Package. Outputs the package name and error code.
|
||||
50. OptionalComponentInitCBSSessionFailed - 63340812-9252-45F3-A0F2-B2A4CA5E9317
|
||||
- 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.
|
||||
51. DISMproviderFailure - D76EF86F-B3F8-433F-9EBF-B4411F8141F4
|
||||
- Triggers when a DISM provider (plug-in) fails in a critical operation. Outputs the file (plug-in name), function called + error code, and error message from the provider.
|
||||
52. SysPrepLaunchModuleFailure - 7905655C-F295-45F7-8873-81D6F9149BFD
|
||||
- Indicates a sysPrep plug-in has failed in a critical operation. Indicates the plug-in name, operation name and error code.
|
||||
53. UserProvidedDriverInjectionFailure - 2247C48A-7EE3-4037-AFAB-95B92DE1D980
|
||||
- A driver provided to setup (via command line input) has failed in some way. Outputs the driver install function and error code.
|
||||
|
||||
## Release notes
|
||||
|
||||
12/18/2018 - SetupDiag v1.4.0.0 is released with 53 rules, as a standalone tool available from the Download Center.
|
||||
- This release includes major improvements in rule processing performance: ~3x faster rule processing performance!
|
||||
- The FindDownlevelFailure rule is up to 10x faster.
|
||||
- New rules have been added to analyze failures upgrading to Windows 10 version 1809.
|
||||
- A new help link is available for resolving servicing stack failures on the down-level OS when the rule match indicates this type of failure.
|
||||
- Removed the need to specify /Mode parameter. Now if you specify /LogsPath, it automatically assumes offline mode.
|
||||
- Some functional and output improvements were made for several rules.
|
||||
|
||||
07/16/2018 - SetupDiag v1.3.1 is released with 44 rules, as a standalone tool available from the Download Center.
|
||||
- This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user