Problem with “Intel” display drivers for older Intel chips?

Topic

New Reply

I can’t figure it out. Can you? See https://www.askwoody.com/forums/topic/intel-display-111016-1200-am-20-19-15-4549/#post-100488
[See the full post at: Problem with “Intel” display drivers for older Intel chips?]

1 user thanked author for this post.

PhotM

Reply | Quote

Replies

I am with you on this Woody, as long as it doesn’t get into allot of Legal Beagle silliness.

I have already said a fair amount on those other two Posts.

I like CH100 have mostly made up my mind on this, but I also asked(you{etc} in other posts) to come up with at least a rule of thumb on this issue for:

1. Unsupported(older hardware) hardware component Drivers.
2. Unsupported(older hardware) OEM PC Builds(like Del, HP, ASUS etc) hardware Drivers.

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

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

Crysta
I think the current official recommendation goes more mainstream than our more technical views.
So that recommendation based on majorities and not on technical expertise is to avoid Microsoft drivers and prefer instead the generic drivers from the component manufacturer’s web site.

Reply | Quote

Would this resigning explain it?
I have just picked a random .dll inside of the cab file from Microsoft Catalog.
See that the older Microsoft Certificate was due to expire soon.

… to be continued…

Reply | Quote

Reply | Quote

I went ahead and installed it via the Check for updates method.
It installed correctly, but please be aware that you may get a blank screen for an extended period while the driver is installed.
A better method may be to right-click on the existing device in Device Manager and scan for hardware.

Reply | Quote

I have to admit CH100,

You leave me scratching my head as to what I am suppose to do with all of the above. Other than a few differences, mine being pure Intel(no OEM codes involved) the confirmations were made earlier today. I imagine the problem is mine, since I don’t really have the interest to get so granular. I also know the average PC owner is going to have even less of an interest. I certainly RESPECT your effort to dig into all of this!!! :hand clapsssss:

In other news, Ch100, Woody and others I can now report that the Intel HD Graphics 3000 drivers ARE NOT COMPATIBLE WITH W 8.1 Pro. They would not Install from my Drivers Backups taken from both my W 10.0 Pro partitions, Fast and Preview Rings on to either of my W 8.1 Pro partitions.

Note: For those wondering, I have done this plenty W 8.1 Pro <> W 10.0 Pro quite sucessfully IF, IF the Drivers are compatible with the OS!

So there we have it! That distinction could be caused by Metadate changes ONLY BUT why unless there is something more changed in the Driver that W 10.0 1703 needs, that would compromise W 8.1 Pro?

I will say this, I will leave the Drivers installed on my W 10.0 Pro Partitions which are for the most part Alpha and Beta respectfully. I DO NOT look on them anywhere near Production but then I don’t look on W 10 as a whole that way neither! Just Sayn’……

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

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

Crysta

I normally work with live systems and no backup. I just don’t have enough time in the day to get defensive and as such I take calculated risks.
What is the worst that could happen if you install the newest driver on offer, assuming that it applies to your system?
The worst is blank/black/no display, in which case you may be able to get around a bad graphics driver by doing RDP from another computer in the same network and uninstalling. I don’t know if you have this setup, but it is quite normal these days to have more than 1 PC in the same network for home power users.
The best that can happen is to be up to date and move on.

Reply | Quote

Yes, that is what I was doing yesterday, with my testing.

I have had Drivers go bad for me. My external Radeon Card that my screens currently are driven by has been issued a bad driver, by AMD in the past and I have also had them from a Beta release trying to fix a problem I was having. That is also how I learn about all of this too. The internal is defensive for me and I can switch cables over to it, if needed, now that I don’t have a VGA input, which has been nice to have in the past.

What I have found in the worst case scenario is Microsoft’s fundamental UPnP system works quite well. I have yet to have to restore from a backup of image or registry because of drivers. 1 or 2, 3 at the most, restarts warm and cold will cause the system to either roll back the Driver or punt it in lieu of a generic MS driver and one can reinstall the old Driver package over that.

The problem here and for Woody, is not our voluminous experience, knowledge or even how we would handle things in a new experience. This is not about you and I or even Woody. We are all going to work things out and come out of it Golden 99.99% of the time. The Problem here that I am trying to help Woody address is how to Generally and Basically advise “ALL” users and owner’s of PC’s around all updateable and installable Drivers under the conditions of older but still very viable components and equipment(whole PC’s). I don’t believe we can loss sight of that.

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

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

