iLok you out for no reason! A warning.

[Nielzie]

I have a conspiracy theory. Since it's a low level software driver that is pretty much always on as a service, what if PACE/iLok is secretly gathering all kinds of data from our systems?

[robotmonkey]

It's a well established problem with how Windows 10 does updates. The bigger updates often equal to a clean reinstall with all kinds of system parameter changes and this messes with a lot of C&R protection schemes that think they have ended up on a new computer. Seen this happen a lot with Windows 10.

It's a new normal since Win 10 and it's a Pace's job to fix their piece of sh1t protection software. That they have not done so just shows what a bunch of lazy f%€ks they are. Instead they recommend to deactivate all the licences before updating Windows. What a joke!

[imrae]

Weird, by this point in an iLok thread we usually have some people pop up saying it has never happened to them and is therefore absolutely fine.

[chk071]

I did that though. On page one. At least the part that it didn't happen to me. It also didn't happen on the OP's other computer. And not on the computer of most other people, at least i haven't read anything in that regard here, yet.

You know, it could well have to do with the issues the new Windows Update has with Intel SSD's. Just like many issues with the bigger Windows Updates have to do with certain software and computer configurations. The thing for me about this is rather how PACE handles this. I don't understand why they just can't restore the licenses, because it's all in their database. It's ridiculous that the customer has to mess with every company's support now, to restore the licenses.

[Mushy Mushy]

Same issue here on my Surface. Latest update broke lots of registrations (Cubase, Sonic Charge, etc.) however my SoundToys was already broken so no difference there...

[Rockatansky]

It's that time of the year again. Can't log in to iLok License Manager on different machines, iLok can't sync subscribed licenses on several machines, Gobbler app can't install updates because it thinks my iLok account is not connected any more, AAX signing has been failing all day since PACE servers are so slow to respond that they seem unreachable... just waiting for the obligatory apologetic email at this point.

This is the sort of day when I remember why I love local serial number authorization so much.
I really wonder how they get away with it.

[bmanic]

I put some (27) ilok licences on my MS Surface.

I changed nothing (its a Surface!) other than windows updates.
Overnight, ilok suddenly desided my computer had changed and created a new soft licence identity.
I cant get to my old licences as iloc think that the computer is a different computer (even though they are the same computer and even have the same ilok ID)
I contacted ilok and they basically said they cant help- licences are gone unless I can beg new ones of the individual software companies...this is time consuming and there are no guarantees...

So remember, at any time ilok can decide your computer ID ha changed for any reason (or apparently no reason) and without warning

You will be locked out and will no longer have access to all of those licences (so cant move, delete or reuse them)

This is THE exact scenario that has happened to me too (ages ago) and the very reason I do not use computer locked licenses any more (not just ilok either). I've moved all my licenses to two physical iLoks and the software that comes with 3 licenses I keep the third as a backup.

[perpetual3]

I did that though. On page one. At least the part that it didn't happen to me. It also didn't happen on the OP's other computer. And not on the computer of most other people, at least i haven't read anything in that regard here, yet.

You know, it could well have to do with the issues the new Windows Update has with Intel SSD's. Just like many issues with the bigger Windows Updates have to do with certain software and computer configurations. The thing for me about this is rather how PACE handles this. I don't understand why they just can't restore the licenses, because it's all in their database. It's ridiculous that the customer has to mess with every company's support now, to restore the licenses.

Because they don’t have to - PACE owes nothing to the customer. We are an incidental third party to the transaction. The value proposition to the developer is that PACE provides a copy protection infrastructure to the developer so that they don’t have to. Since there are no competitors to PACE, they are a monopoly and can do basically whatever they want.

The developers evaluate PACE’s value proposition. They are the ones who say - PACE and ILOK is what we’re going with, regardless of the hassle to the cutomer in the event that something goes wrong.

Having recently gone through an ILOK issue, my anecdotal experience was that almost all of the developers responded quickly to my request for new licenses. However, ILOK would be a better product if temporary licenses were free and if the key was cheaper. These are costs that the developers pass on to us, but they don’t have to be. They are made up premiums. Or the cost of doing business - you want my new compressor full of ‘70s stoned out mojo? You got to go ILOK. And yes, if you lose a key or computer has a meltdown, you just might be SOL if you need to work ASAP. PACE is counting on that.

