Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i Support

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.

Læs mere

when i click on my desktop shortcut icons in new firefox 4 i get a dialogue box that says windows cannot find that website

  • 2 svar
  • 3 har dette problem
  • 14 visninger
  • Seneste svar af APZ1

more options

i upgraded from the previous version of firefox to the new firefox v.4 and now all the shortcut icons that i used with the previous version display a popup dialogue box that says windows cannot find that website, check the spelling--address--etc. But immediately after that window pops up the website does load. I tried loading the original website, deleting the old shortcut and dragging the new shortcut to my desktop but Firefox still gives me the same message.

i upgraded from the previous version of firefox to the new firefox v.4 and now all the shortcut icons that i used with the previous version display a popup dialogue box that says windows cannot find that website, check the spelling--address--etc. But immediately after that window pops up the website does load. I tried loading the original website, deleting the old shortcut and dragging the new shortcut to my desktop but Firefox still gives me the same message.

Alle svar (2)

more options

Valgt løsning

more options

cor-el, Thanks for the response. It did solve the problem. I did uninstall and reinstall ff4 but that did not fix the problem. The real problem was my Foxclocks extension. When I disabled that the problem was solved. Thanks, APZ1