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.

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.
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.
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
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
Solutions
Run Microsoft Tunnel Patch Script (mstunnel-patch-2602)
This is the official Microsoft remediation script for fixing upgrade issues with version 20260129.1.
- Connect to your Linux Tunnel server via SSH with administrative privileges
- Download the official patch script from Microsoft:
wget https://download.microsoft.com/download/tunnel/mstunnel-patch-2602.sh - Verify the script integrity by checking the hash:
sha256sum mstunnel-patch-2602.sh - Make the script executable:
chmod +x mstunnel-patch-2602.sh - Stop the Microsoft Tunnel service before running the patch:
sudo systemctl stop mstunnel - Run the remediation script with sudo privileges:
sudo ./mstunnel-patch-2602.sh - Monitor the script output for any errors or completion messages
- Restart the Tunnel service after successful patch completion:
sudo systemctl start mstunnel
Manual Version Verification and Service Reset
If the patch script is unavailable, manually verify and reset the Tunnel service configuration.
- Check the current Tunnel version and service status:
sudo mstunnel --version
sudo systemctl status mstunnel - Verify the installed package version:
dpkg -l | grep mstunnel - Check for corrupted configuration files:
sudo find /etc/mstunnel -name "*.conf" -exec ls -la {} \; - Stop all Tunnel-related services:
sudo systemctl stop mstunnel
sudo systemctl stop mstunnel-agent - Clear temporary upgrade files:
sudo rm -rf /tmp/mstunnel-upgrade/*
sudo rm -rf /var/cache/mstunnel/upgrade/* - Reset service configuration to defaults:
sudo systemctl reset-failed mstunnel
sudo systemctl daemon-reload - Restart services in the correct order:
sudo systemctl start mstunnel-agent
sudo systemctl start mstunnel
Force Update to Version 20260330.1 or Later
Manually force the upgrade to a newer version that resolves the known issue.
- 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 - Update the package repository:
sudo apt update - Check available Tunnel versions:
apt list --upgradable | grep mstunnel - Stop the current Tunnel service:
sudo systemctl stop mstunnel - Force install the latest version:
sudo apt install --reinstall mstunnel=20260330.1-1 - Reconfigure the Tunnel service:
sudo dpkg-reconfigure mstunnel - Start the updated service:
sudo systemctl start mstunnel
sudo systemctl enable mstunnel - Verify the upgrade completed successfully:
sudo mstunnel --version
sudo systemctl status mstunnel
Clean Reinstall with Configuration Preservation
If other methods fail, perform a clean reinstall while preserving your existing configuration.
- 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 - Export current certificate and key files:
sudo tar -czf mstunnel-certs-backup.tar.gz /etc/ssl/certs/mstunnel* /etc/ssl/private/mstunnel* - Stop and disable the Tunnel service:
sudo systemctl stop mstunnel
sudo systemctl disable mstunnel - Completely remove the existing installation:
sudo apt remove --purge mstunnel mstunnel-agent
sudo rm -rf /etc/mstunnel /var/lib/mstunnel - Clean package cache and dependencies:
sudo apt autoremove
sudo apt autoclean - Reinstall the latest Tunnel version:
sudo apt update
sudo apt install mstunnel - 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 - Restore certificates:
sudo tar -xzf mstunnel-certs-backup.tar.gz -C / - Start and enable the service:
sudo systemctl enable mstunnel
sudo systemctl start mstunnel
Advanced Troubleshooting with Log Analysis
For persistent issues, analyze system logs and perform advanced diagnostics.
- Enable detailed logging for the Tunnel service:
Add the following lines:sudo systemctl edit mstunnel[Service]
Environment="MSTUNNEL_LOG_LEVEL=debug" - Check system logs for upgrade-related errors:
sudo journalctl -u mstunnel -f --since "1 hour ago"
sudo tail -f /var/log/mstunnel/server.log - Analyze package manager logs:
sudo grep -i mstunnel /var/log/dpkg.log
sudo grep -i mstunnel /var/log/apt/history.log - Check disk space and permissions:
df -h /var /tmp /etc
sudo find /etc/mstunnel -type f -exec ls -la {} \; - Verify network connectivity to Microsoft services:
nslookup packages.microsoft.com
curl -I https://packages.microsoft.com/repos/tunnel-prod/ - Run system diagnostics:
sudo systemd-analyze verify mstunnel.service
sudo systemctl list-dependencies mstunnel - Generate a comprehensive diagnostic report:
sudo mstunnel --diagnostic-report > tunnel-diagnostic-$(date +%Y%m%d).txt
Verification
After applying any of the above methods, verify the fix using these steps:
- Check the current Tunnel version:
Ensure it shows version 20260330.1 or later.sudo mstunnel --version - Verify service status:
The service should show as "active (running)".sudo systemctl status mstunnel - Test connectivity from the Microsoft Intune admin center by navigating to Tenant administration → Microsoft Tunnel Gateway and checking server health status.
- Verify hash signatures match the expected values:
sha256sum /usr/bin/mstunnel - Check that automatic updates are functioning:
sudo systemctl status mstunnel-updater
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-cacheand ensure base image is updated. - Certificate Problems: Regenerate Tunnel certificates using
sudo mstunnel --regenerate-certsand restart the service. - Database Corruption: Reset the Tunnel database with
sudo rm /var/lib/mstunnel/tunnel.dband reconfigure the service. - Firewall Conflicts: Temporarily disable firewall rules with
sudo ufw disableto test connectivity, then re-enable with proper exceptions. - DNS Resolution: Add Microsoft package repository domains to
/etc/hostsif 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?+
How do I know if my Tunnel server is affected by this issue?+
Is it safe to use the mstunnel-patch-2602.sh script on production servers?+
What should I do if the patch script fails to resolve the issue?+
Will this upgrade issue affect new Tunnel server installations?+
Further Intelligence
Deepen your knowledge with related resources

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

Fix Remote Desktop Connection Security Warning Display Issues – Windows 10/11 2026

Fix Windows 11 File Explorer Performance Issues – Slow Launch & Dark Mode Flashes 2026
Discussion
Share your thoughts and insights
Sign in to join the discussion

