I will put in a SR. I did another 1709 to 1803 update today and ended
up with a 11.4 version, different than the 11.3 I got on my machine.
The one correlation I did see is the one that ends up on the machine is
one of the backups that was on the machines from older updates.

Jim

On 9/5/2018 9:54 AM, CRAIGDWILSON wrote:
>
> Best to open a Service Request...���
> If I had to "GUESS"....There is some OLD Custom bundle created years ago
> that is still active and pushing out an old driver.
> Maybe someone years ago was pushing a Fix for that one file and never
> disabled it.
>
> However. an SR would let an engineer really dig into what is happening
> in your setup....
>
> jdkoerner;2486971 Wrote:
>> After update some of my devices to 17.3 client I started having blue
>> screens when just on Wifi. I had this problem in the past so I
>> immediately checked what caused the problem last time. In the
>> c:\windows\system32\drivers directory I see that zeswifi.sys is version
>> 11.3.0.150 the old version that was backed up during the upgrade is
>> version 17.2.0.123. I am not sure if other ZES driver files reverted
>> back.
>>
>> I had a clean install with no errors but ended up with the 11.3 version
>> of zeswifi.sys. Even the two old backup of the file in the folder are
>> newer. I had a similar downgrade issue with 17.2 so I have fixed this
>> at least once after 17.2.
>>
>> Any ideas where such an old version is coming from?
>>
>> What I see for versions:
>> zesdac.sys 17.1.0.85
>> zesfsmf.sys 17.1.0.085
>> zesfw.sys 17.2.0.90
>> ZesNetAccess.sys 17.1.0.85
>> zeswifi.sys 11.3.0.150
>>
>>
>> Jim Koerner
>> Server - ZCM 2017 Update 3 Appliance
>> Clients - ZCM 17.3.0.1270 on Win10/1803x64

>
>