"Compilation Of Tutorials, Guides, Tips & Updates"

[xyzdev]

I was using the Windows Firewall IP block but since it stopped working, i was just going to run the trial.

I uninstalled IDM a couple of times (with Total Uninstall), i followed this, but no key was found in the multiple times i've tried. I also followed this & this. But, no matter what i do, i end up getting this nag once i download something.

 

 

Am i missing something here?!

After uninstall i didn't register it. I just ran the trial.

 

[Undertaker]

6 minutes ago, xyzdev said:

Am i missing something here?!

 

 

1. Close your IDM fully, modules, agent, background task etc.etc.

 

2. Then follow this guide:-

http://www.nsaneforums.com/topic/222515-compilation-of-tutorials-guides-tips-updates/?do=findComment&comment=1228895

 

3. Do not open IDM yet.

4. Reinstall IDM(just run the setup file again over your already installed IDM without uninstalling).

 

Tell what happens.

[xyzdev]

@Undertaker 

 

I cannot find that key. These are the only ones with 'Empty CLSID key'

 

[Undertaker]

6 minutes ago, xyzdev said:

I cannot find that key. These are the only ones with 'Empty CLSID key'

Hope you have switched to 32-bit mode of RTKF.

 

If you are already in 32-bit mode, try deleting the keys with 'Empty  CLSID key' description and follow the same post as above.

[xyzdev]

Yes, i was using 32-bit mode.

 

It worked! I deleted those 2 entries with 'Empty  CLSID key' and installed IDM over the already installed IDM. No more NAGS!!

 

Thank you

 

EDIT: After further testing, it was the {9b3ae45e-4c95-6b29-2465-96139072fe2e} key which needed to be deleted in my case.

[Undertaker]

Remove Fake Serial Notification

 

 

1. Close your IDM fully (modules, agent, background task, etc.)

 

2. Follow this post : Deleting the Visual Protect 3.5+ Key

    If not present, move on to the next step.

 

3. Next, follow this post : Removing the Fake Serial Nag at Downloads

 

 

 

 

[Undertaker]

@xyzdev Thanx for your feedback, I'm out of likes/thanks but really appreciate your inputs.

[nihilt]

No need to reinstall IDM, deleting Empty CLSID keys will suffice. Using Adguard method here.

 

 

 

6f4506dc-bd28-8ba9-6766-a2f4d9245633

a15749f3-f0d8-6791-cc03-bb93d86e6349

D5B91409-A8CA-4973-9A0B-59F713D25671

de8a0dbb-214d-11d9-4dcf-14987a511757
 

 

[tomm]

22 minutes ago, nihilt said:

No need to reinstall IDM, deleting Empty CLSID keys will suffice. Using Adguard method here.

 

  Hide contents

 

6f4506dc-bd28-8ba9-6766-a2f4d9245633

a15749f3-f0d8-6791-cc03-bb93d86e6349

D5B91409-A8CA-4973-9A0B-59F713D25671

de8a0dbb-214d-11d9-4dcf-14987a511757
 

 

IDM creates different CLSID keys for each computer so posting your CLSID keys here is useless for other members

[hamanokaito]

22 minutes ago, tomm said:

IDM creates different CLSID keys for each computer so posting your CLSID keys here is useless for other members

 

That's right. IDM check SID for any pc after install. After creates keys other.

 

[sledge101]

1 hour ago, hamanokaito said:

 

That's right. IDM check SID for any pc after install. After creates keys other.

 

Correct.    It creates a different clsid keys.  You can actually find the parent registry keys and delete those registry keys and everything will follow .  If you still cannot find keys noted in REg Thrash cleaner and you still get a nag later... there is some keys left that need to be deleted which was re created due to idm still calling home which creates the keys again....   and creates a value of Mdata entry responsible for the nagging issue--> needs to be deleted. In other words block first your idm before activation so to prevent this Mdata key when using random or keygen keys.  For retail. it doesnt matter at all. As once connected and called back, creates 3 keys in a clean install or decontaminated idm.  

 

1. Reg encrypted vp=key  for retail.  Be careful, you dont need to delete it for retail genuine activation. 

2. 6D key --> Mdata key / Therad/Model. Creates branch keys if non genuine

3. D5 key --> Rerouted check to 6D. Creates branch keys if non - genuine

4. 079 key -->  Safe to delete

 

 

@taker,  mines not need to reinstall over unless i install the update from latest version. Nil for issues as long as keys has been decontaminated with no recurrence and block from calling home.

 

 

 

 

[hamanokaito]

12 minutes ago, sledge101 said:

Correct.    It creates a different clsid keys.  You can actually find the parent registry keys and delete those registry keys and everything will follow .  If you still cannot find keys noted in REg Thrash cleaner and you still get a nag later... there is some keys left that need to be deleted which was re created due to idm still calling home which creates the keys again....   and creates a value of Mdata entry responsible for the nagging issue--> needs to be deleted. In other words block first your idm before activation so to prevent this Mdata key when using random or keygen keys.  For retail. it doesnt matter at all. As once connected and called back, creates 3 keys in a clean install or decontaminated idm.  

 

