Windows 10 Anniversary update and Displaylink

ashwinch · 01-12-2017, 05:53 AM

I didn't have issues after the Windows 10 Anniversary Update, but I had very similar annoying issues after a recent Windows update KB3213986. My notification tray wouldn't load instantly, pretty much every Windows settings window would not load unless I pressed the Show Desktop button twice, typing in any text field (browsers, File Explorer, etc.) would be very laggy, etc. etc. After a few stressful hours of troubleshooting (not even considering it may be related to DisplayLink) this is what resolved my issues a few minutes ago:

1. Download and manually install Windows Update KB3213986 from an elevated command prompt. Download link at http://www.catalog.update.microsoft....px?q=KB3213986
2. Reinstalled the latest driver for my graphics card (Nvidia GTX 970)
3. Installed DisplayLink 8.1M0 (I was previously on 7.7M4 without issues until today)

My issues went away immediately, and the resolution persisted after a restart. Hopefully this helps you!

01-12-2017, 05:53 AM	#2
ashwinch Junior Member Join Date: Jan 2017 Posts: 1	DisplayLink 8.1M0 and Windows Update KB3213986 (OS Build 14393.693) I didn't have issues after the Windows 10 Anniversary Update, but I had very similar annoying issues after a recent Windows update KB3213986. My notification tray wouldn't load instantly, pretty much every Windows settings window would not load unless I pressed the Show Desktop button twice, typing in any text field (browsers, File Explorer, etc.) would be very laggy, etc. etc. After a few stressful hours of troubleshooting (not even considering it may be related to DisplayLink) this is what resolved my issues a few minutes ago: 1. Download and manually install Windows Update KB3213986 from an elevated command prompt. Download link at http://www.catalog.update.microsoft....px?q=KB3213986 2. Reinstalled the latest driver for my graphics card (Nvidia GTX 970) 3. Installed DisplayLink 8.1M0 (I was previously on 7.7M4 without issues until today) My issues went away immediately, and the resolution persisted after a restart. Hopefully this helps you!