Windows 10 Technical Preview - There is NO "Hyper-v Virtual Machine Management" service???

hi all,
There's no such Windows Topic as "WTP Virtualization", so I post this thread here, a somewhat "VIRTULIZATION" related.
I installed WTP (not server) x64 enterprise 9879, and added "Hyper-v Management" feature (management only, without Hyper-v core) in Control Panel. Then I found that there was no "Hyper-v
Virtual Machine Management" in Services panel, and there was no such file "c:\windows\system32\vmms.exe". Therefore I cannot connect to Windows Server 2012 R2 Hyper-v through WTP Hyper-v Manager.
I confirm the reason is what I state above. Firewall rules are properly configured on both Hyper-v server and WTP. I also used hvxxxx.wsf to configre anondcom to be "allow". When
I connect WS 2012 R2 through WTP, Hyper-v manager on WTP says "Please confirm VMMS server is running".
Is it a bug, or lack of implementation, or restriction of preview edition?
Any suggestion is appreciated! Thanks!

Okay,  I turned off hyper-v, went to bios and enabled Intel TXT(LT-SX) Configuration.  Made sure that both Virtualization and VT for Direct I/0 are on.  Next, I turned on Hyper-V and I create a brand new Virtual Machine call Windows8 and had
the DVD point to Windows8 ISO file on hard drive.  When I clicked on start, it stayed in the Starting status mode for about 5 minutes.  Then of course it failed.  I looked at the Hyper-V-VMMS log and here is what it output:
Log Name: Microsoft-Windows-Hyper-V-VMMS/Admin
1) Error: The virtualization infrastructure driver (VID) is not running.
2) Info:  Found a certificate for server authentication. Remote access to virtual machines is now possible.
3) Info:  Successfully started the Virtual Machine migration connection manager.
4) Info:  Virtual Machine Management service is started successfully.
5) Info:  The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
6) Info:  The WMI provider 'VmmsWmiEventProvider' has started.
7) Info:  The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
8) Info:  The WMI provider 'VmmsWmiEventProvider' has started.
9) Info:  The Integration Services Setup Disk image was successfully updated.
10) Error: The virtual machine bus is not running.
11) Error: 'Virtual Machine Bus' driver required by the Virtual Machine Management service is not installed or is disabled. Check your settings or try reinstalling the Hyper-V role.
12) Error: 'Storage Virtualization Service Provider' driver required by the Virtual Machine Management service is not installed or is disabled. Check your settings or try reinstalling the Hyper-V role.
13) Error:  The Virtual Machine Management Service failed to start the virtual machine 'Window8' because one of the Hyper-V components is not running (Virtual machine ID 2B393AF4-7B7E-4243-805B-23C09D20F4FB).
14) Error:  'Window8' failed to start. (Virtual machine ID 2B393AF4-7B7E-4243-805B-23C09D20F4FB)
Nick

