- Mar 30, 2014
- 468
I'm having problems activating it with my commercial license.View attachment 186244
EDIT: I figured it out. I had to do a fresh install, NOT a upgrade.
An upgrade 2019 over 2018 can be (should be) done always when both are final releases (or TR), not RC or Beta
if you got it from where we got it, then it's safe
I think these TR installers have been leaked via KL Support -> to some users... (as every new year versions)
Probably final installers will have a different hash, usually because:
- Integrated new updates or patches.
- Fixed links to final online help.
- Minor changes.
if you got it from where we got it, then it's safe
but without more info we can't tell, this says nothing
the safe exe should be signed by Kaspersky and should open the usual installer Kaspersky products have
yea you're fineYes It is signed by Kasper.
The hash is: dd1a79d19e53fa792f0bdb377f7e35b0
See here: Kaspersky Application Advisor - Kaspersky Whitelist
I'm not getting this issue... every installer is EVERY INSTALLER or unknown installers? did any tweaks to the config?
This is because You disabled "Trust in digitally signed applications" it's normal behaviour, even keeping KSN rules on...
same issue i was having in my VM, it seems either KSN integration isn't working or something, but every single thing gets put to untrustedSo far I had to turn off KTS to install Sumo.
Directory Opus required me to manually move all temp files to low restricted from Untrusted...
The only tweak I applied was to turn off automatically trusting signed software. Categories are set to automatically be set by the cloud
View attachment 186327