In one case, the issue was a script that was running over and over but did not close the handle after it ran. This used up the desktop heap space, causing this issue, along with a Policy Override Tool failure
In another case, the cause was found to be the following:
This can be reproduced by running psexec (a Systernals tool) to attempt to open up a command window on the affected machine. An error will be thrown that when researched will point back to Desktop Heap Exhaustion.
Imported Document ID: TECH201666
Subscribing will provide email updates when this Article is updated. Login is required.