One user claims that the update finally showed up on the Surface Laptop, which we already know was on the block list, among other devices.
No issues with build 1803 (I updated as soon it was released.) It didn’t even know there were issues with Intel SSDs and I even have BitLocker enabled. Everything works.
KB4103721 triggered the problem
Many users suggested that update KB4103721 caused the compatibility issues between Intel SSD machines and the April Update.
Just to refresh your memory, here’s what Microsoft posted on the company’s support page about the May 8, 2018—KB4103721 (OS Build 17134.48):
- The issue that used to cause some devices to stop responding or working when using apps, such as Chrome or Cortana after installing Windows 10 April 2018 Update was fixed.
- The problem that prevented some VPN apps from working on builds of Windows 10, version 1803 was also fixed.
- Problems involving updated time zone data were resolved as well.
- The issue that might have caused an error when connecting to a Remote Desktop server was fixed.
- The build includes security updates for Windows Server, Microsoft Edge, Internet Explorer, Microsoft scripting engine, Windows app platform and frameworks, Windows kernel, Microsoft Graphics Component, Windows storage and filesystems, HTML help, and Windows Hyper-V.
Known issues triggered by KB4103721
Among the problems that are triggered by the update, Microsoft noted that:
When attempting to upgrade to the Window 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may repeatedly enter a UEFI screen after restart or stop working.
The company also provides the workaround, saying that they’re working together with OEM partners and Intel in order to identify and block devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series from installing the April 2018 Update.
Well, judging by user reports, it seems that Microsoft managed to fix this problem.
The company has yet to officially confirm the information, so this also leads to a new conclusion: perhaps Microsoft experimentally pushed the hotfix to a few users so as to make sure that it actually works.
RELATED STORIES TO CHECK OUT: