{"id":1202,"date":"2015-10-03T17:20:41","date_gmt":"2015-10-03T21:20:41","guid":{"rendered":"https:\/\/digitalmediaphile.com\/?p=1202"},"modified":"2015-10-05T16:34:04","modified_gmt":"2015-10-05T20:34:04","slug":"recovery-from-windows-10-surface-pro-3-firmware-update","status":"publish","type":"post","link":"https:\/\/digitalmediaphile.com\/index.php\/2015\/10\/03\/recovery-from-windows-10-surface-pro-3-firmware-update\/","title":{"rendered":"Recovery from Windows 10 Surface Pro 3 Firmware Update"},"content":{"rendered":"

 <\/p>\n

I had a bad experience with the September 29 firmware update for the Surface Pro 3 (bot not as bad as some). Unlike many other folks, my own wireless connectivity and speeds have been great with Windows 10, including using the .193 Marvell wireless driver. That was not the case for many, and a fix for some was to find the older .151 driver on the net and roll back to that. Or to use an external 802.11ac USB adapter (as I mentioned in a previous post).<\/p>\n

The 9\/29 firmware was unexpected as there had been one on 9\/15. I installed it and rebooted and the wireless was MIA. I rebooted a second time and had connectivity, but it was intermittent, slow, and unreliable. Fortunately, I had the older zip files and drivers and was able to re-install the .193 driver and regain my great connectivity.<\/p>\n

But this was not the case for others. Reports started appearing on the Surface Answers Forum and customers were reporting loss of wireless, BSOD loops and failed firmware updates in Windows Update history.<\/p>\n

I sent emails to Microsoft on the issues and was forwarding threads for several days. The update was pulled on Friday I believe<\/del> (Edit 10\/5\/2015<\/strong>: I’m told it was pulled on 10\/1, but if the computer has already pulled it down from WU, it can install anytime up to 10 days later<\/strong><\/em>). Customers are reporting<\/a> getting hosed again but the update was probably already on their system awaiting installation<\/strong>.<\/em>\u00a0 A couple of bad files were posted for SP3\/W10 \u2013 both a zip and MSI file \u2013 neither of which contain wireless or bluetooth drivers for the SP3. This means there are no drivers posted on Microsoft\u2019s site officially for Surface Pro 3 owners running Windows 10. I\u2019ve always thought (and asked) that Microsoft should post all the drivers and leave older drivers available for those that need them.<\/p>\n

Word came down that doing a system restore should get people up again followed by running the MSI to get the firmware\/drivers installed, and the Forum owner posted that after doing a system restore, running the MSI file would take care of the issues. This has not been the case for many. And even getting to System Restore has been a problem for some.<\/p>\n

Microsoft posted two files for 9\/29. I looked inside and there are NO drivers for wireless or bluetooth. As of right now, https:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=38826<\/a> has two files you should not<\/strong> use:<\/p>\n

 <\/p>\n

\"badfirmware\"<\/p>\n

Here\u2019s the best fix (minus the step to run the MSI) to get out from under the BSOD groundhog day issue if you are still impacted AND can get to System Restore or if you are having issues after this firmware update:<\/p>\n

\u201c1.Boot Surface using USB recovery media.\u00a0 If you do not have recovery media you can download from here:\u00a0 http:\/\/www.microsoft.com\/surface\/en-us\/support\/warranty-service-and-recovery\/downloadablerecoveryimage<\/a>.\u00a0 Once you have recovery media proceed to next steps.
\n2.Press and hold the volume-down button while you press and release the power button.\u00a0 When the Surface logo appears release the volume-down button.
\n3.When prompted select the language and keyboard layout you want.
\n4.Select Troubleshoot, then Advanced Options, followed by selecting System Restore then select the target operating system.
\n5.Use a system restore point prior to applying the System Firmware update.\u00a0<\/del> Edit 10\/5\/2015<\/strong>: Be sure to use a restore point 9\/28\/2015 or earlier.<\/strong><\/span>
\n6.After moving to an earlier restore point you should boot into Windows.\u201c<\/p><\/blockquote>\n

If you can\u2019t get to restore or don\u2019t have a restore point, it is going to get ugly. I already see this on the Answers Forum. I don\u2019t have a magic bullet and I don\u2019t know if Microsoft is working over the weekend on this.<\/p>\n","protected":false},"excerpt":{"rendered":"

  I had a bad experience with the September 29 firmware update for the Surface Pro 3 (bot not as bad as some). Unlike many other folks, my own wireless connectivity and speeds have been great with Windows 10, including using the .193 Marvell wireless driver. That was not the case for many, and a […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[140],"tags":[286,228,232],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":6}},"jetpack_publicize_connections":[],"featured_image_urls":{"full":"","thumbnail":"","medium":"","medium_large":"","large":"","1536x1536":"","2048x2048":""},"post_excerpt_stackable":"

  I had a bad experience with the September 29 firmware update for the Surface Pro 3 (bot not as bad as some). Unlike many other folks, my own wireless connectivity and speeds have been great with Windows 10, including using the .193 Marvell wireless driver. That was not the case for many, and a fix for some was to find the older .151 driver on the net and roll back to that. Or to use an external 802.11ac USB adapter (as I mentioned in a previous post). The 9\/29 firmware was unexpected as there had been one on 9\/15.…<\/p>\n","category_list":"Surface<\/a>","author_info":{"name":"Barb","url":"https:\/\/digitalmediaphile.com\/index.php\/author\/barb\/"},"comments_num":"0 comments","jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pvFKI-jo","jetpack-related-posts":[],"_links":{"self":[{"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/posts\/1202"}],"collection":[{"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/comments?post=1202"}],"version-history":[{"count":0,"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/posts\/1202\/revisions"}],"wp:attachment":[{"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/media?parent=1202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/categories?post=1202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/digitalmediaphile.com\/index.php\/wp-json\/wp\/v2\/tags?post=1202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}