The computer is Windows 7 Professional 64-bit edition. I could use some help with the following error that occurs each time my computer is reboot: Log Name: System Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager Event ID: 1057 Task Category: None Level: Error Keywords: Classic User: N/A Description: The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was Object already exists. Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}" EventSourceName="TermService" I found {C76BAA63-AE81-421C-B425-340B4B24157F} in my registry in the: HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin -> OwningPublisher HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Analytic -> OwningPublisher HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Debug -> OwningPublisher HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational -> OwningPublisher Microsoft-Windows-TerminalServices-RemoteConnectionManager %SystemRoot%\system32\termsrv.dll When I open as administrator a command prompt window and enter the follow: regsvr32 termsrv.dll I get the following message: RegSvr32 The module termsrv.dll was loaded but the entry-point DllRegisterServer was not found. Make sure that termsrv.dll is a valid DLL or OCX file and then try again.

I found a semi-related webpage that at least lists the same Microsoft-Windows-TerminalServices-RemoteConnectionManager and 1057. However I'm running Windows 7 64-bit edition and I seriously doubt I have a lack of available memory issue. Physical Memory (MB) Total 24567 Cached 6337 Avaiable 21821 Free 15709 The relevant status code says that the "Object already exists" which I think is far more relevant then some memory issue. Do I have to delete some file or registry entry? Or is it a security issue? === Event ID 1057 Terminal Services Authentication and Encryption http://technet.microsoft.com/en-us/library/cc775192%28v=ws.10%29.aspx Updated: January 5, 2012 Applies To: Windows Server 2008 Transport Layer Security (TLS) 1.0 enhances the security of Terminal Services sessions by providing server authentication and by encrypting terminal server communications. The terminal server and the client computer must be correctly configured for clients to make successful remote connections and for TLS to provide enhanced security. For example, a certificate is needed to authenticate a terminal server when SSL (TLS 1.0) is used to secure communication between a client and a terminal server during Remote Desktop Protocol (RDP) connections. Event Details Product: Windows Operating System ID: 1057 Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager Version: 6.0 Symbolic Name: EVENT_TS_SSL_SELF_SIGNED_CERT_CREATE_FAILED Message: The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was %1. Resolve Increase available memory To resolve this issue, increase available memory. If this condition persists, contact Microsoft Customer Service and Support. For information about how to contact CSS, see Support Options from Microsoft Services (http://go.microsoft.com/fwlink/?LinkId=52267). One way to increase the amount of available memory is to determine if there are any programs or processes running on the terminal server that can be closed. Use Task Manager to determine which processes are using the most memory, and to end those processes. To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. To free up memory on the terminal server by using Task Manager: On the terminal server, right-click an empty area of the taskbar, and then click Task Manager. Click the Processes tab. Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, on the View menu, click Select Columns, select the User Name and the Memory (Private Working Set) check boxes, and then click OK. At the bottom of the tab, select the Show processes from all users check box. To sort the processes by memory usage, click the Memory (Private Working Set) column header. Determine if you can end any of the memory-intensive processes. To end a process, click the process name, and then click End Process. Click End Process to confirm that you want to end the process. If you cannot free memory by using Task Manager, or if this issue still occurs after you try to free up memory, restart the terminal server. Verify When Transport Layer Security (TLS) 1.0 is functioning as expected for server authentication and encryption of terminal server communications, clients can make connections to terminal servers by using TLS 1.0 (SSL). To verify that the TLS 1.0 (SSL) settings are correctly configured and working properly on the terminal server to provide server authentication and encryption for connections, use Remote Desktop Connection from a client computer to connect to the terminal server. If you can connect to the terminal server and there is a lock symbol in the upper-left corner of the connection bar at the top of the window, TLS 1.0 (SSL) is being used for the connection. Note: To ensure that the connection bar is displayed when you use Remote Desktop Connection to connect from a client computer, select full-screen mode when configuring Remote Desktop Connection settings. To select full-screen mode in Remote Desktop Connection: Open Remote Desktop Connection. To open Remote Desktop Connection, click Start, click Accessories, and then click Remote Desktop Connection. Click Options to display the Remote Desktop Connection settings, and then click Display. Under Remote desktop size, drag the slider all the way to the right to ensure that the remote desktop that you plan to connect to is displayed in full-screen mode.

Is this a security issue or a file exist issue? Should I post this on a different forum?

The computer was not in a domain environment. Unfortunately as of last night I did a Windows 7 in-place upgrade to try and fix the issue. If after all of the windows updates, etc are completed the problem remains I will do what you suggested. I will update this thread once I finish doing all of the windows updates, etc and see where the system is at.

Anyone have any ideas or am I going to have to do a windows in-place upgrade repair again?

I completed the in-place windows 7 upgrade, installed all of the windows updates, etc. The error is still there! /sigh I modified the policy as you said and there was no change in computer behavior. The error still appears each time the computer is reboot.

Hi, May I know if the computer is in domain environment? If so, I recommend to post in Server Forum to get more insights. Meanwhile, please modify the following policy for a test. [Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security] In the right pane, double click "Require use of specific security layer for remote (RDP) connections", in the security layer list, select RDP. Niki Han TechNet Community Support