GetWindowsDirectory May Return Incorrect Data

This article has been archived. It is offered "as is" and will no longer be updated.
Out of process COM server applications that attempt to discover thelocation of the Windows folder by calling the GetWindowsDirectory() API mayfail when run on Windows NT Server version 4.0, Terminal ServerEdition.

For example, when the Orgchart application supplied with Microsoft Officeis started as an embedded object, Orgchart fails with the following errormessage when it tries to write to the Windows folder:
Unable to load MS Organization Chart. Press F1 for Help.
This message is followed by:
The server application, source file, or item can't be found. You shouldreinstall the server application.
On Windows NT Server, Terminal Server Edition, the GetWindowsDirectory()API should return the user's home folder, not the real Windows folder. Thereal Windows folder is write-protected for "ordinary" users. When theserver application (Orgchart.exe in the above example) subsequently attempsto write to the folder, the write request fails.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
4.00 wts tse DCOM COM COM+

Article ID: 215358 - Last Review: 06/22/2014 19:47:00 - Revision: 5.0

  • kbnosurvey kbarchive kbHotfixServer kbqfe kbbug kbfix KB215358