The Desktop Window Manager process has exited Process exit code: 0xc00001ad

Hello!

After windows update last weekend our user complains about freezing RDS sessions. After some investigation in the application logs on the RDS session host (windows 2016 server standard) i can see that the Windows Desktop Manager restarts for the users repeatedly. Sometimes as often as every 5 minutes.

The windows update wasKB4343884. I have tried rolling back, but the problem remains.

I have checked the version of the local dwmcore.dll and its10.0.14393.1715.

On the other servers that are patched the version is10.0.14393.2457

Its really annoying for the users, anyone had this problem? Any ideas what to do?

Keywords: dwmcore.dll dwm.exe windows server 2016 rds connection freeze flicker

Here is copy of application logs:

Log Name: Application
Source: Application Error
Date: 2018-09-13 08:27:22
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: XX
Description:
Faulting application name: dwm.exe, version: 10.0.14393.0, time stamp: 0x578999ab
Faulting module name: dwmcore.dll, version: 10.0.14393.1715, time stamp: 0x59b0d15f
Exception code: 0xc0000225
Fault offset: 0x0000000000045fec
Faulting process id: 0x2c50
Faulting application start time: 0x01d44b2a8598084b
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\system32\dwmcore.dll
Report Id: 609bd1cf-1c2e-4ad6-ba08-7f21f2a1786d
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-09-13T06:27:22.409448600Z" />
<EventRecordID>67809</EventRecordID>
<Channel>Application</Channel>
<Computer>XXXXX</Computer>
<Security />
</System>
<EventData>
<Data>dwm.exe</Data>
<Data>10.0.14393.0</Data>
<Data>578999ab</Data>
<Data>dwmcore.dll</Data>
<Data>10.0.14393.1715</Data>
<Data>59b0d15f</Data>
<Data>c0000225</Data>
<Data>0000000000045fec</Data>
<Data>2c50</Data>
<Data>01d44b2a8598084b</Data>
<Data>C:\Windows\system32\dwm.exe</Data>
<Data>C:\Windows\system32\dwmcore.dll</Data>
<Data>609bd1cf-1c2e-4ad6-ba08-7f21f2a1786d</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dwm.exe
P2: 10.0.14393.0
P3: 578999ab
P4: dwmcore.dll
P5: 10.0.14393.2273
P6: 5ae409d5
P7: c0000225
P8: 0000000000045fec
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_dwm.exe_4fd69b8d2b46a52b527b3b87e68145f26d420ac_e69b2600_1448af53

Analysis symbol:
Rechecking for solution: 0
Report Id: 802acf33-3a79-49d9-8475-4630a1686a75
Report Status: 4
Hashed bucket:

The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 1, Primary display device ID: RDPUDD Chained DD)

The Desktop Window Manager has registered the session port.

Hello Everyone,

We currently moved on of our Remote Applications from a Windows Server 2008 R2 to a new Windows Server 2016. Unfortunately, things dont seem to work as intended any more.

We have a Remote App, where Users can choose from different other Remote Servers and connect to them via rdp. So when the users chooses a certain server, it runs the command "start mstsc serverX.rdp" or "start mstsc serverY.rdp", which then lets the user connect to the specific server via the remote app.

However, sometimes when a Users wants to connect, the mstsc window does not pop up, instead the RemoteApp just loses focus and nothing happens. In the task manager i can see that there is a mstsc.exe for the user, but he is not able to see it or interact with it.

I hope someone can help us here.

Thanks in advance!

Regards,

Chris

All systems in lab environment running Windows Server 2012 R2 RTM Evaluation

Hello

I'm new to setting up and managing Remote Desktop Service infrastructure. I am having problems getting Domain Joined clients to connect to RDS hosted sessions with SSO (delegated credentials) when connecting through a RD Gateway.

I have set up the Delegate Credentials GPO, and SSO works fine with a direct connection to the Broker (no RD gateway)

However, when I try to establish a connection via an RD Gateway, I am always requested for one password. Either:

If the "Use my RD Gateway credentials for the remote computer" is selected, the RD Gateway credentials are passed automatically. However, I am prompted for the Broker credentials, even though the connection explicitly details that "Your Windows logon credentials will be used to connect" (GPO Setting)

If the "Use my RD Gateway credentials for the remote computer" is deselected, then I am prompted for the RD Gateway credentials. When the Gateway credentials are entered, the Broker credentials are then passed automatically, as expected via the explicit"Your Windows logon credentials will be used to connect" (GPO Setting)

Why can't I get both credentials not passed automatically? Is this by design?



------

