My WL demo expired and no one at Steinberg was interested in giving me another 30 days so I would have to purchase WL to test if this works.
This is a language issue.
The Gear Diagnostic program confirms the drivers do not work. You get error 30000. Also the drivers are listed as not-started in system tray when you look at processes and applications. You read my response to mean someone from Gear actually answered me (They have not. I’ve written three case logs, one direct email to them - no reply. Nothing from Gear).
But the first day I installed WL in 10 the first thing I did was rip a CD using fast and picky mode - to test the differences. I did. It worked fine. The next day, WL would not recognize the CD Drive anymore. I started the entire litany of Gear Drivers and test programs.
Well I hope Steinberg reconsiders and sends you another trial. But you don’t need to use Wavelab to try the Gear install I suggested, and if the Gear works and verifies, I’d be willing to bet the drive would show up again in Wavelab, because that’s exactly what happened when I got it going.
Bob99, you are a Prince among men. Thank you for your help on this. I’ll test when I can and report back.
GEARAspiWDM service is not running
Driver verification has completed.
Drivers are not correctly installed. Error 3000000.
It might seem trivial, but are you running the install as administrator? Even if the instructions don’t require this, I have come across situations when it can make the difference.
Paul
PS: I mean using “run as administrator”, not just being logged in as user “administrator” or another user with admin privileges.
Sorry it didn’t work. To see if I could reproduce it, I uninstalled and tried normal and compatible installs again. And now I can’t get it running and verified again with either. I’ve had at least one Windows 10 update session since I got it working a few days ago, but I’m pretty convinced this is now a moving target with Win 10 Updates and new Gear installs until Gear takes a look at what’s going on.
If I’d left my install as it was earlier tonight, it would still be working fine, as everyone else’s is who hasn’t touched their systems. (if you’re not having a problem I wouldn’t touch anything).
In my case it might be because of other Gear powered software (itunes, symantec) but I’ve run both without issue for years, and I’ve always been able to install the Gear drivers successfully, but not now. I much more suspect (since I got it working with compatible install before) that it’s the gear installer itself and all the Win 10 updates going on. Maybe everything will work fine in a week after another Win 10 update. But maybe it’ll get worse.
I know there are only 2 cases so far (me and RPITA), but if Steinberg is the support for the Gear Drivers in this case (as Gear says on their website), it would be helpful if somebody from Steinberg could ask Gear to take a look at this discussion. And to try the install themselves on Win 10 anniversary edition with current updates. The installer hasn’t changed (it seems to be 3 years old), but Win 10 seems to be currently changing things.
It’s a good suggestion but it’s made no difference in my case all along. run as admin attemped for installs and uninstalls etc. without change.
Yes.
Its not trivial, either. People who don’t use Windows a lot probably don’t know about the pitfalls of installing applications as a general user.
Yes.
(Aside:I would bet lots of money that being logged in as Administrator in 10 isn’t really Administrator. They still withhold permissions, especially with respect to writing to root. But that is a different topic. And one that has been discussed extensively on the Microsoft forums by confused/angry users).
Was a beta tester for for WIndows for Workgroups and Office version(s) 1, 2, and 3.
I ran the latest GEAR update and it still produces the 30000 error mentioned earlier. I have no GEAR processes running that I can see.
WL6 sees and imports from CD with no problem. The only way I see that I can burn a CD at the moment is to create a CUE sheet and use WL6 - this is not a good situation to be in.
Jim
Have you tried removing the “UpperFilters” and “LowerFilters” entries from the registry? It’s Method 5 on this page, and has solved such problems for me in the distant past.
Paul
That thread assumes the CD drive is not recognized.
The CD drive is recognized and can read and write by every Windows Application except Wavelab 9pro.
The following have no issue using the drive and burning a CD:
Sequoia 12
Sonoris DDP Player / OEM
iTunes (flipping iTunes on Windows - and it works).
JRiver Media Player
Windows Explorer
etc…
I finally got this going again, but what it took is way out of line with what should be expected of anyone.
I had to do a manual uninstall of Gear in an Administrator account in Safe Mode, and then set the compatibility of the Gear installer to Vista Service Pack 2 (my previous compatibility that worked once and only once before my last Win updates was Windows 7 compatibility). Not sure if it was the Vista compatibility or Safe mode uninstall that made the difference this time, but Gear should really take a look at what’s going on with this, how the uninstalls, reinstalls, and repairs don’t seem to make any difference when GearASPIWDM won’t start. If the only solution is manual uninstalls in the registry, can’t they at least make reg files to do at least some of that? I got it to work once with a Win 7 compatibility install without going into the registry, but I have no idea why that worked, and it only worked once.
No matter what the state of a user’s system, it shouldn’t be this hard.
Using Windows 10 Redstone 1 with latest updates.
The other problem is that the Gear issue can be made to happen pretty easily.
On the computer I’ve been testing, I have 4 versions of Wavelab 9: Pro 32 and 64, and Elements 32 and 64. I uninstalled both Elements versions, reboot, and then GearASPIWDM won’t start. And from what I can tell the only way to get Gear back is to do the registry manual uninstall. Not impossible, but an aggravating, time consuming process.
Trying to get it back with any of the functions in the Gear installer (uninstall, repair, reinstall) doesn’t work as far as I can tell, at least not on Win 10 Redstone 1.
I made no such assumption; even if the solution I suggested seems generic, I have certainly seen it affect programs selectively.
Paul
PG, if this can be reproduced, it seems like it shouldn’t be happening, because it means uninstalling one Wavelab version breaks another? And the Gear fix is not easy.
I would consider it a bug in Gear and Wavelab, if I came across it.
Sorry, you can disregard that last one. Have to have the drive plugged in and turned on. Duh, I guess. The verify will sometimes indicate ok without a drive, like after a successful repair, but other times not. And will other times indicate bad if a drive is not in, when it would otherwise indicate successful. Should probably have the drive plugged in and turned on when doing any of this I think. (The CD Drive apparently should be plugged in and turned on when doing installs, repairs, or uninstalls). ymmv. Strangely I haven’t seen anything about that on the Gear site, because results can be quite different. Maybe they just assume you have an internal drive plugged in and turned on all the time. And you might need to at least try to open Wavelab to get the Gear service started if it’s stopped.
Sorry for the endless posts.
Bottom line, if after all that, the installer is still not fixing the problems, the registry manual uninstalls on this page should do it:
and then reinstall with the installer.
Doing bob99’s manual uninstall (per the Gear directions, with the two reboots),
Then Installing the drivers AS ADMINISTRATOR
and rebooting
Seemed to solve the problem.
As GEAR is WaveLab’s driver of choice for optical drives can anyone from Steinberg state whether they are putting pressure on the company to sort this out so that users don’t have to jump through hoops to try and get this working again?
Jim
Gear could not reproduce any problem whatsoever on Windows 10 x64.