Surface Pro 3

Blue Screen Crash on Surface Pro 3 with wificlass.sys


Microsoft Communities users are reporting a blue screen crash in wificlass.sys in a growing thread:


As yet, there is no official participation from office Surface support.

I’m wondering how many people are afflicted with this issue. If you are experiencing this, please post in the thread above and also tweet @barbbowman.

How to Manually Install the July Surface Pro 3 Firmware Updates


Updated Jul 27, 2014

I’ve been seriously afflicted by the Wi-Fi connectivity issues on the Surface Pro 3 and have been considering returning to Best Buy as their short 15 day return window expires Friday. Microsoft states that the firmware updates are being throttled and to keep checking Windows Update. I checked and checked and checked and after 18 hours didn’t have the luxury of waiting for the throttled updates to show up as I wanted time to test these fixes.

Microsoft posted the complete SP3 driver/firmware pack overnight so decided to install what I needed manually. For the convenience of others similarly afflicted by the missing throttled update, here are instructions to use at your own risk. I can’t officially support you. Reboot when you are prompted. Keep your fingers crossed throughout.

Here are the instructions:

1. Manually check for updates and install anything offered before beginning.

2. Make sure your Surface Pro 3 is fully charged and plugged in.

3. Go to and download Surface Pro 3 – 16 July (168.0 MB) . You will need to scroll the list to find it.




4. Click Next and download to your hard drive.

5. Extract the Surface Pro 3 – 16 July and open it.

Note as shown below the files named Marvell and Microsoft. These are the two folders containing the bits you need to manually install the firmware and drivers made available via Windows Update to some users on July 8 and which are slowly being rolled out according to Microsoft.



6. Open The Microsoft Folder. The FW, SurfaceTypeCoverV3FwUpdate (if you bought a new SP3 type cover)and SurfaceAccessoryDevice folder are the ones you will be using.

7. Open the SurfaceTypeCoverV3FwUpdate folder, right click on the inf file and select install

8. Open the SurfaceAccessoryDevice folder, right click on the inf file and select install



9. Now open the FW folder

10. Open the EC folder, right click the inf file and install. Reboot if prompted.

11. Open the SAM folder, right click on the inf file and install. Reboot if prompted.



12. Navigate to the Marvell folder.

13. Open the BT folder, right click the inf file and install

14. Open the wlan folder, right click the inf file and install


15. Reboot (maybe reboot twice for insurance).


Best of luck!

Surface Pro 3: Connected Standby is Disabled When Hyper-V is Active


Microsoft has released a “bleeding edge” Surface Pro 3 designed to replace both a laptop and a tablet. Early reviews are mostly positive. A few negatives are emerging, including an incompatibility between Connected Standby and Hyper-V.

While Connected Standby has been a feature of phones and devices like the Nokia Lumia 2520 RT tablet, this is the first time this technology has appeared in an Intel non Atom x86 device. The Surface Pro 3 is the only Surface “Pro” device that supports Connected Standby. Surface Pro (original) and Surface Pro 2 do not support this power management protocol. For Windows Phone developers who wish to use Visual Studio 2013 with the phone emulator, this might be problematic as the emulator uses the Hyper-V functionality. If you install Visual Studio 2013, Connected Standby is no longer operational. Developers who install Visual Studio 2013 may notice that after installing VS 2013 that their Surface Pro is no longer performing in the same manner with respect to power management and resume from sleep and that Connected Standby no longer works.

Bottom line: this occurs because Connected Standby is not supported on a system running Hyper-V virtualization.

A current work-around to restore Connected Standby functionality is to use BCDEDIT to turn Hyper-V off when not needed and on again when you need to use the VS 2013 emulator to test Windows Phone Applications. If you are not developing phone apps, you can turn Hyper-V off and leave it off.


Steps to Turn Off Hyper-V:

1.If you have installed Visual Studio 2013, verify that Connected Standby is on or off by opening an administrative command prompt and typing

powercfg /a


As you can see in the screen capture below, Standby (Connected) is NOT supported. (The entry" The  hypervisor does not support this standby state" indicates that Hyper-V is active and the Connected Standby is not available).


hyperv enabled


2. Turn Hyper-V off by typing the following into the command window:

bcdedit /set hypervisorlaunchtype off


3. Restart your Surface Pro 3 (You must restart for the new configuration to become active)

After the Surface Pro 3 has been restarted, Connected Standby should be active again. You can check this by opening an administrative command prompt and typing

powercfg /a


As you can see, Standby (Connected) is now available which is the default configuration for Surface Pro 3.




When you need to enable Hyper-V, you can easily make it active again.


Steps to turn on Hyper-V:

1. Open an administrative command prompt and type:

bcdedit /set hypervisorlaunchtype auto 

2.  Restart your Surface Pro 3

After restarting, Hyper-V will again be active (and Connected Standby will no longer function). You will be able to use the Phone Emulator in Visual Studio 2013.

Windows 10 users: Read this blog with my PWA (Progressive Web App) from the Windows Store

Read this blog with my Windows 8 App

Get the App