Hardware identifier feature - useless
Hardware identifier feature - useless
Hello,
I cannot use this feature in our commercial product.
1) Key do not work(wrong hw) just after installing HyperVisor client (Vmachine) on Windows 8.1 PRO and Windows 10 PRO- (probably CPU value)
(NOT inside vm, in parent OS where protected software is installed!)
2) It do not allow do reinstall OS on the same computer - shows wrong HW id, so practically also useless.
All software protector vendors offer flexibility regarding that, developer is able to choose which values should be checked for example: only CPU, or only Ethernet or all options.
I cannot use this feature in our commercial product.
1) Key do not work(wrong hw) just after installing HyperVisor client (Vmachine) on Windows 8.1 PRO and Windows 10 PRO- (probably CPU value)
(NOT inside vm, in parent OS where protected software is installed!)
2) It do not allow do reinstall OS on the same computer - shows wrong HW id, so practically also useless.
All software protector vendors offer flexibility regarding that, developer is able to choose which values should be checked for example: only CPU, or only Ethernet or all options.
Re: Hardware identifier feature - useless
Especially when it's not possible to send custom data and code own checking in relation to Web license manager:
http://vmpsoft.com/forum/viewtopic.php?f=4&t=2814
I confirm after installing HyperV client and reboot Windows 10 serial state is wrong.
I agree that giving flexibility to developer is better than thinking for him what will be better and hardcode algo checking.
It should be fully configurable at SDK/DDK
http://vmpsoft.com/forum/viewtopic.php?f=4&t=2814
I confirm after installing HyperV client and reboot Windows 10 serial state is wrong.
I agree that giving flexibility to developer is better than thinking for him what will be better and hardcode algo checking.
It should be fully configurable at SDK/DDK
- Attachments
-
- HW_Hyper.png (125.41 KiB) Viewed 18905 times
Re: Hardware identifier feature - useless
It seems that the installed HyperV changes CPU value in HWID.
Re: Hardware identifier feature - useless
Checked it and I can only acknowledge. CPU is changing.Admin wrote:It seems that the installed HyperV changes CPU value in HWID.
There is needed swift, flexible system for checking cetrain values which will work with license manager.
Possibility to choose which values are send to web server or later checked could be solution and allow developer for more flexibility.
Re: Hardware identifier feature - useless
Any updates so far which fix mentioned issues? E.g.
Re: Hardware identifier feature - useless
Hello guys,
I have same problem - checked on public demo version.
Developer should have option to make allow+1 change.
I can't find this option in SDK or in VMP GUI
Operating system change with format make key useless
(values passed while activation are different on system reinstall)
CPU+Ethernet in some cases could be enough.
With using online php Activation server developer should have possibility which and what values to check.
If you implement this feature I will be happy to buy Ultimate License.
Regards from Germany
I have same problem - checked on public demo version.
Developer should have option to make allow+1 change.
I can't find this option in SDK or in VMP GUI
Operating system change with format make key useless
(values passed while activation are different on system reinstall)
CPU+Ethernet in some cases could be enough.
With using online php Activation server developer should have possibility which and what values to check.
If you implement this feature I will be happy to buy Ultimate License.
Regards from Germany
Re: Hardware identifier feature - useless
VMProtect and WebLM already allow to change one "device" in HWID, so don't need any additional option for this.
Re: Hardware identifier feature - useless
Admin wrote:VMProtect and WebLM already allow to change one "device" in HWID, so don't need any additional option for this.
This is what I'm talking about, it shoud allow 1+1 or +custom number or (and) type.
Now it cause troubles after system reinstall since users usually do reformatting which cause HDD + SYS change
Other problem is CPU with Hyper-v
Everything is already explanied nonsense to repeat again the same.
Yes there is problem with current solution.
Thanks
Re: Hardware identifier feature - useless
We are not going to change anything here, because it's useless.This is what I'm talking about, it shoud allow 1+1 or +custom number or (and) type.
Re: Hardware identifier feature - useless
Either you have problem with English understanding or you aren't developer
Please show it to developer, it's obvious disadvantage/bug.
Looks like it's time wasting support.
скоко тебе лет?
Please show it to developer, it's obvious disadvantage/bug.
Looks like it's time wasting support.
скоко тебе лет?
Re: Hardware identifier feature - useless
still no basic option which EVERY other protection software has to choose how many and which Hardware is checked?
Should re-install Windows make HWID bad - NO. Still it have this bug BUG.
Should re-install Windows make HWID bad - NO. Still it have this bug BUG.
Re: Hardware identifier feature - useless
Maybe same problem to me.
If you enable/disable Hyper-V and restart, the hwid will change.
If you enable/disable Hyper-V and restart, the hwid will change.