Documentation · Troubleshooting
Hyper-V problems
What helps when the test machine will not start.
since 0.9.7.6
Hyper-V is unavailable on Windows Home
Causes
- Hyper-V is not part of Windows Home.
Solution
- Use VirtualBox instead. VirtualBox runs on Windows Home and Windows Pro and can run the test machine.
- Set up VirtualBox on the Requirements step with the Install VirtualBox… button. The download is about 170 MB.
The optional Hyper-V test machine requires at least … GB RAM
Causes
- The PC has less memory than a test machine on Hyper-V needs. The message names the figure.
Solution
- Use VirtualBox.
- Or skip testing. The installation medium is finished without the test as well.
Hyper-V couldn’t be enabled automatically
Causes
- You did not confirm the administrator rights prompt.
- The component that requests those rights is missing from the program folder.
Solution
- Repeat the action and confirm the administrator rights prompt.
- Or turn Hyper-V on by hand under “Turn Windows features on or off”. The Requirements step has the Open Windows Features… button for this.
- Then restart the computer. Only then does the change take effect.
When there is no message
-
VirtualBox is very slow. When Hyper-V is active on this PC, VirtualBox runs on the Windows Hypervisor Platform and is noticeably slower. If you need VirtualBox at full speed, switch Hyper-V off. Check beforehand whether Hyper-V is still needed for anything else on this PC.
-
The mouse and keyboard stay inside the machine window. VirtualBox has captured them. The right Ctrl key releases them again.
For support
For support, provide the Setup Foundry version, the message word for word, the virtualization used (Hyper-V or VirtualBox), the Windows edition of the PC (Windows Home or Windows Pro), whether Hyper-V is switched on, the PC's memory, when the error occurred, and the error log.