Fixing WinRM Error: Invalid Stream ID Index

Description of the Error

This error occurs during Windows Remote Management (WinRM) sessions. It typically happens when using PowerShell Remoting or tools like Ansible and Jenkins.

The error triggers because the WinRM client and server get out of sync during data transmission. Specifically, the client sends a data packet with a stream ID index that the server does not recognize or support. This mismatch is usually caused by:

• Corrupted WinRM sessions hanging in the background.
• Outdated PowerShell versions between the local and remote machines.
• Size limits on the WinRM request packet being exceeded.
• Corrupted WinRM configurations on the host machine.

Step-by-Step Fixes

Follow these steps in order to resolve the issue.

Step 1: Restart the WinRM Service

The quickest fix is to clear out hung remote sessions by restarting the management service.

1. Open the Start Menu.
2. Type cmd, right-click Command Prompt, and select Run as administrator.
3. Type the following command and press Enter:

   net stop winrm

4. Type the following command and press Enter to start it again:

   net start winrm

Step 2: Increase WinRM Max Envelope Size

If your scripts send large blocks of data, the packet might get truncated and corrupt the stream ID. Increasing the allowed envelope size fixes this.

1. Keep your Administrator Command Prompt open.
2. Run this command to check your current configuration:

   winrm get winrm/config

3. Run this command to increase the max envelope size to 8192 KB:

   winrm set winrm/config @{MaxEnvelopeSizekb="8192"}

Step 3: Increase Max Memory Per Shell

Low memory allocation for remote shells can cause the data stream to fail abruptly.

1. In the Administrator Command Prompt, run the following command:

   winrm set winrm/config/winrs @{MaxMemoryPerShellMB="2048"}

2. Restart the WinRM service again to apply changes:

   net stop winrm && net start winrm

Step 4: Re-register and Reset WinRM Configuration

If the configuration parameters are corrupted, you can reset the entire WinRM setup back to defaults.

1. Open PowerShell as an Administrator.
2. Run this command to completely reset the WinRM service configurations:

   winrm quickconfig -q

3. If you are configuring a secure environment, ensure your setup allows remote connections by running:

   Enable-PSRemoting -Force

Step 5: Update Windows Management Framework (WMF)

Ensure both the source machine and the target machine are running compatible versions of PowerShell.

1. Check your current version by running this in PowerShell:

   \$PSVersionTable.PSVersion

2. If either machine is running an older version (like PowerShell 4.0 or lower), download and install the latest Windows Management Framework or PowerShell 7+ from Microsoft's official website.