This appears to be a common error, associated with mixing 32bit and 64bit DLLs?
Most of my PortableApps are suddenly failing with this on my Windows 10, x64 machine where Portable Apps in in fact installed on my secondary hard drive.
Some apps will run successfully, noteabley, Firefox, Chrome and one or two other native 64bit applications. I tried re-installing PortableApps itself. It runs fine, only the portable.exe apps fail. E.G. Notepad2Portable.exe fails but Notepad2.exe in the App folder will run just fine? Attempting to re-install individual applications fails because the PAF.exe executable fails with the same error. Any suggestions would be appreciated.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Error code 0xc000007b means INVALID_IMAGE_FORMAT, and generally occurs due to absence or damage of some system or application files. The most common cause of this error – problems with NVIDIA drivers, other video cards are also subject to look at.
Since you're using Windows 10, try to run the application using the compatibility mode. If this doesn't work than I suggest checking the integrity of the system files. To do this, open the command prompt with administrator privileges and execute the command:
sfc /scannow. Windows will scan your system files and fix some errors. If you receive an error like, "Windows Resource Protection found corrupt files" than enter the following commands:After that I can say try to check and fix DLL dependencies with Dependency Walker.
Hope this helps.
EDIT:
I forgot to link to Dependency Walker: http://www.dependencywalker.com/
daemon.devin
Thanks for your response and suggestions. The SFC indicated that it flagged a couple of files and reported they were fixed, a second scan reported that no errors were found.
I don't have any fancy graphics cards and I certainly haven't had any driver problems, until now apparently? The most recent Windows Insider was updated days ago so I don't suspect that becuase I had no problems until this afternoon. No applications other than whateverProtable.exe and whatever-paf.exe are affected (so its more of an annoyance than a worry, at the moment.) As I said not even PortableApps itself has any problem, neither do the actual apps being invoked by PortableApps.
Still, Dependancy Walker threw out all kinds of errors with regard to a bunch of 32bit DLLs in the system32 folder of Windows for the couple of portable.exe executables I tried. The DLLs themselves are there and I have no problems running any other 32bit apps?
Still looking for answers I'm afraid and please don't tell me I need to re-install .NET. I can just as well wait for the next Windows Insider update.
After doing further research, I'm seeing a lot of people who are using Windows 10 coming across this error message as well. There doesn't seem to be any immediate fix for those who are using Windows 10 as the suggestions I've made were geared towards people with Windows 7, 8, and 8.1 (I won't upgrade to Windows 10 until I feel it's as solid as Windows 7; that's just me though.).
Hope you find a solution.. I'm sorry I can't be of any further assistance. Good luck.
daemon.devin
Take a look at this support forum thread. It gave the proper hint!
The affected machine has forced ASLR enabled. This will cause current launchers (AppNamePortable.exe) built with PAL 2.x to fail. Most NSIS 2-based installers will similarly fail on these machines. PAL 3.x will likely fix the issue as it is built with NSIS 3. It's due for public testing soon. Custom launchers like those used by Firefox Portable, Thunderbird Portable, Google Chrome Portable, etc should work without issue as those are built with NSIS 3.
Sometimes, the impossible can become possible, if you're awesome!
While most apps are not recompiled to NSIS 3, running this command on a elevated PowerShell windows will allow you to run most applications:
ForEach ($filename in (Get-ChildItem -Filter "Portable.exe" C:\PortableApps\*\*).FullName) { Set-ProcessMitigation -Disable ForceRelocateImages -Name $filename }I tried this on Windows 11 but it doesn't work (I changed the drive letter to k and added the portableapps.com folder before the portableapps one) however manually making an exception does, any better way to not have to do that for 145ish apps?