I have a very new Surface Pro 3 (1 day old) so I'm not sure if its hardware or a general issue.
My WiFi adaptor sometimes completely disappears and I have to reboot to restore the adaptor. It is not just disconnecting it is completely missing from device manager.
Does the firmware auto update or can it be pulled manually? cannot even figure out how to update anything.
Based on my experiences with Surfaces, I advise against resetting. In the past I've tried that in the hopes of resolving outstanding issues, and most of the time it didn't help. For the one time that it did, the problem mysteriously reappeared shortly after.I just got the firmware and another definition update. After several sleep/wake cycles, as well as shutdown/startup cycles, I've determined that my wifi problem is not improved (well, maybe the speed, which I haven't tested in all this). If I shut down, when I start back up the wifi works immediately. If I put it to sleep, when I wake it up I have to turn wifi off and back on - it is "limited" until then. And by limited, I mean there is no connectivity. I was really hoping this would fix it.
I'm tempted - a little bit, not much - to reset the computer. But I've got so much installed... Visual Studio 2013, Telerik DevCraft, SQL Server 2014 (not set to run, but just installed with service set to manual start), and so much more - those are just the biggies. I'm starting to ponder whether Hyper-V is causing the problem, but not much I could do about that without uninstalling VS.
Based on my experiences with Surfaces, I advise against resetting. In the past I've tried that in the hopes of resolving outstanding issues, and most of the time it didn't help. For the one time that it did, the problem mysteriously reappeared shortly after.
In the end, it'll just accelerate bringing you to a point of greater frustration.
But I've got so much installed... Visual Studio 2013, Telerik DevCraft, SQL Server 2014 (not set to run, but just installed with service set to manual start), and so much more - those are just the biggies. I'm starting to ponder whether Hyper-V is causing the problem, but not much I could do about that without uninstalling VS.
I'm concerned because that's a very similar set up to what I plan to have when I get my SP3 (I'm in Australia, pre-ordered for 'end of August'). I was intending to either not install, or disable, Hyper-V though. I was under the impression that Hyper-V only installs with the Windows Phone SDK (i.e. not with VS general)? I need the SDK but I was hoping to just ditch the emulators that run in Hyper-V and test directly on my device (an annoyance but do-able for the apps I have).
Are you able to temporarily disable Hyper-V and see if the issue improves? I've seen some guides around for doing that.
bcdedit /copy {current} /d "Disable Hyper-v"
bcdedit /set {your-guid-goes-here} hypervisorlaunchtype off
Bcdedit /timeout 0
Bcdedit /default {Guid-goes-here-of-hyper-v-off}
Thanks. I'm about to go to bed, but I'll have to give this a shot tomorrow.Hyper-v is the issue. You need to clone your boot configuration and turn it off on one. I set my Hypervisor off boot to default and set the timeout to 0 seconds on boot selection so by default I keep the more tablet like power states unless I want to go run a VM. I also don't leave an external network configured. You lose sleep states and most importantly you lose Intel SpeedStep so your processor is always running at max frequency.
Here is a guide I wrote up.
<trim>
It's almost a certainty that it is driver-related. Unfortunately, it's the nature of Surface ownership.Well, never mind. The update introduced a different issue for me. Twice in the past two days, after coming back from sleep, I lose all network drivers, including Bluetooth. I have to restart to fix. Do you guys think this is a hardware defect or something fixable in a firmware update? If it's the former, I have a few days to return.
Posted via Windows Phone Central App
It's almost a certainty that it is driver-related. Unfortunately, it's the nature of Surface ownership.
It's almost a certainty that it is driver-related. Unfortunately, it's the nature of Surface ownership.
How long have you owned a Surface? 3 weeks? You are free to believe that this is a rare occurrence, but there have been similar issues across ALL Surface devices in the 10 months that I've been here. It's not an isolated incident. Issues that Microsoft actually produced a fix for that fixed for some but not for others only to return after the next monthly update.Yet there are probably a majority of us that have zero issues... makes me think someone has installed one of the gazillion programs out there without the proper driver or some other extremely rare software issue.