Intel(R) Wireless WiFi/Bluetooth drivers v22.x.x.x

Tom wrote: wrote:

Intel releases only UWD drivers public for their graphic cards, they call it DCH
The UWD driver you request is not available (yet) from Microsoft.
Out of curiosity, why you need UWD drivers?
Can't install standard drivers? Run Windows 10S?
 

Microsoft has nothing to do with it, it places the Intel driver in the repository.
Example, Dell uses a UWD driver...
The driver is just needed, there is no need to breed an extra flood here.

samovar wrote: wrote:

Microsoft has nothing to do with it, it places the Intel driver in the repository.
Example, Dell uses a UWD driver...
The driver is just needed, there is no need to breed an extra flood here.
 

And Intel doesn't do it like that, they develop the UWD drivers, submit to Microsoft and when Microsoft approves it (WHQL), it will be distributed (assuming Intel submitted to MS).  Not necessarily anymore through Microsoft catalog as seen recently with Intel SGX 2.12 which is still not available through the catalog. In addition, manufacturers need to approve it also, if there are customizations for "their" product.

Cheers
Tom

Tom wrote: wrote:

Not sure whether its UWD but the following subsystem ID are included in the package in the folder JFP after extraction
USB\VID_8087&PID_0AAA&REV_0000
USB\VID_8087&PID_0AAA&REV_0001
USB\VID_8087&PID_0AAA&REV_0002

Cheers
Tom


 

I also want the UWD driver for AC 9560
I have 22.30.0.4 for AX200

My Intel DQ77MK + Intel AX200 motherboards pull the latest driver
My Dell Vostro 3770 + Intel AX200 pulls a 2019 driver
MY Gigabyte Z390 Aorus Master + Intel AC 9560 Pulls a 2019 driver
MY Gigabyte Z390 M Gaming + Intel AC 9560 Pulls a 2019 driver

Microsoft have a whitelist for oem's who can and cant have the driver its stupid
oem's simply never follow up with approval for newer drivers


anyway
AX200 is UWD AC 9560 AC 9260 is not
mega.nz/file/IyIwCRTI#C37kaO-dhPz7FkKSTn...I0BX3Mwda61kvsmVJuyU

Intel 9260
%iBT_USB% = ibtusb, USB\VID_8087&PID_0025&REV_0001
%iBT_USB% = ibtusb, USB\VID_8087&PID_0025&REV_0002

Intel 9560
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0000
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0001
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0002

Intel AX200
%iBT_USB% = ibtusb, USB\VID_8087&PID_0029&REV_0000
%iBT_USB% = ibtusb, USB\VID_8087&PID_0029&REV_0001
 

Nepo Nei wrote: wrote:

Intel Bluetooth 22.20.0.3
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0000
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0001
%iBT_USB% = ibtusb, USB\VID_8087&PID_0AAA&REV_0002

www.upload.ee/files/12656584/ibtusb.zip.html
 

Nepo Nei any chance you can pull us 22.30.0.4 from windows update

Tom wrote: wrote:

In addition, manufacturers need to approve it also, if there are customizations for "their" product.

 

The UWD drivers are the same and you can check it yourself.
It is checked by byte and by hash sum.

samovar "post = 4763 The UWD drivers are the same and you can check it yourself.
It is checked by byte and by hash sum.
 

Before we have a misunderstanding, which driver are you referring to?
I compared the driver Shonk offered for download and the one Intel provided for AX200.
The first picture shows the binary of the driver, left side Intel driver shared from Intel Website, right side the UWD driver Shonk shared.
Showing a different file size, so there are some additional modifications
The second picture shows the CRC checksums, left again the shared driver from Intel website, right side the driver Shonk shared.
In this case, byte by byte doesn't match also the checksum is different.

AX 200 Checksum (Intel website driver):
Name: ibtusb.sys
Size: 1016312 bytes (992 KiB)
CRC32: 4D8B2E65
CRC64: 751D52AF9E848C2B
SHA256: 37C087F83EB4CD92571AB0EA593058D09A657F3FA5CF1FC0FA759649F76D531F
SHA1: 71F5AB759E65165B4722269C36275F4143DE8EED
BLAKE2sp: DA3BB320A98492197B1F1E6F4134F1676828D6E8E8D69A3753DD41CCCF17009D

AX200 (UWD driver):
Name: ibtusb.sys
Size: 1129952 bytes (1103 KiB)
CRC32: E2797881
CRC64: A05A15FD1E26C1A0
SHA256: 79DEC95F45B253B781F5E8C47EB104A0A7E40B042BE8BA5AE77BB4FB173A4884
SHA1: 2300D60BF6C5C589B252FAC89359B10581AAFFF8
BLAKE2sp: 8D8605D95A1E9FBB01A84293ABDC2F674A93B215C456D559EA87CB4DDB00D1DD

Edit: So it looks like there is an UWD for ur device, so maybe someone can pull it from his system who has the same Product ID.
The shared driver also doesn't show up in the MS Catalog.

Cheers
Tom