Adobe Tool
#41
Unfortunately, the older stable tool (v.3.7) doesn't seem to work on Windows 10. Is there a way to make it run? Tried a few compatibility modes with no success.
Reply
#42
I have 4.9.4.0 which afaik is the latest version. I posted it up here: https://dropfile.to/sKkXI (although I guess this website makes it expire after 24 hours).

Here's another, not sure if this one expires: http://uploadduck.com/48e

(Aug 02, 2015, 20:05 pm)panic82 Wrote: I have 4.9.4.0 which afaik is the latest version.  I posted it up here: https://dropfile.to/sKkXI (although I guess this website makes it expire after 24 hours).

Here's another, not sure if this one expires: http://uploadduck.com/48e

Btw, here's the virustotal for that rar.  I don't think any of the "detected" items are legit, everything just says Generic and has no specific issue.  At least I hope so, because I've used it several times over the last 6+ months Smile.
Reply
#43
appreciate the work thanks guys
Reply
#44
So I checked Adobe Tool's Profile and he hasn't been on since he made this post which was back in Mar 14, 2015, 14:40 pm. It's August already and I would suggest that this thread is dead.... Hopefully he'll make a new profile or come give us some great news if there is still hope. Big Grin
Reply
#45
Does anyone know how do I make the hosts file work? At first I thought I had the outdated Adobe activation servers list, but then the same list checks out on another system - a laptop running Windows 7, it reports that the adobe activation is blocked.

I used the same tool/list to create the same hosts file on Win 8.1 and Win 10 and the tool reports that the hosts file is correctly "patched" but at the same time it reports that Adobe activation isn't blocked. I tried everything, flushing the DNS cache for like 100 times, tried everything that I could find on the Internet and what I could think of myself and nothing worked.

It's as if Windows ignores the hosts file.

It's curious that everything worked, even Adobe Tool v3.7 on Windows 8.1 Enterprise Preview, but when the preview expired I installed the regular Windows 8.1 Pro VL and Adobe Tool v3.7 wouldn't work anymore and though the v4.x did work it reported the aforementioned problem - that the hosts file doesn't block adobe activation. Same thing on recently upgraded Windows 10.

Is there another way of blocking those hosts? I really need to run PS on this new system and I only have it up and running on the old/slow/lousy display laptop. Even the Adobe Update works on it and I've just received Camera Raw latest update the other day, but can't have it on my new laptop.
Reply
#46
(Aug 13, 2015, 20:22 pm)kriket Wrote: ...

Is there another way of blocking those hosts? I really need to run PS on this new system and I only have it up and running on the old/slow/lousy display laptop. Even the Adobe Update works on it and I've just received Camera Raw latest update the other day, but can't have it on my new laptop.

For hosts, disable Defender/other antivirus and use V.3.7. Always had similar issues with v4.
Reply
#47
Thanks, already tried disabling Defender, no luck. v3.7 wouldn't work on Win 8.1 Pro and it doesn't work on Windows 10.

It did work on Win 8.1 Enterprise Preview a few months back (as I already said), but not anymore on these other/newer Windows. Although I can't seem to figure out the difference between Win 8.1 Enterprise and Win 8.1 Pro that renders Adobe Tool v3.7 broken. (cryptic "module 7 error")

Though, now I'm thinking, if you think that Adobe Tool v4 is at fault, that maybe the hosts file works even though the Tool v4 claims it doesn't. If the Tool is at fault, maybe I should just ignore that report and go ahead with the installation. I guess noone would know how it'd turn out until tried.
Reply
#48
(Aug 18, 2015, 18:54 pm)kriket Wrote: Thanks, already tried disabling Defender, no luck. v3.7 wouldn't work on Win 8.1 Pro and it doesn't work on Windows 10.

It did work on Win 8.1 Enterprise Preview a few months back (as I already said), but not anymore on these other/newer Windows. Although I can't seem to figure out the difference between Win 8.1 Enterprise and Win 8.1 Pro that renders Adobe Tool v3.7 broken. (cryptic "module 7 error")

Though, now I'm thinking, if you think that Adobe Tool v4 is at fault, that maybe the hosts file works even though the Tool v4 claims it doesn't. If the Tool is at fault, maybe I should just ignore that report and go ahead with the installation. I guess noone would know how it'd turn out until tried.

This is strange, I have it now working on Win 10. Try it on Safe Mode. Worst case scenario, use VMware Player or Virtual Box to make a virtual Windows XP/7 machine, and create/copy/check your hosts from there. Once set up once, it should be easy.
Reply
#49
Here's what's worked for me on Win 7 Ultimate x64, Win 8 Pro x64, and Win 8.1 Enterprise x64. I haven't ventured into Win 10 yet.

