# Check if ComSpec variable is defined correctly

> The `ChromeNativeMessaging.exe` process runs under the current user and it uses `cmd.exe` to start the browser.

## Description

The `ChromeNativeMessaging.exe` process runs under the current user and it uses `cmd.exe` to start the browser.

If the `ComSpec` environment variable is missing or has an invalid value, then Google Chrome cannot launch the `ChromeNativeMessaging.exe`.

Furthermore, the administrator may disable the command prompt for some users or configure it to always run with elevated privileges.

## Solution

Manually add the correct value for the `ComSpec` environment variable. This variable is set at Windows installation and must be set to: `%SystemRoot%\system32\cmd.exe`.

![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/2024-10-docs-image-170041-817f01af.webp)

## Other workarounds

If the `ComSpec` environment variable is set correctly but the problem persists, the user may not have permission to run the command prompt. In this case, the `ChromeNativeMessaging.exe` process cannot be started with `cmd.exe` running under the current user.

Starting with [Chromium 120.0.6090+](https://chromiumdash.appspot.com/commits?commit=57c3662e332095c8e7d98255d86e29d3a86c530c&platform=Windows), a `NativeHostsExecutablesLaunchDirectly` [Group Policy](https://chromium-review.googlesource.com/c/chromium/src/+/4918033) allows admins to turn this on for users in restricted environments (Cloud PCs that forbid `cmd.exe`, for example).

![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/2024-10-docs-image-359247-e44f5446.webp)

![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/2024-10-docs-image-359251-d6847b13.webp)