PowerShell Logo Small

Invoke-TroubleshootingPack



This is the built-in help made by Microsoft for the command 'Invoke-TroubleshootingPack', in PowerShell version 5 - as retrieved from Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.

For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.

SYNOPSIS

Runs a troubleshooting pack.

SYNTAX


Invoke-TroubleshootingPack [-Pack] <DiagPack> [-AnswerFile <String>] [-Result <String>] [-Unattended] [<CommonParameters>]



Search powershellhelp.space

DESCRIPTION


The Invoke-TroubleshootingPack cmdlet runs a troubleshooting pack in either interactive or unattended mode. A troubleshooting pack determines the root causes of issues,
resolves the issues, and verifies that the issues were resolved. The cmdlet can save reports that detail issues and resolutions.


In interactive mode, you can select the resolutions to use and provide input to interactions with the troubleshooting pack. In unattended mode, the troubleshooting pack
determines which resolutions to use at run time. While in unattended mode, if the troubleshooting pack requires input, you need to provide answers or specify an answer file.
To create an answer file, use the Get-TroubleshootingPack cmdlet.


You can save the result report and the debug report, along with XSL and any linked files. Both reports contain the issues and resolutions. The debug report contains
additional information.



<

RELATED LINKS

Online Version: http://go.microsoft.com/fwlink/p/?linkid=287585
Get-TroubleshootingPack

REMARKS

<

Examples


Example 1: Run a troubleshooting pack

PS C:\> Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio" | Invoke-TroubleshootingPack



This example runs the Audio pack in interactive mode. This example does not save reports.

The command uses the Get-TroubleshootingPack cmdlet to get a DiagPack object and pipes it to the Invoke-TroubleshootingPack cmdlet.




Example 2: Save troubleshooting reports

PS C:\> $Audio = Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio"
PS C:\> Invoke-TroubleshootingPack -Pack $Audio -Result "C:\DiagResult"



This example runs the Areo pack in interactive mode and saves the results to a folder.

The first command uses the Get-TroubleshootingPack cmdlet to get a DiagPack object and stores it in the $Audio variable.

The second command invokes the troubleshooting pack stored in $Audio. The pack saves reports in the specified folder.




Example 3: Run a troubleshooting pack in unattended mode

PS C:\> $Audio = Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio"
PS C:\> Invoke-TroubleshootingPack -Pack $Audio -AnswerFile "AudioAnswerFile.xml" -Unattended



This example runs the Audio pack in unattended mode with a specified answer file.

The first command uses the Get-TroubleshootingPack cmdlet to get a DiagPack object and stores it in the $Audio variable.

The second command invokes the troubleshooting pack stored in $Audio in unattended mode. The command specifies an answer file, previously created by using the
Get-TroubleshootingPack cmdlet.