Work Around for Surface Pro 3 Issue Where Connected Standby is Disabled when Hyper-V is Active

Technical Level : Intermediate

Summary
If you install Visual Studio 2013, there is a conflict between Connected Standby and Hyper-V. Connected Standby is no longer operational. This article provides a work-around.
Details

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.

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 and that Connected Standby no longer works. This occurs because Connected Standby is not supported on a system running Hyper-V virtualization.

The emulator for Windows 8 Phone development in Visual Studio 2013 requires Hyper-V.

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).

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.

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.

Was this article helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this article?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this article?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

This affects no only those with VS Installed but other like me that enabled Hyper v thinking about running some Virtual Machine in my Surface Pro 3. I hope that MS finds a letter workaround. For now, this works.
Frank J Garcia (ctitanic)
Surface MVP
http://www.ultramobilepc-tips.com

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

This affects no only those with VS Installed but other like me that enabled Hyper v thinking about running some Virtual Machine in my Surface Pro 3. I hope that MS finds a letter workaround. For now, this works.

Frank, obviously anyone wanting to run Virtual Machines on a constant basis would find this problematic.  I don't know if there is a solution coming from MSFT, but for now, as you say, this works.

Barb - Windows and Devices for IT MVP
*Please click Yes below if your problem is resolved. This may help others with the same issue.*

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

Thanks for the article, Barb! This was exactly my issue... Ugh, it was super frustrating.
enOZero
Software Development Engineer - Windows Phone
Microsoft Corporation

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

Thank you for this page, it resolved all of my Sleep powerstate issues!

I do need Hyper-V to be functional for work purposes, awaiting any news on that.

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

Thanks for this! symptoms showed up as very slow resume times & wireless limited after resume - requiring reconnection to wireless network each time. in rapid addition of all my 'essential software' to my new SP3 I almost passed up visual studio/hyper-v as a possibility for the root cause of this problem. I was only clued in because I noticed new virtual NICs installed for windows phone. then searching for "visual studio surface pro 3" brings this article to the top. thanks again!

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

I was about 24 hours away from ditching the Surface Pro 3 due to these issues.  I'll wait a bit to see if this fixes the wifi issues that have essentially ruined an otherwise great experience with the surface pro 3.  Thanks for the info and hopefully this will get resolved fully soon so I can actually use the Microsoft Product I purchased to dev with (VS 2013) on a Microsoft Product (Surface) correctly. 

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

Folks may find this article to be more helpful: http://support.microsoft.com/kb/2973536

This will allow you to quickly switch between Hyper-V on and off without having to open up command line every time.

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

I'm only about 1 day into the "work around" and so far the limited wifi on sleep is still happening, and wifi connectivity is barely (if at all) improved from previous.

Drivers have been updated, various solutions tried (per threads on this site) and this workaround has failed.

Any other options short of ditching Surface for something else.  I feel that I've already been required to waste far too much time adapting to or trying to work around a fairly critical issue ion the overall usage of the Surface Pro 3.  Very dissatisfied with MSFT around this.

/FAIL

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

I'm only about 1 day into the "work around" and so far the limited wifi on sleep is still happening, and wifi connectivity is barely (if at all) improved from previous.

Drivers have been updated, various solutions tried (per threads on this site) and this workaround has failed.

Any other options short of ditching Surface for something else.  I feel that I've already been required to waste far too much time adapting to or trying to work around a fairly critical issue ion the overall usage of the Surface Pro 3.  Very dissatisfied with MSFT around this.

/FAIL

It works for me.

Frank J Garcia (ctitanic)
Surface MVP
http://www.ultramobilepc-tips.com

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

Folks may find this article to be more helpful: http://support.microsoft.com/kb/2973536

This will allow you to quickly switch between Hyper-V on and off without having to open up command line every time.

Which method are you taking about?

Frank J Garcia (ctitanic)
Surface MVP
http://www.ultramobilepc-tips.com

Was this comment helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this comment?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this comment?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Forum Article Info


Last updated October 21, 2022 Views 15,931 Applies to: