9/29/2015 firmware caused wifi "device cannot be started"

Anonymous

Split from this thread.

I have no idea what the update contained, other than the fact that it totally hosed my wifi. Device manager reports that the "device cannot be started". Wonderful.

Is it possible to go back to an older firmware version? If so, how?

How does something like this happen when a single company has complete control of both hardware and software? A complete lack of ability to execute a product, in my opinion.

Unbelievable, Microsoft!

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

Answer accepted by question author

Anonymous

On Mon, 5 Oct 2015 02:44:21 +0000, Arnold001 wrote:

>>I know that there was an update on Sept 30, and I find the coincidence too great that suddenly I got device error messages then and now my WiFi devices don't work. Is there a fix coming?

If you've rebooted twice and there is no change, right now the fix is to do a

System Restore back to before this firmware update was installed.

Edit 10/06/2015: Two people have reported in that uninstalling Kaspersky fixes their issue.

__________________________________________________________________________________________________

Barb

Windows Experience MVP

My Blog - http://digitalmediaphile.com/

Please mark as answered if this answers your question

0 comments

Answer accepted by question author

Anonymous

Hey all,

Thanks for sharing the details regarding your experiences with the Surface Firmware Update from 9/29. Barb Bowman already mentioned to perform two (2) restarts so I'm just adding a little bit more to her advice (thanks Barb).

MODERATOR EDIT (10/6/2015): I am adding/updating steps to help address Wi-Fi availability after taking the 9/29/2015 Surface Firmware Update.

Step 1 – System Restore Point

1. After Windows Update install, Surface will automatically request a restart (not shutdown).

2. After Surface restarts, sign in and perform another restart (not Shutdown) to finish installing the update. Press the Windows Start Menu, press Power and select Restart.

3. After Surface restarts, sign in and see if you can now connect to your Wi-Fi network.

If you are able to connect to Wi-Fi, no additional steps are needed. If you are not able to connect to Wi-Fi then go to step 2 below.

Step 2 – Uninstall the Wi-Fi Driver

1. Right-click the Windows Start Menu and click Device Manager.

2. Double-click on Network Adapters to expand the list of network adapters.

3. Double-click on the Marvel AVASTAR network adapter.

4. Click on the Driver tab.

5. Click Uninstall.

6. Make sure that “Delete the driver software for this device” is not checked. Click OK.

7. Click the Action menu and click Scan for hardware changes.

8. Restart (not Shutdown) Surface. Press the Windows Start Menu, press Power and select Restart.

If you are able to connect to Wi-Fi, no additional steps are needed. If you are not able to connect to Wi-Fi then go to step 3 below.

Step 3 – System Restore Point

1. Boot Surface using USB recovery media. If you do not have recovery media you can download from here: http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/downloadablerecoveryimage. Once you have recovery media proceed to next steps. Note: The USB drive must be formatted to FAT32 (not NTFS) in order to work correctly.

2. Press and hold the volume-down button while you press and release the power button. When the Surface logo appears release the volume-down button.

3. When prompted select the language and keyboard layout you want.

4. Select Troubleshoot, then Advanced Options, followed by selecting System Restore then select the target operating system.

5. In System Restore, click Next.

6. Click on a system restore point that was prior to applying the System Firmware update. Please use a restore point 9/28 or earlier.

7. Click Next.

8. Click Finish.

9. Click Yes when asked if you want to continue.

10. After moving to an earlier restore point you should boot into Windows.

If you are able to connect to Wi-Fi, no additional steps are needed. If you are not able to connect to Wi-Fi then go to step 2 below.

Step 4 – Reset Surface to factory settings

1. Follow the steps in the article below to boot Surface using USB recovery media and reset Surface back to factory settings:

http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/usbrecovery

As always, if this information doesn't address the missing WiFi scenario we want to hear from you.

Thanks,

Josh

P.S. We are working to manage your feedback and experiences with the blue screen after update here: https://answers.microsoft.com/en-us/surface/forum/surfpro3-surfusingwin10/repeated-bsod-after-firmware-update-surface-pro-3/529a1da2-3657-43f9-9af1-81c183650ce4. Please post comments on the blue screen scenario in that thread.

