Hi,
I've just tried to install Ventuz for the first time and I'm unable to open Ventuz Designer - it gives me an error message which says:
Use of unlicensed feature(s)
Run on virtual machine. Process needs to shutdown!
Please contact your sales agent to enable features.
This machine isn't running a VM - it's a native Windows 10 desktop and I've checked that Hyper-V is disabled already. How can I bypass the issue?
Thanks,
Joe
Hello Ventuzians!
THE FORUMS ARE CLOSED!
Please join our discord server HERE!! << click me
We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server
Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!
THE FORUMS ARE CLOSED!
Please join our discord server HERE!! << click me
We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server
Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!
"Virtual Machine" error preventing opening
Moderator: Support
Re: "Virtual Machine" error preventing opening
Hey and welcome,
if you a re pretty sure you disabled it in the bios and for windows:
User Manual System Requirements - Hyper V
due to the fact of nature it could be needed to reboot the machine several times until hyper-v is completely off for the OS.
regArts
Dee
if you a re pretty sure you disabled it in the bios and for windows:
User Manual System Requirements - Hyper V
due to the fact of nature it could be needed to reboot the machine several times until hyper-v is completely off for the OS.
regArts
Dee
-
- Posts: 2
- Joined: 10 Sep 2021, 18:01
Re: "Virtual Machine" error preventing opening
Hi Dee,
Yes, I've checked and it's disabled both in BIOS and Windows and I'm still getting the same error after multiple reboots.
Is there anything else it's checking for that I could eliminate from the equation or a way to debug what's causing it to flag and bring up the error?
Thanks,
Joe
Yes, I've checked and it's disabled both in BIOS and Windows and I'm still getting the same error after multiple reboots.
Is there anything else it's checking for that I could eliminate from the equation or a way to debug what's causing it to flag and bring up the error?
Thanks,
Joe