Sound Forge Pro Won't Open or Crashes on Startup: 9 Fixes

Sound Forge Pro won't open, or it opens and crashes before you get anywhere near a waveform. Which fix actually applies depends heavily on where it's failing: nothing happens at all, it hangs on the splash screen, or it opens and then dies the moment you touch a file. Check Windows' own crash report before you touch anything else, since it usually points at the actual failing component instead of leaving you guessing.

Part of the Sound Forge Pro 2026 Guide — start there if you’re new to the site.

This fix is part of the Sound Forge Pro Core Editing hub. If Sound Forge is launching again, continue with recording, cutting, normalizing and exporting.

This guide is part of the Sound Forge Pro Troubleshooting hub. Start there if you need symptom-first fixes for no sound, recording/input problems, ASIO routing, Windows audio devices or missing VST plugins.

Start Here: Where Does It Actually Stop?

Nothing happens when you click the icon: activation, a post-activation registry issue, or a corrupted install
It hangs on the splash screen while a plugin name is displayed: likely the VST scan
It hangs on the splash screen before any plugin name appears: check preferences, licensing, and audio initialization instead
It opens, then crashes loading a specific file: test a new empty file first, since a working empty file points at that media or its plugins rather than the install itself
It only crashes when you record: an ASIO or audio driver problem, separate from a full startup failure
Windows shows an AppHangB1 or similar hang report: check Reliability Monitor, though a hang report doesn't always name a faulting module the way a full crash does

Use Reliability Monitor to Choose the Right Fix

Before jumping to a specific fix, it's worth spending two minutes finding out what's actually failing. Windows records app crashes and hangs in Reliability Monitor. A full crash report often names a specific faulting module; an AppHangB1 report may only show a hang signature and the application path, with no module named at all.

Press Windows+R, type perfmon /rel, and press Enter. Find the entry for Sound Forge around the time it crashed and click it for details. If a faulting module is listed, treat it as a strong lead rather than proof: a graphics-related DLL makes the display driver a strong lead, an ASIO-related DLL makes the audio driver or interface software a strong lead, and a DLL carrying a plugin vendor's name points toward the VST scan. The named module can be the last thing in the failure chain rather than the actual root cause.

This one habit saves more time than any single fix on this list. Sound Forge itself gives you almost no information when it fails; Windows' own crash logging usually gives you more, even when it's incomplete.

Fix the Official Post-Activation Launch Failure

If Sound Forge activated successfully but won't launch afterward, Boris FX has an official fix for this exact failure that doesn't require running the program as administrator.

Close Sound Forge if it's running. Open Registry Editor and navigate to HKEY_USERS, then [your user SID]_Classes, then VirtualStore, MACHINE, SOFTWARE, Wow6432Node, Sony Creative Software, and the Sound Forge Pro or Sound Forge Audio Studio folder for your version. Right-click the version-number folder inside that path and choose Export first, saving the .reg file somewhere outside the registry so you can restore it if anything goes wrong. Then delete that same folder only, without touching anything above it. Close the editor and launch Sound Forge again.

Sound Forge 2026: Fix the Official Post Activation Launch Failure

This comes directly from Boris FX's own support article on this exact issue. The exact folder name varies by edition and version, so delete only the final version-specific key described there. This fix applies specifically when a launch failure starts right after activation; if that's not your situation, the reset steps below are the better starting point.

Reset Preferences and Clear Cached Data

Sometimes Sound Forge opens partway, hangs, or crashes right after the splash screen because of corrupted preference files or cached data left over from a bad shutdown. That's a different failure than the activation issue above: the program actually starts loading here, then dies partway through.

On MAGIX-era versions such as Sound Forge Pro 15 through 18, hold Ctrl+Shift while launching to open a dedicated reset tool, even if the main program won't start normally. On the current Boris FX build, check Help, then Reset to Factory Defaults first if the application opens far enough to reach the menu.

Sound Forge 2026: Reset Preferences and Clear Cached Data

Resetting can wipe custom preferences, window layouts, keyboard shortcuts, and cached plug-in data along with whatever's actually corrupted. Screenshot or export anything you can still access before you reset it.

