flashplayer install broken on adobe site?

[Jeff]

A customer called because their browser isn't displaying any flash swf files. I told them to go to the macromedia/adobe site and download the latest flash player just in case their flash plugin was corrupt. However when they clicked download flash player, they only got an error on the resulting page. (www.adobe.com/shockwave/download/triggerpages_mmcom/flash.html)

Sure enough, on a windows 2000 box running IE6, I get the same thing. No flash player download/install, only an error on the page"an error has occurred in this dialog Error: 58 Error in loading DLL.)

Any thoughs on how they can install/update their swf plugin and get past this error on the adobe site?

(it works fine on my xp machine in firefox, but telling them to change browsers seems a bit extreme :rasberry: )

[Adam]

It worked fine for me in IE6, maybe it's been fixed now?

If they still can't get through, here is a direct link to the standalone installer (the one you get when you do it with Firefox, but it says it also works for IE):

http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player.exe

If I remember, that asks which browsers you wan't to install it in when it's run.

[Jeff]

Thanks Adam. That just installs straight to mozilla though... doesn't install for IE6 here or give any prompt asking which browsers.

It must be something messed up with the IE6 browser on both my test box and the client's computer... strange.

[Adam]

Hmm IE6 uses ActiveX to install it dynamically from the website. Maybe there's a problem with the ActiveX settings in the browser?

These are my settings in Tools > Internet Options > Security > Custom Level...

Automatic promplting for ActiveX controls: Disable
Binary and script behaviours: Enable
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disable
Initialise and script ActiveX controls marked as safe: Disable
Run ActiveX controls and plug-ins: Enable
Spript ActiveX controls marked safe for scripting: Enable

Then again, maybe it's a corrupted DLL or something completely different. :dunno: