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

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.

Welp there goes my idea to get a new Intel powered laptop.

Hello as of this posting my lappy with windows 10 is updating and it has been almost 2hours and still it is only 20% complete. I have good internet connection. Can you make an update that is faster and quick to finish? My lappy is two months old. Im really tired waiting.man this would take forever to finish. And this is not the first time.

Mr. Greetz,

You were exactly right everything it's the matter of timing. I was just totally unlucky to have bought a brand new computer right a week or two before a major version update and Microsoft messed up my brand new computer without thoroughly check on the compatibility with the hardware beforr automatically roll out version 1803.  It wasted millions of users tenth of thousands of hours to reinstall and recover to the previous built of windows 10.

Hello all,

In the afternoon of 29th of June my Windows update came up with the 1803 upgrade package automatically. The installation went pretty fast, I guess it was done in about half an hour all together. I didn't use my laptop very much since the 29th, but it seems everything works as it should. So as far as I can see the problem is fixed now (fingers crossed). I am on version 1803 build 17134.137 and my Windows update states I am fully up to date.

So my first guess was right after all, just wait! I did nothing more after the first corrupted upgrade failed to install. I didn't pause Windows updates or alter any standard setting after the first upgrade failed. Installation was cancelled at 49% automatically, afterwards the ugrade was paused and lateron even removed from Windows updates, all automatically.

No offence, but I did not follow one well-meant advice which was given to me here or in another thread on this forum. Such major faults are most of the time resolved aftwerwards by Microsoft and/or hardware manufacturers, because of the many systems concerned. However it was pretty careless to release the faulty upgrade which in my case luckily was blocked automatically so I didn't have to 'roll back' to version 1709.

Greetz, Master