X
Tap here to go to the mobile version of the site.

Support Forum

I tried to update to 66 but i got this: Microsoft(C) Register Server has stopped working. Why?

Posted

I tried to update from 56 to 66 but got this message: "Microsoft(C) Register Server has stopped working." I didn't have this problem upgrading from 54 to 56 two days prior, why suddenly now? I'm on Windows7 64, and i was able to go and download and install "Vivaldi" browser, so it's really Firefox that is doing this, is it because i have to go to 57 first THEN to 66?? I have no idea. Anyone get this same thing?

I tried to update from 56 to 66 but got this message: "Microsoft(C) Register Server has stopped working." I didn't have this problem upgrading from 54 to 56 two days prior, why suddenly now? I'm on Windows7 64, and i was able to go and download and install "Vivaldi" browser, so it's really Firefox that is doing this, is it because i have to go to 57 first THEN to 66?? I have no idea. Anyone get this same thing?
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 28.0 r0

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0

More Information

Tyler Downer
  • Top 25 Contributor
  • Moderator
1529 solutions 10654 answers

Can you download Firefox 66 from https://www.mozilla.org/firefox/all/

Can you download Firefox 66 from https://www.mozilla.org/firefox/all/
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17415 solutions 157316 answers

There are some 'watershed' builds that have special migration code to prevent profile issues with incompatible file. This can require multiple updates to get to the current release, but is usually safer.

  • Bug 1415172 - Set up watersheds to move users to Firefox 57

Such watershed build can also be used to prevent future accidents like recently happened.

  • Bug 1549018 - create a transition plan to prepare for the add-on signing root expiring in 2025

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

There are some 'watershed' builds that have special migration code to prevent profile issues with incompatible file. This can require multiple updates to get to the current release, but is usually safer. * Bug 1415172 - Set up watersheds to move users to Firefox 57 Such watershed build can also be used to prevent future accidents like recently happened. * Bug 1549018 - create a transition plan to prepare for the add-on signing root expiring in 2025 (<i>please do not comment in bug reports<br>https://bugzilla.mozilla.org/page.cgi?id=etiquette.html</i>)

Modified by cor-el

Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.