After update to Win 10 build 10586.164 drivers not compatible

[ginit]

Hi,

windows update update my laptop to Win 10 build 10586.164 and now my displaylink usb 2 hdmi does not work, I have installed the latest drivers but still shows the error "driver is not compatible with your version of windows"

Also, I have disabled the Nvidia graphic card of my dual graphic card.

What can I do

[AlbanRampon]

Hello,

I can see several reasons for that.
It could be, for instance, that your graphics card doesn't meet the Windows 10 requirements.
Or it could be that what is installed on your machine is an old version.
Would you please look at my forum signature to generate the logs files so I can see what is the most likely reason and advise on something to try?

Kind regards,
Alban

[Rheco]

Hi,

I have had exactly the same issue this morning.

I previously bought the doc about 3 months ago and used the disc to install the drivers. Everything worked perfectly and I was incredibly happy with it.

Last night, after work my laptop decided to run windows update, which is quite normal with Windows 10! I then shut it down and left it for the night. This morning, I power on my laptop to find an Ethernet connection, but absolutely no display coming from my connection.

I have tried EVERYTHING. I tried the clean install with the tool. I tried VARYING combinations of the Windows software for Display Link - of which mainly only M0 worked. For some reason, It said I had the wrong type of OS when attempting to install M3, M2 etc.?

I even tried completely uninstalling my USB drivers and getting a fresh install on windows restart to see if it was a Windows 10 USB driver update that caused an issue - still with no joy.

Either way, I have attached my logs in MASSIVE hope there is something I have missed, because I quite simply need my additional monitors for my work.

Many Thanks

[AlbanRampon]

Hi Rheco,

I'm a bit puzzled by the report of the versions not being working on your computer. Would you have a screenshot of the error message so I can see the exact wording against our code base.

The current status of your machine cannot work. I'll start with why, and then will go on to suggest how to recover.

1. What's going on
You have the peripheral driver files from 7.9 M5. That's normal as Microsoft made 7.9 M5 Critical on Windows Update.
However, for unknown reasons, the software you use has both 7.9 M0 and 7.9 M5 libraries. We've changed a few things between these and they cannot talk to each other. So no pixel sent to the dock.
NVidia changed the way their drivers work in October and we need to work hand in hand with them. Therefore you cannot use 7.9 M0 with an NVidia driver from October 2015 onwards.

2. Yeah, but how do I fix this mess?
- The first step is to disconnect your Targus dock and keep it disconnected until specified.
- Use Add/Remove programme to remove DisplayLink drivers
- Use the End User Cleaner
- Reboot. This step is necessary as Windows doesn't touch graphics drivers when running.
- Download 7.9 M5, and just not to have Windows Update interfering, cut all network connections. It's probably not necessary... but Windows should have done the job right the first time, and it does, otherwise Microsoft would not have put the update as Critical (they use installation success).
- Install 7.9 M5 and, only when asked, connect your Targus docking station.
- Wait for the drivers to be associated
- Reboot once again, for the same reasons.
- Do you have pixels now? If you don't may you please send me a new set of logs so I can see what's new?

Many thanks,
Alban

[Rheco]

Hi arampon,

I have attached the screenshot with the error message I received.

Because of the stated issue with the 7.9 M5 installation issues, I am unable to try your solution sadly.

Additionally, you mention:

'- Do you have pixels now? If you don't may you please send me a new set of logs so I can see what's new?'

I never had issues with pixels, the issue I have is that my monitors, which are connected to my Dock with an HDMI cable and DVI cable are bot picked up, but my ethernet connection from my docking station to my laptop is.

Hope all of this helps a bit more? and thank you for the information.

I am looking forward to your response.

[AlbanRampon]

Would you please be able to right click on the .exe, go to details, and then tell me what the "File version" field says?

I don't see why it talks about "upgrades" when you have used the cleaner to remove the current installation. And it looks different than what I am expecting.

[AlbanRampon]

I forgot to mention that your only graphics card working is an nvidia.
You can see that in system_details.txt
Graphics: NVIDIA GeForce GTX 980M (NVIDIA)
Graphics Driver: 10.18.13.6200 Dated 2016/02/23

I don't see any other graphics card in the Device Manager (DevManView.html) but the nvidia is connected and not disabled.

[Rheco]

Hey,

It actually gives exactly the same error message on both types of installation. If I try to fresh install and or if I try to upgrade from one of the versions that actually installs.

I am not quite sure what your other post means? I understand that the only Video Card I have is the Nvidia one, should this make any difference?

The requested information is:

File Version: 7.9.1505.0

[AlbanRampon]

The initial post it was written "Also, I have disabled the Nvidia graphic card of my dual graphic card." and "the graphics don't work".
You said I have exactly the same... So I assumed you had the same all the way.

Pixels are displayed on a monitor. Do you have pixels displayed or you don't? Would you please be able to reformulate your sentence explaining what works and what doesn't?

I don't believe the issue is with our installer. That driver is available from Windows 10 Windows Update as a Critical update. For Microsoft to decide to put a driver as critical, it must first pass a certain number of successful installation with a max number of failures allowed.
Of course, we also run that installer in our offices and during tests... And you'll see many people running it.

On top of this your setupapi.dev.log shows it is installing 7.9.1488.0 (which is the driver within 7.9.1505.0 installer) on Section start 2016/03/10 12:56:05.216... So I'm a wee bit puzzled.

