Sound Forge 17 and issues with Microsoft Sound Mapper

Sdeleon101 wrote on 7/14/2025, 10:20 AM

Sound forge 17 causes my laptop to lose Microsoft Sound Mapper and I lose sound on everything. I can restart the laptop, and it will recover and start working again but as soon as start Sound forge it knocks it out again. I am currently running windows 11 and everything is up to date as far as I can tell

Comments

SP. wrote on 7/14/2025, 10:38 AM

@Sdeleon101 Maybe it has nothing to do with the Microsoft Sound Mapper. Some computer systems might encounter problems with the Magix Low Latency audio driver that gets installed alongside Sound Forge. This is an old version of ASIO4ALL.

If you want to uninstall Magix Low Latency you can press the Windows key + R on your computer keyboard, and type REGEDIT in the Open field:

Then navigate to: HKEY_LOCAL_MACHINE > SOFTWARE > ASIO > Magix Low Latency 2016:

Now, simply right click the Magix Low Latency 2016 folder, and delete it.

Then restart your computer. Please select the Restart option and not the Shut down option.

I hope this helps.

Sdeleon101 wrote on 7/14/2025, 11:03 AM

@Sdeleon101 Maybe it has nothing to do with the Microsoft Sound Mapper. Some computer systems might encounter problems with the Magix Low Latency audio driver that gets installed alongside Sound Forge. This is an old version of ASIO4ALL.

If you want to uninstall Magix Low Latency you can press the Windows key + R on your computer keyboard, and type REGEDIT in the Open field:

Then navigate to: HKEY_LOCAL_MACHINE > SOFTWARE > ASIO > Magix Low Latency 2016:

Now, simply right click the Magix Low Latency 2016 folder, and delete it.

Then restart your computer. Please select the Restart option and not the Shut down option.

I hope this helps.

So, it's just a part of Sound forge that were deleting?

rraud wrote on 7/14/2025, 11:15 AM

Removing the low-latency driver will not affect any Sound Forge functions.
btw, The low-latency driver is not installed with SF Pro, only SF Audio Studio.

Sdeleon101 wrote on 7/14/2025, 11:24 AM

Thanks guys! That fixed the issue!