Zonke iiMveliso Community Forum

I don't know who was the absolute [edited] to have the idea of forcing updates while the user is still working on the browser by shutting the browser down. Can someone else help me understand how to stop this nonsense??

And yes, I had the option "Check for updates but let you choose to install them" selected, and I'm still being molested by this forced restart """feature"""!

Every time I'm in the middle of an important work session, Firefox will suddenly refuse to open new tabs and prevent the ones that are already open from connecting and receiving updates. It erase private tabs and messes up everything!

I was in a call with my boss, and it got dropped because Firefox decided to update?? And DEMANDED that I close the browser IMMEDIATELY to continue using it????? What the hell???????????

I've only been running into this problem in the past few months, and I'm honestly shocked by how little uproar I'm seeing online about this bug. This is by far the worst think I've ever seen in a browser.

Anyway, I appreciate any help. I saw a trick to permanently disable updates, but I don't want to disable them. I just want them to be installed either when I CHOOSE or when the bloody browser is NOT in use!

I have my Firefox update settings on "Check for updates but choose when to install". When I get the pop-up to advise that there is an update available I select the "Update later" option but the update loads regardless of my choice. This happens on both my PC and laptop. I use a variety of online software for my work and frequently one or more will stop working or crash and Firefox advises that the problem is caused by an update needing to restart. The reason I choose to Update Later is so that I can just get on with my work and then update Firefox when it suits me. Currently, I end up having to shut down all open browser windows and then go through and sign in to all required windows and tabs again before I can continue with work. Needless to say this is VERY ANNOYING. Please advise why the updates are loading automatically when I have set my preference set to Update Later.

I think Firefox is probably the best browser on the internet. But one major flaw that has always been with it but has never been fixed is that unlike other browsers, Firefox updates on startup. It may only take a few moments, but it's not very pleasant for the user to wait even a few moments for the browser to launch. It seems better to either update in a separate process like other browsers, or at least give the user the option to decide to update at startup or in the background like other browsers.

There are way too many annoying updates and they all need admin login -- which doesn't work. How can I turn these off?

I'm switching browsers until these weekly updates are stopped.

I have Firefox set to NOT update unless I tell it to. However, it still updates on its own without asking me if it should. So every time Firefox updates, I have to close the app and log back in to everything that I was using. Since, I use browser based software for work and need to open and close tabs pretty much all day. Thus, the ability to NOT update is actually fairly crucial to getting my work done.

My browser is always open with a lot of open tabs that needs login. Every time the browser updates a beta update, I must restart the browser and all the logins are lost and I need to login to all my different ongoing tasks (google mail, rumble and other pages with login) in the tabs. How can I set up the Firefox browser so I only get the full version updates (like 152.0) and not the beta versions (like 152.02) ?

I have changed the website hosting company from my previous one to scalahosting.com, which in turn appears to be using grok.viawebhost.com as their mailserver.

I was a user of Eudora 7.1 for many years, but because of this change of hosting company, the Eudora email program would not connect to the Scalahosting site.

Thus I was forced to change to Thunderbird. After reading several webposting on this matter, I found and uploaded V17.0.9 and proceeded to convert the Eudora email, filters and addresses to the Thunderbird format.

This was not an easy task, and even with Google's AI assistance, I had to restart several times, but as of today - mid-Jun I have now completed the task of cleaning up all the email, installing the correct headers, etc that allows the Thunderbird program to open and correctly display all of those email without any problems.

I further cleaned up and corrected all of the Eudora filters to the TB format and now have those filters in TB to be able to be installed and correctly are accepted by the TB program.

Like wise with the contact addressee that were in the Eudora NNdbase.nnt file were cleaned up and correctly installed in the TB program.

However, the current status of the TB program is that it does not seem to be able to connect to the Scala Webhosting email site at grok.viawebhost.com. Enclosed is a pic of the supposed correct set up for the STMP at Port 465.

The other Port info from Scala is: POP3 - 995 (SSL) IMAP - 993 (SSL)

But I am not sure what else I need to do to correctly set up this older version so that I can start the collection process of the most recent emails sitting in the mailserver.

Further, it was suggested that I need to update the TB V17.0.9 to the most recent V151 by following the below sequence of updates:

According to Mozilla Support Documentation, this is the exact, official sequence to migrate safely from a legacy version:

Step 1: Run V24.8.0 (32-bit) (This updates the raw database schema out of V17. Upgrades the raw Mbox structures.)

Step 2: Run V45.8.0 (32-bit) (Stabilizes the folder indexing schema.)

Step 3: Run V52.9.1 (32-bit) (The final 32-bit staging version.60.9.1 (64-bit). Migrates the architecture to 64-bit processing.)

Step 4: Run V60.9.1 (This is the critical gatekeeper version required to unlock modern automatic profile conversion).

Step 5: Run V78.14 (This shifts the mail indexing formats).

Step 6: Run V102.15.1 (This modernizes the folder structure configurations).

Step 7: Final jump to V151.0.1 (Updates the background engine to current web standards).

I am looking any advice or suggestions from the Community that can assist me in completing this conversion to the TB program and get it fully functional so I can connect to the Scala Hosting mailserver.

Many thanks in advance for your assistance.

/s/ James T Saint