RDS 2016 Event 1511 User Profile Service Slow logons

Question

We are getting tons of slow logon issues and black screen issues on our 2016 RDS session host all of a sudden since last week .

I found this one in the Event logs not sure if this could be to root cause.. How to Fix this one ????

***The server where the UPD's reside is separate from the RDS server .

Log Name:      Application
Source:        Microsoft-Windows-User Profiles Service
Date:          12/20/2021 9:58:51 PM
Event ID:      1511
Task Category: None
Level:         Error
Keywords:      
User:          DOMAIN\username
Computer:      RDS1.domain.local
Description:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
    <EventID>1511</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2021-12-21T03:58:51.546247400Z" />
    <EventRecordID>782025</EventRecordID>
    <Correlation />
    <Execution ProcessID="1524" ThreadID="7984" />
    <Channel>Application</Channel>
    <Computer>domain-RDS1.domain.local</Computer>
    <Security UserID="S-1-5-21-1060284298-1390067357-725345543-5694" />
  </System>
  <EventData>
  </EventData>
</Event>

Answer 1

This event id 1511 means that you have entered a temporary profile. Usually the cause is because the profile was accidentally deleted or corrupted.

To fix this follow the instruction below:

Log into the workstation with a different administrator account and back up the user profile. Open regedit.exe and back up the registry. Delete SID.bak corresponding to the user account in HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ ProfileList. Close regedit.exe and log off. Ask the user to login and verify that the error no longer occurs.

---

--If the answer is helpful, please vote positively and accept the answer--