Kudu PowerShell throwing: Window title cannot be longer than 1023 characters

Question

Kudu PowerShell randomly throws an error:

Window title cannot be longer than 1023 characters

This appears similar to the historical Kudu GitHub issue #2635, which was closed when the Kudu repo was archived, but the behavior is still reproducible.

Steps to Reproduce

1. Open a Kudu PowerShell session
2. Commands vary, but here are two examples on which it triggered:

      PS C:\home> tcpping ubuntu-serve.net.local:3306; echo test
      Connected to ubuntu-serve.net.local:3306, time taken: 489ms
      Connected to ubuntu-serve.net.local:3306, time taken: 530ms
      Connected to ubuntu-serve.net.local:3306, time taken: 80ms
      Connected to ubuntu-serve.net.local:3306, time taken: 170ms
      Complete: 4/4 successful attempts (100%). Average success time: 317.25ms
      Window title cannot be longer than 1023 characters.
      At line:1 char:1
      + tcpping ubuntu-serve.net.local:3306; echo test
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
          + FullyQualifiedErrorId : Argument
       
      test
   

      PS C:\home> exit
      exit
      
      process [2556] terminated!  Press ENTER to start a new cmd process.
      
      PS C:\home> git --version
      git --version
      git version 2.46.0.windows.1
      PS C:\home> git --version
      git --version
      git version 2.46.0.windows.1
      Window title cannot be longer than 1023 characters.
      PS C:\home> 
      At line:1 char:1
      + git --version
      + ~~~~~~~~~~~~~
         + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
         + FullyQualifiedErrorId : Argument
   
   
      PS C:\home> git --version
      git --version
      git version 2.46.0.windows.1
      Window title cannot be longer than 1023 characters.
      PS C:\home> At line:1 char:1
      + git --version
      + ~~~~~~~~~~~~~
         + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
         + FullyQualifiedErrorId : Argument
   
      git --version
      git --version
      git version 2.46.0.windows.1
      Window title cannot be longer than 1023 characters.
      PS C:\home> At line:1 char:1
      + git --version
      + ~~~~~~~~~~~~~
         + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
         + FullyQualifiedErrorId : Argument
   
      git --version
      git --version
      git version 2.46.0.windows.1
      PS C:\home> 
   

Environment

• Azure App Service (Windows)
• VNet Integration enabled
• Region: West US 3
• App Service Plan SKU: Basic
• Site architecture: 32-bit (x86)
• Kudu version: 2026.08.1.2?
• PowerShell version: 5.1.20348.5499
• Git version: 2.46.0.windows.1

Observations

• The issue is intermittent and cannot be reproduced on every execution: the same command may trigger the exception several times in a row and then later succeed without issue.
• The exception is emitted after the command completes (though sometimes the output is interleaved).
• The exception does not kill the process: subsequent commands continue to execute normally (echo test still executes).
• The same behavior occurs for several different commands: the original GitHub issue mentions git --version causing the issue, but I can also reproduce it with tcpping.
• This suggests the issue is related to the Kudu PowerShell host rather than the command being executed.

Questions

1. Is this a known issue in the current Azure App Service Kudu environment?
2. Was the issue ever fixed, or was it closed as part of the Kudu repository archival process?
3. Is there a supported workaround for the Kudu PowerShell console when this exception occurs?
4. Is there a replacement channel for reporting Kudu defects now that the GitHub repository is archived and Basic support plans cannot open technical support incidents?
5. Can anyone provide any additional information on this issue?

Answer 1

I’m looking for clarification regarding an issue in the Azure App Service Kudu environment.

• Is this a known issue in the current Kudu environment, specifically when the PowerShell console throws this exception?
• Was the issue ever fixed, or was it effectively closed when the Kudu GitHub repository was archived?
• Is there a supported workaround or alternative for using the Kudu PowerShell console when this exception occurs?
• Now that the Kudu repository is archived, what is the recommended channel for reporting Kudu defects?
• If a customer is on a Basic Azure Support plan and cannot open a technical support incident, what is the appropriate way to escalate or report the issue?
• Has anyone encountered the same exception recently, and can you provide any additional information about its cause or resolution?

Any information regarding the current status of this issue, a supported workaround, or the appropriate Microsoft reporting channel would be greatly appreciated.