Blog Post

Intune Customer Success
2 MIN READ

Known issue: Upgrading Microsoft Tunnel version 20260129.1

Intune_Support_Team's avatar
Intune_Support_Team
Silver Contributor
May 08, 2026

We identified an upgrade issue with the early March release of Microsoft Tunnel version 20260129.1 that caused servers to become stuck and unable to complete the upgrade. The issue can be resolved by uninstalling and reinstalling the server to a newer version (20260330.1 or later). Alternatively, we’ve created a script to help you update affected servers. This blog explains how to use the mstunnel-patch-2602 script to remediate the issue.

Before you begin

Before you run the script, make sure you have the following:

  • Access to the Linux virtual machine hosting the Microsoft Tunnel server
  • Permission to run commands with sudo
  • The patch script downloaded to the server from https://aka.ms/mstunnel-patch-2602

When to use this script

Use this script if your server is showing one or more of the following behaviors:

  • The server remains on the affected version (20260129.1) and doesn’t move to the latest version
  • In the Intune admin center, the server health state appears as Healthy, but the upgrade banner shows an error
  • The server rolls back to the affected version because of a version mismatch in Agent Settings

Identify impacted servers

The issue affects servers on version 20260129.1, use the following hash to identify whether your deployment is on this version:

  • Agent: 
    sha256:abbdcd854aa5ac376aed32c828e4c84917e776a701855cd1e3febed18a3e4dae
  • Server:
    sha256:ad57d6a7ffe21f64fc1577713063ae9b180914cf65bc70b4e49be21299cfc1d3


The issue was resolved with version 20260330.1, released March 30, 2026. You can verify your servers are on this version with the following hash:

  • Agent: 
    sha256:163214b94af6d91a5ef02690f891c5a41e87b1059b9530324716ee34778c1785
  • Server: 
    sha256:dd62c292528e8e5aa4e7b84418efa42fd3830ec0db40467947cde8125aa17d7e


Additionally, in the Intune admin center check the server site auto upgrade setting. If auto upgrade is turned off (Automatically upgrade servers at this site = No), select "Upgrade servers" to configure the latest image for site.

Figure 1: Screenshot of the Microsoft Intune admin center showing a Microsoft Tunnel Gateway site named “SimpleSite” with theUpgrade servers option highlighted.

Run the script

After downloading the script to the server, complete the following steps.

Step 1: Enable execution permissions

If needed, make the script executable:

chmod +x mstunnel-patch-2602.sh

 

Step 2: Run the script

Run the script with elevated permissions:

sudo ./mstunnel-patch-2602.sh

When the script runs, it performs the following actions automatically:

  1. Checks whether the current server is using the affected build hashes.
  2. Creates backups of the current configuration so the system can revert if the update fails.
  3. Stops the Tunnel agent and server services.
  4. Updates the configuration with version 20260330.1 hashes
  5. Pulls version 20260330.1 and forces mst-cli install without requiring additional user input

Expected results

After the script completes successfully, the server should be updated to the March 30, 2026 version 20260330.1. This remediation is intended to resolve upgrade failures caused by a version mismatch and eliminate the need for a manual uninstall and reinstall workflow.

If you have any questions or issues running the script to update your servers, reply to this post or reach out to the team on X @IntuneSuppTeam.

 

Post Updates:
6/15/26: Added guidance to check the server site auto-upgrade setting in Intune and use the Upgrade servers option when auto upgrade is disabled to apply the latest image.

Updated Jun 15, 2026
Version 2.0

4 Comments

  • hathat's avatar
    hathat
    Copper Contributor

    We have a cert imported that has a password and I was running into errors running the script because it forces "yes" answers to everything when running 'mst-cli install' to upgrade after setting known-good digests.

    Here's the ERROR:
    Mac verify error: invalid password?
    fail: Error executing RunContainerCommand

    There's maybe a more elegant way to fix this but in the script I replaced:
    "
    log "Running mst-cli install (auto-confirm yes)..."
    # mst-cli reads its 'Continue installation?' prompt from /dev/tty, so a plain
    # `yes | mst-cli install` pipe is ignored. `script` (util-linux, ships with
    # every supported distro) allocates a PTY and lets us feed 'yes' answers in.
    printf 'yes\n%.0s' {1..10} | script -qec 'mst-cli install' /dev/null
    "

    with 

    "
    mst-cli install
    "

    This allowed me to run through the install prompts manually and enter the TLS Cert Import Password.

  • Biochemistry101's avatar
    Biochemistry101
    Copper Contributor

    I raised this issue with MS Support on 13th April. Despite numerous emails to chase progress I never got any response or updates from MS Support. Obviously it has taken some time for MS engineers to review this problem and supply a fix, but it would have been nice for the issue to be acknowledged and published on the Intune Health status page - so that all organisations using MS Tunnel were aware of the issue and that it was being worked upon.

    • Intune_Support_Team's avatar
      Intune_Support_Team
      Silver Contributor

      Hi Biochemistry101​, incident IT1262345 was posted to the Service Health Dashboard (SHD) to notify impacted customers of this issue. If your tenant was identified as affected, you should have seen the advisory there, or under "past incidents/advisories" now that the incident has passed. If you’re not seeing it in either location, please send us a private message with your tenant details and support request number. We’d be happy to take a closer look and follow up with the appropriate support team. Thanks!