Flash 15.0.0.152 32-64 Bit Plugin
Reece Pourier
When I uninstall and then reinstall Chrome, however, the problem goes away. I am able to view flash videos. But when I sign into Chrome and have all of my bookmarks, settings, and extensions synced automatically, the problem comes back.
When the flash player stops loading from one day to the next, it's possible that a recent DLL update to C:\Users\\AppData\Local\Google\Chrome\User Data\PepperFlash\20.0.0.xxx\pepflashplayer.dll is the cause. The xxx can vary over time: 267, 286..
To test the DLL, hide/rename it as pepflashplayerHide.dll. Close/open Chrome, which will now use it's builtin DLL. If the player works, you've found the culprit. You can stop with the Hide workaround or try to fix the problem.
To correct the problem, delete the PepperFlash folder. Close, open Chrome: the flash player should load. If the problem reappears (after the folder auto updates), there may be permissions problem (see below).
The better approach is to fix the folder permissions.. You only need to fix the 20.0.0.xxx folder, the critical permission is 'Read and Execute'. Try this succinct Best Answer (old but good) or see this recent longer one.
The 32/64-bit conflict is being worked as bug 546017. Institutional users may see the same "Couldn't load plugin" failure, but this is related to network share permissions. See bug 572131 for details.
Users might be using weird browsers - IE and Firefox are common, and we probably have an Opera user somewhere; maybe a Chrome user too. I know that 64-bit Windows 7 ships with 32-bit and 64-bit versions of IE, and I'd like to send them both the 64-bit version of my download.
(Edited to add: I know that I should provide all the options, and I will. But people don't read the options. So I wanted to provide the right download by default, to improve usability. Of course, while this is helpful if I get it right, it's extremely unhelpful if I get it wrong. And from the answers so far, it doesn't look like there's a reliable way of doing this).
I'm not sure your situation, but I would consider just doing what most other sites do and let the user choose which download they get. They could be downloading it for another machine, to put on a flash device, or just may simply want the 32-bit version to run on their 64-bit box. Whatever reason, I would rather have the choice.
I've checked the other two answers from RC and Pino. They both do not work because of the same problem as you suggest - 32-bit IE on 64-bit Windows will wrongly identify the platform as 32-bit. As most people run 32-bit IE on 64-bit Windows (many plugins e.g. Flash are not available in 64-bit), there will be a lot of innacurate identifications
It worked everywhere expect Mac computers. And unfortunately seems that it's not possible to get that information via JavaScript :(. However one more trick could be done there. Because Adobe didn't support flash player on x64 browsers, you can just try to detect it. If detection is successful, than it is definitely 32 bit browser, if no, than it's 32 bit browser without flash plugin or it's 64 bit browser. Because penetration rate of Flash player is quite huge(see _census/flashplayer/version_penetration.html), this should be good enough to at least detect x32 browser under Mac.
Both window.navigator.cpuClass and window.navigator.platform return the browser platform. Not the system platform. So if you are running a 32-bit browser on a 64-bit system then both varibales would return 32-bit. Which would be incorrect.
Many of the most common issues that arise when using Mozilla Firefox, Portable Edition are addressed here. Please read through the various topics to see if any of them address your question. You can also post a question in the Firefox Portable Support Forum.
To install Firefox Portable, just download the portable package at the top of the Firefox Portable page and then double-click it. Select the location you wish to install to and click OK. A FirefoxPortable directory will be created there and all the necessary files installed. That's all there is to it.
To start up Firefox Portable, just double-click FirefoxPortable.exe file where you installed PortableFirefox on your portable drive. Then, use it just like you would a local copy of Firefox. There are acouple of things to keep in mind:
To upgrade to a newer version of Firefox Portable, just install a new copy of Firefox Portable right over your old one. All your data will be preserved. You can use the built in updater as well, but some non-personal files or directories may be left behind.
If you're upgrading from Portable Firefox (older name and directories), make a copy of your existing profile folder within the PortableFirefox\Data\profile directory on your portable drive. Then download the new version of Firefox Portable and copy your profile from the old version into the new version withinFirefoxPortable\Data\profile. If you added any plugins or searchplugins, you should copy those directories as well (PortableFirefox\plugins to FirefoxPortable\Data\plugins and PortableFirefox\firefox\searchplugins to FirefoxPortable\App\firefox\searchplugins).
If you're using a local copy of Firefox, you may wish to just copy your local Firefox settings right into Firefox Portable. Your local Firefox profile is usually installed in C:\Documents and Settings\[user]\Application Data\Mozilla\Firefox\Profiles\default.???\ After running Firefox Portable once to let it setup its data directories, just copy the contents of that folder (except the cache directories) to the FirefoxPortable\Data\profile directory. Then, and this is important, delete the file FirefoxPortableSettings.ini within the FirefoxPortable\Data\settings directory, if there is one. When you start Firefox Portable for the first time, it's recommended that you turn off disk cache, password saving and history if you're using a flash-based portable device. You can set all of these within the Privacy tab of the Firefox Options window. Sometimes, certain profiles will cause the launcher to fail or hang. It's best to give it a few minutes to see if it's just checking compatibility and adjusting the locations of the extensions before giving up on it. If it fails, it is usually due to an incompatible extension.
Firefox Portable can be configured to open mail links in Thunderbird Portable or another portable mail client of your choice. To do so, click the menu icon in the toolbar (sometimes called the hamburger menu) and select Options. In the Options tab, scroll down to Applications. Scroll down until you see mailto in the Content Type column and click the dropdown in the right hand column next to it. Select "Use other..." from the dropdown. Click the Browse button and select the ThunderbirdPortable.exe launcher or similar for another client. Do not select the main thunderbird.exe executable as that will cause Thunderbird to run in non-portable mode. Click OK in the popup window and then close your Options tab. Mailto links will now open in Thunderbird Portable. The path will be adjusted automatically as you move PCs.
A second profile can allows you to setup another set of settings (bookmarks, extensions, preferences, etc) for Firefox Portable that you can use independent of your main settings. This is useful for sharing a flash drive with someone, testing extensions and configuration options or separating our work from personal details.
To use a second profile, install the Firefox Portable 2nd Profile 2.0.2 app in the same PortableApps directory that FirefoxPortable is in (so, if Firefox Portable is installed to X:\PortableApps\FirefoxPortable, you'd install this to X:\PortableApps\FirefoxPortable2ndProfile). In the PortableApps.com Menu, it will show up as "Mozilla Firefox, Portable Edition 2nd Profile". You can easily rename it to something more useful by right-clicking and selecting rename. When you run it, it will start Firefox Portable up with your second profile without affecting your main profile. You can even install a 3rd or 4th profile by installing the 2nd Profile app again to another location (like X:\PortableApps\FirefoxPortable2ndProfile_Copy_1 so the platform will update it for you) and then renaming it in the PortableApps.com Menu.
To use the private window mode shortcut, install the Firefox Portable Private Window Mode 1.0.1 app in the same PortableApps directory that FirefoxPortable is in (so, if Firefox Portable is installed to X:\PortableApps\FirefoxPortable, you'd install this to X:\PortableApps\FirefoxPortablePrivateWindow). In the PortableApps.com Menu, it will show up as "Mozilla Firefox, Portable Edition Private Window". You can also rename it for the other channels of Firefox Portable. For example, renaming the shortcut's directory to FirefoxPortableTestPrivateWindow will launch the beta version of Firefox Portable in the FirefoxPortableTest folder.
Note that all plugins except Flash require Firefox to run in 32-bit mode, which you can force with AlwaysUse32Bit. Like many browsers, Firefox will be dropping support for all plugins except Flash by the end of 2016.
Notes: It should be noted that Adobe Flash does *not* officially support running in any portable configuration. And, as it is a closed source application, we can neither modify it nor package it into a more portable-friendly installer. It should also be noted that it is illegal to redistribute either flash or shockwave without the full installer.
Firefox Portable includes both the 32-bit and 64-bit versions of Firefox and will use the appropriate version on each PC. There are some reasons why a user might wish to run a 32-bit version on 64-bit Windows. Reasons include plugin compatibility (older versions of Firefox allow plugins besides Flash), testing extensions, etc. The launcher has a setting called AlwaysUse32Bit which, when set to true, will cause the 32-bit version to be launched regardless of the host OS. It can be activated by copying the FirefoxPortable.ini configuration file from the FirefoxPortable\Other\Source directory to the FirefoxPortable directory and editing it to set AlwaysUse32Bit=true
7fc3f7cf58