In recent weeks, Microsoft has faced a series of challenges within its enterprise sector, with various issues emerging that have raised concerns among IT administrators. Among these, a notable incident has come to light involving the unintentional release of Windows 11 to devices that do not meet the necessary eligibility criteria, a situation attributed to a bug within Intune.
Windows 11 for the masses
While Microsoft aims to transition as many users as possible to Windows 11, the company has been clear about its stringent hardware requirements. These guidelines are designed to ensure optimal performance and security. However, many IT administrators were caught off guard when it became apparent that Windows 11 was being rolled out to unsupported PCs, despite existing Intune restrictions.
According to a recent advisory published in the Microsoft 365 admin center, the issue has persisted since April 12, stemming from a “latent code issue” that prevents Intune from adhering to certain rollout block policies. It’s essential to clarify that this bug does not mean Windows 11 is being pushed to unsupported Windows 10 devices; rather, it is being made available to “ineligible” Windows 10 desktop devices that IT admins had previously blocked from receiving the update.
A targeted fix is on the way
In response to this situation, Microsoft is actively deploying a targeted code fix aimed at resolving the issue before it escalates further. In the interim, the company has advised IT administrators to pause any Windows feature updates until they can thoroughly test and implement the Intune code fix. Additionally, Microsoft has recommended that affected IT personnel manually revert impacted devices back to the appropriate version of Windows 10.
While the exact number of companies affected by this bug remains unclear, Microsoft has categorized the incident as an advisory, suggesting that the overall impact may be limited. Nevertheless, the necessity for manual rollbacks could pose additional challenges for IT administrators in the coming days, particularly since there are currently no automated scripts or Intune functionalities available to streamline this process.
