Page 1 of 1
[Solved] Firefox 144 has been installed but the key cannot be found
Published: October 27, 2025 - 6:01 PM
by marcolefo
Good morning,
We have the package retrieved from the WAPT store for FF:
https://wapt.tranquil.it/store/fr/tis-firefox
During deployment I get this error:
Code: Select all
Installing: Firefox_Setup_144.0.exe (144.0)
Waiting for key: Mozilla Firefox 144.0 (x64 fr) to appear in Windows registry
Traceback (most recent call last):
File "C:\Program Files (x86)\wapt\common.py", line 4454, in install_wapt
exitstatus = setup.install()
File "C:\Windows\TEMP\waptv8shresh\setup.py", line 24, in install
File "C:\Program Files (x86)\wapt\common.py", line 4371, in new_func
return func(*args, **kwargs)
File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 1754, in install_exe_if_needed
error('Setup %s has been installed but the %s can not be found' % (exe,searchparam))
File "C:\Program Files (x86)\wapt\waptutils.py", line 2038, in error
raise EWaptSetupException('Fatal error : %s' % reason)
waptutils.EWaptSetupException: Fatal error : Setup Firefox_Setup_144.0.exe has been installed but the key Mozilla Firefox 144.0 (x64 fr) can not be found
Is this coming from the package or the FF installer?
Thank you for your help
Re: Firefox 144 has been installed but the key cannot be found
Published: October 27, 2025 - 6:12 PM
by sfonteneau
Firefox did something very strange in its latest version:
https://github.com/mozilla-firefox/fire...6ed710b293
So we added this code to the latest version of Firefox on the store:
Code: Select all
if windows_version() < Version(WindowsVersions.Windows11):
app_uninstallkey = "Mozilla Firefox"
So if the computer is running Windows 10, then the key becomes "Mozilla Firefox"
Is your computer running Windows 11?
Re: Firefox 144 has been installed but the key cannot be found
Published: October 27, 2025 - 6:33 PM
by marcolefo
Good evening
Yes.
So, I went and tested it on a Windows 10 machine that's still lying around
(we don't have much left, but unfortunately we're not going as fast as we'd like)
)
Under Windows 10, the task takes an unusually long time and displays:
Code: Select all
Installing: Firefox_Setup_144.0.exe (144.0)
Waiting for key: Mozilla Firefox 144.0 (x64 fr) to appear in Windows registry
I'm going to add the code snippet to the package, it'll give us some green on Windows 11, that's always nice.
Re: Firefox 144 has been installed but the key cannot be found
Published: October 27, 2025 - 6:35 PM
by marcolefo
By the time I sent my previous post, I realized that:
- You've done the work on the store (I read your message too quickly). So I'm going to test the new package.
- Same message under Windows 10:
Code: Select all
Installing: Firefox_Setup_144.0.exe (144.0)
Waiting for key: Mozilla Firefox 144.0 (x64 fr) to appear in Windows registry
Traceback (most recent call last):
File "C:\Program Files (x86)\wapt\common.py", line 4454, in install_wapt
exitstatus = setup.install()
File "C:\Windows\TEMP\wapt5xxriay5\setup.py", line 24, in install
File "C:\Program Files (x86)\wapt\common.py", line 4371, in new_func
return func(*args, **kwargs)
File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 1754, in install_exe_if_needed
error('Setup %s has been installed but the %s can not be found' % (exe,searchparam))
File "C:\Program Files (x86)\wapt\waptutils.py", line 2038, in error
raise EWaptSetupException('Fatal error : %s' % reason)
waptutils.EWaptSetupException: Fatal error : Setup Firefox_Setup_144.0.exe has been installed but the key Mozilla Firefox 144.0 (x64 fr) can not be found
Re: Firefox 144 has been installed but the key cannot be found
Published: October 28, 2025 - 09:59
by sfonteneau
From what I've seen, under Windows 10 the key should be "Mozilla Firefox"
and under Windows 11 it doesn't change and should be "Mozilla Firefox 144.0 (x64 fr)".
In your case, what is the key on Windows 11?
Re: Firefox 144 has been installed but the key cannot be found
Published: October 28, 2025 - 10:48 AM
by marcolefo
Good morning.
Indeed, the key is "Mozilla Firefox 144.0 (x64 fr)" under Windows 11...
So I think I made a mistake. The original post must have been under Windows 10.
In any case, it seems to be working now. Thank you.
