New Windows 10 Drivers on Microsoft Update

Topic

New Reply

I have just received a driver update for an older Intel Graphics card, HD Graphics 3000.
Because this is in Windows 10, I have to use a third party tool to identify new updates and choose what to do with them.
Here is a snapshot from WUMT

This is extremely likely to be this driver with the Catalog date as 5/19/2016.

Why is it offered only now and with a changed date of 3/9/2017, while the underlying date of the driver is different?

My guess, ongoing preparations for the imminent release of the Creators Update, 1703.

Reply | Quote

Replies

This driver was already discussed here, long time ago.
https://www.askwoody.com/2016/new-win10-compatible-intel-sandy-bridge-graphics-drivers/

I currently have the latest version from Intel’s web site for this “card” (built-in, Sandy Bridge, Dell XPS L502X) which is compatible with my laptop and which is the second latest in the Catalog, version 9.17.10.4229.

The latest version, pushed only now from Microsoft Update is not published on the Intel’s site, but it is compatible with my Hardware Id.

It is likely to be Optional if the documented behaviour applies, as I have a fully functional driver installed and a newer one would be pushed only if it is Important (Security or Critical).

Why is this driver needed and/or pushed now, after almost 1 year since release?
I scan MU regularly and based on the publishing date, this driver has become available only today or yesterday, at least on my hardware.

Reply | Quote

I’ve manually downloaded this v9.17.10.4459 Intel Graphics driver cab package myself from MS Update Catalog (CAB file name 200026483.cab) and here are the hardware device IDs mentioned in its IGDLH64.INF file:

[Intel.Mfg.NTamd64]
%iSNBGM1% = iSNBM0, PCI\VEN_8086&DEV_0106
%iSNBGD1% = iSNBD0, PCI\VEN_8086&DEV_0102
%iSNBGM2% = iSNBM0, PCI\VEN_8086&DEV_0116
%iSNBGD2% = iSNBD0, PCI\VEN_8086&DEV_0112
%iSNBGM2P% = iSNBM0, PCI\VEN_8086&DEV_0126
%iSNBGD2P% = iSNBD0, PCI\VEN_8086&DEV_0122
%iSNBGD3% = iSNBD0, PCI\VEN_8086&DEV_010A
%iIVBGD0% = iIVBD0, PCI\VEN_8086&DEV_0162
%iIVBGM0% = iIVBM0, PCI\VEN_8086&DEV_0166
%iIVBGD0SRV% = iIVBD0, PCI\VEN_8086&DEV_016A
%iIVBGD0GT1% = iIVBD0, PCI\VEN_8086&DEV_0152
%iIVBGM0GT1% = iIVBM0, PCI\VEN_8086&DEV_0156
%iIVBGD0SRVGT1% = iIVBD0, PCI\VEN_8086&DEV_015A

My family’s Dell Inspiron 620 desktop PC uses Intel HD Graphics 2000 hardware beginning with the following hardware ID:
PCI\VEN_8086&DEV_0102

The full hardware ID on the Dell machine for Intel HD Graphics 2000 is the following:
PCI\VEN_8086&DEV_0102&SUBSYS_04ED1028

1 user thanked author for this post.

PhotM

Reply | Quote

More information here
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/intel-graphics-driver-917104459-only-ivy-bridge-or/350d9305-b8a8-4f0a-91a1-9c022ab66121
Mystery deepens.

Reply | Quote

Very strange. I think you’re right – there’s something in Creators Update that wants this particular driver…

1 user thanked author for this post.

ch100

Reply | Quote

It sounds like I should get it on my rig as well. I will install it on my Test partitions a see what it tells me.

I am just getting going so it will be awhile but I wonder if they have made it available for W 8.1?
I always scan MU it is my default, I have to specify WU to scan there.

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

1 user thanked author for this post.

ch100

Reply | Quote

For me comes under Windows 10 and later upgrade & servicing drivers.
Crysta, you can lookup in the Catalog for Windows 8.1 release if there is any newer release, but I doubt.

In plain English, the driver which I received means that it is targeted to :

Windows 10 any edition and future editions when there is none installed
Upgrade (which is the same with servicing, only that servicing means it is for newer editions of Windows 10) for existing drivers

Normally the newer version offered now 9.17.20.4459 has been released for Intel only for Ivy Bridge chipsets (4000).
For Sandy Bridge (2000 and 3000), the latest (“last”) version released by Intel should be the previous one 9.17.10.4229

It is possible that either Intel or Microsoft bundled both drivers for Sandy Bridge and Ivy Bridge and released them under the version which actually offers an update only on Ivy Bridge.

