Thank you - it worked for me. This is now the 3rd time this happened to me just after a microsoft 'update'. I don't usually re-start the surface just because of an update. 'But' when there is an update that blows the wifi out, one is forced to do a re-start (after deleting the Marvell driver). So what happens if I decide I don't want any more updates bloating my surface because it's running just fine? I did that on an XP machine for almost two years with no problems. Curious ain't it?
Definitely curious - however, as annoying as those updates are, Microsoft is constantly patching vulnerabilities which is why I would recommend keeping up to date with them. It is definitely a pain, but the end definitely justify the means in this situation. If I had to guess - this is a hardware and device driver issue. It is very disappointing.
Invested over 90 minutes with Microsoft Surface Pro Technical Support... only to conclude you have a hardware problem (please spend $320.00). Well the recommendation to Uninstall the Marvell AVARSTAR wireless software was 100% correct. Removed driver, restarted Surface Pro 2, Re-Installed Marvell AVARSTAR driver s/w and everything worked... cleared the error and the Wireless appears. Thank you.
Wow some nerve they have saying it is hardware. I haven't had the problem since another recent windows update. Like 4-5 batches back. I strongly believe this is all driver related. To further my point, I used to be able to tether my android with my surface. Ever since a recent windows update, now I get blue screens if I even think about it. Problem with watchdog. Go figure.
I'm sorry to hear that. I have completely given up on the Surface Pro 2 and I moved to Surface Pro 4. Microsoft was having a great promotion where they take your Surface Pro 2 and give you a $300 credit towards a 4. Good riddance.
Have had the pro 2 for a few years with constant battles, rubbed the Buddha belly,crossed my fingers & toes, here goes nothing....... Annnd wow! really???.. are you.** Kidding me? That easy??. Thank you!!!!!!!!!! I've been web searching for hours. For an easy fix. Good job Microsoft! Now fix the Xbox one. I for sure will share this
Boom son. It worked for me. Thanks!
ReplyDeleteI love this!
ReplyDeleteHappends on the original Surface Pro also. Very random. Fix worked perfectly. Thx!
ReplyDeleteThanks for this! It worked perfectly on my original Surface Pro. You made my day! : )
ReplyDeleteThank you - it worked for me.
ReplyDeleteThis is now the 3rd time this happened to me just after a microsoft 'update'. I don't usually re-start the surface just because of an update. 'But' when there is an update that blows the wifi out, one is forced to do a re-start (after deleting the Marvell driver). So what happens if I decide I don't want any more updates bloating my surface because it's running just fine? I did that on an XP machine for almost two years with no problems.
Curious ain't it?
Definitely curious - however, as annoying as those updates are, Microsoft is constantly patching vulnerabilities which is why I would recommend keeping up to date with them. It is definitely a pain, but the end definitely justify the means in this situation. If I had to guess - this is a hardware and device driver issue. It is very disappointing.
DeleteI owe you something for this. I'm gonna' get you a nice fruit basket.
ReplyDeleteThank you. I am not big on fruit, but I do accept Tips! Check the top right of this page :D
DeleteThanks! It worked for me.
ReplyDeleteInvested over 90 minutes with Microsoft Surface Pro Technical Support... only to conclude you have a hardware problem (please spend $320.00). Well the recommendation to Uninstall the Marvell AVARSTAR wireless software was 100% correct. Removed driver, restarted Surface Pro 2, Re-Installed Marvell AVARSTAR driver s/w and everything worked... cleared the error and the Wireless appears. Thank you.
ReplyDeleteWow some nerve they have saying it is hardware. I haven't had the problem since another recent windows update. Like 4-5 batches back. I strongly believe this is all driver related. To further my point, I used to be able to tether my android with my surface. Ever since a recent windows update, now I get blue screens if I even think about it. Problem with watchdog. Go figure.
Deleteseveral sessions with this problem the above did not fix it after several reboots.
ReplyDeleteSorry to hear that. The next thing you can try is just using an external USB device. That's what I did when it happened at first.
DeleteYour post helped after over 2 hours of random and fruitless troubleshooting. Many thanks.
ReplyDeleteYou are very welcome
DeleteHoly shit. I can't believe it worked. Thanks.
ReplyDeleteWorked a treat! Thank you very much.
ReplyDeleteWTF? It worked!!! Thanks for the AWESOME tip!!!
ReplyDeletenot for me
ReplyDeleteI'm sorry to hear that. I have completely given up on the Surface Pro 2 and I moved to Surface Pro 4. Microsoft was having a great promotion where they take your Surface Pro 2 and give you a $300 credit towards a 4. Good riddance.
DeleteThis worked for me too!!
ReplyDeleteMe too, years after you firdt did this. Thank you for sharing, you saved me a ton of headaches !!
ReplyDeleteHave had the pro 2 for a few years with constant battles, rubbed the Buddha belly,crossed my fingers & toes, here goes nothing....... Annnd wow! really???.. are you.** Kidding me? That easy??. Thank you!!!!!!!!!! I've been web searching for hours. For an easy fix. Good job Microsoft! Now fix the Xbox one. I for sure will share this
ReplyDeletei have been solving this issue since two month :-D i just followed your trick and it worked :-D Thanks
ReplyDeleteI'm glad this still worked for you.
Delete