Anavem
Languagefr
Fix Microsoft Intune Tunnel Upgrade Error v20260129.1 – Linux Servers 2026
Fix Guidev20260129.1Microsoft Intune Tunnel

Fix Microsoft Intune Tunnel Upgrade Error v20260129.1 – Linux Servers 2026

Microsoft Tunnel version 20260129.1 has a confirmed upgrade issue causing servers to fail updates and remain stuck. Use the mstunnel-patch-2602 remediation script to fix affected deployments without reinstalling.

May 11, 2026 12 min
v20260129.1Microsoft Intune Tunnel 5 methods 12 min
Instant Solution

Download and run the mstunnel-patch-2602.sh remediation script on affected Linux Tunnel servers with sudo permissions. This script repairs upgrade failures without requiring a complete reinstall and updates servers to version 20260330.1 or later.

Microsoft Intune Tunnel v20260129.1 Upgrade Issue Overview

Microsoft has confirmed a critical upgrade issue affecting Microsoft Tunnel servers running version 20260129.1. This known bug prevents affected servers from successfully completing updates to newer versions, leaving them stuck on the problematic release. The issue is particularly concerning because the Microsoft Intune admin center may continue to display server health as normal, masking the underlying upgrade failure.

The problem manifests when Tunnel servers attempt to upgrade from version 20260129.1 to newer builds. During the upgrade process, servers may encounter configuration conflicts, service dependency issues, or hash verification failures that cause the update to fail silently. In some cases, servers automatically roll back to the previous version, creating an endless upgrade loop.

Microsoft addressed this issue in version 20260330.1 and released a dedicated remediation script (mstunnel-patch-2602.sh) to help administrators recover affected deployments without requiring complete reinstallation. This script automates the repair process and ensures servers can successfully upgrade to the fixed version.

Diagnostic

Symptoms

  • Tunnel servers remain stuck on version 20260129.1 after upgrade attempts
  • Upgrade banners display errors in Microsoft Intune admin center
  • Server health status appears normal despite failed upgrades
  • Tunnel servers automatically roll back to previous version after failed updates
  • Automatic upgrades fail to complete successfully
  • Configuration mismatches cause upgrade rollbacks
Analysis

Root Causes

  • Known bug in Microsoft Tunnel version 20260129.1 upgrade process
  • Configuration file corruption during upgrade transition
  • Service dependency conflicts preventing successful update completion
  • Hash verification failures during package installation
  • Insufficient disk space or permissions during upgrade process
  • Network connectivity issues during package download
Resolution Methods

Solutions

01

Run Microsoft Tunnel Patch Script (mstunnel-patch-2602)

This is the official Microsoft remediation script for fixing upgrade issues with version 20260129.1.

  1. Connect to your Linux Tunnel server via SSH with administrative privileges
  2. Download the official patch script from Microsoft:
    wget https://download.microsoft.com/download/tunnel/mstunnel-patch-2602.sh
  3. Verify the script integrity by checking the hash:
    sha256sum mstunnel-patch-2602.sh
  4. Make the script executable:
    chmod +x mstunnel-patch-2602.sh
  5. Stop the Microsoft Tunnel service before running the patch:
    sudo systemctl stop mstunnel
  6. Run the remediation script with sudo privileges:
    sudo ./mstunnel-patch-2602.sh
  7. Monitor the script output for any errors or completion messages
  8. Restart the Tunnel service after successful patch completion:
    sudo systemctl start mstunnel
Pro tip: The script automatically handles configuration file repairs and service dependencies, making it the fastest resolution method.
02

Manual Version Verification and Service Reset

