Display link software causing TaskBar (Start,Cortana,edge) to crash

PaulJ · 08-20-2015, 12:34 PM

This is a bit of a guess at the moment and please don't rush into trying this until you're happy you can recover if this goes wrong - i.e. you may need to get into Windows to uninstall your DisplayLink software.

Can you try either deleting or, if Windows doesn't let you delete, renaming the dlumdfb*.dll files in c:\windows\system32? I would also do the ones in c:\windows\syswow64 if you have a 64bit OS installed. After that reboot and see what happens. As stated initially there is a chance this could break your DisplayLink installation so you may need to boot in safe mode or recovery mode to recover although I think the chances are slim.

If you feel like trying it please do and let us know how it goes.

robmc5 · 08-20-2015, 01:14 PM

Paul, I tried what you suggested. I did not have the Display Link drivers installed, I renamed both dlumdfb*.dll files and rebooted. I then installed the Display Link 7.9 Driver and rebooted again. After reboot Edge stopped working, along with the Start menu and all Modern UI applications.

When I run the applications this is the error that shows in the log when I try to run Edge -

Activation of app Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdg e failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Here is the Cortana error -

Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

I then uninstalled the DisplayLink software and rebooted and everything works fine.

PaulJ · 08-20-2015, 01:15 PM

Can you try the renaming again now you have the software installed?

robmc5 · 08-20-2015, 08:54 PM

Paul, thanksfor the suggestion.... I tried that, I actually deleted the files -

dlumdfb9.dll
dlumdfb10.dll
dlumdfb11.dll

Rebooted and tried calculator....same error.

Activation of app Microsoft.WindowsCalculator_8wekyb3d8bbwe!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

lokinz · 08-20-2015, 10:55 PM

Quote:

Originally Posted by robmc5

Paul, thanksfor the suggestion.... I tried that, I actually deleted the files -

dlumdfb9.dll
dlumdfb10.dll
dlumdfb11.dll

Rebooted and tried calculator....same error.

Activation of app Microsoft.WindowsCalculator_8wekyb3d8bbwe!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

Did you check to see if they are actually gone? After I restarted the dlls had been restored. I haven't had a chance to go any further with this yet as it's a work machine, and I have work to do

.

robmc5 · 08-21-2015, 12:06 PM

The .dll's were gone but as soon as I installed the Display Link drivers they were back.

PaulJ · 08-21-2015, 12:09 PM

I typed a reply to this thread but it seems to have been lost somehow.

Regardless, what you've seen with the deleted dlls returning is expected. We've done a bit more investigating here and it seems this is not the cause of this issue so I suggest there's no need to delete/rename these dlls to see if it helps.

More when we have it...

08-20-2015, 12:34 PM	#1
PaulJ Member Join Date: Jul 2010 Posts: 83	This is a bit of a guess at the moment and please don't rush into trying this until you're happy you can recover if this goes wrong - i.e. you may need to get into Windows to uninstall your DisplayLink software. Can you try either deleting or, if Windows doesn't let you delete, renaming the dlumdfb*.dll files in c:\windows\system32? I would also do the ones in c:\windows\syswow64 if you have a 64bit OS installed. After that reboot and see what happens. As stated initially there is a chance this could break your DisplayLink installation so you may need to boot in safe mode or recovery mode to recover although I think the chances are slim. If you feel like trying it please do and let us know how it goes.

08-20-2015, 01:14 PM	#2
robmc5 Junior Member Join Date: Aug 2015 Posts: 17	Paul, I tried what you suggested. I did not have the Display Link drivers installed, I renamed both dlumdfb.dll files and rebooted. I then installed the Display Link 7.9 Driver and rebooted again. After reboot Edge stopped working, along with the Start menu and all Modern UI applications. When I run the applications this is the error that shows in the log when I try to run Edge - Activation of app Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdg e failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information. Here is the Cortana error - Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.* I then uninstalled the DisplayLink software and rebooted and everything works fine.

08-20-2015, 01:15 PM	#3
PaulJ Member Join Date: Jul 2010 Posts: 83	Can you try the renaming again now you have the software installed?

08-20-2015, 08:54 PM	#4
robmc5 Junior Member Join Date: Aug 2015 Posts: 17	Paul, thanksfor the suggestion.... I tried that, I actually deleted the files - dlumdfb9.dll dlumdfb10.dll dlumdfb11.dll Rebooted and tried calculator....same error. Activation of app Microsoft.WindowsCalculator_8wekyb3d8bbwe!App failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.

08-21-2015, 12:06 PM	#6
robmc5 Junior Member Join Date: Aug 2015 Posts: 17	The .dll's were gone but as soon as I installed the Display Link drivers they were back.

08-21-2015, 12:09 PM	#7
PaulJ Member Join Date: Jul 2010 Posts: 83	I typed a reply to this thread but it seems to have been lost somehow. Regardless, what you've seen with the deleted dlls returning is expected. We've done a bit more investigating here and it seems this is not the cause of this issue so I suggest there's no need to delete/rename these dlls to see if it helps. More when we have it...