In this article, I will explain how to resolve the COULD NOT GET TEMP DIRECTORY error simply.


From my research this error appears on RDS (WS2012R2) servers using User Profile Disks (UPD).

This error occurs when a user tries to install an extension on Google Chrome, I first think of a problem of right, with the admin account I got the same message, so I search on Google and I came across this article (in English) which explains why and how to solve it.

I first tested the solution with an account made the changes by hand on the environment variables and I was able to install my Chrome extension.


First, you must create on each RDS server, a TEMP folder at the root of the C with write / modify rights for everyone.

Then you have to set up a GPO, which does two things:

  1. For each user who logs in to create a personal folder in the C: TEMP folder
  2. Modify TEMP and TMP environment variables

There are two settings to apply at the user level.

1 – Creating the personal folder in the TEMP folder:

2 – Modification of environment variables:

All you have to do is close and reopen the sessions to install the Chrome extensions without error.

Related Posts

RDS Farm: High Availability Service Broker Configuration

As a follow-up to the article: Deploy a RDS Windows 2012 R2 / 2016/2019 farm, we will see in this tutorial how to configure the high availability service broker. This configuration is optimized for cl

Connecting to Remote Desktop Session Host servers by the Broker

Problem If you followed the article: Setting up an RDS farm under Windows 2012R2/2016, the client connection configuration is done using a Round Robin on the DNS. What happens if the server returned b

RDS: reduce the logon time

Introduction Before I explain how to optimize the opening of sessions on your RDS servers, I will explain the operation. By default, since Windows XP, the group policy processing mode is asynchronous,