Unable to capture ALL session output into a transcript - by xkrissx

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


37
0
Sign in
to vote
ID 315875 Comments
Status Closed Workarounds
Type Bug Repros 10
Opened 12/6/2007 7:01:16 AM
Access Restriction Public

Description

This issue was first reported by me in the windows.powershell newsgroup and 'Jeffrey P. Snover[MSFT]' suggested that I submit a bug report for it.

Start-transcript is supposed to log ALL output from the powershell session. However, if you call an executable from within your powershell session, the output will be visible in the window but won't be recorded in the transcript.

Problem has been found in PowerShell 1.0. Additional feedback by another user also confirms the presence of this problem in CTP 2.0.
Sign in to post a comment.
Posted by Charles Keisler on 8/27/2015 at 8:12 PM
Easy workaround,

Not sure if it's version dependent but I discovered it on 4.0

append " | Write-host" to the command
e.g.
.\ipconfig | Write-host
Posted by Microsoft on 8/25/2012 at 5:21 PM
We've made some improvements in PowerShell 3.0 in allowing the various streams to be redirected (pipeline, error, warning, verbose, debug, etc.). However, we've decided not to invest in being able to log the output from native cmdline tools due to the high cost and technical complexities involved. We'll continue to work on improving cmdlet coverage for native cmdlet tools with the highest usage.
Posted by Microsoft Connect on 1/29/2010 at 2:08 PM
Your bug has not been fixed in PowerShell 2.0. However we have kept the bug active for next version
Posted by Microsoft Connect on 1/29/2010 at 2:04 PM
Your bug has not been fixed in PowerShell 2.0. However we have kept the bug active for next version
Posted by Microsoft Connect on 1/29/2010 at 2:00 PM
Your bug has not been fixed in PowerShell 2.0. However we have kept the bug active for next version
Posted by Microsoft Connect on 1/29/2010 at 1:55 PM
Your bug has not been fixed in PowerShell 2.0. However we have kept the bug active for next version
Posted by fatcat1111 on 10/8/2009 at 2:47 PM
Or at least add a switch, allowing all output to be captured to the transcript log. That would make this cmdlet truly useful.