Over RDP, User Account Control and split admin tokens behave like a local console, but some installers refuse to elevate across a network logon. If Uninstall stays gray, try the same action from a local admin session or use runas only when your policy allows it.
Microsoft Store removals sometimes need the interactive user who installed the package. Have that person sign in, or use the documented PowerShell removal cmdlets your tenant approves.
Log every remote cleanup in your ticket: product name, build, and whether you rebooted. It prevents duplicate work when another tech connects the next day and sees a half-finished wizard.
Session zero vs interactive desktop still matters. Tools that spawn UI on the physical console may not paint the same prompts over RDP. If an uninstaller appears hung, check for hidden windows on the console session or switch the user to local login temporarily when policy allows.
Fast User Switching can leave another profile’s processes resident. Before forcing removal, confirm no other user session has the product open—even if you are connected as admin, their suspended session might still lock DLLs.
Scheduled tasks under \Microsoft\Windows and vendor-named trees often relaunch agents you thought you removed. Export task definitions before deletion so you can restore them if a line-of-business app depended on that hourly sync.
When Store-delivered apps refuse removal remotely, verify whether the package was installed per-user. Have the end user sign in interactively once, or use the automation channel your org approved (Intune removal, PowerShell with delegated rights) instead of repeatedly hammering the same cmdlet from your admin shell.
Capture screenshots of error dialogs with timestamps visible. Remote sessions add latency; a single screenshot plus the exact command you ran beats three paragraphs of “it didn’t work” in the handoff to the next engineer.
Credential Guard and smart-card stacks can block silent uninstalls. If elevation prompts never appear, verify whether the session is running under a split token and whether your RDP client forwards smart-card PINs the installer expects.
When using jump boxes, copy logs to the ticket host before disconnecting; ephemeral session disks may wipe C:\Temp the moment you drop the RDP session.
Latency-sensitive uninstall wizards time out faster over high-latency VPNs. If progress bars snap to “rolled back,” rerun during off-hours or from a data-center–adjacent hop to avoid false failures.
After remote cleanup, ask the user to sign out/in locally once; some shell extensions only refresh on a full profile reload, not on admin reconnect alone.