Devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may crash and enter a UEFI screen after reboot when upgrading to Windows 10 April 2018 Update

Question

When attempting to upgrade to the Windows 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may crash and enter a UEFI screen after reboot.

Microsoft is working with OEM partners and Intel to identify and block devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series from installing the April 2018 Update due to a know incompatibility that may cause performance and stability issues.  If you have encountered this issue, follow the steps to reinstall the previous operating system (Windows 10, version 1709).

Microsoft is currently working on a resolution that will allow the April 2018 Update on these devices in the near future.

Update (6/22/18):

Microsoft has included a solution for this issue in the May 23, 2018 Cumulative Update (KB4100403).  This solution prevents the issue from occurring when installing the April 2018 Update.  Please note that this solution does not restore systems that have already experienced the issue and are currently booting to a UEFI screen.  Any devices already impacted should still follow steps to reinstall the previous operating system (Windows 10, version 1709).  Any devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series that have installed the June 12, 2018 Cumulative Update (KB4284835) will no longer be blocked from installing the April 2018 Update.

Answer 1

Update (6/22/18):

Microsoft has included a solution for this issue in the May 23, 2018 Cumulative Update (KB4100403).  This solution prevents the issue from occurring when installing the April 2018 Update.  Please note that this solution does not restore systems that have already experienced the issue and are currently booting to a UEFI screen.  Any devices already impacted should still follow steps to reinstall the previous operating system (Windows 10, version 1709).  Any devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series that have installed the June 12, 2018 Cumulative Update (KB4284835) will no longer be blocked from installing the April 2018 Update.

To get the Windows 10 April 2018 Update (version 1803), we encourage you to wait until the update is offered to your device. If you’re an advanced user on an actively serviced version of Windows 10 and would like to install the Windows 10 April 2018 update now, you can manually check for updates.  In the Search tab, type “Settings”. On the Settings page, navigate to Update & security > Windows Update > click “**Check for updates”,**which **** will include this resolution.

Answer 2

Not sure what you mean by resolved. My computer is still stuck on the choose keyboard rotary. Are you saying I can now download this solution on another pc, copy to flash drive, and boot my computer that’s been bricked? That would be nice. Nice if Microsoft notified their victims that after a week we can have our computers back...with Office free for life!

Answer 3

This issue has now been resolved in KB4100403.

To get the Windows 10 April 2018 Update (version 1803), we encourage you to wait until the update is offered to your device. If you’re an advanced user on an actively serviced version of Windows 10 and would like to install the Windows 10 April 2018 update now, you can manually check for updates.  In the Search tab, type “Settings”. On the Settings page, navigate to Update & security > Windows Update > click “**Check for updates”,**which **** will include this resolution.

Will the fixed version also be available via download (iso) and MCT? I think this is very important for the users because the affected devices are often hardly bootable.

Answer 4

Since my blue screen experience with april spring update, I went back to 1709 version a I defered feature updates for 60 days. I will wait on this repair to be tested by someone else and then I will install it on my brand new HP 470 G5 laptop. Can't afford suprises anymore.

Answer 5

I agree with Jameskingca, you say it's resolved but I still can't update to 1803 either.  Maybe Microsoft should start over and try again!