{"id":12265,"date":"2018-05-11T06:30:15","date_gmt":"2018-05-11T14:30:15","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/05\/11\/news-6034\/"},"modified":"2018-05-11T06:30:15","modified_gmt":"2018-05-11T14:30:15","slug":"news-6034","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2018\/05\/11\/news-6034\/","title":{"rendered":"Surface Pro (2017) owners hitting Win10 1803 update blue screens. Now we know why."},"content":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Fri, 11 May 2018 06:43:00 -0700<\/strong><\/p>\n

As Win10 version 1803 rattles through the unpaid beta-testing phase, it\u2019s snagged another victim \u2014 Intel\u2019s aging SSD6 solid-state drives. Both Microsoft and Intel now admit that running Win10 version 1803 on Intel 600p or Pro 6000p is a recipe for disaster.<\/span><\/p>\n

Some Surface Pro (2017) models ship with \u201cbad\u201d Intel SSD Pro 6000p drives. Customers are complaining about freezes with Win10 version 1803 \u2014 and the Microsoft support folks don\u2019t have a clue what\u2019s causing the problem. Now we know.<\/span><\/p>\n

Here\u2019s how the drama unfolded.<\/span><\/p>\n

Win10 version 1803 has been in beta testing for centuries, in internet time. The \u201cfinal\u201d version, build 17134.1, entered the Windows Insider Fast ring almost a month ago, on April 16. In a jumble of mixed-up build numbers, Win10 version 1803 has been officially pushed since April 30. Why did it take so long to figure out that the 600p and Pro 6000p cause problems?<\/span><\/p>\n

Surely somebody at Microsoft and some other body at Intel must be testing these things, right? Shirley.<\/span><\/p>\n

Some Surface Pro (2017) computers ship with Intel SSD Pro 6000p drives. Shirley somebody at Microsoft tested those, too, didn\u2019t they? <\/span><\/p>\n

It’s hard for me to imagine Microsoft shipping the new version of Win10 without testing it on the latest Surface Pro 2017 devices. I mean, c’mon. We aren’t talking rocket science here.<\/span><\/p>\n

I first <\/span>heard about the problem<\/span><\/a> on May 7, when a \u201cMicrosoft Agent\u201d (love that term) named Lonnie_L posted on the MS Answers forum:<\/span><\/p>\n

When attempting to upgrade to Window 10 April 2018 Update select devices with certain Intel SSDs may enter a UEFI screen reboot or crash repeatedly.<\/span><\/p>\n

Microsoft is currently blocking some Intel SSDs from installing the April 2018 Update due to a known incompatibility that may cause performance and stability issues. There is no workaround for this issue. If you have encountered this issue, you can roll back to Windows 10, version 1709 and wait for the resolution before attempting to install the April 2018 Update again.<\/span><\/p>\n

Microsoft is currently working on a solution that will be provided in a near future Windows Update, after which these devices will be able to install the April 2018 Update<\/span><\/p>\n

Yesterday, May 10, I received a nudge from a Microsoft PR person, pointing to the <\/span>same Answers forum post<\/span><\/a>. It\u2019s been modified to say:<\/span><\/p>\n

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 \u00a0reboot.<\/span><\/p>\n

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 <\/span>reinstall the previous operating system<\/span><\/a> (Windows 10, version 1709).<\/span><\/p>\n

Microsoft is currently working on a resolution that will allow the April 2018 Update on these devices in the near future.<\/span><\/p>\n

Looking at the post, you\u2019d have no way to know when or how it was modified. Commenting on the topic has always been shut off. See how that works?<\/span><\/p>\n

So now we know that the 600p SSDs don\u2019t like Win10 version 1803. It took Microsoft eight days to acknowledge the problem, and two more days to spill the beans about which drives aren\u2019t copacetic. <\/span><\/p>\n

But the drama doesn’t stop there. Surface Pro (2017) owners have been complaining about blue screens when they try to upgrade to Win10 version 1803. For example, on May 6, eljeffe58 posted this on the <\/span>MS Answers forum<\/span><\/a>:<\/span><\/p>\n

I just got a SP 2017 at Best Buy. I returned the first one cuz after she updated to build 1803 I could not escape BSOD’s. I returned her after a few days and the new one has the same thing. I restored back to the 1709 she came with and will try not to let her update until a new update supersedes the 1803 mess. I also could not get the update downloads to easily complete without running the fix it troubleshooter and\/or just rebooting. A real mess if you ask me. I love the SP 2017 but hate the updates and really hate a BSOD at work in the middle of helping a client.. Thanks. <\/span><\/p>\n

Later in the thread, eljeffe58 says his brand-spanking-new Surface Pro 2017 has an . Intel SSDPEBKF128G7 SSD. BCVHOG says he has an SSDPEBKF256G7. Both of those model numbers are Intel Pro 6000p SSDs.<\/span><\/p>\n

That\u2019s not the worst of it. Microsoft\u2019s tech support on that thread hasn\u2019t helped one whit. On May 9, eljeffe58 reports that he received a Service Request number from Microsoft Surface Technical Support about \u201cthe BSOD that the Surface devices with i5 processor are experiencing with the new Windows version 1803.\u201d<\/span><\/p>\n

You don\u2019t say.<\/span><\/p>\n

At least the bug notification now appears on the official <\/span>build 17134.48 page<\/span><\/a>. Wonder when that was changed?<\/span><\/p>\n

Just bought a Surface Pro 2017? Gotcha. Join us on the <\/span><\/i>AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n

http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: Woody Leonhard| Date: Fri, 11 May 2018 06:43:00 -0700<\/strong><\/p>\n

\n
\n

As Win10 version 1803 rattles through the unpaid beta-testing phase, it\u2019s snagged another victim \u2014 Intel\u2019s aging SSD6 solid-state drives. Both Microsoft and Intel now admit that running Win10 version 1803 on Intel 600p or Pro 6000p is a recipe for disaster.<\/span><\/p>\n

Some Surface Pro (2017) models ship with \u201cbad\u201d Intel SSD Pro 6000p drives. Customers are complaining about freezes with Win10 version 1803 \u2014 and the Microsoft support folks don\u2019t have a clue what\u2019s causing the problem. Now we know.<\/span><\/p>\n

Here\u2019s how the drama unfolded.<\/span><\/p>\n

Win10 version 1803 has been in beta testing for centuries, in internet time. The \u201cfinal\u201d version, build 17134.1, entered the Windows Insider Fast ring almost a month ago, on April 16. In a jumble of mixed-up build numbers, Win10 version 1803 has been officially pushed since April 30. Why did it take so long to figure out that the 600p and Pro 6000p cause problems?<\/span><\/p>\n

To read this article in full, please click here<\/a><\/p>\n<\/section>\n<\/article>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[11062,10643],"tags":[714,10525],"class_list":["post-12265","post","type-post","status-publish","format-standard","hentry","category-computerworld","category-independent","tag-security","tag-windows"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/12265","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=12265"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/12265\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=12265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=12265"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=12265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}