PlugData Standalone crashes silently on launch – Exception 0xc0000005 (Win 11 24H2)
Tried to run PlugData standalone (v0.9.1 and v1.3.1) on Windows 11 Version 24H2. No GUI ever loads. Executable briefly appears in Task Manager, then disappears. Consistently crashes with exception 0xc0000005 (access violation). No useful logs or error output.
-
Installed PlugData using the official .msi (v1.3.1 and also v0.9.1).
-
Also extracted .msi contents manually using 7-Zip.
-
Located STANDALONE_EXE and renamed to PlugData.exe
-
Found and renamed PD_DLL → pd.dll
-
Attempted to run:
-
Double-click
-
Right-click → Run as Administrator
Via Command Prompt
All attempts result in instant crash (icon briefly appears, then disappears)
What I Tried (all failed): Installed latest x64 and x86 Visual C++ Redistributables
-
Ran sfc /scannow and DISM /RestoreHealth (no errors found)
-
Disabled all audio devices
-
Set dummy paths via VST3_PLUGIN_PATH, LV2_PATH, CLAP_PATH
-
Created clean config.json and ran with --settings flag
-
Tried compatibility mode (Win 8, admin mode)
-
Rebooted and reattempted after every step
-
Verified crash info via Event Viewer
Crash Info (from Event Viewer):
Faulting application name: PlugData.exe, version: 0.9.1.0 Faulting module name: PlugData.exe, version: 0.9.1.0 Exception code: 0xc0000005 Fault offset: 0x000000000007cc79 Faulting process id: 0x5AE4 Faulting application start time: 0x1DBCE94996EE2DA Faulting application path: C:\PlugDataManualPortable\PlugData.exe
🖥 System Info:
- OS: Windows 11 Pro
- Version: 24H2 (KB5058411 fails to install)
- Architecture: x64
- RAM: 16 GB
- GPU: [Your GPU model here if you'd like to include it]
- Audio: [Realtek / ASIO / etc.]
📎 Notes:
- I am not using an installed version of PlugData anymore — I manually extracted the MSI to isolate
PlugData.exeand avoid installer corruption - I’ve tried launching it completely sandboxed (no plugin scanning, no config), still crashes
- There are no crash logs generated — only Event Viewer entries
- The crash persists even when using environment variables to disable plugin path scanning
- Attempted launching with
--settingspointing to a hand-craftedconfig.json
✅ What I’d Like:
- A portable
.zipversion of PlugData with logging enabled - Or a debug/diagnostic build that can print more verbose crash output
- Or a list of known runtime dependencies (DLLs, drivers, registry keys) used by the standalone EXE
- Any way to disable audio and graphics subsystem initialization via flags or config, for deeper diagnosis
📎 Additional Context:
This was attempted over multiple hours of debugging — including:
- SFC and DISM scans
- Manual rename and relocation of DLLs
- Compatibility mode and admin elevation
- System-wide environment overrides for VST3/LV2/CLAP paths
- Testing after disabling audio devices and updating all system drivers
What is v1.3.1? this is not a plugdata version.
Have you tried the latest nightly build?
Looks like the same problem I have and reported on 2025-4-1: https://github.com/plugdata-team/plugdata/issues/2097