locked
Surface Pro 4 Virtualization with Hyper-V RRS feed

  • Question

  • Hi,

    I am having an issue with Hyper-V virtualization on a new Surface Pro 4 running my company's Win10 Enterprise image (a few apps added but nearly stock). User launches Hyper-V Manager and chooses Connect to Server..., selects Local computer radio button, and gets an error that the Virtual Machine Management service is running. Service is already running. The Surface in question has an i7-6650u and supports VT-x according to http://ark.intel.com/products/91497/Intel-Core-i7-6650U-Processor-4M-Cache-up-to-3_40-GHz .

    I've worked with Microsoft support on the following to no avail (using this page as a general troubleshooting guideline https://social.technet.microsoft.com/Forums/Windows/en-US/ff34070e-91d7-44b0-aa11-28941a36f31f/hyperv-manager-cannot-connect-to-local-server?forum=winserverhyperv ):

    - manually restarting the Virtual Machine Management service

    - uninstalling and reinstalling Hyper-V (using appwiz.cpl checkbox as well as powershell)

    - verifying user account permissions (user is local admin and member of Hyper-V Administrators group)

    - logged off of the domain user account and onto local .\Administrator account

    I got some facetime with five other Surface devices at my company and have compiled the data below as reported by msinfo32 on each machine, each with the same Win10 Enterprise image. Each CPU is listed as "VT-x supported" by Intel. I spoke with an Intel phone support agent who said vendors (Microsoft, in this case) can limit or disable chip functionality in BIOS. Do not see virtualization options in BIOS.

    Surface Pro 4 and Surface Book running Microsoft's BIOS all exhibit the same VMMS (Virtual Machine Management Service) failure. Surface Pro 3 running the AMI BIOS can connect to the Hyper-V local computer virtualization server. 

    My Microsoft support ticket is pending but I could not find anyone else reporting this issue, please advise if you have any suggestions. Thanks in advance for your time and expertise.

    Hyper-V working? Hyper-V Works as expected Hyper-V Works as expected Hyper-V error Hyper-V error Hyper-V error Hyper-V error
    OS Name Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise Microsoft Windows 10 Enterprise
    Version 10.0.10586 Build 10586 10.0.10240 Build 10240 10.0.10586 Build 10586 Version 10.0.10586 Build 10586 10.0.10586 Build 10586 10.0.10586 Build 10586
    System SKU Surface_Pro_3 Surface_Pro_3 Surface_Pro_4 Surface_Pro_4 Surface_Book Surface_Book
    Processor Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 2301 Mhz, 2 Core(s), 4 Logical Processor(s) Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz, 2301 Mhz, 2 Core(s), 4 Logical Processor(s) Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2496 Mhz, 2 Core(s), 4 Logical Processor(s) Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz, 2208 Mhz, 2 Core(s), 4 Logical Processor(s) Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2496 Mhz, 2 Core(s), 4 Logical Processor(s) Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2496 Mhz, 2 Core(s), 4 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. 3.11.1150, 12/9/2015 American Megatrends Inc. 3.11.0950, 6/5/2015 Microsoft Corporation 104.1121.768, 3/1/2016 Microsoft Corporation 104.1121.768, 3/1/2016 Microsoft Corporation 88.870.770, 11/6/2015 Microsoft Corporation 88.1121.768, 3/1/2016

    Tuesday, June 14, 2016 10:25 PM

Answers

  • The complete text of the error is:

    An error occurred while attempting to connect to server "machinenamehere". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server. The computer 'machinenamehere' could not be resolved. Make sure you typed the machine name correctly and that you have network access. (emphasis mine - the key to the fix)

    link to image here imgur.com/a/E6r04

    Our deployment task process names machines after the last several characters of their serial numbers. In the case of Surface devices, these are all 12-digit numbers.

    The resolution for my issue was to add non-numerical characters to the front of the machine name, like "SP123456789". Hyper-V did not like the all-number machine name. I still don't know why the earlier Surface devices (SP3) did not exhibit this symptom.

    My Surface Pro 4 with i7-6650u now runs Hyper-V as expected. Hope this helps someone out there.

    • Marked as answer by John-1012 Thursday, December 15, 2016 2:52 PM
    Thursday, December 15, 2016 2:52 PM

All replies

  • Hi I am facing the same problem

    Surface Pro 4 with latest 64bit Windows 10 build

    Hyper V is turned on at the OS level

    BUT VT-x is disabled and BIOS has no way of turning it on.

    checked by installing Intel HAXM and running:

    VT support -- no
    NX support -- yes

    Can someone PLEASE help??

    Thanks.

    Zurich31

    (zurich31@msn.com)

    Thursday, November 3, 2016 1:49 AM
  • The complete text of the error is:

    An error occurred while attempting to connect to server "machinenamehere". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server. The computer 'machinenamehere' could not be resolved. Make sure you typed the machine name correctly and that you have network access. (emphasis mine - the key to the fix)

    link to image here imgur.com/a/E6r04

    Our deployment task process names machines after the last several characters of their serial numbers. In the case of Surface devices, these are all 12-digit numbers.

    The resolution for my issue was to add non-numerical characters to the front of the machine name, like "SP123456789". Hyper-V did not like the all-number machine name. I still don't know why the earlier Surface devices (SP3) did not exhibit this symptom.

    My Surface Pro 4 with i7-6650u now runs Hyper-V as expected. Hope this helps someone out there.

    • Marked as answer by John-1012 Thursday, December 15, 2016 2:52 PM
    Thursday, December 15, 2016 2:52 PM
  • Were you manage to resolve this issue? I have the same problem...

    thanks

    Sunday, November 26, 2017 4:59 PM