Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


capei

Installing Hyper-V Causes License Loss

Recommended Posts

Hello,

I have just installed Hyper-V on my Windows 8.1 x64 installation that had a licensed copy of Aero Glass running. Upon reboot to finish the installation of Hyper-V, Aero Glass now shows its watermark and instantiates a messagebox titled "Information" and reads "This is free version of Aero Glass for Win8.1+ 1.4.6.610"... and includes my machine code and the option to copy it to my clipboard.

I have donated twice now and don't mind necessarily doing so again, but is there a fix for this? I have changed no hardware or installed anything else... just Hyper-V.

I searched the forum and found this thread:

but it appears to have no visible solution for this.

Thanks in advance :)

Edited by capei
fixed incorrect link

Share this post


Link to post
Share on other sites

Hello, sure thing. I'll get the output for both scenarios and post back once I get back from work :)

Share this post


Link to post
Share on other sites

So since I had Hyper-V installed, I ran the tool:

  • with it installed,
  • during uninstallation (pre-reboot)
  • after uninstallation (post-reboot)

and redirected the output to *.txt files. It seems the information only changed only after/post-reboot. The results:

 

Hyper-V Installed

SystemDrive C:             ZCH0BNA6, Machine ID: Q6UMOMLTPOG3ELI4MW7CLSCFGFULMBADAYLEKOMILLAVPRLA
PhysicalDrive0:             ZCH0BNA6, Machine ID: Q6UMOMLTPOG3ELI4MW7CLSCFGFULMBADAYLEKOMILLAVPRLA
PhysicalDrive1: NA7H1LE8, Machine ID: MZQ3IJLCPOG3ELI4IXO3LQMBGFULMBADQXLFZ6EILLAVPRLA

result: 2

Hyper-V Not Installed

SystemDrive C:             ZCH0BNA6, Machine ID: Q6UMOMLT2XAY6L2IMW7CLSCF6VLLL3C3AYLEKOMIBL7FXUEQ
PhysicalDrive0:             ZCH0BNA6, Machine ID: Q6UMOMLT2XAY6L2IMW7CLSCF6VLLL3C3AYLEKOMIBL7FXUEQ
PhysicalDrive1: NA7H1LE8, Machine ID: MZQ3IJLC2XAY6L2IIXO3LQMB6VLLL3C3QXLFZ6EIBL7FXUEQ

result: 2

 

Thanks again, and please let me know if you need anything else :)

Share this post


Link to post
Share on other sites

Thank you, at least now I know where the problem lies :-) I will try to find the easy solution.

  • Like 1

Share this post


Link to post
Share on other sites

No problem, and thank you! I eagerly await a future update/solution :)

Share this post


Link to post
Share on other sites

Sure thing :)

 

Hyper-V Installed

CPU:
D;0;0;0;47;65;6E;75;6E;74;65;6C;69;6E;65;49;E3;6;5;0;

Hyper-V Not Installed

CPU:
16;0;0;0;47;65;6E;75;6E;74;65;6C;69;6E;65;49;E3;6;5;0;

 

 

 

Entire output below in case you need it:

 

Hyper-V Installed

CPU:
D;0;0;0;47;65;6E;75;6E;74;65;6C;69;6E;65;49;E3;6;5;0;

HDD:
SystemDrive C:             ZCH0BNA6, Machine ID: M2VOWALCPOG3ELI42RQUL2Z3GFULMBADLPLJWCRILLAVPRLA
PhysicalDrive0:             ZCH0BNA6, Machine ID: M2VOWALCPOG3ELI42RQUL2Z3GFULMBADLPLJWCRILLAVPRLA
PhysicalDrive1: NA7H1LE8, Machine ID: K7JZJZLWPOG3ELI4LNB7LANBGFULMBAD7PL3DH5YLLAVPRLA

result: 2

Hyper-V Not Installed

CPU:
16;0;0;0;47;65;6E;75;6E;74;65;6C;69;6E;65;49;E3;6;5;0;

HDD:
SystemDrive C:             ZCH0BNA6, Machine ID: M2VOWALC2XAY6L2I2RQUL2Z36VLLL3C3LPLJWCRIBL7FXUEQ
PhysicalDrive0:             ZCH0BNA6, Machine ID: M2VOWALC2XAY6L2I2RQUL2Z36VLLL3C3LPLJWCRIBL7FXUEQ
PhysicalDrive1: NA7H1LE8, Machine ID: K7JZJZLW2XAY6L2ILNB7LANB6VLLL3C37PL3DH5YBL7FXUEQ

result: 2

 

Share this post


Link to post
Share on other sites

Thanks. Whole problem lies in Microsoft Win8.1+ (and higher) bug (errr, they called it "feature by design"), that it does not report all CPU-supported features when Hyper-V is enabled (i.e. when Hyper-V is disabled, it reports "Skylake-based processors", but when Hyper-V is enabled, it reports "Core 2 Duo 8000 series").

I will try to develop some workaround but I must ensure that it does not influence backward-compatibility.

  • Like 3

Share this post


Link to post
Share on other sites

No problem. And thank you for the explanation! Interesting that to know that Windows does this.

At any rate, thanks again for your time and attention to this matter-- can't wait for your next update. I'd say my donations were definitely well worth :)   

  • Like 1

Share this post


Link to post
Share on other sites

I've pinned this topic until it is fixed, so others with the same problem know about it.

  • Upvote 1

Share this post


Link to post
Share on other sites

Don't know if it matters, but I had to use the website to update my machine ID after I installed the 1809 upgrade. (Yes, I know 1809 isn't supported yet)
But AeroGlass was prompting me with a new machine ID. I don't think my hardware would have triggered it. I feel like this happened once before.
I think the last time I added a drive was back before 1803. I recently got a sata power splitter cable and got my blu-ray burner back online, but that didn't trigger it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×