I noticed there’s also an offer to compensate for the fact that WaveLab 9 will no longer work with the latest Windows 10 updates, so I used the opportunity to upgrade my last remaining WaveLab Elements 9.5 license, but the activation code I got doesn’t work. I’ve raised a support ticket, so let’s see what happens.
This is the first time I’ve ever had any problem with activation, so I’m just wondering if anyone else has had this issue with the upgrade from 9 to 10. The error message says a “communication problem occurred while accessing the license server” but it’s clearly not a network issue as I can run the maintenance and sync without any problem.
Please don’t use my post to justify whatever you are on about. This is only the second time I’ve had to use Steinberg support and only mentioned the fact as it would have been a question that someone might reasonably ask.
My post is about a license activation issue related to the title of this topic. I also stated that it’s the first time I’ve ever had any problem with activation. Perhaps if you took the time to give the detail of what problems you encountered (assuming it’s relevant to the topic), some of us might have the possibility of offering help.
Sorry you are Right ! i should not express my frustration with steinbert specially in the ateinbergs comunity forums as we are often here looking for enswers that we dont get from stenberg. Your issue is all over these forums if you sarch you will find that it has been around sinse they upgraded their new elicencer sofware. And yes im upset that there is no support for people like you and me that spend our hard earned money on the software . I hope you have better luck than i did . I have been a steiberg user since the very begining of cubase and have spent many thousands of dollars on their sofware i own just about every main software they sell ! throughout the years i gues that is why im upset when we file support issues with them and Never get a Response.
Fair enough then, I wasn’t aware there were many other cases (links?). I am also a long-time user and have never had issues before. Let’s see what happens – I still haven’t been able to activate the purchased upgrade and I still haven’t gotten a response to my support request.
I’m still using Wavelab 9.5 on two installs without problem on Windows 10 20H2 latest and Windows 10 2004 latest. The Steinberg full document below only mentions Wavelab 9.0 and 9.1, which have the browse crash problem with latest 20H2 and 2004
There is now one mention of a Wavelab 9.5 startup problem on the German forum, but that’s the only thing I’ve seen of a 9.5 problem and I’m not experiencing any problems at all on two systems with the latest Win 10 updates, I recall having to run maintenance on elicenser when 20H2 installed because of error messages on start, but it was unrelated to 9.5 specifically.
I think Microsoft should fix the 9.1 browse crashing problem, because their update caused it, and I would imagine there are other programs out there that are also affected by this besides just Wavelab 9.1. There’s probably a forum discussion going on somewhere else right now for app XYZ, which crashes when browsing for files with Win 10 20H2, whereas yesterday it worked fine with Win 10 1909.
I’ll be submitting Compatibility test results to Microsoft because it’s easy and automatic (right click the Wavelab 9.0 or 9.1 icon, Troubleshoot Compatibility, run through the few steps, and it should submit results at the end). The Compatibility Troubleshooter really seems like it should work to fix this problem, but it doesn’t. Whether anything results from submitting the reports is a question, but if they get more than just my one report they might take a look at it, because they really should imo. I read about bug fixes in their updates all the time. And Wavelab 9.1 was working fine in Windows 10, and their update broke it.
Mmmm … when I go to activate the upgrade, the upgradeable 9.5 license is recognised properly and the upgrade does specifically state it is also for 9.5 …
I agree it should be up to Microsoft to fix a problem that Microsoft caused, but it will take a while for the finger-pointing to abate (Cubase 10.5 and Kontakt 6, anyone?) so I wouldn’t be holding my breath.
My motivation was simply to upgrade what is a spare license when I saw the offer. Now that it doesn’t work, it would be nice to get some response from the official Steinberg support; still nothing.
I guess you’re right, but it doesn’t really make sense if Wavelab 9.5 has shown no ill effect from 20H2, which as far as I know is the case. Wavelab 9.5 doesn’t have the browse crash problem like 9.0 and 9.1, as stated in the Steinberg document, and I’ve had no problems at all with Wavelab 9.5 in Win 20H2.
I’d be interested to hear from Steinberg about any confirmed compatibility problems with Wavelab 9.5 and Win 20H2, because I’ve seen no mention of anything like that, except the German forum poster startup problem (a whole different issue), which has gotten no response, question, or explanation. I would suspect it might be elicenser related but it’s impossible to know without further discussion.
Thanks for the link! Just to be 100% clear though, the problem is not with the discount code, it’s with the activation code. The eLicenser throws a “communication” error, which it clearly is not; if the code were incorrect, I’d expect it to say that and somehow reject the activation attempt. Instead, it starts the activation process, which then appears to fail.
I agree, or at least, if the activation code is supposed to work only with 9.0/9.1 and not 9.5, then that should be specified, which might have prevented me making what may have been an incorrect product choice when purchasing. But then, if that is in fact the case, why does the eLCC recognise 9.5 as an “upgadable license”, then offer to upgrade and actually start the process?
Hopefully I’ll get a response to my support request soon.
Im happy for you ! But what about the ones that are having issues ? I just spent 6 hours with microsoft they told me they suspect wavelab is not compatible with windows latest update ! My case its been sent to tear2 for farther Analizing . You have to understand i i have Nuendo11 ’ cubase11 spectral layers’ and many other software aplications on my system but wavelab is the only program that has issues using the file explorer to import anything in to it. At least they are trying to help ! More than i can say about Steinberg!.
js4sabdig, please create another topic for your case, because it out of subject for the current thread.
And attach a link to a video and crash dump, else nothing can be done to try helping your particular case.
There might be something to what the poster in the German forum said about a startup problem with Wavelab 9.5, presumably in 12H2. (link below). I got the same thing twice today, just hanging on the startup window. Force quitting and restarting Wavelab worked. This seems new, probably with the latest 12H2 updates. Maybe too soon to tell, but possibly not a good sign for 9.5 and 12H2. Latest elicenser installed.
Windows 10 is a bit sensitive these days. End of last week, there was a Windows 10 update that caused the upper bar of some applications to be covered by a blank banner, making it impossible to use the menu of certain applications such as Google Chrome, Firefox, and… Cubase, WaveLab…
Today there was yet another update from Microsoft, that solves the problem!
Wow. That’s pretty amazing. The version I have right now, 20H2 19042.804 does now seem to be causing these startup hangs with Wavelab 9.5, (and 9.1 and 9.0 64 bit). Not every time, but most of the time, especially after first boot. But like the poster in the German forum described. What I found was when they are hanging on the startup logo, you can double click the logo and get the Windows “Wavelab is not responding” message, and from there select “close the program” and it does and reports it to Microsoft. After that, open Wavelab again, and it opens pretty normally, at least for the time being. I also tried disabling “logo on startup” in all 3 versions and found that prevented hanging forever completely. It sometimes did hang forever with logo enabled. So I think this has started affecting 9.5 now too, with this different problem. I haven’t gotten any blue screens but definitely not right startup hangs. Doesn’t happen with Wavelab 10 on the same machine.
Also I re-enabled logos after testing without logos successfully, and things seemed more back to normal even with logos enabled. Maybe just a coincidence or maybe the toggling made a difference (?)