From 189d86fd69236c15d8c6a562d422070ff4190868 Mon Sep 17 00:00:00 2001 From: Thomas Lee Date: Tue, 18 Jul 2017 21:37:11 +0100 Subject: [PATCH] Minor updated to Get-Troubleshootingpack 1. Noted full name of the object returned from the cmdlet in the description. 2. Added an additional example to show ALL the root causes 3. I kept the new example next to a simar one - thus renumbered the later examples. --- .../get-troubleshootingpack.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docset/windows/troubleshootingpack/get-troubleshootingpack.md b/docset/windows/troubleshootingpack/get-troubleshootingpack.md index e8942be8e0..ba088c4047 100644 --- a/docset/windows/troubleshootingpack/get-troubleshootingpack.md +++ b/docset/windows/troubleshootingpack/get-troubleshootingpack.md @@ -29,7 +29,7 @@ Get-TroubleshootingPack [-Path] [-AnswerFile ] [ $Audio = Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio" +PS C:\> $Audio.Rootcauses +``` + +Tgus example dislays all the root casues this troubleshooting pack investigates. + + +### Example 4: Get a resolution for a root cause ``` PS C:\> $Audio = Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio" PS C:\> $Audio.RootCauses[2].Resolutions[0] @@ -70,7 +79,7 @@ The second command displays a resolution for a root cause. The $Audio object contains an array of root causes, each of which contains an array of resolutions. This command uses conventional array notation to access the first resolution for the third root cause. -### Example 4: Generate an answer file +### Example 5: Generate an answer file ``` PS C:\> Get-TroubleshootingPack -Path "C:\Windows\Diagnostics\System\Audio" -AnswerFile "AudioAnswerFile.xml" ```