Ill redownload it but Im pretty sure I have the right one......and after that, I think its pretty easy...just navigated to the right folder...so I went to the MARVELL folder, then 8.1 then WLANYou must have done something wrong, the wireless driver in that package is "DriverVer=06/03/2014,15.68.3042.79". At least for the "Surface Pro 3 - July 2014.zip" file... did you download the wrong one perhaps?
http://blogs.technet.com/b/deployme...ying-drivers-and-firmware-to-surface-pro.aspx
Use that guide to install your drivers/firmware.
Couple notes on the above guide;
-> 1. Execution policy for powershell scripts needs to be changed to Unrestricted for this to run.
-> 2. If you see Access is Denied messages it is because you didn't run as administrator.
-> 3. Not all drivers will install in that package so don't freak out if you see that occur.
-> 4. If you see a pause during the script execution, try and press enter.
-> 5. Once you run through this, a reboot is required although not prompted. When you reboot you will get the traditional a system update is being applied message. When I did this I heard my fan kick up speed. After reboot, I checked some of my drivers firmware and the wireless as an example has a date of 6/3 which is the official latest now.
All that said, I'm seeing an improvement on stability of the connections with both Bluetooth and Wireless N as to similar to what I had on my Surface Pro 1st Generation.
You must have done something wrong, the wireless driver in that package is "DriverVer=06/03/2014,15.68.3042.79". At least for the "Surface Pro 3 - July 2014.zip" file... did you download the wrong one perhaps?
http://blogs.technet.com/b/deployme...ying-drivers-and-firmware-to-surface-pro.aspx
Use that guide to install your drivers/firmware.
Couple notes on the above guide;
-> 1. Execution policy for powershell scripts needs to be changed to Unrestricted for this to run.
-> 2. If you see Access is Denied messages it is because you didn't run as administrator.
-> 3. Not all drivers will install in that package so don't freak out if you see that occur.
-> 4. If you see a pause during the script execution, try and press enter.
-> 5. Once you run through this, a reboot is required although not prompted. When you reboot you will get the traditional a system update is being applied message. When I did this I heard my fan kick up speed. After reboot, I checked some of my drivers firmware and the wireless as an example has a date of 6/3 which is the official latest now.
All that said, I'm seeing an improvement on stability of the connections with both Bluetooth and Wireless N as to similar to what I had on my Surface Pro 1st Generation.
Yeah, come on Microsoft! We waited patiently for this update. Now please let us all have it, LOL.No update. WTH?
It's a shame that MS doesn't test important things like WiFI before they start selling a new product. My IT manager has been teetering on replacing our laptop users with SP3s, but he gave me this article about all the WiFI problems and is asking me if I thought it was still safe to consider their purchase. Naturally, I'm biased, having been supportive of the Surfaces since day one and I'm also anxious to start supporting them here where I work. This crazy stuff probably really hurts MS chances of the Surface computers being purchased by corporate.
I believe they do it staggered for a couple of reasons....
1 - There is no way to test an specific update against all of the varying configurations in the PC World, MS Employee Dog-fooding is still fairly homogenous - so a Staggered Release gives them the ability to pull back before impacting the whole install base (lesson learned after the infamous December Firmware of the SP2)
2 - The Staggered Release allows for faster downloads once all of the staging servers have the update....
This is pure speculation on my part....
I believe they do it staggered for a couple of reasons....
1 - There is no way to test an specific update against all of the varying configurations in the PC World, MS Employee Dog-fooding is still fairly homogenous - so a Staggered Release gives them the ability to pull back before impacting the whole install base (lesson learned after the infamous December Firmware of the SP2)
2 - The Staggered Release allows for faster downloads once all of the staging servers have the update....
This is pure speculation on my part....