Windows Server 2025 rdp sessions - profiles issues

Hello Alexandru,

I had the same issues on Windows Server RDP hosts. Here is what I learned:

Taskbar and Settings issue:

• The error happens because Windows tries to load modern apps that don't work well in RDP sessions.

Fix: Disable Windows Spotlight and consumer features via Group Policy. Also remove AppX packages for all users using PowerShell.

Outlook error:

This is usually related to the same profile corruption.

Fix: Clear Outlook credentials from Credential Manager and rename the .OST file.

My advice: Stop deleting profiles and rebooting. That only fixes the symptom. Instead, use FSLogix Profile Containers or mandatory profiles. This prevents corruption from happening in the first place.

I hope you find this helpful

♠ ♠ Ace ♠ ♠

The symptoms point to RDS session/profile corruption or resource leaks on the RDP server rather than a single app issue. Use a structured RDS troubleshooting approach and focus on server-side health and user profile integrity instead of repeatedly deleting profiles.

1. Check if the issue is user-specific or widespread

• Identify whether only some users are affected or many/all.
• If only one or a few users have the taskbar and Settings issues, focus on their profiles and permissions.
• If both administrative and regular users are affected, this suggests a broader security, service, or resource problem on the server.

2. Verify RDS permissions and access rights

• On the server, open Active Directory Users and Computers → under the domain node, select Built-in → right-click Remote Desktop Users → Properties and confirm affected users are members.
• If the server is not domain-joined, open Lusermgr.msc → Groups → Remote Desktop Users and confirm membership.
• If this is a domain controller, ensure only Domain Admins are using RDP.

3. Check RDS collection and app permissions (if using Collections)

• In Server Manager → Remote Desktop Services → Collections → select the relevant collection.
• In Properties, review User Group and ensure the affected users or their groups are listed.
• For any RemoteApp programs, right-click the app → Edit Properties → User Assignment and verify the user/group assignment.

4. Investigate server resource and leak issues Because problems improve after a reboot and then return, this suggests leaks (memory, sessions, or tokens) on the RDP server:

• Monitor memory and CPU usage over time on the server.
• If restarting the whole server temporarily fixes RDP-related issues, try restarting only the Remote Desktop Services (RDS) service as a test:
  • Use Services.msc (or Server Manager → Tools → Services) to restart the RDS service.
  • Note: Restarting RDS disconnects all RDP users, but sessions remain and users can reconnect.
• If restarting RDS also temporarily resolves the behavior, investigate for:
  • Memory leaks: look for processes or services with steadily increasing memory usage.
  • Session leaks: issues that do not show obvious high CPU/memory but accumulate “under the hood,” often caused by non-Microsoft software (AV/endpoint protection, session hooks, shell extensions, etc.).
• As a test, gradually remove or update non-Microsoft software that interacts with RDP sessions (security software, shell customizations, UI add‑ons) and monitor whether the issue stops.

5. Check for Remote Desktop Services service issues

• Confirm the RDS service is running on the server. If it is stopped or unstable, start it and monitor.
• For larger deployments with multiple RD Session Hosts, verify the service status on each host.

6. Validate connectivity and basic RDP health

• Confirm that an administrative RDP connection works: from another machine, run mstsc /admin and connect.
• Verify the server is reachable (e.g., ping, nslookup) to rule out network/DNS issues.

7. Profile-related actions (minimize destructive resets) Since deleting and recreating profiles temporarily fixes the taskbar and Settings issues, profile corruption is likely a symptom, not the root cause. After addressing server resource and RDS service health:

• For affected users, consider creating a fresh profile once, then monitor whether it corrupts again after some time.
• If corruption recurs, correlate the timing with:
  • Server uptime since last reboot.
  • RDS service uptime since last restart.
  • Installation or updates of non-Microsoft software.

8. Outlook error correlation The Outlook “Something went wrong. [4nsvw]” error on the same sessions that show taskbar/Settings failures suggests broader shell or profile issues rather than a standalone Outlook problem. After stabilizing RDS and profiles as above, re-test Outlook. If the error persists only for specific users, treat it as a profile-specific issue (new profile, new Outlook profile) after confirming server health.
9. When to escalate If, after:

• Verifying permissions and collections,
• Monitoring and addressing memory/session leaks,
• Restarting RDS instead of full server reboots,
• Removing or updating non-Microsoft software that hooks into RDP sessions,

the problem still recurs, collect detailed logs and performance data and open a support case so that the underlying leak or bug on Windows Server 2025 can be analyzed.

References:

• Troubleshooting access denied and user not authorized issues in Microsoft Remote Desktop Services
• "Remote Desktop Service is currently busy" message during RDP connections
• RDS session connectivity troubleshooting guidance
• Poor performance or application problems during remote desktop connection