> For the complete documentation index, see [llms.txt](https://docs.keyfax.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyfax.biz/product-suite/client/installation/known-issues.md).

# Known Issues

The below lists known problems you may encounter when installing the Keyfax Client. Workarounds are provided were available.

### Keyfax fails to launch for non-admin users 

You may see a 'Permission denied' message or Keyfax simply fails to launch. 

For Citrix/Terminal Server/RDS® installations, the Keyfax Client must be installed using an Administrator account (not a user that has merely been assigned Admin privileges) from the machine's desktop (i.e. not from a terminal session).

When diagnosing problems with the Keyfax integration, if you find that the Keyfax components (typically **Keyfax.OCX** or **KeyfaxMIS.OCX**) have been installed in the folder (e.g.)

```
  C:\Documents and Settings\CXBOX01\WINDOWS 
```

or beneath

```
  C:\Users\username 
```

this indicates that the software has been incorrectly installed (probably without installing via **Add/Remove Programs** or setting the server to **Install Mode**). The Client will need to be uninstalled and re-installed correctly.

### The file C:\Windows\system32\oleaut32.dll could not be opened. Please check your disk is not full and that you have access to the destination directory."

This can occur when installing the Client ; rerun in XP Compatibility mode. Right click on the installation executable (e.g. **KF40client\_4-0-0-41.exe**) and select the **Compatibility option** as shown:

<div align="left"><figure><img src="/files/FpLfY20q1zAT4bW7Gzz7" alt=""><figcaption></figcaption></figure></div>

### **This software requires an addtional 159K bytes free on the G: drive**

The environment variable 'HOMEDRIVE=G: can cause this problem. It can also be caused by not setting to INSTALL mode, i.e. **CHANGE USER / INSTALL**