<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PowerCli/Start-transcript bug in VMware PowerCLI Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2957423#M110993</link>
    <description>&lt;P&gt;Just to add the output from console around the point where Start-Transcript seems to fail:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator&amp;gt; $DebugPreference = "Continue"
PS C:\Users\Administrator&amp;gt; $VerbosePreference = "Continue"
PS C:\Users\Administrator&amp;gt; Start-Transcript
Transcript started, output file is C:\Users\Administrator\Documents\PowerShell_transcript.ARK.FGUYhsln.20230302123120.txt
PS C:\Users\Administrator&amp;gt; [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\Administrator&amp;gt; $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\Administrator&amp;gt; Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
WARNING: Please consider joining the VMware Customer Experience Improvement Program, so you can help us make PowerCLI a better product. You can join using the following command:

Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true

VMware's Customer Experience Improvement Program ("CEIP") provides VMware with information that enables VMware to improve its products and services, to fix problems, and to advise you on how best to deploy and use our products.  As part of the CEIP, VMware collects
technical information about your organizationâ€™s use of VMware products and services on a regular basis in association with your organizationâ€™s VMware license key(s).  This information does not personally identify any individual.

For more details: type "help about_ceip" to see the related help article.

To disable this warning and set your preference use the following command and restart PowerShell:
Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true or $false.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Exporting variable 'message'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'message'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\ICSharpCode.SharpZipLib.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\ICSharpCode.SharpZipLib.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\Newtonsoft.Json.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\Newtonsoft.Json.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Ls2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Ls2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Sts.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Sts.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.WsTrust.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.WsTrust.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.Sspi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.Sspi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Http.Handlers.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Http.Handlers.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.SsoAuthentication.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.SsoAuthentication.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Commands.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Commands.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.OAuth2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.OAuth2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Wcf.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Wcf.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\JsonSubTypes.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\JsonSubTypes.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Sdk.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Sdk.OpenApi.dll'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Format.ps1xml'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.ps1'.
PS C:\Users\Administrator&amp;gt; Stop-Transcript^C
PS C:\Users\Administrator&amp;gt; ^C
PS C:\Users\Administrator&amp;gt; ^C
PS C:\Users\Administrator&amp;gt; Stop-Transcript
Stop-Transcript : An error occurred stopping transcription: The host is not currently transcribing.
At line:1 char:1
+ Stop-Transcript
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationException
    + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptCommand

PS C:\Users\Administrator&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the other transcripts "Importing function 'Get-Version'." Is the last output before transcripting fails - Running the commandlet Get-PSVersion does not seem to break anything, so whatever the next line means seems likely to be a clue.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Mar 2023 11:37:12 GMT</pubDate>
    <dc:creator>MichaelRyom</dc:creator>
    <dc:date>2023-03-02T11:37:12Z</dc:date>
    <item>
      <title>PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909663#M106701</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have an old script(from 2020, running monthly as a windows schedule task) which seems to be failing recently (less than 6 month ago). Checking the log showed an (almost) empty log file.&lt;/P&gt;&lt;P&gt;In this script I'm using the powershell command start-transcript, to catch output and errors. A lazy mans logging.&lt;/P&gt;&lt;P&gt;But it seems that with one of the recent PowerCli version, PowerCli breaks the Start-transcript command for some reason.&lt;/P&gt;&lt;P&gt;Running the below code as a schedule task (using an AD user, which is local admin)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Start-Transcript -Path "C:\temp\test.log" -Append -Force
import-module VMware.PowerCli -force
Write-host "Hallo World!"
Stop-Transcript&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Output&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;**********************
Windows PowerShell transcript start
Start time: 20220518103905
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx (Microsoft Windows NT 10.0.17763.0)
Host Application: powershell.exe -file C:\scripts\repository\Scheduled Scripts\Capcity Report\test.ps1
Process ID: 27140
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
**********************
Windows PowerShell transcript end
End time: 20220518103913
**********************&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note no "Hallo World!"&lt;/P&gt;&lt;P&gt;If I run this code instead the same way as above&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;import-module VMware.PowerCli -force
Start-Transcript -Path "C:\temp\test.log" -Append -Force
Write-host "Hallo World!"
Stop-Transcript&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Output&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;**********************
Windows PowerShell transcript start
Start time: 20220518104935
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: powershell.exe -file C:\scripts\repository\Scheduled Scripts\Capcity Report\test.ps1
Process ID: 20956
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
Hallo World!
**********************
Windows PowerShell transcript end
End time: 20220518104935
**********************&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Note "Hallo World!" is now in the output.&lt;/P&gt;&lt;P&gt;So it seems to be a bug in PowerCli, when modules are being loaded. I first noticed this issue when just running a command ( $cred = Get-VICredentialStoreItem -File $TokenFilePath ) and then did the testing with import-module, which seems to produce the same result.&lt;/P&gt;&lt;P&gt;Running this first script manually (in a powershell console) produces this result in the log file&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;**********************
Windows PowerShell transcript start
Start time: 20220518105520
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 21748
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx&amp;gt; import-module VMware.PowerCli -force
**********************
Windows PowerShell transcript end
End time: 20220518105528
**********************&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and here is the output in the console&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;PS C:\Users\xxx&amp;gt; Start-Transcript -Path "C:\temp\test.log" -Append -Force
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx&amp;gt; import-module VMware.PowerCli -force
          Welcome to VMware PowerCLI!

Log in to a vCenter Server or ESX host:              Connect-VIServer
To find out what commands are available, type:       Get-VICommand
To show searchable help for all PowerCLI commands:   Get-PowerCLIHelp
Once you've connected, display all virtual machines: Get-VM
If you need more help, visit the PowerCLI community: Get-PowerCLICommunity

       Copyright (C) VMware, Inc. All rights reserved.


PS C:\Users\xxx&amp;gt; Write-host "Hallo World!"
Hallo World!
PS C:\Users\xxx&amp;gt; Stop-Transcript
Stop-Transcript : An error occurred stopping transcription: The host is not currently
transcribing.
At line:1 char:1
+ Stop-Transcript
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationExc
   eption
    + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptC
   ommand

PS C:\Users\xxx&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which seems to agree with me on the fact that something inside PowerCli module is stopping/failing the transcript commandlet. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@8D3AC78033E090809829B1C8262B7619/emoticons/1f61e.png" alt=":disappointed_face:" title=":disappointed_face:" /&gt;&lt;/P&gt;&lt;P&gt;Can anyone reproduce this?&lt;/P&gt;&lt;P&gt;PowerCLI Version&lt;BR /&gt;----------------&lt;BR /&gt;VMware.PowerCLI 12.6.0 build 19610541&lt;BR /&gt;---------------&lt;BR /&gt;Component Versions&lt;BR /&gt;---------------&lt;BR /&gt;VMware Common PowerCLI Component 12.6 build 19600917&lt;BR /&gt;VMware Cis Core PowerCLI Component PowerCLI Component 12.6 build 19601368&lt;BR /&gt;VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 12.6 build 19601570&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 10:40:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909663#M106701</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-18T10:40:22Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909669#M106702</link>
      <description>&lt;P&gt;Just a quick question, why do you explicitly import modules?&lt;BR /&gt;If the modules are in one of the directories listed in &lt;STRONG&gt;$env: PSModulePath&lt;/STRONG&gt; there is no need for that.&lt;BR /&gt;&lt;BR /&gt;Also, importing VMware.PowerCLI, implicit or explicit, generates a number of verbose message (where they inform you about the CEIP).&lt;BR /&gt;This might cause the transcript issues.&lt;BR /&gt;Perhaps try piping the Import-Module to Out-Null&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 09:27:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909669#M106702</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2022-05-18T09:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909672#M106703</link>
      <description>&lt;P&gt;As additional info, the Start-Transcript cmdlet is notorious for mssing output.&lt;BR /&gt;See for example &lt;A href="https://github.com/PowerShell/PowerShell/issues/10994" target="_blank" rel="noopener"&gt;#Issue&lt;/A&gt;&lt;SPAN class="f1-light color-fg-muted"&gt;&lt;A href="https://github.com/PowerShell/PowerShell/issues/10994" target="_blank" rel="noopener"&gt;10994&lt;/A&gt; on the PowerShell repository.&lt;BR /&gt;&lt;BR /&gt;I'm not sure if what you are seeing is caused by PowerCLI, I sooner suspect the type of output some PowerCLI modules produce when loaded might confuse the Start-TRanscript&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 09:43:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909672#M106703</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2022-05-18T09:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909680#M106704</link>
      <description>&lt;P&gt;Hi Luc&lt;/P&gt;&lt;P&gt;I don't explicitly import the module, only here to show case the issue. The original commandlet I used where is failed is Get-VICredentialStoreItem, but also Connect-OMServer does it and others (and here I do not import the module - The orginal script is more than 2000 lines of code so not something I can or will share here &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt; ). That is why I started testing with import-module.&lt;/P&gt;&lt;P&gt;The VMware.PowerCli module(s) are in path &lt;STRONG&gt;$env: PSModulePath.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;CEIP was been disabled for all users, so that should not be an issue and havn't been before.&lt;/P&gt;&lt;P&gt;Testing with "import-module VMware.PowerCli -force | Out-Null" does not work, same issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My laptop is running PowerCli 12.0.5 19195797 and the problem does not seem to be in this version.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 10:37:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909680#M106704</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-18T10:37:57Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909681#M106705</link>
      <description>&lt;P&gt;In which PowerCLI version do you see the problem then?&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 10:52:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909681#M106705</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2022-05-18T10:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909696#M106706</link>
      <description>&lt;LI-CODE lang="markup"&gt;PowerCLI Version
----------------
VMware.PowerCLI 12.6.0 build 19610541
---------------
Component Versions
---------------
VMware Common PowerCLI Component 12.6 build 19600917
VMware Cis Core PowerCLI Component PowerCLI Component 12.6 build 19601368
VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 12.6 build 19601570&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 18 May 2022 11:52:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909696#M106706</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-18T11:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909701#M106707</link>
      <description>&lt;P&gt;I have the exact same error on multible Windows computers. I think it started after a Windows patch some months ago.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 12:16:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909701#M106707</guid>
      <dc:creator>CLRYN</dc:creator>
      <dc:date>2022-05-18T12:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909720#M106708</link>
      <description>&lt;P&gt;Okay, interesting. Will update my laptop which is window 11 and powercli 12.5 to 12.6 to see what is does then.&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 13:04:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909720#M106708</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-18T13:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909829#M106711</link>
      <description>&lt;P&gt;I have upgraded an tested on 12.6 on Windows 11 and it works here &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;P&gt;Do you have any idea to which windows update that might be at fault?&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 19:01:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909829#M106711</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-18T19:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909862#M106712</link>
      <description>&lt;P&gt;Looking back at the beginning of this thread, I noticed that where it fails PowerShell is called with&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe&lt;/LI-CODE&gt;
&lt;P&gt;Could the one that works perhaps have picked up&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;%SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;Would that make a difference?&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2022 20:46:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909862#M106712</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2022-05-18T20:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909916#M106716</link>
      <description>&lt;P&gt;Nice catch Luc&lt;/P&gt;&lt;P&gt;But still no luck&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;**********************
Windows PowerShell transcript start
Start time: 20220519072841
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\syswow64\WindowsPowerShell\v1.0\powershell.exe
Process ID: 2648
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Windows\syswow64\WindowsPowerShell\v1.0&amp;gt; import-module VMware.PowerCli -force | Out-Null
**********************
Windows PowerShell transcript end
End time: 20220519072849
**********************&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 19 May 2022 06:32:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909916#M106716</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-19T06:32:03Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909959#M106718</link>
      <description>&lt;P&gt;Just to make sure you understand why I say it's a PowerCli issue. Here you can see me loading a non VMware module and you can see it working as expected.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;**********************
Windows PowerShell transcript start
Start time: 20220519084317
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 5696
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx&amp;gt; import-module ActiveDirectory
PS C:\Users\xxx&amp;gt; Write-host "Hallo World!"
Hallo World!
PS C:\Users\xxx&amp;gt; Stop-Transcript
**********************
Windows PowerShell transcript end
End time: 20220519084321
**********************&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 08:54:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909959#M106718</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-19T08:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909960#M106719</link>
      <description>&lt;P&gt;I understand, but I'm still somewhat convinced it is the unhealthy habit of the PowerCLI modules to show those messages when the modules are loaded.&lt;BR /&gt;Most other modules don't do that.&lt;BR /&gt;Combine that with a new "flaw" in Start-Transcript, and I suspect it might be a combination of the two.&lt;BR /&gt;&lt;BR /&gt;Btw, I have asked ages ago to remove those messages.&lt;BR /&gt;See&amp;nbsp;&lt;A href="https://powercli.ideas.aha.io/ideas/PCLI-I-164" target="_blank"&gt;Eliminate, or provide option with | VMware PowerCLI (aha.io)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 09:00:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909960#M106719</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2022-05-19T09:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909963#M106721</link>
      <description>&lt;P&gt;Thanks Luc.&lt;/P&gt;&lt;P&gt;We have another way of logging today internally, so I will just migrate the script to that way of logging instead of using transcript &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for everybody's help. Think I will leave it at that &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 May 2022 09:04:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2909963#M106721</guid>
      <dc:creator>MichaelRyom</dc:creator>
      <dc:date>2022-05-19T09:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919346#M107450</link>
      <description>&lt;P&gt;Just to confirm, this still appears to be an issue in 12.7&lt;/P&gt;&lt;P&gt;We just upgraded from 12.3 and have begun to encounter this very issue.&lt;/P&gt;&lt;P&gt;Right after the line:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\12.7.0.20067789\net45\VMware.VimAutomation.Common.ps1'.&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;**********************&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;Windows PowerShell transcript end&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;End time: 20220719084406&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;**********************&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;We are now explicitly loading the &lt;FONT face="courier new,courier"&gt;VMware.VimAutomation.Common&lt;/FONT&gt; module in the profile, before we start our script transcript, in order to avoid this issue.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jul 2022 15:08:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919346#M107450</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-07-19T15:08:11Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919957#M107524</link>
      <description>&lt;P&gt;I was not able to reproduce this.&lt;/P&gt;&lt;P&gt;Can you try to edit that file and see if this changes anything -&amp;nbsp;&lt;SPAN&gt;'...\Modules\VMware.VimAutomation.Common\12.7.0.20067789\net45\VMware.VimAutomation.Common.ps1'?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;(use the location from where you load the module from).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For example make it empty first and see if that changes anything - if it does, try to remove sections of it until you find what is making the difference.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Jul 2022 13:03:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2919957#M107524</guid>
      <dc:creator>AtanasAtanasov</dc:creator>
      <dc:date>2022-07-22T13:03:56Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2920920#M107559</link>
      <description>&lt;P&gt;Thank you for the follow up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steps to reproduce:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Launch powershell 5.1 console with empty profile (no autoloading modules)&lt;/LI&gt;&lt;LI&gt;&amp;gt; $VerbosePreference = "Continue"&lt;/LI&gt;&lt;LI&gt;&amp;gt; Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log&lt;/LI&gt;&lt;LI&gt;&amp;gt; Get-Process&lt;/LI&gt;&lt;LI&gt;&amp;gt; Import-Module VMware.PowerCLI&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;If you open the transcript file, you'll notice that it begins logging lines, but at some point during the middle of that import process, it stops logging and closes the transcript file properly with a&amp;nbsp;Windows PowerShell transcript end and an End time.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As for your troubleshooting suggestion, that was a good idea. And initially, when I opened VMware.VimAutomation.Common.ps1 and commented out the content, and relaunched a new console, the transcript would progress, but still end - just this time at like VMware.VimAutomation.Cis.Core.ps1.&amp;nbsp; When I edited that file and commented out the content, it would progress to VMware.VimAutomation.Core.ps1. And commenting that one resulted in the transcript ending at VMware.VimAutomation.ViCore.Cmdlets.dll - and since I don't know how to edit a dll, that's where I stalled.&lt;/P&gt;&lt;P&gt;This is starting to feel like a line involving ending a running debugging transcript was accidentally left in a function of the compiled code and is getting called at the conclusion of each (or at least many) modules.&lt;/P&gt;&lt;P&gt;Thanks again for your suggestions. I'm still open to any troubleshooting recommendations.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: Easier steps:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Launch powershell 5.1 console with empty profile (no autoloading modules)&lt;/LI&gt;&lt;LI&gt;&amp;gt; $VerbosePreference = "Continue"&lt;/LI&gt;&lt;LI&gt;&amp;gt; Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log&lt;/LI&gt;&lt;LI&gt;&amp;gt; Measure-Command {Get-VM}&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This will end in an error, but will import less modules and you'll still be able to see the log be stopped and closed prematurely.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Aug 2022 18:15:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2920920#M107559</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-08-05T18:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921050#M107570</link>
      <description>&lt;P&gt;The output for me in the .log file is exactly the same as what I see in the console.&lt;/P&gt;&lt;P&gt;What is the value of $PSVersionTable where you reproduced this? I tested this on Windows 11 (10.0.22000.653) and Window 10 (10.0.19041.1682), what version is the OS where you run this?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2022 12:06:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921050#M107570</guid>
      <dc:creator>AtanasAtanasov</dc:creator>
      <dc:date>2022-07-28T12:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921065#M107572</link>
      <description>&lt;P&gt;That's strange.&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;PS &amp;gt; (Get-WmiObject -class Win32_OperatingSystem).Caption&lt;BR /&gt;Microsoft Windows Server 2019 Datacenter&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; [System.Environment]::OSVersion.Version&lt;BR /&gt;&lt;BR /&gt;Major Minor Build Revision&lt;BR /&gt;----- ----- ----- --------&lt;BR /&gt;10 0 17763 0&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; $PSVersionTable&lt;BR /&gt;&lt;BR /&gt;Name Value&lt;BR /&gt;---- -----&lt;BR /&gt;PSVersion 5.1.17763.2931&lt;BR /&gt;PSEdition Desktop&lt;BR /&gt;PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}&lt;BR /&gt;BuildVersion 10.0.17763.2931&lt;BR /&gt;CLRVersion 4.0.30319.42000&lt;BR /&gt;WSManStackVersion 3.0&lt;BR /&gt;PSRemotingProtocolVersion 2.3&lt;BR /&gt;SerializationVersion 1.1.0.1&lt;BR /&gt;&lt;BR /&gt;PS &amp;gt; Get-Module -ListAvailable VMware.PowerCLI |ft -AutoSize&lt;BR /&gt;VERBOSE: Populating RepositorySourceLocation property for module VMware.PowerCLI.&lt;BR /&gt;VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCLI\12.7.0.20091289\VMware.PowerCLI.ps1'.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Directory: C:\Program Files\WindowsPowerShell\Modules&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ModuleType Version Name ExportedCommands&lt;BR /&gt;---------- ------- ---- ----------------&lt;BR /&gt;Manifest 12.7.0.20091289 VMware.PowerCLI&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All of our servers experience this behavior.&amp;nbsp;I'll have to try some wider testing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2022 12:52:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921065#M107572</guid>
      <dc:creator>Tocano</dc:creator>
      <dc:date>2022-07-28T12:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: PowerCli/Start-transcript bug</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921680#M107597</link>
      <description>&lt;P&gt;Can you try with PowerShell Core?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Aug 2022 13:40:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/PowerCli-Start-transcript-bug/m-p/2921680#M107597</guid>
      <dc:creator>AtanasAtanasov</dc:creator>
      <dc:date>2022-08-01T13:40:59Z</dc:date>
    </item>
  </channel>
</rss>

