Adobe Flash Player 10 issues with IE8 64-bit editions

Installing Adobe Flash Player 10 ActiveX (version 10.1.102.64) and related plugin on IE 8 64-bit Edition can cause ActiveX problems. You would not be able to view content with the Flash Player and some Windows management tools such as, Windows Services fail to load with an ActiveX error message.

Before proceeding further, I recommend you to try this free system scan from Uniblue (a Microsoft Gold Certified Partner). You will be able to identify and fix generic Windows errors.

If you install Adobe Flash Player version 10 on IE 8 64-bit editions, you may not be able to view ActiveX content in your 64-bit browser and start experiencing ActiveX warnings when trying to run Windows native management tools. Windows Services console fails to load with error messages such as:

  1. Your current security settings prohibit running ActiveX controls on this page
  2. You have blocked a Publisher of one of the controls, as a result the page may not display correctly

Some users reported same errors with other management tools as well. Adobe states that Flash Player 10 does not run in most 64-bit browsers and it fails to install in a 64-bit browser, however, I tried an installation and it completed successfully, while I still experienced the above mentioned problems afterwards. On other occasions, installing the Flash Player on a clean 64-bit IE 8 did not create the problem mentioned above; hence, the problem may be specific to certain environments or triggered by a third-party component when you install the Flash Player!

Solutions:

According to Adobe, you must use a 32-bit Web browser on your 64-bit operating system to install the Flash Player. All major browsers are available in 32-bit versions and the Internet Explorer 32-bit browser is the default browser on Windows 64-bit systems.

According to Microsoft, knowledge base KB907343 should help you in solving the problem. Additionally, one would need to delete a registry zone entry located just before zone 0 as referred to in the mentioned kb. This problematic key would normally be labeled with a character or number, where in my case it was named L.

This last part actually solved my problem but I would like to remind you to be cautious with registry modifications and I suggest to back up the registry before performing any actions on it!

Share