[THE INTRANCER]

I've been advising people to stay away from iLoks for years.... but some people still end up learning the hard way... thinking that they know better.

I've over 350 VST2 plugins, none of them require iLoks, my main production synthesizers bought outwith of those of the DAW's own are UHE's Hive and those from Reaktor for my current DAW, Studio One 3.5. I'd estimate that 85% of my plug's are free, and free from any propriety iCrap. Other friendlier registration systems exist for commercial software, use them instead.

[beely]

It's that time of the year again. Can't log in to iLok License Manager on different machines, iLok can't sync subscribed licenses on several machines, Gobbler app can't install updates because it thinks my iLok account is not connected any more, AAX signing has been failing all day since PACE servers are so slow to respond that they seem unreachable...

I also had a lot of iLok related problems today - I wanted to install something, and the servers were going down and a lot of weird stuff was hanging. After trying off and on for an hour, I gave up and did other things, and when I tried a few hours later, the stuff was still hanging but I got the licence through regardless and so I was able to complete the install/activation procedure.

But yes, today it was along way from the usual fairly straightforward (though convoluted) process it normally is...

[perpetual3]

True, Intrancer.

I purchased one iLok plugin years ago, had no problems until a few months ago. So, in the meantime I thought it wasn’t such a big deal.

When you get burned, it’s another story. It’s resentful because we PAY for the software, and then the burden is on US to get it to work on the event of legitimate problems inherent to the PACE system, a burden put in place for PACE to extort Money from the end user, who isn’t even their customer. It’s amazing.

[SLiC]

I've been advising people to stay away from iLoks for years.... but some people still end up learning the hard way... thinking that they know better.

I've over 350 VST2 plugins, none of them require iLoks, my main production synthesizers bought outwith of those of the DAW's own are UHE's Hive and those from Reaktor for my current DAW, Studio One 3.5. I'd estimate that 85% of my plug's are free, and free from any propriety iCrap. Other friendlier registration systems exist for commercial software, use them instead.

I don’t like having to use it, it seems pretty pointless that UVI, Soundtoys, Eventide et al force users down the PACE route when it’s been hacked anyway...

The point is if you want to use UVI Falcon and Sountoys, so you are forced to use ilok

[jdnz]

I tend to prefer machine licenses in general, as using my iLok on a laptop is a pain, but it does cause problems where, for instance, if your machine dies, and those licenses weren't deactivated and can no longer be accessed (as the machine is dead), there is no way to get them back. (This has happened to me before.)

The ilok in the cloud function should be the ultimate fix for this (presuming you have internet access wherever you go) - trouble is I'm not aware of a single vendor actually supporting cloud activation as yet (and it's been out quite a while)

[jdnz]

I don't understand why they just can't restore the licenses, because it's all in their database. It's ridiculous that the customer has to mess with every company's support now, to restore the licenses.

From Pace's end there's no way for them to tell whether your 'new' machine is due to win10 updates or you getting a 2nd computer and trying to 'game' them into giving you licenses. Plus of course they're just the middle-man, it's actually up to the software vendor to issue new licenses (if you have a physical ilok fail and have paid for ZDT Pace only issue temporary time limited licenses - to keep you going whilst you deal with the actual vendors to get new permanent licenses)

What they need to do is convert to using something smarter to ID your system for soft-ilok - something that doesn't change with software updates. Other vendors use just the MAC address of your ethernet or wifi adaptor - but I've seen plenty of vendors come unstuck with that approach when facing things like people disabling wifi or using usb adaptors.

Or vendors need to start supporting ilok in the cloud....

[pekbro]

Apparently, they’ve got some less than appealing monetary scheme for the cloud thing. I’m guessing more expense for developers. Someone has to pay for running the iLok cloud servers.

Anyway, certainly one can get by without any iLok protected products. Just as certainly, there are many excellent products that make the hassle worth it, imo. If it’s not that way for you, good on you then, your sensibilities are less demanding than mine.