Explorer not capturing screenshots

View as Markdown

Why didn’t the runZero Explorer capture screenshots?

The runZero Explorer needs a working install of Google Chrome to capture screenshots. Install Chrome in one of the locations the Explorer checks, listed below for each OS.

Windows

On Windows, the runZero Explorer looks for Chrome in:

c:\Program Files (x86)\Google\Chrome\Application\chrome.exe

The Explorer also checks these environment variables:

  • ProgramFiles(x86)
  • ProgramFiles
  • ProgramW6432

Each may point to another directory, in which case the Explorer also looks in \Google\Chrome\Application\chrome.exe under each of those directories.

To see what the environment variables are set to, open a Windows command prompt and enter the command set.

On a default Windows 10 install, ProgramFiles and ProgramW6432 are both c:\Program Files, so the Explorer also checks:

c:\Program Files\Google\Chrome\Application\chrome.exe

This is the default location for Chrome on Windows 10 (64 bit).

macOS

On macOS, the Explorer checks these locations:

  • /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
  • /Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary
  • /Applications/Chromium.app/Contents/MacOS/Chromium

Linux

On Linux, the Explorer checks these locations:

  • /usr/bin/google-chrome
  • /usr/bin/google-chrome-beta
  • /usr/bin/google-chrome-unstable
  • /usr/local/bin/chrome
  • /usr/bin/chrome
  • /opt/google/chrome/google-chrome
  • /usr/bin/chromium
  • /usr/bin/chromium-browser

Chrome is installed, but screenshots still don’t work

Check the Explorer log file for details about the scan. If Chrome is installed in one of the standard locations but the Explorer still can’t find it, it could be a permissions issue. Chrome can also fail to run for other reasons, such as a corrupt Chrome profile.

You also won’t get a screenshot of an http(s) service when:

  • The service is on an IPv6 link-local IP address (Chrome cannot access these)
  • It uses a TLS version lower than 1.2 (Chrome no longer supports accessing these)
  • The browser timed out while taking the screenshot (for example, an unresponsive host)
  • The host returned an error code
Updated