Similar Messages

  • Error Creating VM on 2011 iMac - The Hyper-V Virtual Machine Management service encountered an unexpected error: The remote procedure call failed. (0x800706BE).

    I am running Hyper-V in Windows 8.1 on a late 2011 27 inch iMac. Whenever I try to create a virtual machine I get the error below and Windows warns that it will restart in 1 minute. I tried a clean install of Windows, but my PC still crashes ever
    time I try to create a VM. I was able to successfully use Hyper-V in prior versions of Windows on this same PC. Any clue as to what is going on? A driver? Windows 8.1? Mac Hardware related?
    I see the following two entries in event viewer but have no other clue as to what is happening:
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          1/10/2014 10:48:46 AM
    Event ID:      16000
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      Charles-PC.CHARLESPOOL.local
    Description:
    The Hyper-V Virtual Machine Management service encountered an unexpected error: The remote procedure call failed. (0x800706BE).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
        <EventID>16000</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-01-10T15:48:46.770451300Z" />
        <EventRecordID>58</EventRecordID>
        <Correlation />
        <Execution ProcessID="2488" ThreadID="8704" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Charles-PC.CHARLESPOOL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
          <ErrorMessage>%%2147944126</ErrorMessage>
          <ErrorCode>0x800706BE</ErrorCode>
        </VmlEventLog>
      </UserData>
    </Event>
    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:          1/10/2014 10:48:46 AM
    Event ID:      16010
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:      Charles-PC.CHARLESPOOL.local
    Description:
    The operation failed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066f867-7ca1-4418-85fd-36e3f9c0600c}" />
        <EventID>16010</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-01-10T15:48:46.773497100Z" />
        <EventRecordID>59</EventRecordID>
        <Correlation />
        <Execution ProcessID="2488" ThreadID="8704" />
        <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
        <Computer>Charles-PC.CHARLESPOOL.local</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <ProcessingErrorData>
        <ErrorCode>15005</ErrorCode>
        <DataItemName>Parameter0</DataItemName>
        <EventPayload>
        </EventPayload>
      </ProcessingErrorData>
    </Event>

    Hi CharlesPool,
    I am assuming that the win8.1 is in-place updated from win8 .
    Maybe you need to check the state of hypervisorlaunchtype .
    If it is off , please run command " bcdedit /set hypervisorlaunchtype auto "
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Cant create replica and Hyper V virtual machine management service slow shutting down

    Hi,
    I cant create replica and Hyper V, I go through the process and all looks good it even starts to create the hard disk but it stops at 4096K and the wizard just keeps going.
    The management console is also slow or wont load virtual machines - stuck on loading virtual machines
    The Hyper V virtual machine management service slow shutting down over 30 minutes on re boot of Hyper V core 2012 R2
    Any ideas ?

    Hi Sir,
    I assume that you have a standalone hyper-v server 2012R2 and you are using hyper-v manager to manage the hyper-v host .
    Which system you are using to manage hyper-v host , win8 or win8.1 or other ?
    Have you created VMs on the HOST ?
    I would suggest  you to create vhd or someother operation on hyper-v host directly  to check the result .
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows 8 Hyper-V - Virtual Machine Management Service failed to start the virtual machine

    I have Hyper-v running on Dell Precision T3600 with Windows 8 OS.  I am trying to start a VM (called Windows8VM) to install Windows 8 in the hyper-v virtual machine, but I keep getting the following message:
    "Windows8VM" failed to start.
    Failed to start the virtual machine "Windows8VM" because one of the Hyper-V components is not running.
    "Windows8VM" failed to start.  (Virtual machine ID D670D3BB-9AE2-0453D-9191-EA6EFC242A9C)
    The Virtual Machine Management Services failed to start the virtual machine "Windows8VM" because one of the Hyper-V components is not running.
    I have turned the hyper-v feature on in the "Turn Windows feature on or off.  The BIOS has virtualization enable.  Help!!! driving me nuts for a week now.
    Nick :(

    Okay,  I turned off hyper-v, went to bios and enabled Intel TXT(LT-SX) Configuration.  Made sure that both Virtualization and VT for Direct I/0 are on.  Next, I turned on Hyper-V and I create a brand new Virtual Machine call Windows8 and had
    the DVD point to Windows8 ISO file on hard drive.  When I clicked on start, it stayed in the Starting status mode for about 5 minutes.  Then of course it failed.  I looked at the Hyper-V-VMMS log and here is what it output:
    Log Name: Microsoft-Windows-Hyper-V-VMMS/Admin
    1) Error: The virtualization infrastructure driver (VID) is not running.
    2) Info:  Found a certificate for server authentication. Remote access to virtual machines is now possible.
    3) Info:  Successfully started the Virtual Machine migration connection manager.
    4) Info:  Virtual Machine Management service is started successfully.
    5) Info:  The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
    6) Info:  The WMI provider 'VmmsWmiEventProvider' has started.
    7) Info:  The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
    8) Info:  The WMI provider 'VmmsWmiEventProvider' has started.
    9) Info:  The Integration Services Setup Disk image was successfully updated.
    10) Error: The virtual machine bus is not running.
    11) Error: 'Virtual Machine Bus' driver required by the Virtual Machine Management service is not installed or is disabled. Check your settings or try reinstalling the Hyper-V role.
    12) Error: 'Storage Virtualization Service Provider' driver required by the Virtual Machine Management service is not installed or is disabled. Check your settings or try reinstalling the Hyper-V role.
    13) Error:  The Virtual Machine Management Service failed to start the virtual machine 'Window8' because one of the Hyper-V components is not running (Virtual machine ID 2B393AF4-7B7E-4243-805B-23C09D20F4FB).
    14) Error:  'Window8' failed to start. (Virtual machine ID 2B393AF4-7B7E-4243-805B-23C09D20F4FB)
    Nick

  • The hyper-v virtual machine management service encountered an unexpected error logon failure 0x80070569

    I dont understand why Microsoft people can't make things simpler
    They are LITERALLY MOTHER F%^%RS
    Bill Gate and his team need to learn hot to F^&&IN make things.

    I agree, the use of profanity is completely unnecessary, we've all been in the stressful situation before, it still doesn't call for it.
    The network you're receiving an APIPA IP on, is it the virtual switch you setup when adding the Hyper-V role?  If so you can get the warnings to go away and subsequently hide the adapter by unchecking the 'Allow host to manage this adapter' setting
    in the virtual network manager of Hyper-V manager on each node.
    Tim is also right, while disk resources are only owned by one node, you'll see the mount points for CSVs located under C:\ClusterStorage.
    More importantly, you're logon issue sounds directly related to group policy.  I had the same problem moving to Server 2012.  Yes, it's an annoying process but in the end you will have a working cluster.  I did the following steps:
    1. Install 'Group Policy Manager' on one of the nodes in your Hyper-V cluster
    2. Log on to the node you installed it on with a Domain Admin or appropriately endowed account that can edit the GPO relating to 'Logon as a service right'
    3. Edit the GPO where you specify who can logon as a server, OR if you don't have one, make a new one and link it to the OU with the Hyper-V nodes
    4. Add permission to that right for 'NT Virtual Machine\Virtual Machine Group', save and exit
    5. As an optional step I would reboot the nodes so you make sure they get it
    The problem here is that security group ONLY exists on servers that have Hyper-V installed on them.  If you add the group on a machine that has it to the GPO, the SID for the group is saved and each Hyper-V host will know what group that is.  The
    problem you're having right now is most likely related to a GPO changing 'Logon as a service right' to your needs and setup in Group Policy.  When a Hyper-V node starts up, it automatically adds the right for that group to the local security policy, however,
    group policy's auto refresh will remove it after a certain amount of time.

  • Hyper-v virtual machine management in status stopping

    Hello,
    I had a problem with one vm showing status backing up.
    I read on TechNet that restarting the hyper-v virtual machine management service would solve the problem.
    I have tried to shutdown the service but it now says status stopping...
    How long time does it take to shutdown the service? Is there anything I can do to hurry it up?
    ps. I have production vm running on the host that I can't take down...
    Regards
    Roger

    Hi Roger,
    I also tested in my lab to disable  that service forcibly ,then I found that it will leads the VMs to unexpected shutdown .
    Based on this ,it seems that restarting the host is necessary .
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Hyper-V Virtual Machine manager

    When using the Hyper-V Virtual Machine Manager and Connecting or Viewing using RDP is there any way to configure the app to span multiple monitor, (3) would be great

    Hi Sir,
    I'm afraid you need to use "mstsc.exe" to RDP to that VM instead of "vmconnect" in hyper-v manager .
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Hyper-V - "Verify that the Virtual Machine Management service on the computer is running."

    i can give the details  but as a reply by Brandon RecordsModerator already applies the short details are: that the entry for Hyper-V in windfows features doesn't allow "Hyper-V Platform" to be ticked and is greyed out.
    also can hyperv be run from powershell to give a different result?(module for Powershell is available and is ticked)_
    Problem solved Bradon had it right but i didn't realize the sequence to be followed mattered and when i turned virtualization technology on and booted HyperV platform was available

    That could mean a couple things.  First you need Windows 8.x Pro (or Ent),
    not just Windows 8.x.
    The second is that your hardware does not have the required features,
    (VT-x) and/or SLAT, or that they are not enabled in your BIOS.  You should
    contact the PC's manufacturer on that.
    There's no way to bypass the checks for hardware or OS from powershell.
    Bob Comer

  • Hyper V Virtual Machine Creation

    While we try creating a new virtual machine for our windows phone application, we are facing the following error.
    -Failed to add device 'Virtual Hard disk
    -Hyper V virtual machine management service account does not have permission to open attachment.
    ERROR: General access denied error(0x80070005)

    Unblock whatever it is that you downloaded.
    Check that your antivirus software is set with the proper exclusions.
    I don't recall anyone reporting this error before - as the installer for the phone emulator generally takes care of the machine creation and permissions.
    I can only guess that you are attempting to duplicate the phone emulator VM.  If so, use Export and Import.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • Nested Hyper v virtual machine won't start

    I have a development environment on Hyper-v i want to be able to develop windows phone apps for this i need a Hyper v installation on my dev environment so i installed Hyper-v.
    But if i start debuging the virtual hyper v says : The Virtual Machine Management Service failed to start the virtual machine 'Emulator 8.1 WVGA 4 inch.administrator' because one of the Hyper-V components is not running (Virtual machine ID)
    can anybody help me out on this one as it looks all good. If i try to start the hyper v machine within hyper v i get the same error.
    thanks in advance.
    Check my website http://kbworks.nl or follow me on
    @KbWorks be sure to Check my
    SharePoint-Specialist.nu for dutch information workers check
    Wat Is microsoft SharePoint.nl for dutch readers who want to know what
    microsoft office365 is.

    Hi Paul Keijzers KbWorks,
    Additional, Windows Phone 8 Emulator runs as a virtual machine on Hyper-V, the virtualization technology for Windows 8. To run the emulator, your computer must meet the requirements
    to run Hyper-V. Please refer the following article to realize more detail require about the WP emulator install requirement.
    System requirements for the emulator for Windows Phone 8
    https://msdn.microsoft.com/en-us/library/windows/apps/ff626524(v=vs.105).aspx
    How to enable Hyper-V for the emulator for Windows Phone 8
    https://msdn.microsoft.com/en-us/library/windows/apps/jj863509(v=vs.105).aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • VGPU with Nvidia GRID and Hyper-V in a future Version of Windows Server Technical Preview possible?

    Hi Windows-Server Team!
    We've got 8 XenServers with NVidia GRID K2 cards in it and using it for our Citrix XenApp/XenDesktops Farms.
    Works very good. But we want to do it with Hyper-V.
    Is there a plan to do vGPU like XenServer with Hyper-V too?
    Thanks
    Thomas

    Hi Thomas,
    Windows Server Technical Preview adds support for OpenGL 1-4.4 and OpenCL 1.1.  You will need Windows 10 Enterprise Technical Preview for the guest VM and Server Technical Preview with Hyper-V installed on the physical host.
    What's New in Remote Desktop Services for the next version of Windows Server?
    http://blogs.msdn.com/b/rds/archive/2014/10/07/what-s-new-in-remote-desktop-services-for-the-next-version-of-windows-server.aspx
    -TP

  • [Forum FAQ]Tips on Upgrading Windows 10 Technical Preview from Build 9841 to 9860

    The new Build 9860 for Windows 10 Technical Preview has been released recently. Here, I would like to share some experience on upgrading Windows 10 Technical Preview from Build 9841 to 9860.
    Tip 1: How to use Refresh option to upgrade.
    Scenario
    In order to upgrade to Build 9860, the new preview build should be downloaded firstly:
    PC settings-> Upgrade and recovery->
    Preview builds, which is as shown below.
    If there are multiples PCs which are running Windows 10 Technical Preview Build 9841 need to be upgraded, you may just want to use one copy of downloaded preview build to upgrade all of them instead of downloading the new build on each PC.
    Solution
    If you have upgraded one PC from Windows 10 Technical Preview Build 9841 to 9860, the downloaded preview build (install.esd) can be used to upgrade other PCs. Here we can use install.esd to export the install.wim, then this intall.wim can be used as a recovery
    image.
    Step 1: Understand the basic information about install.esd.
    Install.esd file is located at C:\ $WINDOWS.~BT\sources folder at first. When the upgrade is finished, it would be copied to
    C:\RecoveryImage folder. Here is the information in setupact.log which contains information about setup actions during installation:
    2014-10-28 19:03:38, Info SP Moving file D:\$Windows.~BT\Sources\Install.esd to D:\RecoveryImage\Install.esd
    What’s more, the command Dism /Get-Wiminfo /Wimfile:<path_to_install.esd> is used to display the information about the file install.esd:
    Step 2: Export the file install.wim.
    The following command is used to export Windows 10 Technical Preview Build 9860 image:
    Dism /Export-Image /SourceImageFile:<path_to_install.esd>
    /SourceIndex:4 /DestinationImageFile:<path_to_install.wim> /Compress:recovery
    Step 3: Copy exported install.wim to other Windows 10 Technical Preview Build 9841 computers, and set the recovery image.
    For example, the install.wim has been copied to C:\image folder, the following command is used to set the recovery image:
    Reagentc /setosimage /path C:\image /index 1 /target C:\Windows.
    Step 4: Use Refresh option to upgrade your PC.
    Go to
    Update and recovery setting under PC settings, choose
    Refresh your PC without affecting your files:
    Note:
    Applications needed to be reinstalled.
    System would use the exported install.wim to refresh Windows 10 Technical Preview from Build 9841 to 9860:
    Note: If you use install.esd to refresh directly, just need point the index location as 4:
    Reagentc /setosimage /path C:\image /index 4 /target C:\Windows. However, install.wim is easier for deployment, such as creating bootable USB, WDS and SCCM deployment.
    Tip 2: Workground to upgrade native boot VHD.
    Scenario
    Many users use the method native boot into VHD to test Windows 10 Technical Preview. However, there is a limitation on native boot when using VHDs:
    If you boot from a VHD, you cannot upgrade the Windows version in the VHD to a newer version. This article describes how to upgrade VHD system Windows 10 Technical Preview from Build 9841 to 9860.
    Solution
    Step 1: Upgrade in Hyper-V.
    Use Hyper-v to create a new virtual machine, and use your native boot VHD
    as an existing virtual hard disk:
    If booting from this virtual disk directly, it would fail to start due to lacking of boot files. You can use Windows 10 Technical Preview Build 9841 ISO file to repair the startup issue:     
    You can boot intosystem successfully in Hyper-v, then the upgrade process would be supported.
    Step 2: Create Native Boot to VHD.
    When the upgrade is finished, shut down the virtual machine, use the same way to create Native Boot to VHD:
    Mount the 9860 native boot VHD file.
    Use the following command to create boot entry for VHD system: Bcdboot
    v:\windows (v: represents the mounted virtual disk drive letter).
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi Arman mohseni,
    From my observation, if I click download now, it would create a BITS task:
    We can use following command to check:
    Import-module bitstransfer
    Get-bitstransfer –allusers
    From the output, we can see the system account created a BITS job for transferring, under the C:\Windows\Software Distribution\download, we can get the temporary downloaded file, which is approximately about 2.5G.
    After we restart, and go to C:\Windows\Software Distribution\download, the temporary file is gone.
    If I click the download again, the BITS would create a new task, a new temporary file, if we compare the JobIds of the two times downloading, they are totally different.
    On the other hand, if we download a windows update, the JobId would be kept, and the temporary files would be kept, too.
    Alex Zhao
    TechNet Community Support

  • About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

    Scenario:
    With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
    addition, the following error log may also be found via Event Viewer:
    Rejected an insecure guest logon.
    This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
    guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
    Background:
    The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
    Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
    With guest access authentication, the user does not need to send a user name or password.
    The security change is intended to address a weakness when using guest access.  While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
    matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere.  Without an account and password, the client doesn’t end up with a secure connection to the server. 
    A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data.  This is not necessarily a big concern in your home, but can be an issue when you take your
    laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify.  Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
    to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation. 
    As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
    Suggestion:
    You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
    We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
    The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections.  It is a one-time inconvenience,
    but the long term benefits are worthwhile.  If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
    Alex Zhao
    TechNet Community Support

    Hi RPMM,
    Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
    My shares settings is like this:
    Alex Zhao
    TechNet Community Support

  • Installing administrative tools for Windows 10 Technical Preview for Enterprise

    At first I was upgrade my Windows 8.1 to Windows 10 Technical Preview for Enterprise every things done will then
    I try to install administrative tools for windows 10 technical preview for enterprise I found the .msu file from Microsoft website but when I tried to install it, it gives me the following error:
    Windows Update Standalone Installer
    installer encountered and error: 0x8024001d
    is there anyone to help me regarding above issue.
    Thanks
    Zelgay Kunari

    Hi zelgay,
    This is my result:
    From your error code, it seems this is relate to your windows update, please use following command to fix corrupted files:
    DISM.exe /Online /Cleanup-image /Restorehealth
    In the meantime, you can delete temporary update files in the SoftwareDistribution folder:
    Stop Windows Update service.
    Open File Explorer.
    Double-click the local hard disk where Windows is installed, typically drive C.
    Double-click the Windows folder, and then double-click the
    SoftwareDistribution folder.
    Double-click the DataStore folder to open it, and then delete all files and folders in the folder.
    Note If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
    Click the Back button. In the SoftwareDistribution folder, double-click the
    Download folder to open it, and then delete all files in the folder.
    Restart Windows Update service.
    Alex Zhao
    TechNet Community Support

  • Windows Server Technical Preview - RDS - RemoteFX 3D

    Hi Windows Server Team,
    I am having an issue with the Windows Server Tech Preview and Remotefx 3D. I installed the RDS role and have it all configured with no problems. I loaded a VM of Windows 10 Enterprise Tech Preview. It works fine, however when I activate the RemoteFX 3D on
    that virtual machine. It then just shows a black screen in my Hyper-V Manager and just stays hung on the black screen. I have been working with RDS and RemoteFX 3D since the Windows 2008 R2 days and have never had this problem at all. When I try to Shut down
    the VM it stays hung when I try to Turn Off the VM it stays hung. I am forced to reboot the server and when it comes back up it still just shows a Black screen for the Windows 10 Enterprise VM with RemoteFX 3D turned on. I really wanted and was interested
    in testing the new OpenGL features and other ehancements that have been mentioned with this version of RDS and remotefx 3d. I also noticed that Gen 2 VM's now also support the RemoteFX 3D features and even tried to create a Windows 10 Enterprise as a
    Gen 2 VM but I have the same problem. My server is a Dell PowerEdge R720. Thanks and I look forward to your reply and can hopefully get this working.
    Regards,
    Robi Rodriguez

    Hi,
    Thank you for posting in Windows Server Forum.
    Initially we need to check whether the device is supported for latest version of features available. To use new feature available with Windows Serer Technical Preview we need to see that device supports the latest available OS. Please go through
    this article for information. You can contact Dell for further information whether it
    still have any updates for Windows Server Technical Preview.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