This is not about you and I or even Woody. We are all going to work things out and come out of it Golden 99.99% of the time. The Problem here that I am trying to help Woody address is how to Generally and Basically advise “ALL” users and owner’s of PC’s around all updateable and installable Drivers under the conditions of older but still very viable components and equipment(whole PC’s). I don’t believe we can loss sight of that.

It is very true, but as I believe you suggested, the hardware is so diverse and the software which each user installs is so different and many users install without knowing security software which does more harm than good to functionality and again other users install patches selectively that it is impossible to find a solution which works for all.
It makes one wonder if Apple’s way is not the right way?

Reply | Quote

ROFLMAO Well Ch100 you can wonder all you want…..

I will not be wasting my time on that, not even fo a pico sec.

There is no doubt diversity is difficult. One just has to look at society, at least here in NA but I truly believe it is worth it. I can’t even comprehend what it would be like if we were all the same.

A monolithic human OR a monolithic computer approach, …. UUUUCKKK!

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

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.

Elly

Reply | Quote

Our problem, now, is that win 7, 8.1 that use Intell chips and drivers will soon not be able to retrieve drivers or purchase chips (for a build). In my reading, I understand that Intell has struck an agreement with MS, that would mfg only drivers and chips for newest OS’S and newest software products. Any idea’s?

Reply | Quote

PC and device manufacturers often have support sites where the correct OEM and updated drivers can be downloaded for older OS versions. This may not continue forever, but it’s still the case with most brands.

Usually a working driver only needs to be updated if there’s a security issue. Even at the Intel sites, I have found surprisingly old drivers which suddenly got updated for security reasons. Otherwise, if it ain’t broke, don’t fix it!

You do not need to update a driver just because a newer version number has been slapped on it.

-- rc primak

1 user thanked author for this post.

Elly

Reply | Quote

Let me repeat my long standing recommendations about driver updates:

1) If it ain’t broke, don’t fix it. You probably do not need to update working drivers on older hardware or an older OS version. Newer driver versions usually only include new features which the older OS and the older hardware cannot make use of anyway.

2) If a driver is not working, the sequence is as follows (for automatically updating OS versions like Win 8 and Win 10):

a) set up Windows 8 and 10 to Never Download Drivers from Microsoft Update. This setting may be ignored sometimes.

b) get onto a Metered Connection ASAP, preferably before any drivers have been downloaded. If a new driver update was already installed, roll it back using the Windows Device Manager after getting onto a Metered Connection.

c) use wushowhide before or after a new driver shows up in MS Updates. Hide all Ms Updates Driver Updates.

d) go to your device manufacturer’s web site when a new driver shows up in MS Updates. It is possible for security patches to be issued even for very old drivers. If there is a newer driver for your make and model, download it directly and install it.

e) If the device has no updated drivers, you may check the hardware component manufacturer’s web site, but this may lead you into Intel’s own site, where the driver they have waiting for you may be a device killer or an OS version killer.

But if you have an Image Backup, a Restore Point, and Driver Backups (possible with third-party tools, but NEVER download a driver using third-party driver update tools!) or media with device OEM drivers, you should be able to recover from almost anything Intel has yet been accused  of doing.

f) as a LAST RESORT ONLY, use the Windows Device Manager and let Microsoft update the driver, so as to have a driver compatible with your present OS version. This may backfire if the MS Updates version is designed as a device killer or an OS version killer.

Having a Full Image Backup and not letting any Windows version do automatic updates of any kind — especially not driver updates — could save your bacon. If you do end up in the hands of a retail technician, you will be upgraded to the latest Windows version. Or worse, they may insist that your hardware (your device) is out of date and cannot be repaired. It helps to have technical skills or friends and colleagues with these skills in such cases.

And by all means, keep up with this site and others, so you know when these changes are happening.

Personally, I have not seen Windows fail to support hardware including Intel hardware, in devices dating back to as old as 2010. I have seen NVidia stop supporting hybrid graphics on my old laptop. This actually only cause issues with that laptop in Ubuntu Linux, starting with Linux kernel version 4.8, but especially version 4.9.

So it isn’t Intel, Microsoft or Windows which dealt my laptop the death blow due to lack of driver support. It was Linus Torvalds and the NVidia Developers, carrying out their ridiculous feud, which killed off that laptop for me.

Windows users, you are not alone!

-- rc primak

1 user thanked author for this post.

Elly

Reply | Quote