Update to Instalod 2020 with Free Seat License: Authorization Error

Answered
Follow
Simon P

Hi there,

I just tried to update to the new 2020 version of instalLOD Studio XL.Did uinstall my previous version as prompted by the installer. If I then try to authorize my machine with the new version i get the following error:

"Authorization Failed" Authorized Machine but license not entitled for virtualization/remote sessions. Please deactivate this machine to avoid hitting machine activation limit.

Thing is: I only use one machine (the one the previous version was running fine on), no others were used for authorization.

What to do?

Cheers,

Simon

0

Comments

11 comments

Date Votes
  • Official comment
    Andreas Strunski
    • Edited

    Hello Simon,

    As we always recommend upgrading InstaLOD to the latest version, we typically don't provide older versions for download.

    To get InstaLOD Studio XL 2020 or InstaLOD Pipeline 2020 working on your machine again, I'd recommend trying to disable Hyper-V under Windows. More information on how to enable or disable Hyper-V can found in the Microsoft documentation.

    Thanks,

    Andreas

    Comment actions Permalink
  • Andreas Strunski

    Hello Simon,

     

    With the release of the InstaLOD 2020 product wave, using InstaLOD in a remote session or on a virtual machine requires a new license entitlement. Do you use a VM on your computer?

     

    Thanks,

    Andreas

    0
    Comment actions Permalink
  • Simon P

    Hi Andreas,

    Thanks for your reply and sorry for the wait.. Happy new year!

    To Answer your question: No I am not. At least not for or in conjunction with InstaLOD.
    I do have Hyper-V installed though as I did try some ML things with docker recently. However as far as I can remember I did install it after trying to update to the new 2020 version of instalod.

    Cheers,

    Simon

    0
    Comment actions Permalink
  • Simon P

    Hi Again,

    I just tried to go back to InstalodStudio2019 unfortunately you removed the downloads from the instalod cloud. Could you please add them again so I can at least do my work? I also tried authorization with instaLodCmd.exe and it works for the 2019 version but refuses to update for the 2020 version (see screenshot attached). Any help to get this working again would be highly appreciated.

    Cheers

    Simon

    0
    Comment actions Permalink
  • Simon P

    Hi Andreas,

    And Indeed, removing Hyper-V solved the issue. Thanks for the hint, I would have never guessed it would interfere in such a way.

    What I do not understand is: Why does the mere existence of it disturb instaLOD in such a way that it ceases to work? I mean, InstaLOD is not installed on the VM or anything. And I need the VM for some of my work. So as a feature request: Please allow a VM to be installed on the same computer InstaLOD is installed on.:)

    Thanks and enjoy your week,

    Cheers,

    Simon

    0
    Comment actions Permalink
  • Andreas Strunski

    Hello Simon,

    It's great to hear that you're able to use InstaLOD again.

    We will consider weakening the virtualization checks in an upcoming release. In the meantime, please disable Hyper-V when using InstaLOD as a workaround.

     

    Thanks,

    Andreas

    0
    Comment actions Permalink
  • Simon Velthuis

    Hi Simon

    I do have the excate Same Problem, unfortunatly disabling Heyper-V did not solve the Problem:

    Cheers Simon

    0
    Comment actions Permalink
  • Support
    Hello Simon,
     
    After changing Hyper-V settings in some cases Windows needs an additional restart to have the changes in full effect.
    Also please make sure that you are not connected through Remote Desktop or similar connections as these will also prevent InstaLOD from execution.
     
     
     
    Thanks,
     
    Erhan
    0
    Comment actions Permalink
  • Ben Woodford

    Has there been any update on this? It seems nonsensical to check if Hyper-V is running on the host when InstaLOD is running on the host.

    It would also be useful to know what it has detected, I've just shutdown Parsec and Streamer and still get the error so I guess it is Hyper-V still?

    0
    Comment actions Permalink
  • Norbert

    For me, it took a few more steps - but finally it works.

    https://petri.com/how-to-disable-hyper-v-completely-in-windows-10/

    1
    Comment actions Permalink
  • Andreas Strunski

    Thanks, Norbert, for sharing the link!

     

    Hello Ben,

    please excuse us for missing your post. If you didn't have any remote control apps running, it's very likely that Hyper-V was still causing the issue.

    I can confirm that in some cases it may be necessary to use the command line to fully disable Hyper-V:

    bcdedit /set hypervisorlaunchtype off

    In addition to Norbert's link, more information on the BCEDIT command can also be found in the Microsoft documentation:

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdedit-command-line-options?view=windows-11 

    Thanks,

    Andreas

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post