Maybe you are looking for

  • New Macbook + 320gb WD = Problem

    Hi, i just got the new macbook 2ghz and bought a 320gb WD 5400/min hard drive. It works just fine except for the fact that it makes a sound every 5 - 30sec when the hdd is not in use. "clack" ... 5 sec ... "clack" ... 30 sec ... "clack" ... 10 sec ..

  • Sales order amount should be fall in Old date agrrement date

    Dear sd Experts please explain me How to achieve Return Rebate accrual amount ex: Time period is 01/01/2014 to 25/04/2014  If customer Purchased 100000 Rs stock he use to get some discount 2000 rs ' On settlement day Now customer achieved His Full ta

  • Photoshop CS2...no abre mis archivos!!!!

    Tengo este grave problema... habia estado trabajando bien con photoshop, y de repente asi de la nada, ha dejado de abrir mis archivos...me los muestra en el navegador pero no abre nada. Puedo crear un nuevo documento, pero no abrir nada de lo anterio

  • PREPROCESSOR_ACTIVITY_ERROR (Code 8010)

    Hi All, In our Trex system we are facing a error in one of the log file error is "PREPROCESSOR_ACTIVITY_ERROR (Code 8010) & a rfc communication failed ===>protocol mismatch found for table. We have found various threads reg PREPROCESSOR_ACTIVITY_ERRO

  • Msn email on a 8320

    I've read and read post after post and couldn't help but to surrender and post myself. got my BB on fri. (awesome) I added my personal email (this is a personal phone not a business) and saw my new icon next to the "messages" icon. everything was goi