These are the RDP file settings below, generated and downloaded from RD Web Access. With these settings, the Gateway credentials are being passed automatically but I am still explicitly being requested the BROKER credentials (though I shouldn't because of GPO delegation - it works when Gateway not being used). Any help would be very much appreciated! Thanks in advance!

Team,

Thanks in advance, I've configured RDS environment with session host, web access, connection broker and a RD gateway server.

I've enabled MFA calling through Azure MFA Server using the below link which Microsoft suggests. But I wanted MFA calling for external users and not when users coming from internal IPs.

In MFA console we have trusted IPs tab where we have to put in the users IP or IP range, but here as the authentication is sent by the RD gateway server everything is ignored by the MFA server and for internal users as well I'm getting MFA Calling.

Has anybody tried it before? This cannot be achieved through Azure MFA but can be achieved through NPS policies but unable to achieve it.

https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfaserver-nps-rdg

We are experiencing a RemoteApp default printer redirection issue in Windows Server 2016 that we are not seeing in Windows Server 2012R2. We have the following simple environment:

1. Windows Server 2012R2 with RDS Quick Start installed.
2. Windows Server 2016 with RDS Quick Start installed (configured identically)
3. Window 10 Client with attached HP printer configured as Default printer.

When we launch WordPad as a RemoteApp on the client (via RDWeb) and try to print a document, we see different behaviors: 1) When launched on Server 2012R2, the clients default printer (HP printer) is shown as the default printer (expected behavior), 2) When launched on Server 2016, the servers default printer (XPS Document) is shown as the default printer (unexpected behavior).

Weve verified that all of the Group policies and connection settings are correct and identical between the two servers. However we noticed the values ofHKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows:Device keys are different: 2012R shows redirection to client printer, 2016 shows server printer.

Is this a bug in Server 2016? Anything else we should check or configure?

Thanks,

cyorlano

Hi,

Connection to a RemoteApp program from within an RDP session does not work if the user has a startup program defined in the user profile.

I'm using Windows Server 2012 R2. I used calculator as the RemoteApp program to verify that it's not a problem in my custom program.

1st scenario - works:

1. Connect to the server using RDP (no RemoteApp) --> Desktop opens
2. From the RDP session, try to make an RDP connection using RemoteApp. I'm using a pre-configured RDP file with remoteapplicationmode and remoteapplicationprogram parameters and I'm connecting to the same server in this example --> The RemoteApp screen appears and after entering credentials the RemoteApp program opens

2nd scenario - does not work:

1. Using an admin account, on the server, go to local user management and set a startup program for the user that is used for the test, cmd.exe for example (Environment tab --> Starting program --> Start the following... --> Program file name ="cmd.exe").

2. Connect to server with the test user --> cmd.exe opens

3. Try to connect with RemoteApp like step 2 in the previous scenario --> the RemoteApp screen appear but the program does not start, after a while the session closes.

I checked using ProcMon and the Event Viewer and I see that a connection is established, but for some reason the program does not start (rdpinit.exe should start the program, but it doesn't - I don't see any call for CreateProcess).

Is this a bug in Windows?

Thanks,
Gabriel

I'm having an unusual issue and I'm not able to pinpoint where it is coming from.

We have a network with Hyper-V servers and VLAN tagged NIC cards on the servers and routing between them.

I am able to RDP directly to our second DC but not to our PDC.

If I ping DC1, I get a response.
If I ping DC1.domain, I get a response.
If I tracert DC1.domain, it follows the relevant route.
If I nslookup DC1.domain, it pulls the correct IP from the DC1 itself and DC2 if I specify it.

If I try RDP to DC1, connection times out.
If I try RDP to DC1.domain, connection times out.
If I try RDP to DC1.local, it connects fine.

Anyone know where to start my search for how to resolve this issue?

We are looking to move our current hosted solution to Azure.

Ourcurrent solution in the cloud consists ofthree Windows 2008 R2 VMs in a workgroup One SQL Server VM heavily dependent on SQL Database Mail and SQL Scheduled Jobs , One Web Server VM, One RDP server that uses RemoteApp to distribute a Windows Client application after connecting to a VPN. We also use the RDP server to run several windows applications (windows service and scheduled task). I had originally posted to the Azure VM forum and was referred to this forum for RDP issues.

With Windows 2008 R2 server I was easily able to create RemoteApp. .rdp files (without RDWeb)for our Windows application and use those .rdp files to distribute to our customers.The user accounts were created using Computer Management / Local Users / Groups.

From my understanding is that the functionality changed with Windows 2012 R2 and later.To be able to set up RemoteApp, the machine must be joined to a domain as this give you a setup UI to publish your application(RDWeb to create rdp file).This would mean two additional servers (domain controllers) and incur additional costs.The user accounts would then have to be created on the Azure DC Active directory. Is RemoteApp supported on a Windows 2016 workgroup VM in Azure without using RDWeb to publish the application?I found an article on the forum that talks about creating / editingyour own rdp file and registry entries in lieu of a UI.I also found a third party application (RemoteApp Tool) which creates a .rdp file.Could we use those methods and still be supported by Microsoft?I also see there was a RemoteApp Service on Azure that is been now discontinued.It has been replaced with Citrix Virtual App Essentials.From my understanding, this too would require domain controllers at additional cost.Are there any better solutions to achieve our goal? Will we be able to set up a VPN connection for our customers to the RDP (RemoteApp) server on Azure with any of the solutions?

Thanks,