If I use basic session, everything works fine, but when I connect in enhanced mode, login prompt is not appearing.
Guest OS: Win 10 Pro x64 Build 18990.vb_release.190921-1704
RDP services are enabled.
Event Log for RemoteDesktopServices-RDPCoreTS/Operational shows a error:
'Failed GetConnectionProperty' in CUMRDPConnection:QueryProperty at 3318 err=[80004001] (RemoteFX module)
Host OS: Win 10 Pro x64 1903 (18362.418)
Hper-V Version: 10.0.18362.1
I disabled RemoteFX in Guest OS with policies, how it is described here, but still no success.
I had the same problem until I stumbled across this Microsoft thread where someone said, "disabling Windows Hello on the VM did the trick for some reason."
Go to Settings -> Accounts -> Sign-in options. Turn off the setting for "Only allow Windows Hello sign-in for Microsoft accounts on this device (Recommended)". Then reboot the VM and enhanced sessions should work.
Related
When using VMWare Workstation 16.2, if we try to create Windows VM, we get the following error when starting the Virtual Machine.
VMware Workstation unrecoverable error: (vcpu-0)
Exception 0xc0000005 (access violation) has occurred.
A log file is available in "C:\Users\name\Documents\Virtual
Machines\Windows_Server_2019\vmware.log".
You can request support.
To collect data to submit to VMware support, choose "Collect Support
Data" from the Help menu.
You can also run the "vm-support" script in the Workstation folder
directly.
We will respond on the basis of your support entitlement.
There are no official communication from VMWare at this moment.
This issue appears to be caused by the setting that allows VMWare to work alongside Hyper-V. There are two fixes, if you want to use Hyper-V along with your VMWare solution, we need to set the core count and processor count to 1.
This should solve the issues, but this isn't ideal.
The other option is to disable Hyper-V. I came across this when I was trying to run Faceit-AntiCheat Client. It needs Hyper-V to be disabled. If we follow the following steps we can disable Hyper-V and the VM should work fine.
Click Start and search for Command Prompt
Right-click on Command Prompt and then click Run as administrator
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue
Then type: "bcdedit /set hypervisorlaunchtype off" Press enter
Then type:reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f Press enter again.
Restart your computer
Now you should be able to start the VM with the desired number of processors.
I did not get the same results.
I ran the bcdedit and reg add with confirmation that it "worked", it did not. I also set the processor to 1/1 after reset.
VMWare 16.2 Windows 10 and Windows Server 2019 clients (both updated and working on another system with NVIDA graphics card
specs below
[System Summary]
Item Value
OS Name Microsoft Windows 11 Pro
Version 10.0.22000 Build 22000
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Dell Inc.
System Model Precision 7560
System Type x64-based PC
System SKU 0A69
Processor 11th Gen Intel(R) Core(TM) i7-11850H # 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date Dell Inc. 1.7.0, 12/10/2021
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Dell Inc.
BaseBoard Product 03DXD2
BaseBoard Version A00
Platform Role Mobile
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume3
Locale United States
Hardware Abstraction Layer Version = "10.0.22000.1"
User Name BAE0004233\GXP
Time Zone US Mountain Standard Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.2 GB
Available Physical Memory 23.2 GB
Total Virtual Memory 36.2 GB
Available Virtual Memory 25.9 GB
Page File Space 5.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Running
Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization
Virtualization-based security Services Configured Hypervisor enforced Code Integrity
Virtualization-based security Services Running Hypervisor enforced Code Integrity
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
After installing windows 98 in virtualbox, I clicked 'start' button. Then it showed me an error:
Failed to open a session for the virtual machine windows 98.
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
You need virtualization Technology enabled in the Bios
Reboot your machine
Press F10 to enter BIOS.
Security-> System Security
Enable Virtualization Technology (VTx) and Virtualization Technology
Save and start the machine.
Failed to open a session for the virtual machine windows 98.
There are different approaches to solve this, try whichever works for you
1
open windows features win+R --> then optionalfeatures
Disable Hyper-V (if it is available on your machine)
Enable "Virtual Machine platform"
Enable "Windows Hypervisor platform"
Disable "Windows Sandbox" (if available on your machine)
Restart the machine
2
Windows Subsystem for Linux (WSL) feature was enabled.
Disabling it solved it for me.
Restart the machine.
3
If it still doesn't work:
Open Powershell command prompt as admin and then run the following command:
bcdedit /set hypervisorlaunchtype off
Restart the machine
View the full answer:
Unable to launch Ubuntu18.04 on VirtualBox [VERR_NEM_VM_CREATE_FAILED]
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 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
I'm working on a legacy app that needs to be continued in VS 2003; I cannot effectively debug it, though, because when I try to run it, I get the following dialog:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Deploy
Choose the device to target. If the .NET Compact Framework is not already on the selected device, it will be deployed along iwth your application.
Pocket PC 2002 Emulator
Pocket PC Device
Windows CE .NET Device
Windows CE .NET Emulator (Default)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am running this (VS 2003) in XP Mode (Virtual Machine) on Windows 7. I do not have a connection (from XP Mode) to the device - a Symbol/Motorola PDT 3090 - so I get, "Unable to connect" when trying to run/debug/deploy in VS 2003.
What has been the case up to now is the developer would build the binary, adding debug messages, and then copy the binary over to the device and run it. Rather than continue this method, I would prefer to be able to debug it from within VS 2003. Is there a way to do this? None of the options (Pocket PC 2002 Emulator, etc.) seem to work...the device is attached to the computer via a usb. The Emulators won't work because they don’t have the necessary hardware (barcode scanner). So I need to use one of the *Device options, but have not been able to connect the usb port to XP Mode.
Does anybody have any ideas on how to debug without the constant copying-and-replacing of binaries, and the use of "show message"?
UPDATE
Alternately, if I can't run the app from within VS 2003 / XP Mode as an emulator, it would also be fine to run it on the attached Motorola handheld, attached via usb cable from the cradle to the desktop computer; I prefer the former, for the debugging capabilities afforded, but even the latter would be better than my current predicament (copying the files to the handheld device, detaching it from the computer, attaching it to the belt printer, firing it up, testing and repeat ad nauseum ad infinitum). ASAP (within two hours), I will set a bounty on this question.
UPDATE 2
If I try to run from VS 2003 in an emulator, and select "Windows CE .NET Emulator (Default)", I get:
"Emulator for Windows CE will not run within another copy of Emulator for Windows CE.
You just had to try, didn't you?"
?!? Is it saying this because I'm in a VM (XP Mode) session?
Then I select "OK" (the only option), and get, "There were deployment errors. Continue?" That trick never works; it even causes the build to fail (a rebuild fixes that, though).
UPDATE 3
Perhaps my problem with not being able to debug by connecting to the device itself is related to this msg I saw when booting up this morning (but I don't know what to do about it, IF this is the problem - do I need to search for a new driver for the Motorola MC3100?):
Devices or applications disabled.
Virtual PC/Windows CE Emulator will cause Windows to become unstable. Windows has prevented these drivers from loading. click here for more details.
The "more details" are:
Virtual PC/Windows CE Emulator
Microsoft
--------------------------------------------------------------------------------
Issue Description:
A driver is installed that causes stability problems with your system. This driver will be disabled. Please contact the driver manufacturer for an update that is compatible with this version of Windows.
Contact Information:
Web Site: http://go.microsoft.com/fwlink/?LinkId=26320
Telephone: 1-800-936-5800
That link (http://go.microsoft.com/fwlink/?LinkId=26320) ended up as: "Internet Explorer cannot display the webpage"
UPDATE 4
There is some headway (or perhaps just false hope) on the connecting to the device front:
I have 4 USB ports on my desktop machine. I plugged the USB cable into the 3rd from the top for the first time a bit ago. It then said it was recognized, and ActiveSync was finally able to make a connection.
So I then tried deploying the app again. The fourth option (the default - C.E. Device Emulator) failed as always. So did the penultimate choice (C.E. device). The second option, though (Pocket PC device), seems to possibly be working.
However, I got a cryptic err msg that just said:
#183:
I dismissed that and since then (it's been a good ten minutes now), the bottom of the VS Output windows has been saying "Launching Application" (with a blinking cursor beneath it) and the task bar has been claiming "Deploy started..."
Whether that is really of any value, though, it doesn't appear to be, as I am just "stuck" there...
Windows CE .NET Emulator (Default)
This should be the one you want, if you are running Windows CE.
The Barcode Reader takes the code and converts it to a string for you, so your code will never need to "decode" a barcode.
So, when you are testing your software using the CE Emulator, simply select the textbox you want to read the barcode to, and type that value in using your keyboard.
In your Windows 7 host PC's task bar, right click on the XP Mode VS2003 application. In the menu that appears select "Manage USB Devices".
Select your Windows Mobile device and hit the "Attach" button. Your XP Mode PC should connect via ActiveSync. (This assumes you've installed ActiveSync on the XP Mode VM. If not, you should do that first.)
Try rebooting the virtual machine. (Not the same as closing and re opening it). If that doesn't work, try a different USB port. You may end up reinstalling XP mode.
See also: How to Access USB Devices in Windows Virtual PC for Windows 7