I won't update this until it's been tested like 1000times and made sure there isn't any problems.
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.
Windows for home | Windows 10 | Install and upgrade
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
114 answers
Sort by: Oldest
-
Anonymous
2018-05-29T07:20:19+00:00 -
Anonymous
2018-05-29T19:28:08+00:00 we have received in the last 10 days more than 12 PC stucked in a way or another after the update.
The worst case was a PC wit ADATA SSD su700 that had the firmware deleted.
Start the update,
after reboot is going straigth to UEFI
looking at boot device the disk is now recognized has generic FCR sata loader device capacity 4Mb,
connected the disk to another PC same issue
the tool to upload the firmware doesn't recognize the device as an ADATA product, so no way to reload the firmware
In conclusion the disk is bricked, can you explain how I can apply the patch.
for us is nice to have a lot of work to invoice, but I not happy that my customer having problem like those
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2018-06-01T04:52:22+00:00 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.
I wouldn't recommend attempting the update at all at this stage, even with this "fix". It seems KB4100403 is a fix ONCE 1803 is installed, which, if you have an Intel SSD (I have a brand new Surface Pro) means you will end up with issues before you can get a chance to get KB4100403. Surely you would have pushed that KB4100403 into the 1803 in some fashion and/or a preliminary patch to avoid errors getting 1803 installed?
My experience over the past 2 weeks- https://answers.microsoft.com/en-us/surface/forum/surfpronew-surfupdate/windows-10-version-1803-wont-install-on-new/59d85a0c-a106-4616-a125-ade69903ed95
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more