You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The installer for ObsidianPortable v1.9.14 is causing a critical runtime error (0xc000007b) on modern 64-bit Windows systems.
Problem Description
After running the installer and accepting the prompt to install "32-bit support", the main launcher (ObsidianPortable.exe) fails to start and shows the error 0xc000007b. This action also breaks other previously working PortableApps launchers on my system, causing them to fail with the same error.
However, the core application executable (e.g., App\Obsidian\Obsidian.exe) can still be launched directly without any issues. This confirms the problem is with the launcher, not the application itself.
Steps to Reproduce
Use a modern 64-bit Windows system (e.g., Windows 10 or 11) with up-to-date C++ runtimes.
Run the installer for ObsidianPortable.
When prompted, agree to install the "32-bit support".
Try to start the application via its main launcher (ObsidianPortable.exe).
The launcher will fail with error 0xc000007b.
Technical Analysis
The installer script (Installer.nsi) forces the installation of the Microsoft Visual C++ 2010 Redistributable (x86).
NSIS
${If} ${RunningX64}
ExecWait '"$PLUGINSDIR\VC2010Redist_x86.exe" /passive /norestart'
${EndIf}
This package is very outdated. Forcing its installation on a system with newer C++ runtimes can corrupt or create conflicts within the system's DLLs, leading directly to the 0xc000007b error (which signifies a 32/64-bit component mismatch).
Suggested Solution
Please remove the forced, automatic installation of the legacy VC++ 2010 Redistributable from the installer.
A better approach would be to:
Check if the necessary dependencies are missing.
If they are, inform the user and provide a link to download the latest supported Visual C++ Redistributable from Microsoft's official website.
This prevents breaking users' systems and follows modern software distribution practices. Thank you for your work on this project!
Thanks for reporting this issue!
This problem isn’t related to my package specifically — it comes from the PortableApps.com Launcher itself.
Anyway, I’ve forwarded this issue to the PortableApps.com Launcher team so they can take a closer look. PortableApps/Launcher#22
All those portable applications with 32-bit launchers didnt open normally anymore without that 0xc000007b error, and it wasn't so until I installed this v1.9.14 (with that 32-bit option) Before that, the Obsidian v1.9.12 portable worked without any problems and I actually had to reinstall my entire system to finally get these programs working properly again.
In other words, the 32-bit option in that installation can corrupt the entire system pretty badly, so I would recommend disabling that option in that installer because I kind of accidentally installed it myself and then everything stopped working.
Activity
xmha97 commentedon Oct 14, 2025
Thanks for reporting this issue!
This problem isn’t related to my package specifically — it comes from the PortableApps.com Launcher itself.
Anyway, I’ve forwarded this issue to the PortableApps.com Launcher team so they can take a closer look.
PortableApps/Launcher#22
MarkTheta commentedon Oct 14, 2025
All those portable applications with 32-bit launchers didnt open normally anymore without that 0xc000007b error, and it wasn't so until I installed this v1.9.14 (with that 32-bit option) Before that, the Obsidian v1.9.12 portable worked without any problems and I actually had to reinstall my entire system to finally get these programs working properly again.
In other words, the 32-bit option in that installation can corrupt the entire system pretty badly, so I would recommend disabling that option in that installer because I kind of accidentally installed it myself and then everything stopped working.