none
Windows Server 2012 R2 Start Menu Crashing

    Question

  • Hello,

    I have been looking in to an issue for the last few weeks with our 2012 R2 RDS environment. For a handfull of users, they are experiencing issues with their Start Menu after logging in. It is freezing completley and is unresponsive. This happens across all 3 of our host servers. Below is a list of fixes I have attempted to resolve this but the issue still persists after each attempt:

    • Logging users on to each host server
    • Tried logging users on to a Windows 7 desktop PC and then remoting from the PC on to the RDS
    • Keyboard shortcuts to bring up Start Menu (Ctrl+Esc and Windows+X)
    • Re-creating profile disks
    • Running SFC /Scannow, no corrupt files
    • Moving taskbar to the side, Start Menu button highlights when hovered over but does not function
    • Stopping and starting explorer.exe

    There is an error that appears in the Event Log when this happens where explorer.exe has crashed with a faulting module of windows.immersiveshell.serviceprovider.dll. I have tried replacing this dll with a good version from another 2012 R2 server but again the issue still persists. I can also confirm that the server is fully patched and up to date.

    I am rapidly running out of ideas to try and fix this issue so any help that anyone can offer would be great!

    Thursday, February 22, 2018 9:53 AM

All replies

  • Try to resolve this by updating servers and client with latest windows patches and increasing memory of server..

    Can you monitor what are processing high at that time in server and client?

    Thursday, February 22, 2018 12:28 PM
  • All servers are up to date with patches and currently have 12Gb of RAM for each host.

    Currently with 15 users on a host it is sitting at around 25% CPU usage and 65% Memory so they aren't exactly being taxed.

    The clients being used are just HP Thin Clients that authenticate against the domain but aren't domain joined although, as I said, the issue still persists when RDPing from a domain joined desktop PC.


    • Edited by James10100 Thursday, February 22, 2018 1:04 PM
    Thursday, February 22, 2018 1:04 PM
  • Which type of HP thin client are you using? We have been experiencing the same issue lately and it seems to be related to a specific model (T5550)

    Once the user logs on with this thin client explorer crashes on the immersiveshell dll and then their profile becomes unusable on any other computer or thin client and the only fix is creating a new user which then experiences the same issue again if it connects using this specific thin client.


    error information:

    Faulting application name: Explorer.EXE, version: 6.3.9600.18231, time stamp: 0x56b8c9f1
    Faulting module name: windows.immersiveshell.serviceprovider.dll, version: 6.3.9600.17415, time stamp: 0x54503ee6
    Exception code: 0x80270233
    Fault offset: 0x000000000000cf07
    Faulting process id: 0x2560
    Faulting application start time: 0x01d3ac7bee9305af
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\System32\windows.immersiveshell.serviceprovider.dll
    Report Id: 2d21fd8d-186f-11e8-824c-0050569648e8

    • Edited by bvanl Friday, February 23, 2018 9:07 AM
    Friday, February 23, 2018 8:38 AM
  • That error is the exact same one we are getting in Event Viewer.

    We are using HP T520 Thin Clients with the HP ThinPro OS installed on them. There was only around 3 users affected but that number is slowly creeping up and I'm pretty sure it is going to affect more and more people.

    We have been using RDS for around 2 years and this is the first the issue has appeared while using the same model of Thin Clients. We have a bit of a suspicion it might have been some patches applied in January, specifically the Meltdown or Spectre patches that have done it but not 100% certain. You would think more people would be posting about the issue though if those patches had caused the issue.

    Our error info:

    Faulting application name: Explorer.EXE, version: 6.3.9600.18231, time stamp: 0x56b8c9f
    Faulting module name: windows.immersiveshell.serviceprovider.dll, version: 6.3.9600.17415, time stamp: 0x54503ee6
    Exception code: 0x80270233
    Fault offset: 0x000000000000cf07
    Faulting process ID: 0x12a8
    Faulting application start time: 0x01d3ac7669ceedfe
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\System32\windows.immersiveshell.serviceprovider.dll
    Report ID: ab1d55ea-1869-11e8-8191-0050569933ec
    Faulting package full name:
    Faulting package-relative application ID:

    • Edited by James10100 Friday, February 23, 2018 11:55 AM
    Friday, February 23, 2018 9:43 AM
  • Hi James10100,

    We have exact the same issue as you described.  Hard to find solution. Only restart server will fix it in our case for first time login. As soon as user logged out, they can't login anymore. This is not the case for all users. Seems issue with latest installed updates. Not sure which one causes this issue. Still searching.

    Hopefully fix will come soon !!

    Monday, February 26, 2018 9:46 PM
  • Hi Ricarco,

    Thanks for your reply. Yes it hasn't been easy trying to find a way to fix it. We are in the same boat with a restart allowing it to work first time but after that, they won't work. It's a bit like being stuck between a rock and a hard place with an update causing it. Either we have a working start menu for users or we have vulnerability without an installed update which isn't really an option for us.

    I think our next step will be to try and raise a case with Microsoft.

    Tuesday, February 27, 2018 7:43 AM
  • Hi guys,

    Just want you to know that you are not alone with this issue.
    I have the same problem with 2 of about 25 users.
    I have tried restoring profiles and starting with a clean profile but the result is the same.
    Even managed to break a working server by trying too much.. :-)

    Please post updates if you resolve this!

    Edit: I run Windows 2012 (not R2)

    Thanks

    Martin


    • Edited by dkmart75 Tuesday, February 27, 2018 11:45 AM
    Tuesday, February 27, 2018 10:33 AM
  • Hello,

      I'm having the same issue using Win 2012 R2 RDS.

    Still unable to resolve it. Affects some users even after deleting their profile. I'm using HP ThinClients, too. But the problem persist even when logging from other clients.

    Must be some of the auto-updates installed lately: KB4074594 or KB4055001. I'll try to recover the server from a backup and let you know.

    Thanks for any information.

    Ondrej

    Tuesday, February 27, 2018 12:37 PM
  • Thanks Ondrej.

    If you could let us know the results of restoring before those patches that would be great. Glad I'm not the only person having the issue. Sometime tomorrow I will get a case raised with Microsoft, hopefully it is a known issue that has a fix being worked on.

    Tuesday, February 27, 2018 3:09 PM
  • I have the same issue, started a week ago. I tried creating new profiles and still the same. Affecting 2 people now. Never had issues before. Terminal Server 2012.  I have to restart the server, then all is working again.

    I hope that someone knows the answer how to fix this!!

    • Edited by worldsdream Tuesday, February 27, 2018 9:35 PM
    Tuesday, February 27, 2018 9:33 PM
  • Hi also have the same exact error, Same hp thin clients included....
    Wednesday, February 28, 2018 7:53 AM
  • Same problems also with HP HP EliteBook Folio 1040 G3. I think KB4074594 or KB4074597 are causing those issues.
    Wednesday, February 28, 2018 9:00 AM
  • Same issue after installing the latest windowsupdates on both terminal servers with hp T5550 thin clients
    • Edited by Bart Dewulf Wednesday, February 28, 2018 9:03 AM
    Wednesday, February 28, 2018 9:03 AM
  • The same problem here

    It happens also when I try to establish a connection from the localhost via RDP as the problematic user. After server reboot the first login often works but when the user disconects and connects again, the problem appeared again.

    OS: German
    Version. Server 2012 R2 std.
    Client: not sure but HP Thin Clients are involved

    Patchstatus of Server: fully patched

    Stephan

    Wednesday, February 28, 2018 9:05 AM
  • it might be useful to note that we've been experiencing this issue since late January/Early February

    • Edited by bvanl Wednesday, February 28, 2018 9:09 AM
    Wednesday, February 28, 2018 9:09 AM
  • We have noticed this problem since 20th February on a HP Server Windows 2012 with ThinClients not HP.

    There is no update available to correct this!

    Wednesday, February 28, 2018 10:14 AM
  • Hi Guys,

    I have the similar issue with Windows Server 2012 R2 which start mid February, I managed to resolve the issue by removing the following Windows updates.

    KB 4055001, KB 4074594 and KB 4054980. After the restart the user profile showed icons on the desktop and the taskbar was responsive.

    Give this a try it might resolve your problem as well.

    Thank you.

    • Proposed as answer by Ben Greeve Wednesday, February 28, 2018 2:34 PM
    • Marked as answer by James10100 Tuesday, March 13, 2018 8:32 AM
    • Unmarked as answer by James10100 Tuesday, June 12, 2018 12:23 PM
    Wednesday, February 28, 2018 11:13 AM
  • Hi Harold,

    Removing those KB did indeed fix this issue !

    Thanks for sharing this information.

    Best regards,

    Ricardo!

    Wednesday, February 28, 2018 11:26 AM
  • Hi Guys,

    I have the similar issue with Windows Server 2012 R2 which start mid February, I managed to resolve the issue by removing the following Windows updates.

    KB 4055001, KB 4074594 and KB 4054980. After the restart the user profile showed icons on the desktop and the taskbar was responsive.

    Give this a try it might resolve your problem as well.

    Thank you.

    I had the same problem, but i did not have KB4074594 installed. I de-installed the other two and it seems to be working. Thank you

    Wednesday, February 28, 2018 2:35 PM
  • I have the same issue, but I do not have any of these 3 updates installed.

    KB4074594 is planned to be installed, but not yet installed.

    Wednesday, February 28, 2018 3:15 PM
  • I only have the KB4074594 that was installed before the issue occured.  The other 2 are not installed. Will try to remove the KB4074594 
    Wednesday, February 28, 2018 4:51 PM
  • Hi all,

    I did the suggestion by Harold:

    I removed those 3 updates and restarted my server.

    Will reply to you all if that fixed the issue.

    Wednesday, February 28, 2018 7:03 PM
  • I have the same issue on an RDS server 2012 R2. 2 users have now had this issue. The user has no desktop, taskbar or start menu items. Running explorer from Task Manager. gives them access to the mapped drives. Restoring the user's profile doesn't fix it. However, I have got them working again by creating a new profile and restarting the server.

    I will try removing the security patch (KB4074594) this evening. But I'm not happy with this as a permanent fix.

    Wednesday, February 28, 2018 10:34 PM
  • Hi Guys,

    I have the similar issue with Windows Server 2012 R2 which start mid February, I managed to resolve the issue by removing the following Windows updates.

    KB 4055001, KB 4074594 and KB 4054980. After the restart the user profile showed icons on the desktop and the taskbar was responsive.

    Give this a try it might resolve your problem as well.

    Thank you.

    I have the same problem with Windows server 2012 (not R2) and none of the mencioned updates. Any idea which kb causes the problem in 2012?

    Thank You.

    Regards, 

    Abilio Rocha

    Wednesday, February 28, 2018 11:11 PM
  • I have just removed security patch (KB4074594) and restarted the server. This seems to have resolved the problem for now.
    Thursday, March 1, 2018 12:47 AM
  • Abilio, KB:s are different between 2012 and 2012R2.

    On these it was one digit down on all KB:s, ie. KB4055001 (R2) is 4055000 in Windows 2012 (Not R2).

    Check MS KB article and you will find wich OS it made for.

    /Martin

    Thursday, March 1, 2018 6:52 AM
  • Thanks Martin.

    I found the info online and removed the KB4055000. Today there wasn´t any problem .

    I hope that Microsoft will correct the problem.

    Regards,

    Abilio Rocha

    Thursday, March 1, 2018 12:22 PM
  • Removed only KB4074594 on all our 2012 R2 servers (and restarted). For now it seems to be working. Hope it keeps working fine now. 
    Thursday, March 1, 2018 1:23 PM
  • Same problem. KB4074594 (Server 2012R2) uninstall solved it.
    Thursday, March 1, 2018 2:23 PM
  • Hi, I uninstalled KB4074594 and KB4055001 and restarted. And it indeed fixed the problem for us now.

    Tuesday, March 6, 2018 10:37 AM
  • Thanks man, this fixed it for us :)
    Tuesday, March 6, 2018 12:46 PM
  • Hi Everyone,

    Thanks for the replies. I can see that removing those patches does resolve the problem. However, we are in the unfortunate position where removing the KB4055001 creates a vulnerability on our servers which we cannot have due to certian certification requirements so I believe we are stuck between a bit of a rock and a hard place =(

    I will leave this thread open for the next few days to see if there is any other way to fix the problem but if not I will mark Harold's response as the answer.

    Tuesday, March 6, 2018 2:48 PM
  • Hi Harold, how did you manage to delete the update? In the list of history of updates I see that the KB 4074594 update is installed but if I search in the list of installed updates I can't find it to delete it.
    Tuesday, March 20, 2018 9:04 AM
  • I also have this issue at another customer site , HP T5540 , mentioned KB updates are not installed there, but some days ago the KB4088876 and some office updates were installed.
    Tuesday, March 20, 2018 12:53 PM
  • Hi Robert,

    Please can you check for KB 4075212 and uninstall this update then test. There is an update that superseded the 4074594 update.

    Thank you.

    Tuesday, March 27, 2018 12:47 PM
  • I have the same issue on an RDS server 2012 R2. 2 users have now had this issue. The user has no desktop, taskbar or start menu items. Running explorer from Task Manager. gives them access to the mapped drives. Restoring the user's profile doesn't fix it. However, I have got them working again by creating a new profile and restarting the server.

    I will try removing the security patch (KB4074594) this evening. But I'm not happy with this as a permanent fix.

    Well, the issue has resurfaced and funnily enough, it started after the '2018-03 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4088876)'. This is getting ridiculous. Albert_TC has also experienced the exact same issue and has uninstalled this rollup.

    I'm now about to uninstall KB4088876 and monitor. I will give you an update on the next months Quality Rollup or after Microsoft has resolved this issue.





    Wednesday, March 28, 2018 10:20 AM
  • Hi Guys,

    I have the similar issue with Windows Server 2012 R2 which start mid February, I managed to resolve the issue by removing the following Windows updates.

    KB 4055001, KB 4074594 and KB 4054980. After the restart the user profile showed icons on the desktop and the taskbar was responsive.

    Give this a try it might resolve your problem as well.

    Thank you.

    Thanks this fixed it for me.
    I Also blocked KB4088876 from installing.

    Friday, March 30, 2018 8:32 AM
  • Hi Guys,

    This problem started with KB4074594. But after that 2 new updates started the problems again. I can confirm that uninstallation of kb4088876 and kb4088879 solves the issue again. No black screens anymore. But will there be a real solution by Microsoft? In this other Microsoft forum

    "taskbar-unresponsive-in-rdp-sessions-to-server-2012r2-server-farm"

    they are trying it with the new KB4088882

    Anyone?

    Friday, March 30, 2018 12:11 PM
  • Hi Guys

    i also have a client with exactly the same issue, they have two RDS windows 2012 R2 servers (both virtuals) and they have a mix of thin clients and desktops, the thin clients are various also, mainly VXL. 

    I noticed that this started after the January IMPORTANT quality rollups and has persisted into Feburary and March. If i remove that one particular update the issue goes away or as others have said, a reboot also fixes.

    i have logged this with Microsoft and they are currently working on it but have made no mention of anyone else having this issue so i am very glad to come across this post. it was after looking in the event log that i looked up the same error that a lot of you have and thats how i found this post. googling start menu errors etc brought me no joy.

    will keep you posted since i have logged this with microsoft (and hoping they will reverse the fee now)



    Tuesday, April 10, 2018 1:38 AM
  • Yesterday we had the user call us again about the problem.
    We found out that he is the only one working on a Windows CE 6.0 based Thin Client.

    We are going to replace it with a new thin client and then push all the updates again.
    Hope that will solve the problem as it did with the server 2016 issues with Windows CE 6.0.

    https://social.technet.microsoft.com/Forums/en-US/6b6d83a2-f0e8-4102-964a-596f50c23770/rds-2016-explorer-keeps-crashing-at-login?forum=winservergen

    • Proposed as answer by m0nkm0nk Wednesday, April 25, 2018 2:21 PM
    • Unproposed as answer by m0nkm0nk Wednesday, April 25, 2018 2:21 PM
    Wednesday, April 18, 2018 12:18 PM
  • Installing KB4093116 (2012) or KB4093121 (2012R2) should resolve the issue. It fixed it for me on several servers (2012 and 2012R2)

    Kind regards, Kees Alderliesten

    Friday, April 20, 2018 10:42 AM
  • Well i thought it was worth a try. i installed the kb4093121 for my clients Windows 2012R2 server but no go.

    Still have the Start Menu issue or task bar icons. i do still have microsoft working on this, they have set up a dump of the issue as the user logs in and picked one of these up on Friday so hopefully they come up with a resolution soon. it does seem to be just affecting the older thin clients.

    i havent had anyone on a pc report this issue as yet. but it seems that once a user has had the issue from an (older) thin client they will have it from wherever they logon. Users on newer thin clients and pc's dont have the issue at all.

    will keep you posted. 

    Sunday, April 22, 2018 11:32 PM
  • Well i thought it was worth a try. i installed the kb4093121 for my clients Windows 2012R2 server but no go.

    Still have the Start Menu issue or task bar icons. i do still have microsoft working on this, they have set up a dump of the issue as the user logs in and picked one of these up on Friday so hopefully they come up with a resolution soon. it does seem to be just affecting the older thin clients.

    i havent had anyone on a pc report this issue as yet. but it seems that once a user has had the issue from an (older) thin client they will have it from wherever they logon. Users on newer thin clients and pc's dont have the issue at all.

    will keep you posted. 

    That is correct, its the same thing we are seeing.
    We replaced a old thin client for a newer one, restarted the server and it appears to be working fine for now.

    Monday, April 23, 2018 7:45 AM
  • No, also with preview update KB4093121 installed users are getting the black screen. In application log error 1000 in module windows.immersiveshell.serviceprovider.dll
    Tuesday, April 24, 2018 12:34 PM
  • On the 2012R2 server the problem came back, installing KB4093121 didn't help (KB4093116  on the 2012 fixed it). After contacting microsoft they advised to uninstall 2 packages:

    DISM.exe /Online /Remove-Package /PackageName:Package_for_KB4088785~31bf3856ad364e35~amd64~~6.3.1.0

     

    DISM.exe /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~9600.18964.1.4

    So far so good....


    Kind regards, Kees Alderliesten

    Wednesday, April 25, 2018 2:26 PM
  • Hi,

    I have the same problem in my 2012R2 Serveur.

    The KB4093121 is installed but I don't have KB4074594 and KB4055001 so i can't uninstall them.

    The DISM.exe command don't match too. The serveurs have fully updated.

    How can I solve the problem ? My user impacted use HP T5550 too. The others users don't have probleme.

    Thanks for your repply.

    Regards;

    Wednesday, April 25, 2018 2:59 PM
  • Hi,

     I have the same problem again (also HP T5550, Win 2012 R2). I uninstalled KB4055001 and KB4093114 and after restart it is ok.

      I have only one T5550, so I'm going to replace HP T5550 with other computer. Because there is no hope for solution and it is unacceptable to remove security updates once they are installed.

    Sincerely Ondrej


    Friday, April 27, 2018 1:41 PM
  • Interesting, but cannot remove the mentioned updates on 2012 and 2012r2 since we installed an rollup afterwards :( And indeed, this happend since installing the Specte/Meltdown patch.
    Only sessions from the HP Thin clients. windows.immersiveshell.serviceprovider.dll

    No any sign of Microsoft fixing this.

    Wednesday, May 2, 2018 2:07 PM
  • So this is still a problem for me. After removing various KB's and reboots. Lucky that it's only affecting 3 users. But I have found a common ground to these users, they are all located in the same office sharing an HP T5550 Thin Client. I will be changing their Thin Client to a later model. However, the only way to resolve the problem is to restart the RDS 2012 R2 server.

    Will update this post once I confirm if changing the Thin Client removes the problem.

    Monday, May 7, 2018 3:00 AM
  • I'm having the same issue with a client.. seems updating the thin client made things a bit better but it still happens every now and then.. anyone can confirm if replacing the thin clients has solved their issues?

    crash_pr A+ N+ S+ MCP MCTS MCITP:SA

    Monday, May 14, 2018 2:02 PM
  • Hi Guys

    There is still no fix. I am still in conversation with Microsoft to fix this (paid for) so it will be fixed (hopefully). They are aware that it is still an issue. My client that has this issue has two RDS 2012 R2 servers and i am only applying the Monthly Roll up on one of them as that is most definately what is causing the issue. obviously as others have said, uninstalling that kb fixes the issue but it is a workaround only at this stage.

    Will keep you posted once Microsoft have produced a fix. Remember though this is the Quality Monthly Rollup that comes out about every 2nd Tuesday of the month and it is the RECOMMENDED one not the OPTIONAL that is causing the problem with certain Thin Clients (my client has mainly TermTeks).

    Please also note that i have several other clients running with RDS 2012 R2 servers and thin clients that DO NOT have this issue. So there is something in the mix there that is causing it to certain environments.

    Monday, May 14, 2018 10:16 PM
  • I'm also in conversation with Microsoft (paid). maybe the could join forces, my case number is  REG:118042418060122

    Kind regards, Kees Alderliesten

    Tuesday, May 15, 2018 9:21 AM
  • Hi,

     I'm looking forward to hearing from you soon. Problem still persists. I've got also strange behavior (problems with taskbar - user unable to switch appliactions) on other thin client, which started happening few weeks ago. And is also recurring after installation of latest roll-up.

    That one is Windows Embedded Standard 7 HP Thin Client. So it seems the problems are not limited only to HP5550 with Windows CE.

     Sincerely

    Ondrej Gratz


    Tuesday, May 15, 2018 5:41 PM
  • Microsoft needs to put up a KB with a guidance on what patches caused this so that at least we can uninstall them.. I have uninstall a few but still no go.

    So far the steps to reproduce for us is:

    1) Login to RDS with the thin client

    2) Log off

    3) Logon again to RDS with the thin client now the session is a black desktop(no icons) and the unresponsive start menu, if you right click the desktop you will see the icons.

    But there is some timing involved, resource utilization or number of connected users because it does not happen immediately after rebooting the server.

    I will seek to also open a case.


    crash_pr A+ N+ S+ MCP MCTS MCITP:SA

    Wednesday, May 16, 2018 4:05 PM
  • I do also have a case open by Microsoft about this issue. Our case number: REG:118043018096318.

    We are currently investigating if the issue can be related to 3rd party software that is embedded into the Explorer.exe. As soon as we know more we will post an update.


    • Edited by rdzegers Thursday, May 17, 2018 8:55 AM
    Thursday, May 17, 2018 8:54 AM
  • My case number is: REG:118040317923936. what is the 3rd party software you guys are using? my client uses DisplayFusion, mind you we had tried disabling but not uninstalling to see if that was the issue. mind you they have been running it for 2 years and the issue only appeared after the January Monthly Quality Update.

    DF is for the use of multiple monitors. they had been using splitview on 2008 RDS but it didnt work very well on 2012 R2, hence the change over to DF.

    Thursday, May 17, 2018 8:45 PM
  • Hello,

     crash_pr: could you share with us what kind of clients are you using (model and operating system) ?

    I'm trying to figure out what do we have in common with all the people having the same problems.

      Regarding the 3rd party software that could interfere with Explorer.exe: we do have a Vipre Business Premium Antivirus running. But I'm not going to uninstall it to test if this is causing problems. I'm sorry I don't have test environment available. But we too have been using same system for around 2 years without any problems until some of the KBs installed in the end of January (no other software was installed, no other changes).

    Sincerely

    Ondrej

    Friday, May 18, 2018 7:09 AM
  • The client is using HP t5540 with Windows CE 6.0.

    This problem seems to have started some time between February or March, other than updates, software was not changed or installed at the time.


    crash_pr A+ N+ S+ MCP MCTS MCITP:SA

    Monday, May 21, 2018 5:43 PM
  • Same problem here.

    After updating our servers some users start to have this problem (5 out of 35).

    When on a black screen (with only the start logo on the left bottom) pressing F5 shows the desktop items.
    Restarting a virtual server and let the user log in again, solves the problem (temporarily?). On next login, the error might re-occur.

    This problem isn't 100% user specific. Today a 5th users started to experience this problem.

    We have three virtual servers where the users log on to (2012 R2).

    We are on HP T510/T520 thin clients and some intel NUC with W10.

    Tuesday, May 22, 2018 10:55 AM
  • Are the users with W10 NUC having issues too?
    Tuesday, May 22, 2018 11:43 AM
  • Here we are June 4th and still no answer?

    I have an open case with Microsoft REG:118043018097983 and they are having us jump through hoops trying to isolate the issue with their RDSTRacing tool, but it's not really helping. They want us to reproduce the error after running the tool, then reboot, well, with a reboot, the issue may be resolved for that user.

    Same issues as everyone else in the thread. Black screen with a white cursor. Can right click on the desktop and refresh to get icons, but the client's application will not work without a reboot of the server.

    Out of the 30 Remote desktop users, only 4-6 users will have the issue and the only thing to fix it is to reboot the servers.

    After the reboot, the users that were having problems will work fine and it may be another user that has never had the issue before.

    This is getting ridiculous. Looks like a big problem that multiple people are having.

    How long is it going to take for a fix???

    Tuesday, June 5, 2018 2:23 AM
  • Hello,
    We have the same problem. Multiple users remain stuck with the start menu that is crashed. The only way for these users to reconnect is to reboot the server. The seveur is an HP Proliant G7 on Windows 2012 R2 full patched and the clients are HP terminals. It's very disturbing.

    Tuesday, June 5, 2018 4:12 AM
  • We bought new HP T530 W10 IoT Thin Clients, removed the patches and the problem still happens...

    Microsoft is just pathetic when it comes to fixing their issues... Odly enough the problem seems to happen every 3 to 4 days after the reboot.



    • Edited by rickesp Tuesday, June 5, 2018 4:09 PM edit
    Tuesday, June 5, 2018 4:06 PM
  • Hello everybody,

    I have the exact same issue, but because I skiped all 3 updates (KB 4055001, KB 4054980 and KB 4074594) I have no option to uninstall it. The same issue must be included in the MAY update. 

    Wednesday, June 6, 2018 12:33 PM
  • We ran into this issue as well on one of our customer's RDS servers.  Same Explorer.exe crash, which led to the RDS session desktop being unresponsive.  Our customer normally used the RDS servers with a couple RemoteApps, which exhibited the problem slightly differently.  With a RemoteApp, the app simply doesn't load and the session can get stuck in various 'startup' states.  It is also possible the Explorer.exe crash error doesn't get logged the same as with a full remote desktop, as I only started to see the explorer.exe crash errors when I was trying to log into a full remote desktop.  I didn't have a lot of time to play around with the user account that was getting this error prior to rebooting the server, so I'm not 100% sure this is the case.

    In any event, a reboot of the server returned the failing user account back to normal ... for now.  Our servers are fully patched (with the May 2018 updates).  Hopefully Microsoft can fix this soon ...

    Thursday, June 7, 2018 5:58 PM
  • Hello,

       I'd like to ask everybody having the same issue: are your Remote Desktop Servers virtualized ?

    We're using ESXi 6.0 Patch 4. 

        I still don't know what to do. According to the posts here, the issue doesn't seem to be caused directly by specific client OS, client hardware or specific Windows update. 

    Sincerely

    Ondrej

    Monday, June 11, 2018 6:50 AM
  • Hello,

       I'd like to ask everybody having the same issue: are your Remote Desktop Servers virtualized ?

    We're using ESXi 6.0 Patch 4. 

        I still don't know what to do. According to the posts here, the issue doesn't seem to be caused directly by specific client OS, client hardware or specific Windows update. 

    Sincerely

    Ondrej


    Our customer's RDS servers are hosted by Amazon (AWS EC2), so they are virtual, but not exactly sure what underlying virtualization software/architecture they use.
    Tuesday, June 12, 2018 1:40 AM
  • Hi Ondrej

    my client that has the issue has 2 RDS 2012 r2 servers, both virtual running on a Windows 2012 R2 HyperV server. It is a HP DL server. this issue has been happening since January for my client and it is always the monthly quality rollup that causes it. as my client has 2 servers that are pretty much identical, i have not applied this update to one of them since march whilst we wait for Microsoft to resolve this (I have paid to have this resolved along with a few others in this post!). my client runs mainly thin clients and they have 3 or 4 different brands, ie hp, termtek and it is the older ones that have the issue, it is affecting about 8 users out of 30. there are a couple with desktops, they dont have the issue.

    otherwise the servers are all fully patched and run Symantec Endpoint v14 (latest MP)

    cheers

    Emily

    Tuesday, June 12, 2018 1:45 AM
  • Hi Ondrej, 

    my server is physical HP DL 380 Gen8 and as I wrote, I skipped the February updates directly to MAY and the problem is there as well.

    So, Microsoft must add the same wrong KB in to the MAY's updates.

    Regards, 

    Stan

    Tuesday, June 12, 2018 5:55 AM
  • Hello guys,

       thanks for the information. I was hoping that there was some glitch in ESXi that could be causing it, but your information rules this out... This doesn't seem to be hardware or virtualization platform related (we're using Dell R430 server).

       I've had this problem again yesterday, and did not have May Rollup or any other mentioned KBs installed.

    Restart of the server fixed it. 

       I keep affected users logged-in. And only disconnect RDP sessions. Because I've found out that when the user logs out, the problem usually occurs again.

    Sincerely

    Ondrej

    Tuesday, June 12, 2018 7:38 AM
  • All of our hosts are virtual machines on ESXi 5.5 at the moment. I still have the issue since I first posted about the issue. I have a call open with Microsoft about the issue but all I seem to be doing is jumping through hoops with them rather than getting to the cause of the issue.

    Very frustrating, doesn't look like the end is in sight for this issue.


    • Edited by James10100 Tuesday, June 12, 2018 7:44 AM
    Tuesday, June 12, 2018 7:43 AM
  • ESX 5.5 over here but I dont think virtualization is the cause..

    I created a custom view every time the problem happens this is on the events..

    Log Name:      Application
    Source:        Application Error
    Date:          6/5/2018 9:59:09 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     TS01
    Description:
    Faulting application name: Explorer.EXE, version: 6.3.9600.18231, time stamp: 0x56b8c9f1
    Faulting module name: windows.immersiveshell.serviceprovider.dll, version: 6.3.9600.17415, time stamp: 0x54503ee6
    Exception code: 0x80270233
    Fault offset: 0x000000000000cf07
    Faulting process id: 0x5a50
    Faulting application start time: 0x01d3fcd55f730ec0
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\System32\windows.immersiveshell.serviceprovider.dll
    Report Id: 9d9fb3fb-68c8-11e8-8197-000c290810c2
    Faulting package full name: 
    Faulting package-relative application ID: 
    Tuesday, June 12, 2018 10:59 AM
  • Hi Ondrej, 

    my server is physical HP DL 380 Gen8 and as I wrote, I skipped the February updates directly to MAY and the problem is there as well.

    So, Microsoft must add the same wrong KB in to the MAY's updates.

    Regards, 

    Stan


    The Monthly Rollup Updates are now cumulative, so the May update will contain all of the fixes from the previously monthly updates.  This new update model started some time ago (don't recall when).  So skipping the February updates won't help here, as installing the May updates will also install the April, March, February, and earlier updates.
    Tuesday, June 12, 2018 1:31 PM
  • yes that is part of it. i noticed that in the event log from the very beginning and reported that to microsoft. so they are aware of that error. has to be a virtualisation issue as it is only affecting thin clients.

    microsoft had be invoke a bsod so they could take the memory dump last week. still waiting to hear back on that. they have had it about 5 days now.

    cheers emily

    Tuesday, June 12, 2018 9:58 PM
  • as i have stated already, it is the monthly cumulative QUALITY rollup update (not the optional) and started in January (yep thats how long this has been happening). each month i uninstalled it and it fixed it so since March i have only been installing it on ONE RDS server so microsoft can try and fix it!!!!!

    cheers emily

    Tuesday, June 12, 2018 10:00 PM
  • Emily would you know and share what are the KB Numbers for the "Quality" rollups?

    Im about to start yanking them out..

    Thanks

    Tuesday, June 12, 2018 10:05 PM
  • January - kb4057401

    February - kb4074594

    March - kb4088876

    April - kb4093114

    May - kb4103725

    June - kb4284815 (arrived overnight and havent applied yet)

    they always look like this:

    2018-XX (for the month)-Security Monthly Rollup for Windows Server 2012 R2 (or whatever version your server is) for x64 based systems. so should be easy to find.

    When i look on the server that i have continued to patch they are all showing there under Review your update history.

    cheers emily

    Tuesday, June 12, 2018 10:23 PM
  • Hi all,

    We have a situation with 6 RDS servers with exactly the same problems as described and also in contact with Microsoft for a solution. The last thing they told us is to add/change the login script with the following commands:


    Echo Off
    c:\windows\system32\rundll32.exe shell32.dll,Options_RunDLL 7
    TaskKill /f /im explorer.exe
    start explorer.exe


    This could be a workaround, but seems dangerous for the fact that it will kill all explorer.exe instances, also including the ones from the already logged on users which can work on the server?

    With this information, we tried to contact our account manager of Microsoft in Holland. He told us that we received a script to solve it (the one above). When I told him that this is no solution, but a workaround, he told me that the Support Professional from Microsoft handling the case was been told that providing a workaround was good enough. I was astonished: How can this be a solution?

    Right now we have a situation with 5 RDS servers running on the patchlevel of Januari and 1 RDS server running on the patchlevel of May, which we will upgrade to the patchlevel of June.

    1 thing which I cannot find in this thread (and which we haven't tested yet too): Is there someone with this issue who tried to install the Security-Only updates instead of the Security-Monthly updates? Everywhere I see the KB numbers of the Security-Monthly updates, which also contain other fixes, compared to the Security-Only updates.

    What will happen if we take a RDS server with the patchlevel of Januari and install the Security-Only update of May (KB4103715 ) or June (KB4284878)?


    • Edited by DLA82 Wednesday, June 13, 2018 11:38 AM
    • Proposed as answer by vve2 Wednesday, June 20, 2018 8:59 AM
    • Unproposed as answer by vve2 Wednesday, June 20, 2018 8:59 AM
    Wednesday, June 13, 2018 11:37 AM
  • We have the same issues with hp T510 and RDS 2016.

    We have remove (printer, clipboard and sound) on the local ressource tab. (Setting rdp connection)

    After this change, no more issues.


    • Edited by vve2 Wednesday, June 20, 2018 9:03 AM
    • Proposed as answer by vve2 Wednesday, June 20, 2018 9:18 AM
    Wednesday, June 20, 2018 9:02 AM
  • That is not a solution/answer but a workaround. What if you need the local printer, clipboard or sound?

    Kind regards, Kees Alderliesten

    Wednesday, June 20, 2018 9:21 AM
  • We have the same issues with hp T510 and RDS 2016.

    We have remove (printer, clipboard and sound) on the local ressource tab. (Setting rdp connection)

    After this change, no more issues.


    Not True... we have done this and the problem still happens!! Just a matter of time and it will rear its head again..
    Wednesday, June 20, 2018 10:50 AM
  • Hi,

    I have same issue, lot of thin client on my system.

    I removed last all updates, checked system file with sfc, no matter.

    shame on microsoft why not solved this problem ?

    Thursday, June 28, 2018 9:21 AM
  • So I finally have a response from Microsoft after jumping through the hoops from their support.

    "The issue that you are experiencing is an ongoing issue on Server 2012 R2 and is under investigation by our internal team. The issues that you have shared has similar symptoms that we noticed on other cases. For now we do not have an ETA on investigations and for the further steps. We will archive the case for now as it is pending from our internal team. Once we have any information on this issue we will get back to you on this and will keep you posted regarding further developments on the case."

    At least we know now it is being looked at but no ETA on a fix. Any update I get from Microsoft I will post in this forum.


    • Edited by James10100 Monday, July 2, 2018 2:28 PM
    Monday, July 2, 2018 2:27 PM
  • Hi All,

    same issue:

    2012 R2 Standard,
    different older HP thin clients, ...
    Disabling security updates is also not an option for us.


    Monday, July 9, 2018 11:27 AM
  • Has anybody been able to replicate these issues on a new HP t530?

    Or any HP Thin Client running either Windows 7 Embedded or Windows 10 IoT?

    I've tried logging in/out for roughly 30 minutes but i can't make it happen.

    On an older HP TC running Windows CE it seems to be a lot easier...
    • Edited by Pretesh Thursday, July 12, 2018 3:48 AM
    Thursday, July 12, 2018 3:12 AM
  • So I finally have a response from Microsoft after jumping through the hoops from their support.

    "The issue that you are experiencing is an ongoing issue on Server 2012 R2 and is under investigation by our internal team. The issues that you have shared has similar symptoms that we noticed on other cases. For now we do not have an ETA on investigations and for the further steps. We will archive the case for now as it is pending from our internal team. Once we have any information on this issue we will get back to you on this and will keep you posted regarding further developments on the case."

    At least we know now it is being looked at but no ETA on a fix. Any update I get from Microsoft I will post in this forum.


    Hi James,

    Can you tell us which case number you have with Microsoft? They don't want to acknowledge the problems we have, so if we can reference to your case number, maybe they can connect them and increase the urgency to solve it.

    Wednesday, July 18, 2018 2:45 PM
  • Our case number is 180711005001458. They only acknowledged the problem when I sent an email to them ranting about their attempted fixes and how I knew it was a problem with a patch. I sent them the link to this tech net article and a technical lead replied with what I posted.

    Hopefully you can get the same done if you link it to my case number.

    
    Thursday, July 19, 2018 12:14 PM
  • Has anybody been able to replicate these issues on a new HP t530?

    Or any HP Thin Client running either Windows 7 Embedded or Windows 10 IoT?

    I've tried logging in/out for roughly 30 minutes but i can't make it happen.

    On an older HP TC running Windows CE it seems to be a lot easier...

    Hi,

       I don't know the steps to reproduce it. I think it happens every time new updates get installed automatically. On the same server, HP t620 with Windows Embedded Standard 8 are affected too. When it happens, user is unable to switch applications via taskbar or Alt+Tab. The only way is to minimize the applications...

    Sincerely

    Ondrej


    Friday, July 27, 2018 8:56 AM
  • Has anybody been able to replicate these issues on a new HP t530?

    Or any HP Thin Client running either Windows 7 Embedded or Windows 10 IoT?

    I've tried logging in/out for roughly 30 minutes but i can't make it happen.

    On an older HP TC running Windows CE it seems to be a lot easier...

    Hi,

       I don't know the steps to reproduce it. I think it happens every time new updates get installed automatically. On the same server, HP t620 with Windows Embedded Standard 8 are affected too. When it happens, user is unable to switch applications via taskbar or Alt+Tab. The only way is to minimize the applications...

    Sincerely

    Ondrej


    I'm able to replicate the problem on an older HP thin client running CE simply by signing in/out multiple times.

    I haven't been able to replicate the problem on Windows 7 Embedded, however. 

    Whenever this happens for our users they are always able to switch using Alt+Tab.


    • Edited by Pretesh Wednesday, August 8, 2018 10:23 PM
    Wednesday, August 8, 2018 10:23 PM
  • Has anyone gotten any further information from Microsoft on this issue?  This issue continues to occur for some of our customers and the only resolution we have found is to reboot the RDS server.
    Wednesday, September 5, 2018 1:38 PM
  • Any updates here?

    We have HP T610 and T620's corrupting the user profiles on a RDS 2016.
    We even have to create a new AD user to "fix" the issue :(

    Testing now with same thin clients and updating remote desktop version...

    Monday, September 24, 2018 12:39 PM
  • I installed a fresh 2012R2 server. Installed all updates. Problem is here. I can’t find any windows update KB’e to uninstall that are mentioned in this topic. Please fix this or let me know which KB I have to remove
    Monday, September 24, 2018 6:05 PM
  • I still have no reslution of the ticket I have logged with Microsoft. It has been archived so I don't think I'll get any further information about it until it is fixed in a patch.

    All I can suggest is that you create an incident with Microsoft and try to get it linked to the ticket number that I posted earlier in this thread.

    Tuesday, October 9, 2018 12:24 PM