[QUOTE="Vaijj, post: 290519, member: 3237"
You should also have a look in settings/update & security/Windows defender and see if its on or not. For some reasons you sometimes have to turn it on or off to get it to scan occasionally, it isn't meant to come on by itself by default. I will be very suprized if it has anything to do with the file or keygen itself.[/QUOTE]

windows defender is totally off, i almost eradicated it from my system through all know methods ;)

Oh im sure it has nothing to do with the keygen, its a system based problem, somehow, somewhere...very strange indeed.

 

don't bother for the .cmd it's just for recent releases...

have you tried enable the built-in administrator account and try from there?

 

I have no clue on how to do this, so i checked Google , came up with this :

http://www.zdnet.com/article/window...n-administrator-account-and-why-you-shouldnt/

But they advise not to do it...should i? How can i revert back to my normal account?

 

It's just to verify if it's not a due to a policy (like user rights assignments) or a corrupted account...you can disable afterwards (always better yes, it's just for maintenance or managing in a multi computer environment) and even erase the c:/users/administrator folder after if not deleted (I don't remember if it is). Like, you enable, you log-in, you try the keygen, then disable/erase...
Just to verify if it's the user account or the system, anyway it's not the same registry so it won't solve the pb, but helps to target the pb.

run command prompt as admin then type :
net user administrator /active:yes

or enable it from the computer management snap-in (run: compmgmt.msc), under "Local Users and Groups/users". There you can also verify that your primarily user is member of administrators group, (just to be sure your user is really an admin)

It's just like adding a new user, so you can log out and log in to your normal user

 

Last edited by a moderator: Oct 21, 2017

AMAZING....it worked! How could i thank ever thank you. you are the man...the cow....loll

Ok but now...just for diagnosis purposes. Why did it worked in the built in administrator account and not my normal account ( wich i thought was allready an administrator accout ) Is there a way to migrate the same functionnalities from one to the other? sorry im a total noob regarding these matters. This is way above my head....

 

ok great! but, since it's not the same registry...won't be authorized in your normal account.

*corrected : yes it will be authorized since SNO and KEY are located under HKEY_LOCAL_MACHINE registry key.

verify like I said before in the computer management snap-in if your "normal" user is member of administrators group.

 

Last edited by a moderator: Oct 21, 2017

Whats weird, is that it did authorize it! All good to go...i thought about not being the same registry...but its ok now.

Sorry for pursuing this matter and for your time, but could you elaborate on your last line? Im confused by what you meant.

computer management snap-in? Maybe you could point me to a link that explains on how to do this?

 

ok cool are you logged on your normal account or are you logged on the built-in administrator (the "temporary" account you created)? Just thinking now...yes it's normal it works since the SNO (serial number etc.) is usually located under HKEY_LOCAL_MACHINE key (shared between users) and not HKEY_CURRENT_USER for Native Instruments products.

Just type computer management in the search bar or right click on start menu and run: compmgmt.msc

Then under "Local Users and Groups/users", you can enable/disable admin/guest/etc accounts, but also verify that your primarily user is really a member of the administrators group (its just to be sure your user is really admin) I personally added myseld to all the existing groups just in case hehe.

 

Last edited by a moderator: Oct 21, 2017

So i got lucky this time...ok ill try and plow my way through what you said as its still not very clear, kind of confusing all this Groups, Users, Admin groups, guests accounts....one can easily get lost, wich is my case! Ill let you know if i suceeded...thanks again man! Great help

 

I got the same problem. R2R keygen's not work last weeks.

I have found that
Windows defender prevent R2R keygen.
But when I start keygen.exe, Consent.exe and dllhost exe + dllhost.exe starts. (dllhost.exe two times)

So I should change registry or daha which is prevented by consent.exe.

someone has any idea?
Thank you.

 

i used it as u say and still same no result . i'm getting depressed.

i have this issue with spectrasonics keygen R2R

 

Just create a folder called keygen exclude this folder and your windows temp folder. This should do the trick.

 

Mine was an anti-virus program that caused my issue

 

Dear i was blocked in same fxxk.... Send me request on [email protected]
Will send u file which will open smoothly

 

Exactly. The first thing everybody should do to up the security and make user experience better is to disable all the MS security features and user experience tools.

Must love MS. "Loving" them since about '94... [whilst using Atari and Mac...] They're just like those fungi you get in a public pool... simply unavoidable.

 

i had this problem a while back.. my solution was to make a folder exclusion and a file exclusion in windows defender for any keygen that gets flagged and the folder it is located in.. works like a charm for me without the headaches of disabling windows features that will most likely come back when windows updates..

 

What has worked for me is to boot in safe mode then it usually runs.

 

In Defender I excluded the folders I store all cracked stuff in, and YES the temp folder is used, too.
Anything that gets caught by the temp folder use I have just temporarily turned off Defender active monitoring in its setting window while I run the keygen and then turn it back on.

 

The DoubleTake exclusion method worked for me. Many thanks!
Remember to cancel the exclusions when done so Windows can do it's job.

 

Messing with your account, rights management and security to run keygens isn't the smartest thing to do. Neither is deactivating all anti-virus.

A much better way is to install e.g. Sandboxie (it's free, just gives you a nag screen after 30 days) and run every keygen in a secure sandbox environment. Just temporarily deactivate your anti-virus, right click the keygen and "run in sandbox".