If Sound Forge opens but crashes loading your last project, try creating a new empty file instead of reopening the last one. If the empty file works fine, the problem is tied to that specific media, plugin, or saved setting rather than the application itself, and you can narrow it down file by file. If even an empty session crashes, keep working through the driver, licensing, and installation checks below.

Confirm Your Serial Number and Activation Status

A license that hasn't fully activated can stop Sound Forge from opening at all, and the error message doesn't always make that obvious. If you bought through the Boris FX webshop, activation runs through the MAGIX Service Center: launch Sound Forge, click Enter serial number in the Welcome dialog, and enter the serial number from your Boris FX purchase confirmation, not an old MAGIX confirmation if you're activating an upgrade. Those are two different numbers, and Sound Forge won't accept the wrong one. Boris FX's own documentation confirms serial numbers from previous Vegas Pro, Sound Forge, and Acid Pro purchases carry over into a Boris FX account under the same email, which is what makes this lookup possible in the first place.

Note that Vegas Pro under the same Boris FX Hub uses a separate login-based system where you just sign in and choose Use on This Computer, no serial number involved. That's specific to Vegas Pro; if a Vegas Pro troubleshooting thread doesn't match what Sound Forge shows you, that's why.

If you need offline activation, or your setup needs a different licensing arrangement than the standard single-activation license, Boris FX can issue a separate Activation Key for that specific case through their sales team, tied to one machine.

If activation looks complete but Sound Forge still won't launch afterward, that's the separate VirtualStore issue covered above, not a licensing problem.

Isolate the VST Plugin Stalling the Startup Scan

Sound Forge can scan configured VST folders during startup, especially after plug-in changes, a cache reset, or a fresh installation, and if one plugin hangs during that scan, the whole program hangs with it. This looks like a crash or freeze, but it's actually Sound Forge waiting on a single file that never finishes loading, usually without telling you which one.

Watch the splash screen closely. Some versions display the name of the plugin currently being scanned right before they hang, which tells you exactly what to remove. If nothing shows, move all your third-party plugins to a temporary folder and add them back a few at a time, relaunching after each batch, until the freeze returns.

Sound Forge 2026: Isolate the VST Plugin Stalling the Startup Scan

On MAGIX-era versions, the /NOVSTGROVEL launch parameter and a hidden Skip startup VST grovel setting have both been used to bypass the startup scan entirely. These are legacy troubleshooting switches from older builds, so confirm one actually works on your specific version before relying on it. If your plugins load but don't show up in the effects chain rather than stalling the whole app, that's a related but separate problem covered in the VST plugins not showing guide.

Switch ASIO to WDM Before Touching the Registry

If Sound Forge crashes specifically while initializing audio, or right after you plug in or remove an interface, the driver handling is usually the cause rather than the application itself.

Disconnect the external interface and see if Sound Forge opens on the built-in Windows audio device. If it does, open Preferences, Audio, and switch the driver type from ASIO to Windows Classic Wave Driver or Microsoft Sound Mapper as a test, then update the interface manufacturer's ASIO driver before switching back. This overlaps with driver checks covered in more depth in the Sound Forge Pro no sound guide.

Sound Forge 2026: Switch ASIO to WDM Before Touching the Registry

If none of that helps and you're on a MAGIX-era version after removing or swapping hardware, Sound Forge can store stale references to old ASIO devices in the registry and crash trying to reconnect to one that no longer exists. On some MAGIX-era builds, including a documented Sound Forge Pro 15 case, that entry lived at HKEY_CURRENT_USER\Software\MAGIX\SOUND FORGE Pro\, then the version folder, then Metrics, Audio Hardware, Classes, ASIO Driver Class. Export that key before deleting anything, and remove only the entry for hardware you no longer own.

Confirm Your Windows Version Meets the Requirements

The official standalone Sound Forge system requirements page lists Windows 11 as the minimum operating system for the current release. That's the standalone Sound Forge product page itself, not a bundled suite's requirements or an inference from a related product. Windows 10 isn't listed as supported. Some users report it still installs and runs on Windows 10 without obvious problems, but Boris FX support won't troubleshoot issues on an unsupported OS.

