Error Message: An Application Error Has Occurred and an Application Error Log Is Being Generated
This article provides help to solve an issue that occurs when you log on to a computer running Terminal Server Edition.
Original product version: Windows Server 2012 R2
Original KB number: 240992
This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
When you log on to a computer running Terminal Server Edition, you may receive the following error message:
An application error has occurred and an application error log is being generated. Userinit.exe Exception: access violation (0xc0000005), Address: 0x77f901b3
The address value may be different, depending on your computer configuration.
The Terminal Server client is disconnected after you click OK or Cancel.
This behavior occurs because an invalid value exists in the registry.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition.
If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this issue, delete the invalid registry value:
Start Registry Editor (Regedt32.exe).
Locate the following registry key:HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\IniFile Times
Locate the invalid value (this is usually a value with no name).
Click the invalid value.
On the Edit menu, click Delete, and then click Yes.
Quit Registry Editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT 4.0 Server, Terminal Server Edition, Service Pack 5.