That leads me to believe the issue is local.
I would like to suggest you check the executable is not ran in a compatibility mode. That your hard drive is not corrupted as it could corrupt the installer file you download.
You could also try downloading the installer with another browser or try on another Windows 10 machine to make sure your local security software didn't unilaterally decide to block stuff.

I'll talk with colleagues tomorrow. Everyone is home at that time here!

[Rheco]

The initial post it was written "Also, I have disabled the Nvidia graphic card of my dual graphic card." and "the graphics don't work".
You said I have exactly the same... So I assumed you had the same all the way.

Pixels are displayed on a monitor. Do you have pixels displayed or you don't? Would you please be able to reformulate your sentence explaining what works and what doesn't?

My apologies, let me re-state the issue.

I have two monitors connected to my Docking Station. They are connected with a HDMI cable and a DVI cable. Also connected to my doc is the power cord, an Ethernet Cable and the USB Cable that connects to my laptop.

When the USB cable is connected, normally I would receive a LAN connection AND both the displays extended to my two monitors. But AFTER the Windows update, the two monitors are no longer receiving a signal. They are quite simply Black (no signal). They are Black because after a period of time without any signal them, they return to a hibernation state. But as soon as they receive a signal again, the pick it up and display it.

So as you can see, LAN works, but Display does not.

I don't believe the issue is with our installer. That driver is available from Windows 10 Windows Update as a Critical update. For Microsoft to decide to put a driver as critical, it must first pass a certain number of successful installation with a max number of failures allowed.
Of course, we also run that installer in our offices and during tests... And you'll see many people running it.

I never had any assumption it was local or not, was your installer or not. All I would like to know is IF I am able to resolve it with your help :) I never stated that my faith in Microsofts roll out process was bad or your internal checks, I quite simply state that it does not work and it does not work after the last Windows update as stated above. There were no other changes in the 3 days approaching that update.

On top of this your setupapi.dev.log shows it is installing 7.9.1488.0 (which is the driver within 7.9.1505.0 installer) on Section start 2016/03/10 12:56:05.216... So I'm a wee bit puzzled.

I am also puzzled, sadly. As I have NO idea what you are referring to, would you please explain this a bit more?

That leads me to believe the issue is local.
I would like to suggest you check the executable is not ran in a compatibility mode. That your hard drive is not corrupted as it could corrupt the installer file you download.
You could also try downloading the installer with another browser or try on another Windows 10 machine to make sure your local security software didn't unilaterally decide to block stuff.


I would agree that it is quite probably local. Although I have done the above, the one thing I have not done is use a different browser to download. I shall attempt that again this morning and come back to you.

Thanks

[AlbanRampon]

Hi Rheco,

Could you please try the following in a command line and tell me what is the result:
cmd /c ver
cmd /c ver | findstr "6.1 6.2 6.3 10.0"

After this, please try:
1- Disconnect your dock
2- Run the End User Cleaner with Run as Administrator.
3- Connect the dock and wait. It should download the drivers from Windows Update. Is it installing this way?

I don't see any rule failing in the DisplayLink logs, so I looked at the Installer logs. The file is called setupapi.dev.log. In it, you can see line 466 that the installation proceeds with version 7.9.1488.0. This is 7.9 M5, the same version you get the error message from!

On another side, what is surprising me is that this installer says "Upgrade" in your screenshot. If you ran the End User Cleaner, there should be nothing to upgrade from as there is no DisplayLink driver.
Are you executing the End User Cleaner as an admin. This is important to Run as administrator as even an admin launching the command will NOT launch it as admin by default.

On a third front. There is a Windows utility called System File Check (SFC). This allows to look at the Windows installation itself and it checks for corruption.
You can execute it in an elevated command prompte with sfc /scannow. Does it give you anything? Unfortunately, not finding something doesn't mean everything is good. Also, it sometimes tries to correct things and this is not always enough...

[Rheco]

Morning!

The first command comes back with - Microsoft Windows [Version 10.0.10586].

The second command comes back with exactly the same as above, maybe I am doing something wrong here, I typed it out exactly as you put it.

I tried as you suggest to try and get Windows to push the installation - nothing sadly. I followed your steps exactly quite a few times, just to be sure.

On another side, what is surprising me is that this installer says "Upgrade" in your screenshot. If you ran the End User Cleaner, there should be nothing to upgrade from as there is no DisplayLink driver.
Are you executing the End User Cleaner as an admin. This is important to Run as administrator as even an admin launching the command will NOT launch it as admin by default.

Yes, as I did state before, on the particular screenshot I was showing, it stated that because I was trying to install M5 OVER another, older, working version. But, this exact same message appears even if I do a COMPLETE fresh install. So, take that screenshot with a pinch of salt and just apply it to the two variations please.

As for running as Administrator - I have done this every time.

and just to finalise the sadness of my response. SFC came back all clear.

Back to you arampon! and sorry!

[Rheco]

So, I fixed it!

Sorry arampon, this appears to be completely my end.

I installed some software and in doing so it managed to change certain aspects of PATH and PATHEXT in Environment Variables!

The incredibly odd thing about it was, that I installed this software almost a week prior to the issue occurring, but 'assume' that Windows update caused the problem to become more apparent as it then could not find the correct variables.

Upon returning the missing PATH variables and extensions, a restart, a fresh uninstall and then an install of M5 - everything worked.

My apologies again for running you around the block - sadly, because of the delay in the issue, I was not able to associate that change with the issue I got with the display.

Maybe for anyone in the future with a similar problem can check that any recently installed software changed these variables.

Thanks for all your help.

[AlbanRampon]

Excellent news Rheco. Congratulations. That wasn't an easy one.