Software Installation

Windows Installation

The program installation starts by running the executable file of the distribution package (

If you downloaded FastRawViewer from our site on the first program launch, current versions of Windows will display the following security warning:

After the “Run” button is pressed, the UAC (Windows User Access Control) system will display a warning once again:

Both dialogs allow you to verify that the setup program is signed with unique LibRaw LLC electronic signature.

To proceed with the installation, you must agree to the dialog above, and the usual Setup Wizard will be launched:

At the next screens of Setup Wizard:

  1. The User License is displayed.
  2. An installation folder is suggested; a different folder may be selected by the user.
  3. Creating a Group in the Programs menu is suggested.
  4. A list of possible additional actions is shown: add FastRawViewer to desktop right-click menu, add icon to the desktop, add icon to the Quick Launch menu:

Afterwards, the installation takes place. Upon completion, the following screen appears:

In case of any errors during installation, please contact us via or technical support forum at

Mac OS X

Double click on FastRawViewer-1.x.x.dmg to mount the FastRawViewer disk image you've downloaded. The content of the disk image will appear like this:

Drag FastRawViewer icon onto the Applications icon. The program will be copied to Applications folder and ready to run.

Other items contained in the disk image are:

  • FastRawViewer Manual (FastRawViewer-manual.pdf).
  • Brief description (README.txt) and Changelog (Changelog.txt).
  • End-User License Agreement (EULA.txt), Copyright Information (Copyrights.txt).
  • Licenses and Copyrights for libraries and components used in FastRawViewer (Licenses folder).
  • Scripts folder contains additional scripts used to set parameters that are not needed in a general case and therefore are not placed in the Settings menu. These scripts will be copied upon installation together with the application and are accessible through FastRawViewer menu.

Windows: Hardware Acceleration Method Selection

FastRawViewer uses graphics acceleration for many operations. When working in Windows, the following graphics engines can be used:

  • OpenGL (hardware acceleration).
  • DirectX 9.
  • DirectX 11 (Windows 7 and newer only).

During FastRawViewer’s first launch, an automatic selection of the graphics engine is made, depending on the operating system and the hardware you have:

  • Windows XP/Windows Vista: DirectX 9 will be selected.
  • Computers with old Intel graphics adapters on a separate chip (chipsets like G45, 845G, 965G, etc.): DirectX 9 will be selected.
  • Computers with two or more graphics adapters, or two or more monitors: OpenGL will be selected.
  • All other cases: DirectX 9 will be selected.

The above-listed rules are sorted through “from top to bottom” and the first fitting one is used.

The choice of graphics engine is made once and stored in the Windows Registry, so that the process of the selection of the graphics engine is not repeated during subsequent launches of FastRawViewer.

The automatic selection of graphics hardware acceleration can be, however, changed by the user, either through the FastRawViewer Preferences (see the “GPU Processing” section in the “Program settings” chapter), or by launching the Registry scripts (see the “Setting the graphics acceleration manually” section in the “Troubleshooting” chapter).

In rare cases of problems, usually caused by a buggy old video driver, the automatically chosen graphics engine might not work with your hardware/drivers. In this case one of the following will take place:

  • If in DirectX11 mode: the program will switch to DirectX9 mode (so that DirectX9 mode will be active when the user re-launches FastRawViewer) and exits.
  • If in DirectX9 mode: the program will switch to OpenGL mode (so that OpenGL mode will be active when the user re-launches FastRawViewer) and exits.
  • If in OpenGL mode: the program will suggest switching to DirectX9 mode and re-launching the program.

This is described in more detail in the “Troubleshooting” section.