Wavelab 11 Pro breaks mounting of iso files in Windows 11

I’m not nasty, I just do not like trolling. You have offered no value to the thread.

You say bye, I say good.

1 Like

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.

1 Like

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.

1 Like

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!

2 Likes

Have the same problem:
fresh Windows 11 + WaveLab 11.0.20.
No ISO mount, physical DVD burner does not work.

The “no ISO mount” issue is a real problem as Native Access relies on ISO mounting.
So with WaveLab 11 installed no SW install with Native Access!!!

So i tried several things:

  1. Disabling GEARAspiWDM in autoruns.
  2. Removing Gear option with Program&Features and WaveLab installer.
  3. Finally removed several GEARAspiWDM entries with regedit.
    => now it works as it should (physical DVD, ISO and Native Access).

Not very trustworthy, but should fix the issues until next WaveLab release …

1 Like

@kermit

Do you recall the exact steps you made so we might replicate them and formalise so kind of solution

The solution is simply to disable the Windows option “Core Isolation” (Virtualization-based security , aka VBS)

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…

The other simple solution is to uninstall the Gear driver.
Currently, you can’t access the CD in WaveLab when the "Core Isolation is “ON”.

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…

:wink:

Not a good idea, as security matters.

Not really,
I just deleted all reg entries with “GEARAspiWDM” in the title and one with the key “GEARAspiWDM” and “CDROM”.

I have clients who still want cds burned to listen to, etc. so I am curious as to what the status of this issue is. I agree that it should have been addressed before 11 Pro came out, but now is the time to fix it at any rate. I’ve been using Wavelab for years now. Windows 11 is here now, and has been for months, and to disable features that deal with Windows being secure doesn’t seem logical to me. It appears that just about every other Steinberg product is compatible, so it’s somewhat of a mystery to me. I believe that PG truly cares about the product, so I hope it will be resolved soon. Blessings

1 Like

For this feature, Steinberg depends on the CD driver provider, Gears Sotfware. So far, no update from them.
Again, when this Windows 11 security option is disabled, you don’t run less secure as on most Windows 10 systems.

Why do you think it is enabled by default in Windows 11? Something to do? Of course not…

Disabling Core Isolation will leave your computer venerable to exploits to your processor model-specific registers (MSR).

I suggest you find someone who can supply updated drivers for the CD burning functionality in Wavelab. One look at the Gear website tells you all you need to know about how current they are…

Driver updates - GEAR Software

Surely someone else can supply something that works in Wavelab that is not out of the ark.

:roll_eyes:

PG1, can you explain to me how it is not less secure when you disable Core Isolation? I notice that you have stated that as the way to get around this issue, as I need to be able to burn cds for clients as I had stated before. I’m not disagreeing with you, but it’s not clear to me why you think that is the case. Thank you in advance for your response.

2014 was a while back…

I did not say so. I said, “not less secure as on most Windows 10 systems.”… Simply because Core Isolation is not enabled in most Windows 10 installations.
Therefore, unless you were subject to attacks on your Windows 10 system or are executing untrusted software, you should not worry more today than yesterday. That’s all I want to say. I add I am not a security specialist, my reasoning is simply common sense.

But if you want maximum security anyway, enable Core Isolation, and when you need to burn CDs, unplug from the internet, and disable Core Isolation for a while.

This being said, Core Isolation can impact performances, though it depends on the hardware. There are talks about this on the internet. Or even articles such as