This test app has now been released: https://portableapps.com/news/2019-08-26--gimp-portable-2.10.12-3-released
I'm posting a test of a new dual mode GIMP Portable build with both the 32-bit and 64-bit binaries. It's configured to upgrade your existing GIMP Portable install so be sure to make a backup first. It should preserve your existing plugins, brushes, patterns, palettes, scripts, etc, but there could be issues as the way GIMP Portable is upgraded has changed.
Download: 220MB
Install: 1.2GB - 1.34GB
MD5: fb62ff497eb69f4b13cda9f0ba7f23a5
SHA256: 17b24797af1f2f6017edcd43cb3aba7505dfbb175a14c7d6eb9e4bcab5efed24
The reason for this change is two-fold. Primarily, the 32-bit build of GIMP has had issues for about a year. It will crash on Windows 7 32-bit when you try to do just about anything. We'd previously used a GLIB patch that fixed this issue but the last version of GIMP this worked with was 2.10.6. Secondarily, the 64-bit build allows you to use 64-bit plugins as well as 32-bit plugins since we are including compatibility mode. Thirdly, there will be a small improvement in speed of some operations, but it will be unnoticeable in everyday use.
As to size, this is a much bigger package than the 32-bit built. This is due, firstly, to the fact that the 64-bit package is much bigger (910MB vs 650MB) just by itself. Including 32-bit compatibility to ensure no one loses access to their plugins increases that install size to 1.15GB. If we'd just had installs of full GIMP 32-bit and GIMP 64-bit, the install size would be a whopping 1.79GB. But, thanks to some creative file movements of the shared pieces between the two versions, the actual install size is shrunk to 1.34GB, only about 190MB larger than a 64-bit only package. Choosing not to install the additional locales as you install will save another 124MB bringing install size down to 1.22GB.
Note that you will need to install your plugins separately for GIMPx64 and GIMPx86. In App you will either see a gimp and gimp64 directory (if you ran it in 32-bit mode last), in which case the gimp directory is the 32-bit version, or you will see a gimp and a gimp32 directory (if you ran it in 64-bit mode last), in which case the gimp directory is the 64-bit version.
Please try this out on its own and with your current install being upgraded.
Test 2 fixes an issue with upgrading old versions and being able to update itself.
Test 3 fixes an issue where it broke itself in the process of installing.
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
First, thank you John for working on this! Myself and, based on the forums, many others have been anxiously awaiting both a 64-bit version and an updated version of GIMP.
I downloaded and installed 2.10.12 test 2 over an existing instance of 2.10.6. When I try to run GIMP Portable nothing appears to happen. Running it a second time I get the error, "GIMP Portable cannot be started. You may wish to re-install to fix this issue. (ERROR: App\gimp\bin\gimp-2.10.exe could not be found)". Looking into the "app\gimp\bin" folder does reveal that it's empty.
Based on that message I uninstalled GIMP Portable 2.10.12 test 2 completely, and re-installed to my USB drive (now without a prior GIMP Portable installation). I confirmed that files were installed to "app\gimp\bin". I ran GIMP Portable and the first time nothing appeared to happen again. Running a second time I got the same error message. Sure enough, the files are now missing from "app\gimp\bin". It seems like whatever happens on the first run that those files are being removed. I checked my AV and GIMP Portable wasn't picked up as malicious, so it doesn't look like that's to blame.
Uninstalling 2.10.12 test 2, restoring my 2.10.6 backup and installing 2.10.12 test 2 again results in consistent behaviour. The files are initially there in "app\gimp\bin" then removed during the first run.
Let me know what else I can test to help out.
If you're on a 64-bit machine, the following will happen on first run:
Rename "$EXEDIR\App\gimp\bin" "$EXEDIR\App\gimp64\32\bin"
Rename "$EXEDIR\App\gimp\share" "$EXEDIR\App\gimp64\share"
Rename "$EXEDIR\App\gimp\etc" "$EXEDIR\App\gimp64\etc"
Rename "$EXEDIR\App\gimp" "$EXEDIR\App\gimp32"
Rename "$EXEDIR\App\gimp64" "$EXEDIR\App\gimp"
If anything interferes with that, it'll fail. And you need to wait for it to finish. GIMP is very slow to start the first time whether a local or portable install. When you run it the first time, check if it is still running in Task Manager. If you're running it from a slow external drive and your antivirus is scanning on rename (it shouldn't, but some lesser ones don't work as well), those initial renames may take a while.
Also, don't get too excited. Unless you're scripting huge batches of file conversions or working on massive files (2GB+), you won't notice any difference from the 32-bit version.
Sometimes, the impossible can become possible, if you're awesome!
Understood on hanging high hopes on 64-bit. It's just nice to see progress, and there was a forum post or two about large file support.
The GIMP Portable process appears to stop within a few seconds after it's run the first time. Looks like the rename process isn't completing.
I ran Sysinternals Process Monitor while launching 2.10.12 test 2 on its initial run after install. The process is created and exits in under 6 seconds. It looks like the process exits all of its threads and stops itself. Nothing especially jumps out. The renaming process is definitely not completing before the GIMPPortable.exe process ends.
I manually followed the renaming steps after installing 2.10.12 test 2 and GIMP then runs properly.
I've noticed that an empty "app\gimp32\lib" folder is created on install. Also, once GIMPPortable.exe exits on first execution, the gimp64 folder doesn't seem to get renamed to gimp, as the gimp folder still remains with empty bin and lib folders. For me, all signs point to an issue during the renaming process that GIMPortable.exe isn't taking care of. There's likely a secondary related issue where GIMPPortable.exe exits because it can't find the executable to pass control to due to the renaming issue.
Here are my findings on the "app\gimp*" folders, showing just the immediate child folders of each gimp folder for brevity.
2.10.12 test 2 on fresh install:
App\gimp\bin
App\gimp\etc
App\gimp\lib
App\gimp\share
App\gimp32\lib
App\gimp64\32
App\gimp64\bin
App\gimp64\lib
2.10.12 test 2 after first run (won't run after this):
App\gimp\bin
App\gimp\lib
App\gimp32\lib
App\gimp64\32
App\gimp64\bin
App\gimp64\etc
App\gimp64\lib
App\gimp64\share
2.10.12 test 2 after renaming manually on fresh install (does run after this):
App\gimp\32
App\gimp\bin
App\gimp\etc
App\gimp\lib
App\gimp\share
App\gimp32\lib
Even though manual renaming works, I'll go back to 2.10.6 for now and eagerly await 2.10.12 test 3 (or final!).
I think I messed something up in build 2. The renaming you did is what it's supposed to do. I'll double check and do a Test 3 to resolve this.
The large file support means *very, very* large files.
Sometimes, the impossible can become possible, if you're awesome!
I've updated to Test 3 which fixes the issue with installs and upgrades messing themselves up in attempting to preserve existing files.
Sometimes, the impossible can become possible, if you're awesome!
Hi, is any more work being done on this? The download link is broken (actually, it least to a valid page that tries to auto-download a broken link).
I found the test 3 download link at https://sourceforge.net/projects/portableapps/files/GIMP%20Portable/.
I recently got the prompt to update my GIMP Portable Apps, so I assume it was the release version. I am getting the GIMP Portable unable to start due to gimp-2.10.exe unable to be found message. Did I somehow get a test version?? If so is there a release version available, or is there a way I can find a prior release?
Please create a new thread in Graphics and Pictures support and include the complete details including system details (OS version, 32 vs 64-bit, install path, new vs upgrade, etc).
This closed thread is for a now-discontinued test release.
Sometimes, the impossible can become possible, if you're awesome!