Skip to content

Commit 99d343e

Browse files
authored
Update note on Start-Transcript behavior
editorial
1 parent a4f13a9 commit 99d343e

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

reference/5.1/Microsoft.PowerShell.Host/Start-Transcript.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -266,12 +266,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
266266
-WarningAction, and -WarningVariable. For more information, see
267267
[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
268268

269-
> [!NOTE]
270-
> The `Write-Information` logic is reversed in `Start-Transcript`. This means if the
271-
> **InformationPreference** is set to `Continue`, Information messages will be written to the
272-
> console, but not to the transcript file. If the **InformationPreference** is set to
273-
> `SilentlyContinue`, Information messages will not be written to the console, but will be written
274-
> to the transcript file. This is fixed in PowerShell 6.
275269

276270
## INPUTS
277271

@@ -292,6 +286,13 @@ To stop a transcript, use the `Stop-Transcript` cmdlet.
292286
To record an entire session, add the `Start-Transcript` command to your profile. For more
293287
information, see [about_Profiles](../Microsoft.PowerShell.Core/About/about_Profiles.md).
294288

289+
> [!NOTE]
290+
> When you use `Start-Transcript`, the default value of `$InformationPreference`** is changed to
291+
> `Continue`. Output from `Write-Information` is written to the console, but not to the transcript
292+
> file. If the **InformationPreference** is set to `SilentlyContinue`, Information messages aren't
293+
> written to the console, but are written to the transcript file. This is fixed in PowerShell 6 and
294+
> higher.
295+
295296
## RELATED LINKS
296297

297298
[Stop-Transcript](Stop-Transcript.md)

0 commit comments

Comments
 (0)