Verbose and debug output in PowerShell - Step-by-Step Execution

Concept Flow - Verbose and debug output

Start Script

↓

Set VerbosePreference

↓

Set DebugPreference

↓

Run Commands

↓

If Verbose enabled

→Show Verbose Messages

↓

If Debug enabled

→Show Debug Messages

↓

End Script

The script sets preferences for verbose and debug output, then runs commands that may produce messages shown only if those preferences are enabled.

Execution Sample

PowerShell

Write-Verbose "Starting script"
Write-Debug "Debug info"
Write-Output "Normal output"

This script writes verbose and debug messages plus normal output; verbose and debug messages show only if enabled.

Execution Table

Step	Command	VerbosePreference	DebugPreference	Verbose Output	Debug Output	Normal Output
1	Write-Verbose "Starting script"	Continue	Continue	Starting script
2	Write-Debug "Debug info"	Continue	Continue		Debug info
3	Write-Output "Normal output"	Continue	Continue			Normal output
4	Write-Verbose "Starting script"	SilentlyContinue	SilentlyContinue
5	Write-Debug "Debug info"	SilentlyContinue	SilentlyContinue
6	Write-Output "Normal output"	SilentlyContinue	SilentlyContinue			Normal output
7	End of script	SilentlyContinue	SilentlyContinue

💡 Script ends after all commands run; verbose and debug outputs depend on preference settings.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
VerbosePreference	Continue	Continue	Continue	Continue	SilentlyContinue	SilentlyContinue	SilentlyContinue	SilentlyContinue
DebugPreference	Continue	Continue	Continue	Continue	SilentlyContinue	SilentlyContinue	SilentlyContinue	SilentlyContinue
Verbose Output		Starting script	Starting script	Starting script
Debug Output			Debug info	Debug info
Normal Output				Normal output	Normal output	Normal output	Normal output	Normal output

Key Moments - 3 Insights

Why do verbose messages sometimes not show even if Write-Verbose is used?

Verbose messages only show if VerbosePreference is set to 'Continue' or higher. See execution_table rows 1 and 4 where preference changes affect output.

What controls whether debug messages appear?

Debug messages appear only if DebugPreference is set to 'Continue'. In the table, rows 2 and 5 show debug output present or absent based on this.

Does Write-Output depend on Verbose or Debug preferences?

No, Write-Output always shows normal output regardless of VerbosePreference or DebugPreference, as seen in rows 3 and 6.

Visual Quiz - 3 Questions

Look at the execution_table row 2. What is the Debug Output at this step?

A No output

B Starting script

C Debug info

D Normal output

💡 Hint

Check the 'Debug Output' column in row 2 of the execution_table.

At which step does the Verbose Output stop showing messages?

A Step 3

B Step 4

C Step 1

D Step 6

💡 Hint

Look at the VerbosePreference change and corresponding Verbose Output in rows 3 and 4.

If DebugPreference is set to 'SilentlyContinue', what happens to debug messages?

A They do not show

B They show normally

C They show only once

D They appear as errors

💡 Hint

Refer to Debug Output in rows 5 and 6 where DebugPreference is 'SilentlyContinue'.

Concept Snapshot

Write-Verbose and Write-Debug send messages shown only if VerbosePreference or DebugPreference is 'Continue'.
Set preferences with $VerbosePreference and $DebugPreference.
Write-Output always shows output.
Use verbose/debug to help see script details without cluttering normal output.

Full Transcript

This lesson shows how PowerShell scripts can produce extra messages for debugging or verbose info. The script sets preferences controlling if these messages appear. Write-Verbose messages show only if VerbosePreference is 'Continue'. Write-Debug messages show only if DebugPreference is 'Continue'. Normal output from Write-Output always shows. The execution table traces commands step-by-step, showing when messages appear or not depending on preferences. Variables track preference changes and outputs. Key moments clarify why messages may not appear and how preferences control them. The quiz tests understanding of when verbose and debug messages show. This helps beginners see how to add helpful script messages that can be turned on or off easily.