1. Reg encrypted vp=key  for retail.  Be careful, you dont need to delete it for retail genuine activation. 

2. 6D key --> Mdata key / Therad/Model. Creates branch keys if non genuine

3. D5 key --> Rerouted check to 6D. Creates branch keys if non - genuine

4. 079 key -->  Safe to delete

 

 

 

 

 

 

 

I still delete keys in CLSID and nothing matter with me !?

6D,D5 all check key genuine.

079 creates trial for software.

And software add 3 keys for 2 key nag, one key check sv genuine.

[dcs18]

Once any of the new methods (to prevent IDM from calling home) is correctly implemented and the registry key/s responsible for the nags deleted, IDM should retain activated status regardless of any future registry key/s generated (never mind even if one used a blacklisted key to register ones copy.)

[sledge101]

28 minutes ago, hamanokaito said:

I still delete keys in CLSID and nothing matter with me !?

6D,D5 all check key genuine.

079 creates trial for software.

And software add 3 keys for 2 key nag, one key check sv genuine.

did you use permission block method previously?  i tried your patch it works good but for a newbie  they may have a problem restoring the parent and branch keys" responsible for that . if you delete the parent key only but the branch keys associated with them still exist then you might encounter an issue.

 

As i posted previously , this will all be nullified if your blocking is working as idman.exe reads those parent keys and branch keys.  This is the most improtant of all. have a good blocking method comfortable for you and you may decontaminate idman for traces and recurrences.  I have tested this one over and over again and results no recurrences of those thrashes. Once IDM passes calling home, you will get recreation of keys.and get the so called nag....

 

@dcs18 im no even using blacklisted keys or keygen keys, I typed my own key.  as long as you block IDMAN calling home ( VERY IMPORTANT)

 

[Undertaker]

I don't know why reinstall IDM was such a big thing, removed nonetheless.

[sledge101]

So far i tested and confirmed working in latest build under windows 10 1703/ 8.1/7

Adguard

DNSCRypt

InternetLock

Registry permission block (restore issues not only the parent key but their branch keys as well) need not to block all  clsid under registry just the idm clsid in registry.. so as not to affect other clsid programs.  Overall if you know the method, quite good as my feedback. 

Cfosspeed :  personally not tested as no cfosspeed installed.

 

 Cleaner should be updated especially finding empty clsid keys on specific registry for idm  besides doing reg thrash cleaning method just in case.

 

 

[Undertaker]

Acrylic DNS block + Win FW IP block is also working

[dcs18]

 

[sledge101]

1 minute ago, Undertaker said:

Acrylic DNS block + Win FW IP block is also working

haha thank you... i never really tried acrylic dns sorry but as you say --Working - Thumbs up. so far , i posted those things to let people know that they are definitely working.

 

NAGGING RECURRENCE =  POOR IDM BLOCKING METHOD.

[Undertaker]

3 minutes ago, dcs18 said:

 

In Simple DNSCrypt, the ones that do provide DNSsec have high ping for me.

[sledge101]

1 minute ago, Undertaker said:

In Simple DNSCrypt, the ones that do provide DNSsec have high ping for me.

the clock, show information on the lowest ping you have, i have used asian dns resolved and compared to the original just 1-2 seconds delay browser response. Doesnt matter on me....

[dcs18]

2 minutes ago, Undertaker said:

In Simple DNSCrypt, the ones that do provide DNSsec have high ping for me.

Can you elaborate?

[Undertaker]

Just now, sledge101 said:

the clock, show information on the lowest ping you have, i have used asian dns resolved and compared to the original just 1-2 seconds delay browser response. Doesnt matter on me....

Lowest ping do not have DNSsec.

 

 

Just now, dcs18 said:

Can you elaborate?

As you know not all servers in SimpleDNSCrypt provide DNSsec facility, and the ones that do provide DNSSec facility, have high pings for me.

[sledge101]

Just now, Undertaker said:

Lowest ping do not have DNSsec.

in your setting ?  hmmm.  did you update the dns resolved sites?

 

i updated it initially in the program the lowest possible ping has no dnssec iniitally but updated the package and found a good one near my location.... with dns sec. 

[Undertaker]

2 minutes ago, sledge101 said:

in your setting ?  hmmm.  did you update the dns resolved sites?

 

i updated it initially in the program the lowest possible ping has no dnssec iniitally but updated the package and found a good one near my location.... with dns sec. 

Yes I did update the resolver list. Infact, it was updated several times a day. The closest ping to my location was 42ms and that didn't have DNSsec, the ones with DNSSec was running into 100ms atleast, and sometime in the range of 300-400ms.