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

Anonymous
2018-05-08T00:51:33+00:00

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.

0 comments

114 answers

Sort by: Newest
Most helpful Newest Oldest
  1. 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

  2. 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

  3. Anonymous
    2018-07-22T18:03:51+00:00

    Unless consumers are willing to buy new computers every year, Microsoft, you need to give people an option to update of not. I was told that Microsoft doesn't really plan on releasing any more Windows version, so Windows 10 with updates is it. If this is true, then Microsoft needs to stop releasing updates that damage computers. My Asus cpu has now been in for repairs more times this year than my car has. I've lost my hard drive, I've lost my graphics card, and I have absolutely no guarantees that this won't happen again. I'm seriously looking into buying a Mac. My laptop with Windows 7 works just fine without issues. Its old and slow but I'm not willing to upgrade it to a newer model if all I can get is Windows 10.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-07-22T17:08:41+00:00

    Last Friday we acquired a SurfacePro i5/8GB/256GM. Started the win update process fine at first.

    Then: Installation failed, 0x80240034 of 2018-07 Cumulative update for Win v1709 for x64 (KB4338825). I was not able to update to win 1803.

    SSD is a Toshiba KBG30ZPZ256G.

    During the failing update processes I notice that there is a lot of writing/reading going on to the SSD, latency times over 500 sometimes even 600ms.

    How to proceed?

    Kind regards Jetze Posthuma

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. 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