Table of Contents
Is Your System Crashing Due to the Problematic Azure Local 2510 Update?
A recent software update for Azure Local, version 2510, has caused serious problems for some users. After installing the update, systems began to crash and show a blue screen. This guide explains the problem, the temporary fix, and the current status of the update.
Understanding the Problem
IT teams, especially those in the critical healthcare sector, reported system failures after installing the Azure Local Solution Update 2510. The main symptom is a blue screen error, also known as a “Blue Screen of Death,” with bugcheck code 0x139. This error, KERNEL_SECURITY_CHECK_FAILURE, indicates that a critical data structure in the computer’s core has been corrupted.
These crashes happened about every 20 hours on all host systems. For a facility like a hospital running around 100 virtual machines, unexpected crashes can be a disaster. Initial attempts to fix the issue by updating drivers and system BIOS were unsuccessful.
Microsoft Support’s Temporary Solution
After contacting Microsoft Support, a temporary fix was provided. The issue appears to be a known problem caused by a specific change within the 2510 update. The solution involves modifying the Windows Registry to turn off the faulty feature.
To apply the fix, you must run the following command on each affected computer node and then reboot the system:
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 556278415 /t REG_DWORD /d 0 /f
This command adds a registry key that essentially disables the change introduced in the update, preventing the system from crashing. This is a temporary measure until a permanent, safe update is released.
Microsoft Withdraws the Faulty Update
Microsoft has officially acknowledged the problem and has temporarily pulled the update. This means it is no longer available for download while they investigate the cause.
Microsoft is reviewing two main issues:
- A version mismatch where the system software was not at the expected version number.
- An issue in the Hyper-V socket that can cause a computer node to crash.
This withdrawal prevents more users from installing the problematic update. If you have already installed update 2510 and are experiencing blue screens, use the registry fix provided above. Always back up your system before making registry changes.