FAQs for Standalone Browsers

1. Which Standalone Browsers are included in MultiBrowser?

The standalone browsers are downloaded to your local machine using our download manager or can also be manually copied or installed (contact support for a browser installer or manual download link). The browsers are NOT actually installed on the local machine, instead they are individual exe files that are saved in the PrograData\MultiBrowser folder.

You can easily access the standalone browsers by using the "File", "Open Browsers" folder menu option.

  Current Standalone Web Browsers included (7 Dec 2015):
  • Internet Explorer 6 - 11
  • Chrome 18 - 47
  • Firefox 3.6 - 42
  • Safari 5.1.7 (last Windows version)
  • Opera 32 (more Opera versions coming soon)
  Mobile Browser Emulator:
  • iPhone 4, 5 and 6
  • Samsung Galaxy S6
  • Sony Xperia Z3+
  • iPad
  • Samsung Galaxy Tablet
  • Custom device settings are also supported.

2. The Browser Downloader gives me a "Central Directory is corrupt" error for all browsers downloaded?

The “Central Directory is corrupt” error is almost always due to security software preventing the downloaded file from being unzipped and renamed. The browsers are executable files that have been zipped, the downloader will rename and move them to your browsers folder, normally located at C:\ProgramData\MultiBrowser.  

Check your security /anti-viirus software logs or recent activity to white list the downloads, or try to temporarily disable the anti-virus for while downloading the browsers.

If you are unable to edit your security settings please contact support, which can send you a link to manually download the browsers or a browser installer link, which is an msi file that can install the most commonly used browsers for you. 

3. What are standalone Browsers and how do they work?

A cross-platform emulation layer allows many legacy browsers to run properly on new operating systems such as Windows 7 and 8. A generalized multi-platform virtualization layer dynamically adapts virtual machine behavior based on the endpoint platform, allowing a single universal binary to be deployed for each browser/emulator.

There is a detailed explanation here: 

Still need help? Contact Us Contact Us