Microsoft is releasing the block it placed on some Surface devices to prevent them from updating to the Windows 10 2004/May 20202 update The block prevented users of certain Microsoft-made Surface models, including Surface Laptop 3 and Surface Pro 7, from manually downloading and installing Microsoft’s latest Windows 10 feature update.

According to Microsoft’s Windows 10 release information for the May update, devices with more than one Always On, Always Connected capable network adapter could experience inadvertent shutdowns and restarts. The Surface Laptop 3 and Surface Pro 7 both fit into that category. (Some other Surface devices may, too; I’ve asked Microsoft for the list of devices affected but haven’t heard back.)

Even though Microsoft patched this issue on June 9, Patch Tuesday, with KB4557957, Microsoft continued to impose the block. Sometime in the last day or two, however, the company updated its release information to note that the block was removed effective June 29. Microsoft officials noted that it may take up to 48 hours before the update to Windows 10 2004 will “be offered.”  (Thanks to BleepingComputer.com for reporting on the change in wording on July 1.)

After announcing on May 27 that it was starting to make the May 2020 feature update available via Windows Update, Microsoft also released a list of about a dozen previously undisclosed issues, which potentially could cause problems for anyone applying the May Update. As of today, July 1, there remain a number of officially acknowledged, unresolved issues with Windows 10 2004. 

Among the problems listed under “investigating” include an issue with older NVIDIA display adapters; stop errors when plugging or unplugging a Thunderbolt dock; issues during or after updating devices with Conexant ISST audio drivers; difficulty connecting to more than one Bluetooth device; and variable refresh rates not working as expected with Intel iGPU. There also have been issues with 2004 and Storage Spaces, Microsoft’s RAID-like data protection software, which resulted in Microsoft putting a compatibility hold on 2004. (The Storage Spaces issue isn’t listed on the Release Information page for some reason.)