ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox Upgrade Breaks Windows 10 Default Browser Setting

  • 5 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 9 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย FFus3r

more options

Users on Windows 10 upgrading from 52.4.0 to 60.1.0 are being forced to re-select a default browser after the upgrade. We've determined the cause to be due to the fact that Firefox is automatically changing the file associations/default browser settings during the upgrade and Windows 10 will not allow this behavior to happen automatically. Windows generates a unique hash in the UsersChoice registry key to verify this was set by the user and not malware, since the hash no longer matches it wipes out the default browser setting and forces the user to select a default browser again, or in some cases automatically reverts it back to Edge. Of course the MS stance is that third party apps need to be fixed so they do not make this automatic association changes, and if they do they aren't Windows 10 compliant.

Does anyone know if there is a work around for this issue, or plans to change the Firefox upgrade method to stop this from happening?

เปลี่ยนแปลงโดย joecarder เมื่อ

การตอบกลับทั้งหมด (5)

more options
more options

Hi FFus3r,

Thank you for the response and the link, it's appreciated. Unfortunately though, that link doesn't really address my question at all. What I'm trying figure out is when upgrading Fire Fox, how to stop it from changing the default Windows 10 file associations in the first place which is the root cause of this problem. I already know how to set the default browser, but if the root cause could be addressed then we wouldn't have to do that.

Thanks again for the information though!

more options

hi,

i understand,

see this page:

scroll down to Backup & Restore File Type Associations

more options

Thanks again FFus3r! That is good information on how to deal with the problem after Fire Fox changes the association on an upgrade, but I'm trying to see if the root of the problem can be addressed before it happens. I suppose this would probably more of an appropriate question/bug for the developers forums. Thanks again for your time though!

more options

as far as i know its the easiest way,

BUT

wait for other volunteers to help you.