No. The driver needs to go from Wavelab 11 and be replaced with something that the security of Windows 11 is happy with.
The only thing that would temporarily help right now is to disable Memory Integrity in Core Isolation so that Windows 11 does not check for ancient drivers like GEARAspiWDM.sys. Doing that you leave your computer venerable to. exploits to processor model-specific registers (MSR)
Can you please tell us if installing or reinstalling the Gear drivers In Windows 11 upgrade or clean install causes the computer to become unbootable. And if so, what are the recovery options if System Restore was turned off.
I told the answer earlier…
If you try to using the last Gear installer (which is the same driver anyway) you will prevent your computer from booting and the OS install will be toast unless you have backed up your Bitlocker keys (on by default in Windows 11) to gain access to your drive(s) and have a restore point to roll back to. Bear in mind that System Restore is off by default in Windows 11 so you will need to have remembered to switch it on.
To this I can add that the way out without system restore being active is to access the drive where the driver is from the recovery tools (because you have your Bitlocker keys…I hope)… normally that is the system32 directory and delete the driver. Reboot and then you can get back in Windows 11. Then uninstall the Gear drivers.
(To stress this will happen on clean (and probably update) installs of Windows 11 provided that you have…
Intel 11th generation Core processors and newer
AMD Zen 2 architecture and newer
Qualcomm Snapdragon 8180 and newer
RAM Minimum 8GB
Storage SSD with a minimum size of 64GB
…which are the conditions under which Windows 11 switches on Memory Integrity security.)
And I don’t understand why you are trolling here. We are trying to solve something and I really don’t care whether you understand or not and also don’t care if you think people should stay in the dark ages with you. If you have something positive to contribute that adds value to this thread then fair enough but throw away one liners and brown nosing here as I see you do often in other threads is not welcome.
I wouldn’t do it either (especially since I don’t want to touch my present working system at the moment - and it won’t accept Win11 anyway) - but to the credit of @prismprocess: I’m glad someone is taking the time and effort to look into our possible future issues, so kudos to him!
While it is clear that the problem is currently only when WL11 is used on an OS that is not yet supported, this topic has morphed into beta-testing, and I’m OK with that. In that context, can I ask why we need CD/DVD drivers in WaveLab at all in 2021?
By all means retain the functionality to generate ISO files, but I see no reason to include device drivers with WaveLab. Anyone who still requires that can leave earlier versions of WaveLab installed on earlier OS versions.
@prismprocess please stop be so nasty, if this your style
in general Why? by the way I was a Windows user for a very long time
but in this time I’m not and MrSoundman thanks for being resonable in this discussion. Bye
I was wondering the same thing. People could make an iso and mount it if they wanted to check it. If they had a burner they could do that with say InfraRecoder or ImgBurn. Also this would negate the need to have driver approval from the OS security.
… and just to add, does anyone even have pro-quality burner hardware anymore?
While I still have a pair of SATA Plextors in this machine, I can’t see any current burners on the market that aren’t USB, so IMHO burning an ISO would almost certainly be a safer proposition than trying to burn from WaveLab via the Gear drivers.
Problem is, that a reliable .iso of an Audio CD cannot be made, it’s a format for data. Ofcourse, we have DDP for delivery and that is fine - but to verify the DDP after burning on different players (and especially the metadata that’s on them) there will still be a need for drivers and burners. IMO, as long as Audio CD’s are produced and sold, mastering software will have a need to burn test disks.
So it seems we both approach the same solution which is future proof. That solution would be to find an alternative to the Gear driver that is Windows 11 compatible for the latest CPU and security settings.
Thank you for all the work you’ve done troubleshooting this issue @prismprocess. I recently built a new 12th gen Intel system and did a clean install of Windows 11, as Windows 10 doesn’t take advantage of the efficiency cores in the new Alder Lake chips. I ran into this same issue after installing Wavelab 11 and would have had trouble tracking down what program installed this old Gear driver if not for this thread.
I can confirm running the GEARAspi_Remover.exe program from Index of gearsoftware.com/downloads/freebies/ solves the issue. A quick test confirmed Wavelab still runs after removing the driver, but I’m staying away from the built in CD burning functionality!
Steinberg could easily band-aid this problem by offering a checkbox to not install the CD burning functionality in Wavelab. Like others in this thread, I haven’t used this functionality in ages!
No it’s not. Are you saying that people who use Windows 11 correctly should create vulnerabilities in their up to date systems to suit your software that you refuse to update correctly to move with the times? I know I won’t be buying any new Wavelab that does not support current operating systems and their security features Anyone who does buy it and puts it on a new system is in for a shock Whatever next?
Fixing it so it works with Windows 11 might be an idea…
The problem is only going to get worse (as you can see)…
Don’t say you weren’t told…
Yes, I agree with that but that will not help those who did not read this thread first and because of it proceed to uninstall Gear drivers that ship with Wavelab. If they don’t know (which is reasonable to assume) and they reboot their new Windows 11 machine blissfully unaware after installing Wavelab, Bitlocker will prevent the OS from booting (because of the Gear driver). If they don’t know the Bitlocker key for their drive then they will “Schwierigkeiten haben” und “auf dem falschen Dampfer sein”…
It is nearly 4 months since the release version of Windows 11 came out (05.10.2021) and it was over 4 months in public Beta before that (28.06.2021). In that time (and also since you have known about this issue) you have released the Wavelab 11.0.20 update (01.12.2021) and it is not fixed…
