Resolve LogMeIn session stuck at Windows lock screen

draft · remote-access logmeinserverrdpsession-management

Generated by docuprocessor (prompt article/v3) · 2026-04-22 14:29

Source thread

thread_id: spaces/AAAA05BdS6s/threads/Qtr_SQdUIT8 · 12 msgs · first 2024-12-24 · participants: Tech ATech BTech CTech D

Tech A 2024-12-24 14:38

For Genuine Smiles PA - Livingston, trying to access the Server LIVINGSTON - SVR19, but it seems stuck, Ctrl+alt+del does not work and it does not load the admin profile, is sitting there but then it goes back to "sleep" screen

Tech A 2024-12-24 14:39

(no text)

image/png Screenshot 2024-12-24 093352.png

A LogMeIn Remote Control session is active, connected to a host machine identified as **"ELFAR LIVINGSTON – SVR19"**. The remote desktop displays a Windows lock/login screen with the user account **"GS\Administrator"** and a **"Genuine Smiles"** dental practice logo as the profile picture. No error codes, diagnostic indicators, or numeric readouts are visible.

Tech A 2024-12-24 14:39

(no text)

image/png Screenshot 2024-12-24 093556.png

**LogMeIn Remote Session — Lock Screen (Windows 10)** The remote desktop displays a Windows 10 lock screen showing **9:35, Tuesday, December 24**. A **LogMeIn Connection Alert** notification is visible in the lower-right corner, reading: *"LogMeIn has disabled the keyboard and mouse attached to this computer for the duration of this remote control session"* with an unchecked option labeled *"Don't display this message again."* The LogMeIn toolbar is visible at the top with controls including **Customize Toolbar, Fullscreen, Options**, and a volume/audio indicator.

Tech B 2024-12-24 14:39

you can try doing RDP from the livington TS

Tech A 2024-12-24 14:41

not seeing any TS for Livingston, i do see TS for the other locations.

image/png image.png

The image displays a list of remote desktop or network connections, all labeled **"ELFAR LIVINGSTON"** followed by department/function suffixes: BILLING, DOC1, FD1, IMAGING, OP1 through OP6, and SVR19. All connection icons appear as **blue monitors**, except **SVR19**, which displays a **green monitor icon**, indicating a status or type difference. No error codes or numeric readouts are visible.

Tech C 2024-12-24 14:41

I Clear cache for user folder and reboot server %windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches

Tech D 2024-12-24 14:42

you can try to RDP from any Livingston PC

Tech B 2024-12-24 14:43

oh yeah, I forgot they took it out lol

Tech D 2024-12-24 14:43

also, if Im not mistaken, they have VPN between offices, so u can RDP from any server to Livingston

Tech A 2024-12-24 14:43

will check that!! Thanks guys!

Tech D 2024-12-24 14:44

but sometimes it might be the LMI itself that is not refreshing

Tech D 2024-12-24 14:44

close and relaunch the session

---
title: "Resolve LogMeIn session stuck at Windows lock screen"
category: remote-access
tags: ["logmein", "server", "rdp", "session-management"]
source_thread_id: "spaces/AAAA05BdS6s/threads/Qtr_SQdUIT8"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T14:29:24"
participants: ["Tech A", "Tech B", "Tech C", "Tech D"]
---

# Resolve LogMeIn session stuck at Windows lock screen

## Problem
LogMeIn remote session to server becomes unresponsive at the Windows lock screen. The session displays the login screen with the GS\Administrator account but does not respond to Ctrl+Alt+Del commands. The screen returns to sleep mode instead of allowing login to proceed. The LogMeIn session appears connected but keyboard and mouse input is ineffective.

## Resolution
1. Close the current LogMeIn session completely and relaunch a new session to the server
2. If LogMeIn continues to be unresponsive, establish RDP connection from any workstation within the same office network
3. For offices with VPN connectivity between locations, RDP from any server at another location to reach the target server
4. If the lock screen persists after gaining access, clear the Windows cache folder at `%windir%\system32\config\systemprofile\appdata\local\microsoft\windows\caches` and reboot the server

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/Qtr_SQdUIT8`
- Attachments:
  - ![image.png](../attachments/Qtr_SQdUIT8.-aZBpOf8-io/image.png) — The image displays a list of remote desktop or network connections, all labeled **"ELFAR LIVINGSTON"** followed by department/function suffixes: BILLING, DOC1, FD1, IMAGING, OP1 through OP6, and SVR19. All connection icons appear as **blue monitors**, except **SVR19**, which displays a **green monitor icon**, indicating a status or type difference. No error codes or numeric readouts are visible.
  - ![Screenshot 2024-12-24 093352.png](../attachments/Qtr_SQdUIT8.6VlaTXB-_lo/Screenshot 2024-12-24 093352.png) — A LogMeIn Remote Control session is active, connected to a host machine identified as **"ELFAR LIVINGSTON – SVR19"**. The remote desktop displays a Windows lock/login screen with the user account **"GS\Administrator"** and a **"Genuine Smiles"** dental practice logo as the profile picture. No error codes, diagnostic indicators, or numeric readouts are visible.
  - ![Screenshot 2024-12-24 093556.png](../attachments/Qtr_SQdUIT8.RUo3fjdfQ5E/Screenshot 2024-12-24 093556.png) — **LogMeIn Remote Session — Lock Screen (Windows 10)**

Generated article

draft