Hello Ventuzians!
THE FORUMS ARE CLOSED!

Please join our discord server HERE!! << click me :D

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!

Licensing issues on MacBook Pro

Please report bugs in this group. We will maybe populate a list of known bugs with a possibly modified description at a later time.

Moderator: Support

Post Reply
framefactory
Posts: 2
Joined: 01 Mar 2021, 15:33

Licensing issues on MacBook Pro

Post by framefactory » 01 Mar 2021, 15:44

I'm having troubles starting Ventuz 6.8.0 on my MacBook Pro (running native Windows 10 Pro via Bootcamp). I've added licenses for both Ventuz Community Studio and Ventuz PLE, and they properly show up in the license manager. When trying to start the application, I get the following notice:

Use of unlicensed feature(s). Run on virtual machine. Process needs to shutdown! Please contact your sales agent to enable features.


Note that I'm not using any virtualization, just a dual boot with native Windows 10 Pro.

Cheers and thanks for your help!
Ralph

User avatar
Karol
Posts: 640
Joined: 10 Jan 2012, 12:07

Re: Licensing issues on MacBook Pro

Post by Karol » 03 Mar 2021, 16:43

Hi Ralph,

Long time - no see!

PLE and Community are not allowed to run in a VM.
We use some characteristics to determine if the OS is running in a VM.
Could you please check if Hyper-V is enabled in your Windows installation?

Best Regards
Karol

framefactory
Posts: 2
Joined: 01 Mar 2021, 15:33

Re: Licensing issues on MacBook Pro

Post by framefactory » 04 Mar 2021, 14:51

Thanks, Karol. Hope you're doing well! Say hi to Ralf and the rest of the team.

Hyper-V is not enabled, the first thing I checked. There are virtualization settings at the BIOS level, but the MacBook unfortunately doesn't allow to change any BIOS settings. Bad luck with this laptop then, I guess.

Thanks again,
Ralph

Post Reply