We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

update from 47.0.1 to 49.0.2

  • 2 답장
  • 5 이 문제를 만남
  • 3 보기
  • 최종 답변자: jnygren

more options

Beta news just announced Firefox 49.0.2 (windows 32/64) but my version (47.0.1) says it's fully up to date what gives?

Is beta news faster to get the most recent Firefox than Mozilla's own update channel?

Beta news just announced Firefox 49.0.2 (windows 32/64) but my version (47.0.1) says it's fully up to date what gives? Is beta news faster to get the most recent Firefox than Mozilla's own update channel?

선택된 해결법

I have almost the same problem. I started a PC I haven't used for a while, which was at version 44.something. I get a notification to update to 47.0.1. The update button on the 'About Firefox' screen shows the same. The description of the hotfix mentioned above doesn't sound like it has anything to do with this problem. Is this link correct?

문맥에 따라 이 답변을 읽어주세요 👍 2

모든 댓글 (2)

more options

hi, if you have not set firefox to update automatically, you may have to manually install the following hotfix addon to be able to jump over 47.0.1... https://addons.mozilla.org/firefox/addon/firefox-hotfix/

the reason for this is a bit complicated - it's basically a certain third-party software ("websense") that causes firefox 48+ to crash on startup so we are only updating installations where we know that they aren't users of this thirdparty tool at the moment.

more options

선택된 해결법

I have almost the same problem. I started a PC I haven't used for a while, which was at version 44.something. I get a notification to update to 47.0.1. The update button on the 'About Firefox' screen shows the same. The description of the hotfix mentioned above doesn't sound like it has anything to do with this problem. Is this link correct?