---
title: "xaDriveMapping.exe Causes High CPU Usage"
slug: "xadrivemappingexe-causes-high-cpu-usage"
description: "Sometimes, when XA is installed in Single User Mode, the 'xadrivemapping.exe' will fail to terminate and be running at ~30% CPU usage. This is a troubleshooting article on how to address this issue."
updated: 2022-06-01T20:14:37Z
published: 2022-06-01T20:14:37Z
canonical: "healthcare.rapididentity.com/xadrivemappingexe-causes-high-cpu-usage"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://healthcare.rapididentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# xaDriveMapping.exe Causes High CPU Usage

## xaDriveMapping.exe Causes High CPU Usage

### PROBLEM BEHAVIOR

When XA is installed in Single User Mode, the 'xadrivemapping.exe' will fail to terminate and be running at ~30% CPU usage.

If the session is locked and unlocked, several more instances of xadrivemapping.exe may spawn and the CPU will be pegged at 100% usage.

### EXPECTED BEHAVIOR

xaDriveMapping.exe will terminate itself after starting on a Standard User Mode system.

### AFFECTS:

XA running in Standard User Mode, versions lower than 4.12.3.

### ROOT CAUSE:

There is an infinite loop in the Terminate event of the main form where it is waiting for the drive mapping script to end - but since it never started one, it never receives the notification that it has terminated.

### RESOLUTION

1. Upgrade the client system to 4.12.3(or higher) or
2. Delete the following registry setting

[HKEY_LOCAL_MACHINE\SOFTWARE\HealthCast\eXactACCESS\notification] **XADriveMapping.clsXALoginNotification=eXactACCESS Kiosk Mode Drive Mapping"**