Quote: Originally Posted by whs
Right click on the file > Open With > Choose Default Program > Browse > navigate to the FF .exe > double click
Thanks for the reply. The problem here is that the actual "file" never shows up anywhere I could use File Explorer to access it. The link in the site is supposed to print a claim form. When clicked, it tries to open the viewclaimform.aspx file from Firefox, which just appears as a blank window with the mention if it being viewclaimform.aspx file at the bottom. Then the computer, not knowing what to actually DO with an aspx file, makes its best guess and opens Windows Media Center. But from there I can find no way to view the aspx file anyway.
While all this is happening, the actual claim form file gets downloaded as a PDF file. which we can then access with Adobe Reader. But I am trying to get rid of the issue causing Windows Media to open. When it does, it does not display the aspx file. It just displays its typical startup screen.
I played with it some more, and got it to save a copy of a file named ClaimForm_PrinterFriendly.aspx to a folder. When I went there to look at it, the file name had appended itself to now be ClaimForm_PrinterFriendly.asp.html. I right clicked it and assigned it to Firefox. But when it subsequently tried to open, Firefox just displays the blank window this file created previously before it had opened Media Center. So I deleted the ".html" suffix, because the file extension I had actually created was just ".aspx". I right clicked it, and assign it to Open With Firefox. But it STILL causes Windows Media Center to open. It refuses to use Firefox.
If I close the browser, reopen it and log back into the site, and access the link again, it opens the blank window in Firefox, then opens Media Center on top of it. So I still have not stopped it from automatically opening Media Center. Note that before posting on the forum, one thing I had done is to remove ALL of Media Center's default file associations. It actually shouldn't be opening from ANY file. But it still does.
Perhaps the whole issue is being caused by the insurance claim website itself, and is overriding everything I am trying to do to change its result?