I will stay for now with the version supported by Intel for HD Graphics 3000 which is 9.17.10.4229, although I am not expecting the newer one to cause any issue and I will keep an open mind about it. The newer number may be a requirement for the Creators Edition.
It is messy, but this is always the downside of using old and unsupported hardware with newer OS. Another feasible option may be to allow Creators Edition when it will be released and installed to do its thing, upgrade if needed and rollback later manually to the Intel supported version.

1 user thanked author for this post.

PhotM

Reply | Quote

I understand CH100,

It’s been my experience too. What I have done in the past I try installing on W 8.1 off of my W 10 Driver backups. If is is dual, it will install on W 8.1. If not, it doesn’t….

Give me a few minutes. Down below I will put some screenshots from My Fast Ring partition Build 15048…..

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

I am running the Insider Preview in a Parallels VM on a MacMini (2.6 quad i7, 16GB RAM, Intel HD 4000 + 1536MB, 1.128T Fusion drive, 27″ Thundeerbolt display 2560×1440). I have had this VM for a long time and have had no problem with CU updates – until 1607 v15042.

After a cumulative update installs and reboots, following the login, Parallels Tools is installed. It coordinates the Win10 I/O with the Mac hardware. When I updated v15031 with v15042, after the Parallels Tools installation and reboot, I got a BSOD with stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. After the system tries to repair (and fails to do so) if I choose 3. Allow low-res video, the system comes up in lo-res, pops into high res, and runs OK until the next boot.

There is something different in the Intel graphics starting with v15042 and present in 15046 and 15048. Maybe they have incorporated this Intel driver into the CU. And that is a concern b/c I have three 1607 14393.726 VM’s that are due to get whatever’s Insider now with the Creators next month.

Backup, Backup, Backup. Maybe put  off feature updates for 365 days!!

 

1 user thanked author for this post.

ch100

Reply | Quote

Being about virtualization, I am not familiar with how Parallels presents the graphics to the virtual machine.
There are few ways, but generally speaking it should be transparent to the VM because the display is generally emulated and not passed through as is, unless you select a specific option which may be something like “Enable 3D”. You may have a default option 3D or GPU passthrough for desktop OS like VMWare does (only after installing the tools) and it would be interesting to know what happens if you can disable that option if it exists.
Or maybe try not to install the tools, as this would more than certainly avoid any GPU passthrough and use slower full virtualization instead.

Reply | Quote

Here are some screenshots of the Intel Graphics 3000 Driver Past Install:
I will put some screenshots from My Fast Ring partition Build 15048:

My Reply will include the Driver Events….

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

Here and the Intel Graphics 3000 Driver Events:
I will put some screenshots from My Fast Ring partition Build 15048:

The system is running fine with the Driver but I currently don’t have a monitor connected to the Onboard hardware. It is there as a backup which I was using on a past TV through it VGA Port.

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

They are the same drivers and versions available for Windows 10.

Reply | Quote

Yup CH100,

Your right, I forgot to put this in, forgetting your fixated on W 8.1, Sorry about that, my oversight that is corrected above now.

“I will put some screenshots from My Fast Ring partition Build 15048…..”

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

1 user thanked author for this post.

ch100

Reply | Quote

May be I don’t understand correctly “forgetting your fixated on W8.1”.

You asked for W8.1, I don’t use it and your screenshots are all from W8.1.
I only confirmed that they are the same drivers which I see for W10 1607, so they may have dual functionality, more likely originally released for 8.1 and it is just happening to work on 10 because of similarities between the 2 OS.

I am “fixated” if anything on Windows 10 because this is the area where we all have a lot to learn and adapt, but I pay attention to Windows 7 issues too.
I have little interest in W8.1.

Reply | Quote

ch100 wrote:

May be I don’t understand correctly “forgetting your fixated on W8.1”.

I apologize for confusing you. My main system OS partition is W 8.1. I was just waking up. The following is from that time:

PhotM wrote:

It sounds like I should get it on my rig as well. I will install it on my Test partitions a see what it tells me.

I am just getting going so it will be awhile but I wonder if they have made it available for W 8.1?
I always scan MU it is my default, I have to specify WU to scan there.

I was musing about W 8.1 and talking about W 10.0. I guess I probably shouldn’t have comment at all. I will restrain myself in the future.

Since we have a Fast Ring Build I am focused on that. I have not gotten to the W 8.1 Test Partition to see if the “Device Manager” will install the driver from my W 10 Drivers Backup.

Sorry again CH100, hope no harm done…

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

1 user thanked author for this post.

ch100

Reply | Quote

Which harm?
We know very well that it is difficult to communicate only in writing on an internet forum and this cannot be done in real-time, so misunderstandings happen all the time.

1 user thanked author for this post.

PhotM

Reply | Quote