0 comments

155 additional answers

Anonymous

2015-10-07T18:45:15+00:00

Split from this thread.

Since I am soon leaving a trip, and my SP3 had tried and failed to install both the 9/29 firmware update and KB3093266, I was a bit uneasy about taking it with me, as I need something reliable to keep in touch with business communication.

It had tried to do the firmware update on Oct. 5, and (apparently) failed, but upon rebooting, wifi and Bluetooth didn't work. I uninstalled the Marvell adapter from device manager, and it almost immediately connected and both were working again. I had to re-enter my wifi passcode so I know something had been done.

However, thinking of the update trying to install while I'm traveling was not acceptable, so I removed the cab file for the KB....3266 update from Windows\Software Distribution\Download. Couldn't find anything I could identify as the firmware update files, even looking by date, so gave up looking for that one. My thinking was that if the update HAD been pulled, that it couldn't do much without the files.

But it started downloading (or claimed to have) the KB...3266 file again, and said there was also a firmware update pending, so I went for the next option, system restore before 9/29. However, since I don't use the SP3 at home, my only option was for August 18, which I did.

It did the restore OK, and updated, but it's still trying to do the KB 3093266 update (and failing). At least it's not trying to do the 9/29 firmware update (it did the 9/15 one OK).

NOW the dilemma: I had uninstalled Stardock Start8 a day or so AFTER the 8/18 restore point, so after system restore, it showed again in the start menu and programs/features. However, it now won't uninstall, though it appears to not be running. I can't reinstall and uninstall, because it wont install due to being supposedly incompatible with Win10 (it actually worked fine, I just didn't need it). I can delete the files, of course, but I imagine the registry entries are still there, and the thought of searching and deleting all of them doesn't set well.

The SP3 was working OK prior to this, other than the firmware and KB updates failing, and I can still undo my last system restore and return to where I was. With both the firmware and KB updates wanting to install themselves. Am I better off leaving it as-is, with the Stardock uninstall in limbo, or going back to the latest and hoping the updates don't mess things up? Or taking my big Toshiba laptop which I didn't want to lug along, because it's big. (but it works, and very nicely with Win7...thankfully I was able to disable the Win10 update and nag).

I see some poor guy has left with a business presentation on his SP3, which now doesn't work because of this, and I'm wondering how on earth Microsoft came up with the idea of not letting ANYONE disable the updates. We're not all bozos; make it difficult, buried somewhere in complex settings, make it powershell accessible only, but let us choose whether we want to risk updates while traveling!!! Or at least let us disable specific updates if we want. This is ridiculous, to where I've wondered if I could divert all update downloads using the host file, or some other means of making it not able to connect to windows update (then re-edit the host file to allow at a time when it's not so critical).

Kind of ironic to have to take my Toshiba laptop with me, because I can't trust the Surface Pro to keep working during the trip, having bought it so I'd have a compact device to take with me instead of the bulky Toshiba.
Was this answer helpful?

0 comments No comments
Anonymous

2015-10-07T18:58:51+00:00

I have a Surface 3 that I am taking on an overseas trip. I hear your pain. I am going to make EVERY network connection be seen as metered in order to ensure that no updates come down during my trip.

You can even disable [gawd can't believe I am saying that] the Windows update service while you are travelling.

http://www.askvg.com/fixing-windows-10-automatic-updates-install-problem/ << take a look at that post for lots and lots of options.

Bottom line don't grab the laptop, use these to make you feel comfortable traveling with Windows 10.
Was this answer helpful?

0 comments No comments
Anonymous

2015-10-07T19:02:32+00:00

http://www.askvg.com/forcing-windows-10-to-always-notify-before-downloading-updates/ <<< that one in particular

Solves the problem. You get notified before a download occurs. Yes you have to use the registry but it's certainly doable and gives you back trust in your device as well as allowing you to update when you want to update.
Was this answer helpful?

0 comments No comments