I was used Disk2vhd to convert OS (Windows XP) into vhdx format and use Hyper-V Manager to run it as a virtual machine.
I had inserted integration services already and restart the VM, but "Mouse Not Captured In Remote Desktop Sesion" happened. The mouse cursor is there but cannot use the mouse, only can use keyboard.
I also tried manual insert integration services, but the result is "An error has occurred: One of the update processes returned error code 1603". I unchecked all the integration services (like data exchange, os shutdown) of the setting of the VM in Hyper-V Manager.
Related
I have applied some windows updates on both my host (Windows 10) and my Hyper-V guest (Windows 10). After rebooting the hyper-v VM cant boot anymore displaying the message that there is no active boot item for booting from UEFI.
After some trail and error, the solution was to reinstall hyper-v on my windows 10 host.
Ensure that hardware virtualization support is turned on in the BIOS settings
Configure networking for the Hyper-V environment to support external network connections. Also ensure that a virtual switch has been created and is functional
Remove all security software and AV
System and drivers are up-to-date.
Also, try to use PowerShell command-line to enable Hyper-V.
Install-WindowsFeature –Name Hyper-V -ComputerName <computer_name> -IncludeManagementTools -Restart
I am trying to do HLK testing for my own driver by this instruction https://msdn.microsoft.com/ru-ru/library/windows/hardware/dn915002(v=vs.85).aspx , but I have problems.
I can not do step 5 as I do not see my driver in the list of .sys files I can select for testing in HLK Studio selection tab.
My driver is stored on test machine in location C:\MyDriver\mydriver64.sys. It is 64-bit kernel mode driver used by my application for RAM analysis.
What can I do to add my driver to the selection list and run HLK tests for it?
Thank you.
Make sure the driver is running on the machine
Make sure the machine status is set to ready.
Restart the HLK service on client. (go to services, search for hlk, R-click, restart)
Restart the HLK service on server. (same as client)
Check the machine status again, give it some minutes to get ready
If still not working, try restarting both systems
Sometimes HCK Infrastucture Service crashing, but HLK Communication service still works. You need restart HCK Infrastructure service too. On my job, we had a problem with very long start time of this service and Windows throws timeout error for service start. Because of this, service never starts. We solved this problem, by setting bigger time for service start in Windows registry.
Registry key is HKLM\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout
Make sure the driver is running on the test machine.
Start "HLK Manager", click on "My Machines..."
Select your test machine from the list, right click, "change-status" to "unsafe"
Open "HLK Studio" ... "Configuration"
Find your test machine, right click, "change machine status" to "ready"
Load your project and check for your driver under "Selection"
What kind is your driver? Please provide your inf file or registry entry.
Do you search it under "software device" or "device manager"?
Be sure to
install driver prior to client
start driver
select software device in Studio's Selection tab
I was looking for my driver in "device manager" which was the default and not finding it as it is a driver hence software. Spent far more time on that problem than I'd like to admin
Restart Client Machine
Restart HLK Communication service.
Restart HLK Infra Service.
Now try to load the machine pool, Issue should have resolved now.
I have a Windows Vista virtual machine. From a central computer, I'm launching commands on that virtual machines, using the commands runProgramInGuest and CopyFileFromGuestToHost. Regularly I get the error message VMware Tools are not running in the guest but when I verify the virtual machine, I can see the service VMTools being running, having a PID, corresponding to the process vmtoolsd.exe.
In the event log, I see warnings on a regular basis, saying Error in the RPC loop: RpcIn: Unable to send..
Does anybody know what's going on an how to solve this issue?
Thanks
Documented error here at VMware
We had the same issue with some Vista PC's recently and this hotfix sorted it
My Python application has windows is client and server as Linux. My aim is to automate windows GUI application with pywinauto from Linux server.
Can pywinauto be made cross platform?
It's not possible using pywinauto immediately. But you may copy pywinauto script to the target Windows machine and run it remotely using Jenkins, for example. Or any other CI server. Master node can be on Linux. So Windows node can run as a slave. But there are several requirements for the Windows slave (this check list is based on my recent experience).
Windows slave can be set up with auto logon.
VNC server software (TightVNC or UltraVNC, for example) should be installed.
Video card drivers should be up-to-date for better screen resolution (and for black screen prevention).
Jenkins slave process must run as not a service (i.e. in the existing desktop, so Jenkins task would have an access to the GUI). Just do NOT click menu "Run as a service" in JNLP agent window.
Do not use Remote Desktop connection from another Windows machines (reboot may be required to restore GUI session with VNC client/server pair).
Of course, Python+pywinauto must be installed on Windows node. Just in case.
If UAC is enabled on Windows node, in some cases it should be disabled (if you have to deal with admin access like GUI installers do).
On Linux you need to set up the VNC client and Jenkins. For other CI servers steps may be similar but with some differences.
I have installed windows phone 8 SDK and tried running a simple app which embeds a WebBrowser on a page. When I try to run the app in emulator the emulator does not get internet connection. It displays an error message saying "You don't have permission to modify internal Hyper-V network adapter settings required to run the emulator". Im sure my login has admin permissions. My machine is 64bit, hyper v is enabled and Hyper v manager is running, hardware virtualization is enabled in the BIOS settings, DHCP is enabled and its connected to a wired network. I have checked all the system requirements. What ever I do it keeps on giving the same error message. I setup everything in a different machine and tried running the app in that machine. The same error message is displayed in the that machine also. Can anyone tell me how to get it working.
DHCP is enabled and its connected to a wired network
Can you run ipconfig /all on your host machine and post it here please?
seems you have problem with your DHCP or maybe multiple DHCP and conflict.
You need to add your user account as a member of the "Hyper-V Administrators" group on the machine.
Detailed steps:
Hit Windows key + Q and search for "local users and groups". Change the search scope to "Settings". Click "Edit local users and groups".
Expand the "Groups" section. Right-click on "Hyper-V Administrators" and select "Add to group".
Add your user account.
Some connection tools on the host can have negative effects when used with the emulator; I found having cisco VPN client installed on the host prevented the emulator from finding the internet. Other VPN clients may have similar side-effects. I simply uninstalled cisco (the inbuilt windows VPN is fine for what I need) and it worked perfectly.
I've also seen problems where it won't find the internet after the host has been suspended / resumed. In that scenario, it turned out to be bad network drivers. I installed a dedicated Intel NIC (rather than the on-board NIC on the motherboard) - problem solved.
Basically, Hyper-V is a bit fussy.
try refreshing the hyper-v by unchecking and then checking it again,this worked for me.
Steps:
1.control panel>>programs>>Programs and features>>turn windows features on and off>>hyper-v
2.uncheck it and restart the pc.
3.again go to control panel an check hyper-v and restart the pc again.
the try to run the emulator,should work..
another possible reason is that you did not start vs2013 as admin