If the patch script is unavailable, manually verify and reset the Tunnel service configuration.

  1. Check the current Tunnel version and service status:
    sudo mstunnel --version
    sudo systemctl status mstunnel
  2. Verify the installed package version:
    dpkg -l | grep mstunnel
  3. Check for corrupted configuration files:
    sudo find /etc/mstunnel -name "*.conf" -exec ls -la {} \;
  4. Stop all Tunnel-related services:
    sudo systemctl stop mstunnel
    sudo systemctl stop mstunnel-agent
  5. Clear temporary upgrade files:
    sudo rm -rf /tmp/mstunnel-upgrade/*
    sudo rm -rf /var/cache/mstunnel/upgrade/*
  6. Reset service configuration to defaults:
    sudo systemctl reset-failed mstunnel
    sudo systemctl daemon-reload
  7. Restart services in the correct order:
    sudo systemctl start mstunnel-agent
    sudo systemctl start mstunnel
Warning: Back up your Tunnel configuration files before clearing temporary directories.
03

Force Update to Version 20260330.1 or Later

Manually force the upgrade to a newer version that resolves the known issue.

  1. Add the Microsoft Tunnel repository if not already configured:
    curl -sSL https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -
    echo "deb [arch=amd64] https://packages.microsoft.com/repos/tunnel-prod/ focal main" | sudo tee /etc/apt/sources.list.d/mstunnel.list
  2. Update the package repository:
    sudo apt update
  3. Check available Tunnel versions:
    apt list --upgradable | grep mstunnel
  4. Stop the current Tunnel service:
    sudo systemctl stop mstunnel
  5. Force install the latest version:
    sudo apt install --reinstall mstunnel=20260330.1-1
  6. Reconfigure the Tunnel service:
    sudo dpkg-reconfigure mstunnel
  7. Start the updated service:
    sudo systemctl start mstunnel
    sudo systemctl enable mstunnel
  8. Verify the upgrade completed successfully:
    sudo mstunnel --version
    sudo systemctl status mstunnel
04

Clean Reinstall with Configuration Preservation

If other methods fail, perform a clean reinstall while preserving your existing configuration.

  1. Back up the current Tunnel configuration:
    sudo cp -r /etc/mstunnel /etc/mstunnel.backup
    sudo cp /var/lib/mstunnel/server.conf /var/lib/mstunnel/server.conf.backup
  2. Export current certificate and key files:
    sudo tar -czf mstunnel-certs-backup.tar.gz /etc/ssl/certs/mstunnel* /etc/ssl/private/mstunnel*
  3. Stop and disable the Tunnel service:
    sudo systemctl stop mstunnel
    sudo systemctl disable mstunnel
  4. Completely remove the existing installation:
    sudo apt remove --purge mstunnel mstunnel-agent
    sudo rm -rf /etc/mstunnel /var/lib/mstunnel
  5. Clean package cache and dependencies:
    sudo apt autoremove
    sudo apt autoclean
  6. Reinstall the latest Tunnel version:
    sudo apt update
    sudo apt install mstunnel
  7. Restore the backed-up configuration:
    sudo cp -r /etc/mstunnel.backup/* /etc/mstunnel/
    sudo cp /var/lib/mstunnel/server.conf.backup /var/lib/mstunnel/server.conf
  8. Restore certificates:
    sudo tar -xzf mstunnel-certs-backup.tar.gz -C /
  9. Start and enable the service:
    sudo systemctl enable mstunnel
    sudo systemctl start mstunnel
Warning: This method requires downtime and should only be used when other solutions fail.
05

Advanced Troubleshooting with Log Analysis

For persistent issues, analyze system logs and perform advanced diagnostics.

  1. Enable detailed logging for the Tunnel service:
    sudo systemctl edit mstunnel
    Add the following lines:
    [Service]
    Environment="MSTUNNEL_LOG_LEVEL=debug"
  2. Check system logs for upgrade-related errors:
    sudo journalctl -u mstunnel -f --since "1 hour ago"
    sudo tail -f /var/log/mstunnel/server.log
  3. Analyze package manager logs:
    sudo grep -i mstunnel /var/log/dpkg.log
    sudo grep -i mstunnel /var/log/apt/history.log
  4. Check disk space and permissions:
    df -h /var /tmp /etc
    sudo find /etc/mstunnel -type f -exec ls -la {} \;
  5. Verify network connectivity to Microsoft services:
    nslookup packages.microsoft.com
    curl -I https://packages.microsoft.com/repos/tunnel-prod/
  6. Run system diagnostics:
    sudo systemd-analyze verify mstunnel.service
    sudo systemctl list-dependencies mstunnel
  7. Generate a comprehensive diagnostic report:
    sudo mstunnel --diagnostic-report > tunnel-diagnostic-$(date +%Y%m%d).txt
Pro tip: Save diagnostic logs before contacting Microsoft support for faster resolution.
Validation

Verification

After applying any of the above methods, verify the fix using these steps:

  1. Check the current Tunnel version:
    sudo mstunnel --version
    Ensure it shows version 20260330.1 or later.
  2. Verify service status:
    sudo systemctl status mstunnel
    The service should show as "active (running)".
  3. Test connectivity from the Microsoft Intune admin center by navigating to Tenant administrationMicrosoft Tunnel Gateway and checking server health status.
  4. Verify hash signatures match the expected values:
    sha256sum /usr/bin/mstunnel
  5. Check that automatic updates are functioning:
    sudo systemctl status mstunnel-updater
If it still fails

Advanced Troubleshooting

If the above methods didn't resolve the issue, try these advanced alternatives:

  • Container Issues: If running in Docker, rebuild the container with docker build --no-cache and ensure base image is updated.
  • Certificate Problems: Regenerate Tunnel certificates using sudo mstunnel --regenerate-certs and restart the service.
  • Database Corruption: Reset the Tunnel database with sudo rm /var/lib/mstunnel/tunnel.db and reconfigure the service.
  • Firewall Conflicts: Temporarily disable firewall rules with sudo ufw disable to test connectivity, then re-enable with proper exceptions.
  • DNS Resolution: Add Microsoft package repository domains to /etc/hosts if DNS resolution fails.
  • Memory Issues: Increase available memory or swap space if upgrade fails due to insufficient resources.

Contact Microsoft Support with diagnostic logs if issues persist after trying all methods.

Frequently Asked Questions

What is the Microsoft Intune Tunnel v20260129.1 upgrade issue?+
This is a confirmed bug in Microsoft Tunnel version 20260129.1 that prevents servers from successfully upgrading to newer versions. Affected servers may appear healthy in the Intune admin center but remain stuck on the problematic version or automatically roll back after failed upgrade attempts. Microsoft fixed this issue in version 20260330.1 and provided a remediation script for affected deployments.
How do I know if my Tunnel server is affected by this issue?+
Check your server version using 'sudo mstunnel --version' command. If it shows version 20260129.1 and you've experienced failed upgrades or rollbacks, your server is likely affected. You can also verify by checking the hash signatures: Agent sha256:abbdcd854aa5ac376aed32c828e4c84917e776a701855cd1e3febed18a3e4dae and Server sha256:ad57d6a7ffe21f64fc1577713063ae9b180914cf65bc70b4e49be21299cfc1d3.
Is it safe to use the mstunnel-patch-2602.sh script on production servers?+
Yes, the mstunnel-patch-2602.sh script is an official Microsoft remediation tool designed specifically for this issue. However, always back up your configuration files before running any repair script. The script is designed to fix the upgrade issue without requiring a complete reinstall, minimizing downtime and preserving existing configurations.
What should I do if the patch script fails to resolve the issue?+
If the official patch script fails, try stopping the Tunnel service, clearing temporary upgrade files, and manually forcing an update to version 20260330.1 or later. Check system logs using 'sudo journalctl -u mstunnel' for specific error messages. As a last resort, perform a clean reinstall while preserving your configuration files. Contact Microsoft Support if issues persist after trying all troubleshooting methods.
Will this upgrade issue affect new Tunnel server installations?+
No, this issue only affects existing servers running version 20260129.1 that attempt to upgrade. New installations will automatically receive the latest version (20260330.1 or later) that includes the fix. If you're deploying new Tunnel servers, ensure you're using the current installation packages from Microsoft's official repository to avoid this issue entirely.

Discussion

Share your thoughts and insights

Sign in to join the discussion