Having Problems With Sound Forge 17 Crashing Or Otherwise Not Working?

GregoryP-Lewis wrote on 8/4/2025, 8:21 PM

I recently upgraded to SF17 from SF10 because I bought a new computer with Windows 11. SF10 would not install on the new PC because the license server for that old version no longer exists. I installed SF17 then launched it. Everything looked good until I tried to record an old vinyl record. The program would crash randomly with the maximum recording time being <1 minute. I tried using a different sound source (Microsoft Sound Mapper) and tried changing to a different temporary drive. Nothing helped!

The next day, I decided to see if SF17 might run successfully by running it in "Compatibility Mode". To my utter surprise and delight, the program seems to work properly now and doesn't crash!! I set the "Compatibility Mode" to Windows 8, which was the latest Windows version that was listed in the drop-down box on my Win11 machine.

Of course this applies only to Windows PCs, not MACs or Linux unless they have something similar.

If you want to try this, just google the words 'how to run software in compatibility mode'. If you have different users logging into your computer, there's a button at the bottom of the compatibility tab's box that lets you set the compatibility for all users (if that's what you want!) I also suggest you check the box to run the app as an administrator. I left all other boxes in their default state.

One last caveat - After you make this change, Windows will prompt to allow the software to make changes to your PC. It will ask EVERY time you launch it. It's really a small price to pay to have SF17 actually work.

Hope this might resolve any problems you may be having with the software!!

PS - I've read some posts of similar complaints about other recent versions of Sound Forge. This change might help them too!!!

Best Regards,

Comments

SP. wrote on 8/4/2025, 8:48 PM

@GregoryP-Lewis Sound Forge Audio Studio? Problems and crashes could also be caused by the Magix Low Latency ASIO driver. This is an old version of the ASIO4ALL driver and not really compatible with newer Windows versions.

If you want to uninstall Magix Low Latency you can click on the Windows start button in the bottom left corner and type regedit. Then click on the Regedit app.

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. Make sure to not delete anything else by accident, except you know what you are doing!

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

If you have trouble deleting the folder, try starting Regedit as administrator via the right click option.

GregoryP-Lewis wrote on 8/5/2025, 2:29 PM

Thanks for the tip SP. I went into the registry and deleted the Magix Low Latency 2016 ASIO key and rebooted. I removed the command to run in compatibility mode and my crashing problem immediately returned. Turned the run in compatibility mode option back on and launched SF17 again. It then started working properly again without crashing. Whoever the software engineers are should look into this (assuming the new owners want to continue to develop and sell this software). I would understand if the version was many years old, but it's not!

SP. wrote on 8/5/2025, 3:10 PM

@GregoryP-Lewis Interesting. Can you check the Windows Reliability Monitor for a detailed crash description and copy and paste it here?

To open the Reliability Monitor press the Windows key and R on your keyboard. In the Run window type perfmon /rel and press Enter. Then the Reliability Monitor will open. Look for red error icons in the time table when Sound Forge crashed. You can open the details with a double click. Maybe we can find a problematic DLL there.

GregoryP-Lewis wrote on 8/5/2025, 3:39 PM

Here's the latest fault from Perfmon

Source
SOUND FORGE Audio Studio 17

Summary
Stopped responding and was closed

Date
‎8/‎5/‎2025 2:17 PM

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\SOUND FORGE\SOUND FORGE Audio Studio 17\Audiostudio17.exe

Problem signature
Problem Event Name:   AppHangB1
Application Name:   Audiostudio17.exe
Application Version:   17.0.2.109
Application Timestamp:   6476d2e5
Hang Signature:   515e
Hang Type:   134217728
OS Version:   10.0.26100.2.0.0.256.48
Locale ID:   1033
Additional Hang Signature 1:   515e07b0a858ab572c58d3d929ba94ad
Additional Hang Signature 2:   4244
Additional Hang Signature 3:   424481a518874d4f5979ceb645075d7c
Additional Hang Signature 4:   515e
Additional Hang Signature 5:   515e07b0a858ab572c58d3d929ba94ad
Additional Hang Signature 6:   4244
Additional Hang Signature 7:   424481a518874d4f5979ceb645075d7c

Extra information about the problem
Bucket ID: 4052494e208d3ad30d955653baf43f7c (2131704916248641404)

SP. wrote on 8/5/2025, 3:46 PM

@GregoryP-Lewis I found a Reddit post where the writer solved the AppHangB1 crash by plugging their HDMI monitor cable into the GPU ports instead of the motherboard ports. Are you using aPC or a laptop?

https://www.reddit.com/r/pchelp/comments/1et8db6/apphangb1_error_this_is_going_to_drive_me_insane/

GregoryP-Lewis wrote on 8/5/2025, 4:59 PM

It's a Dell Optiplex 7050 Micro so technically it's a desktop but not a conventional (large footprint) desktop. It has an Intel I7 quad-core 2.84 GHz processor with 32 Gb memory. The HDMI port is on the motherboard and it also has 2 display ports. There is NO separate GPU card nor a place to put any add-in cards. I had all that stuff on my old custom built towers running Win10 but the MBs were too old to run Win11 (good ol' Microsoft strikes again!)