01-28-2026, 06:41 PM
(This post was last modified: 01-29-2026, 09:29 AM by rich2005.
Edit Reason: typo
)
Hmm....same as yesterdays post: https://www.gimp-forum.net/Thread-GIMP-w...sh-install
It is the usual issue - reproducing the problem.
Using a Win 10 (VM) and the gimp-3.0.8.exe installer from Gimp.org (size 303,675,352 bytes)
(1) Install over an existing Gimp 3.0.4 installation. The installer found the old version, removed then installed 3.0.8 Started ok with the existing user profile.
(2) Uninstalled and removed old Gimp 3 installation. Then a default Gimp install (..for me only (recommended) ) and that works here as well.
As previous advise, try starting in a terminal and see if you get any error messages. I get this with that http fail because the Win10 is not connected to the internet.
There are other command line switches try running:
gimp.exe --verbose
also if it is stuck on a broken font gimp.exe --no-fonts
EDIT: It could depend on the computer CPU. This bug report. https://gitlab.gnome.org/GNOME/gimp/-/issues/15766 Which ( in part ) says
quote - I think that maybe the very start of init() in the extension, where BABL_VERIFY_CPU is invoked itself ends up containing instructions beyond x86_64-v2 which is the microarchitecture level supported by i3-530
It is the usual issue - reproducing the problem.
Using a Win 10 (VM) and the gimp-3.0.8.exe installer from Gimp.org (size 303,675,352 bytes)
(1) Install over an existing Gimp 3.0.4 installation. The installer found the old version, removed then installed 3.0.8 Started ok with the existing user profile.
(2) Uninstalled and removed old Gimp 3 installation. Then a default Gimp install (..for me only (recommended) ) and that works here as well.
As previous advise, try starting in a terminal and see if you get any error messages. I get this with that http fail because the Win10 is not connected to the internet.
There are other command line switches try running:
gimp.exe --verbose
also if it is stuck on a broken font gimp.exe --no-fonts
EDIT: It could depend on the computer CPU. This bug report. https://gitlab.gnome.org/GNOME/gimp/-/issues/15766 Which ( in part ) says
quote - I think that maybe the very start of init() in the extension, where BABL_VERIFY_CPU is invoked itself ends up containing instructions beyond x86_64-v2 which is the microarchitecture level supported by i3-530