================

1. Patch hosts file manually (or optionally with AT) & flush DNS.
2. Optionally (just for certainty), verify hosts patch success with AT.
3. Disable network adapter(s).
4. Obtain serial from X-force Keygen Readme (or optionally AT).
5. Launch installer and install Adobe application using above serial.
6. Run Adobe application.
7. When requested to sign in to Adobe account, select, "Sign in later".
8. Get request code from Adobe application.
9. Submit serial & request code to X-force Keygen to obtain response code.
10. Activate Adobe application with response code.
11. Repeat steps 4-10 for each other desired Adobe application.
12. Enable network adapter(s).
13. Update all Adobe applications.

================

To manually patch the hosts file, insert the following:

# <Adobe Licensing Blocks>
#
127.0.0.1 3dns.adobe.com
127.0.0.1 3dns-1.adobe.com
127.0.0.1 3dns-2.adobe.com
127.0.0.1 3dns-3.adobe.com
127.0.0.1 3dns-4.adobe.com
127.0.0.1 activate.adobe.com
127.0.0.1 activate.wip.adobe.com
127.0.0.1 activate.wip1.adobe.com
127.0.0.1 activate.wip2.adobe.com
127.0.0.1 activate.wip3.adobe.com
127.0.0.1 activate.wip4.adobe.com
127.0.0.1 activate-sea.adobe.com
127.0.0.1 activate-sjc0.adobe.com
127.0.0.1 adobe-dns.adobe.com
127.0.0.1 adobe-dns-1.adobe.com
127.0.0.1 adobe-dns-3.adobe.com
127.0.0.1 adobe-dns-4.adobe.com
127.0.0.1 adobe-dns-2.adobe.com
127.0.0.1 adobeereg.com
127.0.0.1 cmdls.adobe.com
127.0.0.1 crl.verisign.net
127.0.0.1 ereg.adobe.com
127.0.0.1 ereg.wip.adobe.com
127.0.0.1 ereg.wip1.adobe.com
127.0.0.1 ereg.wip2.adobe.com
127.0.0.1 ereg.wip3.adobe.com
127.0.0.1 ereg.wip4.adobe.com
127.0.0.1 hl2rcv.adobe.com
127.0.0.1 lm.licenses.adobe.com
127.0.0.1 lmlicenses.wip4.adobe.com
127.0.0.1 na1r.services.adobe.com
127.0.0.1 na2m-pr.licenses.adobe.com
127.0.0.1 ood.opsource.net
127.0.0.1 practivate.adobe
127.0.0.1 practivate.adobe.com
127.0.0.1 practivate.adobe.ipp
127.0.0.1 practivate.adobe.newoa
127.0.0.1 practivate.adobe.ntp
127.0.0.1 prod-rel-ffc-ccm.oobesaas.adobe.com
127.0.0.1 wip.adobe.com
127.0.0.1 wip1.adobe.com
127.0.0.1 wip2.adobe.com
127.0.0.1 wip3.adobe.com
127.0.0.1 wip4.adobe.com
127.0.0.1 wwis-dubc1-vip60.adobe.com
127.0.0.1 www.adobeereg.com
127.0.0.1 www.wip.adobe.com
127.0.0.1 www.wip1.adobe.com
127.0.0.1 www.wip2.adobe.com
127.0.0.1 www.wip3.adobe.com
127.0.0.1 www.wip4.adobe.com
#
# </Adobe Licensing Blocks>
Reply
#50
(Aug 19, 2015, 03:38 am)Bayhey Wrote:
(Aug 18, 2015, 18:54 pm)kriket Wrote: Thanks, already tried disabling Defender, no luck. v3.7 wouldn't work on Win 8.1 Pro and it doesn't work on Windows 10.

It did work on Win 8.1 Enterprise Preview a few months back (as I already said), but not anymore on these other/newer Windows. Although I can't seem to figure out the difference between Win 8.1 Enterprise and Win 8.1 Pro that renders Adobe Tool v3.7 broken. (cryptic "module 7 error")

Though, now I'm thinking, if you think that Adobe Tool v4 is at fault, that maybe the hosts file works even though the Tool v4 claims it doesn't. If the Tool is at fault, maybe I should just ignore that report and go ahead with the installation. I guess noone would know how it'd turn out until tried.

This is strange, I have it now working on Win 10. Try it on Safe Mode. Worst case scenario, use VMware Player or Virtual Box to make a virtual Windows XP/7 machine, and create/copy/check your hosts from there. Once set up once, it should be easy.

Hi @Bayhey 

I have a new Win10 build here - just to confirm from your post above - it was 3.7 you got working?

Cheers GG  Big Grin  
Reply




Users browsing this thread: 3 Guest(s)