Installing Hyper-V Causes License Loss

[capei]

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 September 23, 2018 by capei
fixed incorrect link

[bigmuscle]

Is it possible to get output from this utility before and after Hyper-V install?

http://glass8.eu/out/LicensingTool.zip

[capei]

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

[capei]

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

[bigmuscle]

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

[capei]

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

[bigmuscle]

I updated LicensingTool a bit. Could you redownload and provide CPU part of the output (before and after)?

http://glass8.eu/out/LicensingTool.7z

Edited September 25, 2018 by bigmuscle

[capei]

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

 

[bigmuscle]

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.

[capei]

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    

[bigmuscle]

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

[Klamatiel]

I don't use HyperV, but i can test that if you want. My CPU is an I5-4670K ( https://ark.intel.com/products/75048/Intel-Core-i5-4670K-Processor-6M-Cache-up-to-3-80-GHz-?q=4670k ) coupled with AsRock Z97 Pro3 ( http://www.asrock.com/mb/Intel/Z97 Pro3/#Specification ).

Edited September 28, 2018 by Klamatiel
spelling/yadda yadda

[netsendjoe]

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.

[bigmuscle]

I am unpinning this topic as it should be fixed now in the latest release.

Keys are now generated regardless the HyperV flag and both HyperV on and off keys are accepted.

[SkyySX]

One question @bigmuscle, I'm looking to install Hyper-V for the first time now on Windows 10 1809, will it affect Glass8 in any way if I already run version 1.5.10?