eLicenser mess up after every half yearly Windows update
-
- KVRAF
- 35678 posts since 11 Apr, 2010 from Germany
Is it just me, or does eLicenser mess up after any of the half yearly Windows 10 updates?
Last time, I had it that I had to repair the soft eLicenser, and this time, it told me again that the soft eLicenser was broken. The eLicenser software told me that I had to start the software as an admin user then, but, that ended up with an error message as well, because, obviously, there still was some eLicenser process running or something. I then rebooted, and installed the latest version of the eLicenser software, and that fixed the issue.
Thank god that Steinberg discontinues eLicenser now. Never had such issues with iLok. Or any other copy protection scheme, for that matter.
Last time, I had it that I had to repair the soft eLicenser, and this time, it told me again that the soft eLicenser was broken. The eLicenser software told me that I had to start the software as an admin user then, but, that ended up with an error message as well, because, obviously, there still was some eLicenser process running or something. I then rebooted, and installed the latest version of the eLicenser software, and that fixed the issue.
Thank god that Steinberg discontinues eLicenser now. Never had such issues with iLok. Or any other copy protection scheme, for that matter.
- KVRist
- 78 posts since 18 Jul, 2016 from Moscow
I have this errors after each big update too, but running eLicenser control center as admin fixes everything for me. Never had to reinstall it except for the purpose of updating.
iswr
-
- KVRAF
- Topic Starter
- 35678 posts since 11 Apr, 2010 from Germany
It might have worked after the reboot, when I would have started eLicenser CC as admin. I guess there simply was a process still running after shutting down eLicenser CC the first time.
Nonetheless, the soft eLicenser shouldn't be broken after every half yearly update. As you say, it's been like that for years now.
Nonetheless, the soft eLicenser shouldn't be broken after every half yearly update. As you say, it's been like that for years now.
-
MirkoVanHauten MirkoVanHauten https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=376111
- KVRist
- 454 posts since 12 Mar, 2016
This of course only happens to the 3% of people who use the soft eLicenser.
No issues with the eLicenser, but then I also don't use the soft eLicenser. Doesn't make sense to me to keep a license singleton on something that can be damaged by a flipped bit. And I agree, I had no issues with iLok or other dongle protections either aside from codemeter, which then also messed up the other protections software or drivers. I had no issues in something being messed up by a Windows update at all (besides cleaning up the useless Cortana installation or changing back the keyboard layout).
No issues with the eLicenser, but then I also don't use the soft eLicenser. Doesn't make sense to me to keep a license singleton on something that can be damaged by a flipped bit. And I agree, I had no issues with iLok or other dongle protections either aside from codemeter, which then also messed up the other protections software or drivers. I had no issues in something being messed up by a Windows update at all (besides cleaning up the useless Cortana installation or changing back the keyboard layout).
- KVRist
- 78 posts since 18 Jul, 2016 from Moscow
Oh dammit, i missed that it is about soft elicenser.
I'am using dongle only. Still it brakes on each update and have to repair something running as admin. Dunno maybe it repairs my empty software elicenser container? Still better than codemeter anyway! 
iswr
-
- KVRAF
- Topic Starter
- 35678 posts since 11 Apr, 2010 from Germany
Probably. I only ever had issues with the soft eLicenser after the big updates, not with the dongle. That works fine after the big updates, in my experience.Vee Nee wrote: Fri Nov 19, 2021 2:14 pm Oh dammit, i missed that it is about soft elicenser.I'am using dongle only. Still it brakes on each update and have to repair something running as admin. Dunno maybe it repairs my empty software elicenser container?
-
- KVRAF
- 2772 posts since 28 Mar, 2007
The dongle is always plugged in for each update and is always fine. For some reason Steinberg also installs a soft elicencer and that always breaks, but I leave it broken because its not needed.
On the other hand the i-lok dongle complains all the time. Even if I boot into Linux it asks to be unplugged and plugged back in. If I reinstall windows it thinks its a new computer and breaks. But its still a lot better than a software i-lok licence. The very reason I bought the hardware dongle was because the software one broke continuously for anything and everything.
On the other hand the i-lok dongle complains all the time. Even if I boot into Linux it asks to be unplugged and plugged back in. If I reinstall windows it thinks its a new computer and breaks. But its still a lot better than a software i-lok licence. The very reason I bought the hardware dongle was because the software one broke continuously for anything and everything.
- KVRAF
- 7169 posts since 19 Apr, 2002 from Utah
Serials or keyfiles only for me. i-lok or C/R? No way! Dongle or no dongle...
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
-
- KVRAF
- Topic Starter
- 35678 posts since 11 Apr, 2010 from Germany
If you're on Windows 10, it's the big ones, which resemble a fresh OS install, which break the soft eLicenser. Not the small ones.
-
- KVRAF
- Topic Starter
- 35678 posts since 11 Apr, 2010 from Germany
It's true that I was always able to fix it. "Easily fixed", hmm... most probably not for the not so advanced computer user. Took me some reading in Steinberg's Answerbase as well. It would have been great if they would have fixed this behavior, because, it's been a few years since Windows 10 was released, and, this issue seems to be very widespread, and is existant for a long time now.
Anyway. No more eLicenser soon anyway. *uncorks champaign*
Anyway. No more eLicenser soon anyway. *uncorks champaign*
-
- KVRAF
- 8705 posts since 24 May, 2002 from Tutukaka, New Zealand
Right from the outset I figured I'd avoid the soft eLicenser like the plague. I use a dongle, yet every single time I load up Cubase I get the same silly message that soft eLicenser doesn't have the right something-or-other to allow Cubase to work. Of course the dongle is in, I click OK and continue on and it works fine, but I figure - how come the dumb thing can't recognise that the dongle's already in - which of course it can because it always works, so why put the warning up? It reeks of not working properly. Just never had a single problem with the dongle, no matter what OS update has been done. I feel your pain though - it's a real pain in the tits for any s/w to be so flaky - especially apparently pro s/w. I suspect the new Steinberg protection is going to be a septic tank full of fun for some unlucky users, if the old one is anything to go on... 
- KVRAF
- 26033 posts since 20 Oct, 2007 from gonesville
haven't had a real issue in prob. a decade. (physical key, soft elicenser/tied to the computer NIX.)
for my uses you pretty much have to keep it current. have no idea why, but if not trouble may find you
o' course that's all on windows, amiright
for my uses you pretty much have to keep it current. have no idea why, but if not trouble may find you
o' course that's all on windows, amiright