---
title: Explorer not capturing screenshots
---

## Why didn't the runZero Explorer capture screenshots?

The runZero Explorer needs a working install of ((Google Chrome)) to obtain screenshots. To check for Google Chrome, the Explorer looks in the following locations on each OS. 

### Windows {#screenshots-windows}

The runZero Explorer looks for Chrome on Windows in:

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

The Explorer also checks the following environment variables:

- `ProgramFiles(x86)`
- `ProgramFiles`
- `ProgramW6432`

Each may list another directory, in which case the Explorer looks in `\Google\Chrome\Application\chrome.exe` under each of those directories as well.

To find what the environment variables are set to, open a Windows command prompt and entering the command `set`.

For a default Windows 10 install, the default value of `ProgramFiles` and `ProgramW6432` is `c:\Program Files`, which means the Explorer also checks the following location:

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

This is the default location for Chrome on a 64 bit Windows 10 system.

### MacOS {#screenshots-macos}

On macOS, the Explorer checks for Google Chrome in the following 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 {#screenshots-linux}

On Linux systems, the Explorer checks for Google Chrome at the following 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

If Google Chrome is installed in one of the standard locations, but isn't being found, it could be a permissions issue. It is also possible for Chrome to fail to run for other reasons, such as a corrupt Chrome profile. The next step to take is to check the [Explorer log file](installing-an-explorer.md#log-management) which will have more detail about the scan operation.