Check your Windows version under Settings, System, About. If you're on Windows 10 and not ready to move to 11, Sound Forge Pro 18, the last MAGIX-era release, officially supported Windows 10 and is a more predictable option than fighting an unsupported configuration on the current build. Full details, including RAM and storage, are in the Sound Forge Pro system requirements guide.

Test for a Background Software Conflict

Antivirus tools, update checkers, and audio-related background utilities occasionally interfere with Sound Forge at launch, producing a slow, timing-out startup rather than an instant crash. This is hard to diagnose directly since the conflicting software usually runs invisibly.

Start with a Windows clean boot, or close nonessential update checkers, overlay software, and other audio applications, then try launching Sound Forge. Avoid disabling core antivirus protection entirely. If antivirus interference is specifically suspected, add a narrow, temporary exclusion for the Sound Forge executable or install folder rather than turning protection off, then test and remove the exclusion afterward. If it opens normally with everything closed, re-enable the background software one at a time and relaunch after each one until the problem comes back. That tells you exactly what to leave disabled or exclude Sound Forge from.

Reinstall Sound Forge and Remove Leftover Settings

If nothing above fixes it, the install itself is probably damaged. For the current Sound Forge 2026 release, uninstall through Windows normally, reboot, and reinstall through the Boris FX Hub, since the Hub handles the current license check as part of setup. For Sound Forge Pro 18 and earlier, use your original installer from your MAGIX account rather than a Boris FX 2026 package. Boris FX has said older versions continue to be supported through MAGIX rather than migrated wholesale into the Hub, and in practice not every legacy license shows up correctly in a Boris FX account.

Reboot after uninstalling and try a normal reinstall first before reaching for any third-party cleanup tool. If the same problem comes back after that clean attempt, a leftover registry entry or cached file the standard uninstaller missed is a likely cause. Community moderators on the MAGIX forums have long recommended a third-party uninstaller like Revo Uninstaller's Advanced scan mode for exactly this situation, run after the normal uninstall and before reinstalling. It isn't an official Boris FX tool, so treat it as an optional extra step rather than a required one, and avoid removing shared MAGIX or Boris FX files if you have other products from either company installed.

Common Questions About Sound Forge Crashing

Why does Sound Forge freeze instead of crashing outright?

A freeze means the process is still running but has stopped responding to Windows; a crash means Windows terminated it after an error. Either symptom can come from a stuck VST scan, a driver handshake with a missing device, a licensing check, or corrupted settings, so use the splash-screen stage and your Reliability Monitor report to narrow it down rather than assuming from the symptom alone.

What does an AppHangB1 error actually mean?

AppHangB1 is a generic Windows Error Reporting code meaning an application stopped responding to Windows, nothing more specific than that. It doesn't by itself tell you whether the cause is a graphics driver, an audio driver, or a stuck plugin scan. Check Reliability Monitor for the faulting module named in the report before assuming what caused it.

Is Sound Forge Pro still compatible with Windows 10?

Sound Forge Pro 18, the last MAGIX-era release, officially supports Windows 10. The current Boris FX release lists Windows 11 as the official minimum. If you're not ready to upgrade the OS, staying on Pro 18 is often more predictable than running an unsupported configuration on the newer build.

Does Sound Forge Pro 18 have the same startup problems as the current release?

Mostly, yes. The VST scan and legacy ASIO registry issues are mainly associated with MAGIX-era builds, while the current Boris FX release uses a different distribution workflow through the Hub. The Windows 11 requirement applies to the current release specifically; Pro 18 officially supports Windows 10. Apply only the steps documented for your exact version rather than assuming everything carries over.

Why does Sound Forge only crash when I try to record?

A recording-only crash makes the selected audio device, ASIO driver, sample-rate configuration, and any interface control software the first things to test, rather than a general startup problem. Recording-specific driver fixes are covered in the Sound Forge Pro no sound guide.

Work through these roughly in order, but jump straight to whichever one matches your Reliability Monitor report if you found a faulting module in the first step. That one piece of information usually narrows nine possible causes down to one or two actually worth trying.