Pale Moon 26.2.2 Portable x64 Error

[Eurythrace]

I installed/unzipped Pale Moon 26.2.2 Portable x64 earlier, but it will not load. It consistently gives the "Pale Moon is already running" error message. Yes, I did verify the SHA256 checksum on the package. I just moved back to Pale Moon 26.2.1 Portable x64 from the FTP archive and it works fine. BTW, I wish you would also include a text file of the SHA256 checksums in the archive too. Thanks.

No other changes were made to my system, so it does seem to be something in the Pale Moon 26.2.2 Portable x64 package. Thank you.

[dark_moon]

Can't confirm this.
I test the x86 & x64 and both runs without errors. Make sure Pale Moon is closed and take a look at the task manager.

[Moonchild]

BTW, I wish you would also include a text file of the SHA256 checksums in the archive too.

That's a chicken and egg problem. How can you include a text file with checksums in an archive that contains the checksum of the archive? Any change to the contents of the checksum file will change the checksum of the archive itself, invalidating the checksum in the text file...

As for your "already running" issue: try rebooting your system. If that doesn't help, check your internet security software to see if it's not strictly limiting disk access by the new version (if it can't properly access its profile, it will throw that error)

[Eurythrace]

I just tried again with PM 26.2.2 Portable x64 and I had the same problem, with the already running error. So, I closed my Security S/W and then tried and this time it gave the splash screen like before, but instead of giving me an error message, it just showed the busy cursor. I checked the task manager and saw the PM Portable process and the PM browser process there, but no CPU time given to them. I waited and watched for a couple of minutes, but nothing happened except the busy cursor. There was no indication in the task bar the PM process was running, but the 2 processes did show up in the task manager as stated previously.

I still had the PM 26.2.1 Portable x64 on the USB, so with the "dead" PM 26.2.2 Portable x64 still memory resident, I started the PM 26.2.1 Portable x64 version up and it loaded just fine. So even with the "dead" PM 26.2.2 Portable x64 still memory resident, PM 26.2.1 Portable x64 ran just fine. And yes, I had rebooted the system a couple times before starting this experiment. I am running Windows 8.1 x64 and the PM "installs" are on a FAT32 USB thumb drive.

About a checksum for the archived versions, I understand what you mean about the chicken and egg problem in the archived file itself. I meant as a SEPARATE text file in the archive directory, like a lot of sites do. Not a perfect solution because you can't know if the checksum file itself is uncorrupted, but still better than nothing. Or possibly even having just a separate empty file whose file name is the version and checksum hash might work. Thanks.

[dark_moon]

because you can't know if the checksum file itself is uncorrupted

For that we have the GPG file to verify.

If disable your security software doesn't help, try add Pale Moon to the whitelist or uninstall the security software.

[Eurythrace]

If disable your security software doesn't help, try add Pale Moon to the whitelist or uninstall the security software.

Um, maybe I am missing something, but I do not see how adding PM to my Security S/W whitelist or uninstalling it will help, since PM 26.2.2 Portable x64 will not work even when my Security S/W is not running/loaded/active. PM 26.2.1 Portable x64 works fine with my Security S/W and I do not recall that I had to approve/allow it at all. I admit I am baffled at this situation. Is there some other S/W that might interfere with PM 26.2.2 Portable x64 running?

And could you also include an *.sha1 digest file along with the *.sig GPG file for the related archived file in the archive directory for those of us who do not have or use GPG? Thank you.