What’s going on with the “INTEL – System” patches?

Topic

New Reply

I’ve seen a long line of complaints about Windows Update’s patches called “INTEL – System” followed by a date and time. My original beef was with “INT
[See the full post at: What’s going on with the “INTEL – System” patches?]

Reply | Quote

Replies

The average user and non-Ask Woody reader, probably just installs everything that comes down the Update chute. I can’t imagine what kind of shape their PCs are in. I’ve gotten these Intel updates and they were a quick “hide” and forget. How are we supposed to analyze these types of updates if you’re not an tech expert. What other choice do you have…just hide and forget. Life will go on.

Reply | Quote

Excerpt from…….
https://community.spiceworks.com/topic/1951465-bad-or-at-least-useless-windows-patch
.
(28 Dec 2016)
“I’ve been seeing a couple of various INTEL windows update patches come through today, and the only 2 machines that installed them so far have crashed hard.

System32Drivers sys files MISSING hard.

I managed to copy over the sys files, and then I end up with a Processor1_Initialization error 0x6B that is unrecoverable. So I’m spending my night reloading workstations for payroll and accounts payable.”
.
.
.
Excerpts from…
https://www.reddit.com/r/windows/comments/5jjxlx/anybody_else_getting_a_strange_windows_update_for/?sort=new#bottom-comments
(4 days ago)
“So I legitimately just got f****d by this update for two family computers being used and setup for Christmas.

Auto-updated on two computers and both started having blue screen issues within the next day and took me ~2 hours before I tried a system restore point which thankfully solved the issue on both machines from the random bluescreens.”
.
(2 days ago)
“Installed and broke a network connection to a server running windows 2012 essentials r2. Don’t install this….”

Reply | Quote

This is a good use case for wushowhide. I have all of my WU driver updates hidden.

Unless you are aware of a specific driver update that you need, I would not touch them.

Go to your hardware manufacturer or OEM for their latest drivers.

Reply | Quote

You’re seeing the patches in Win10?

I thought they were Win7 only – maybe Win 8.1.

Reply | Quote

Good sleuthing! Thanks.

Reply | Quote

Yup, just hid 10 fresh ones on my Win 10 Pro 1511, custom home built Asus, Intel based machine.

These were for Intel chipset and various Intel controller driver updates. Plus one HP printer driver.

I gets all my Win 10 drivers from the Asus website. Everything is still running rock solid here.

Been seeing a few of these appear since joining the Win 10 club at the end of July, which I have been hiding as they show up.

But this latest group seems to be a fresh re-issue that presumably replaced any hidden ones, and then added a few more.

So bottom line, if you don’t run wushowhide before you check for updates, you gonna get clobbered!!!

My other PC, a Win 10 Home 1511 laptop (OEM), has received a different collection of drivers. A mixed bag of Intel, Realtek, Qualcomm, and Synaptics, that reflects the hardware components of the on-board laptop devices. I get my laptop drivers from the laptop manufacturer’s website.

Reply | Quote

First let me say, I do not know what is the purpose of these Intel system driver updates that are sitting as optional updates on my W8.1 X64 system. As I do not maintain a dedicated test system and have a personal policy of not sourcing third party drivers through WU, I decided to install the Intel Driver Update Utility and run a driver scan locally on my system. Intel’s own update utility did not flag any system chip drivers that were out of date with a reference to the appropriate replacement driver. Whatever these drivers in WU are for, Intel Corp. does not seem to know about them either. If your system has no known driver issues, I would remain very cautious about installing any of these driver updates, especially considering the complete lack of pertinent documentation.

Reply | Quote

Funny how these mysterious updates appeared just before the Christmas/New Year break.

Its almost like someone at MS ‘pulled the pin, tossed the grenade’ and ran for cover.

As has been mentioned here and elsewhere, perhaps an intern at MS ‘pressed the wrong button’ and this is the result.

Won’t be long before someone at MS (Chris C again, maybe?) comes along with another “oops, sorry – we made (another) mistake”.

Perhaps whoever attempts the apology this time could do a Basil Fawlty impersonation for added effect?

https://www.youtube.com/watch?v=aNXjvXtOguo

MS’s behaviour over the past 18 months is almost like a Fawlty Towers episode.

Reply | Quote

Hi Woody,

I am only seeing this on W 8.1 Pro. I will be checking my W 10 partitions again today.

Somebody commented, ‘to hide and forget’. I personally found that method to be a fools errand that eventually jumps out and bits you. I have WU/AU/MU locked down on all of my partitions/PC but do eventually install everything….
BTW, both my W 8.1 Pro PC’s are running as stable as one can get. W 10, not so much BUT that is W 10, isn’t it…. (SFC, DISM, Disk Cleanup, Disk Defrag and SpinRite L2(both even on SSDs are my friends).

To Quote you, “If so, it doesn’t inspire confidence in the recently announced Kaby Lake chips”. I personally haven’t found anything in the last 2 years to inspire confidence in anything from Microsoft, Intel or AMD, frankly. When ever something slightly does, one gets let down hard….

Best Regards,

Crysta

PS, Thank You, for keeping this site, so one does not have to register for one more thing…..

Reply | Quote

I’m currently seeing 11.0.0.1010 (3/13/16), 10.1.1.38 (10/3/16), and 11.6.0.1042 (11/16/16)– all at once– as optional updates for Win8.1.

Reply | Quote

My Intel-based machine (Windows 7) had already had the original Intel system 10.1.2.80 update hidden, now I’ve been offered:-

Alcor Micro USB 1.0.145.40103

Intel system 10.1.1.38

Intel system 11.0.0.1010

All are unchecked optional updates and have been hidden. None of them has appeared on my AMD-based machine.

Reply | Quote

Crysta –

You bet. Thanks for posting!

I don’t even have a method for registering at the moment. That’ll change when I add the AskWoody Lounge appendage – but even then, anonymous posts are most welcome. Unregistered posters have to wait for me to approve their posts, but ordained “AskWoody Loungers” will be able to post both replies and create topics, without moderation.

Reply | Quote

My theory – it’s only a theory – is that the “big boss” is on vacation, and somebody’s showing a bit too much initiative in pushing these patches out. It’s a real mess.

Reply | Quote

+1

Reply | Quote

Oh, MAN. They didn’t screw up Win10 with its forced updating, too, did they?

Wait a sec… how do these show up on wushowhide? There’s no KB number. Do you have the exact wording of the patch names, or can you email me a screenshot of your wushowhide list?

Reply | Quote

Woody, I ran Intel’s Driver Update Utility IDUU. The results were interesting. IDUU says I need Win10/7*.8.1 graphics drivers update win64-163343-4425.exe (I am Win7-x64). What’s interesting is that it says my “installed version” is xxx4226 and the “latest version” is xxx4225. So, whomever suggested this might be a roll-back by Intel may be correct. People can find the IDUU here: http://www.intel.com/content/www/us/en/support/detect.html, which may be a more reliable source that WU. As I use an installed graphics card, not the chip on the board, I am going to pass, certainly on the WU updates, but also the Intel update.

Reply | Quote

10.1.1.38 showed up here on Win8.1,7×64 sure would explain a lot if John Cleese is doing the updating down at “FawltySoft”

Reply | Quote

Thanks for the link.

Now I’m very, very confused.

Reply | Quote

Oh, it’s getting more fun! What I reported above was for my desktop. When I just ran it on my laptop just now: a) when I ran WU I got those same two Intel drivers and a Realtek USB drive and b) when I ran Intel’s Driver Update, which of course shouldn’t say anything about the Realtek driver, and doesn’t, it give me this result: Intel ProSet/Wireless Software And Drivers (15.11.0.7 Windows* 7, 64-bit for legacy adapters Wireless_16.11.0._s64.EXE installed version 15.4.0 lastest version 15.11.0.7 and nothing for graphics drivers.
It is beyond my skill set to dig into which chipsets I have on each of these computers but, stating the obvious, something seems seriously wrong with what MS is pushing with hardware updates, which is pretty scary.

Reply | Quote

@John W
There are nuances in installing drivers from Microsoft vs OEM and they should be treated case by case.
There are sometimes better and more stable drivers from Microsoft than from the manufacturers and the other way around.
It is difficult to assess though and the general advice for end-users is not to upgrade drivers once they reach a situation where they have a stable machine.
Let’s take the example of NVidia and their release schedule. Their updates are a lot more unreliable even than the updates for Windows 10. Once you get a stable driver from Microsoft for a NVidia card, stick with that version. This advice is obviously not for gamers who have other primary criteria than stability and reliability.

Reply | Quote

I think for Windows 10 in particular is generally a good idea to use the Microsoft drivers, which are in fact all manufacturer’s drivers. Microsoft only publishes them and matches them with the hardware id.
But again, it depends on the age of the machine, how much support for Windows 10 is available from the manufacturer and very important, the level of technical ability of the end user and the availability to spend hours with testing, rolling back etc.
Some drivers from the manufacturer, good for 1511 may not be so good for 1607 as an example.

Reply | Quote

For those with Pro and above, there is a new Group Policy in 1607 which you may find useful.
Computer Configuration/Administrative Templates/Windows Components/Windows Update/Do not include drivers with Windows Updates

If you find it too hard, just get familiar with and use Windows Update MiniTool as Windows Update user interface replacement.

Reply | Quote

Thank you Crysta. Finally getting some help from someone on the patchmanagement.org list I am getting tired of repeating the same advice here.

“Somebody commented, ‘to hide and forget’. I personally found that method to be a fools errand that eventually jumps out and bites you. I have WU/AU/MU locked down on all of my partitions/PC but do eventually install everything….”

Reply | Quote

@JNP
Rollback, or possible completely different reason.
You may just have a driver not recognised by the Intel tool and the latest version recognised is the one which it recommends.

Reply | Quote

Woody,

You and me BOTH!!!!!

This must be a ROLL BACK, BUT for what purpose???? What has gone wrong??? I have seen no problems that I am aware of, with the exception, the NUC 5i7, But this is still new and Intel is still perfecting, especially the video. Every so often, if flash is running(rarely) the PC will crash. VLC greens out or crashes every so often as well. Other than that it has been running my entertainment center very well, for 16-18 hours a day every day.

Here is a question that you might try to get an answer for; Did they have to up issue/change something before they could successfully roll back on most PC’s?

Best Regards,

Crysta

Reply | Quote

I have all three Intel updates installed in test on a Win 7 Pro system and so far, no issues.

Reply | Quote

I’ve not been offered these Intel patches… yet, anyways. but then again, I don’t have an Intel processor in this rig, so that may be the reason for me being lucky in that regard. If I do see them, I’ll definitely be sure to block them.

Reply | Quote

Does it look like they overwrote each other – per your earlier post?

Reply | Quote

Just emailed the screenshots … no KB #’s.

Reply | Quote

I build my own desktops, and the only drivers that belong on there are the ones that I put on there.

There are some class compliant drivers supplied via the OS, but any hardware specific ones are those that I deliberately selected for their purpose. I generally don’t upgrade them if everything is stable. And when I do, I go to the hardware vendors website and download the latest driver for my OS version.

And I’m not running nVidia on my Win 10 machines. Just the on-board Intel HD.

But get driver updates from Microsoft? The casual user should especially avoid these. How do they “evaluate on a case by case basis” when most likely they get slammed by them, without any choice? How are they to recognize when their hardware suddenly stops working, & might be connected to a driver update? Short of spending money at a repair shop?

Reply | Quote

Wow. That’s a HUGE list.

I see you haven’t upgraded to 1607.

I also note that none of them have the telltale text “INTEL – System…” name. They’re all “Intel – Other hardware.”

Reply | Quote

They don’t get overwritten…

The original .INF’s get moved to a unique folder name under C:WindowsSystem32DriverStoreFileRepository after being copied to a new OEF’nnn’.INF file name.

So, 8/19/2016 haswellsystem.inf became oem49.inf and is stored in folder haswellsystem.inf_amd64_neutral_519ef4c07e556e82

and 10/3/2016 haswellsystem.inf became oem51.inf and is stored in folder haswellsystem.inf_amd64_neutral_8bfd0687cd7f39ae

Reply | Quote

“I see you haven’t upgraded to 1607.”

Yup, 1511 still rock solid here, but now that the all clear (CBB) has been given to 1607, I was going to wait until the new year, take an image backup, then hold my nose and update!

I eventually plan to install all Microsoft Windows updates. But I will reserve final judgement on all driver updates, Microsoft or otherwise

Perhaps the difference in the updater list names could be a difference in the Windows 7/8 updater vs. the Windows 10 updater?

Reply | Quote

IDUU told me to get my graphics driver update from the computer manufacturer.

Reply | Quote

Further investigation shows that oem51.inf (10/3/2016) shows up in the registry as…

@oem51.inf,%pciven_8086&dev_0c04desc%;Intel(R) Xeon(R) processor E3 – 1200 v3/4th Gen Core processor DRAM Controller – 0C04

oem49.inf (8/19/2016) is not found in the registry, so it has been superceded.

Reply | Quote

Quite possible. I’d like to get some more examples before I write about blocking the patches, but I don’t have any Win10 machines that show them.

Reply | Quote

@ch100

You are right, this is a new version of the Intel video driver and I was mistaken when I wrote it was a roll-back. I am somewhat dyslectic and I reverse numbers in my head, sometimes, which was not great when I was an attorney trying to look up a citation to a case :).
So, yes, Intel has a new driver, that wasn’t being offered last week, as I ran the Intel tool then and nothing popped up as being new with the Intel tool. But as Woody always advises, it would be better to get it from Intel than MS. This is true as it appears that what is being offered by Intel is different than what is being offered by MS, I think, because shouldn’t MS be offering the same driver update (driver numbers etc.) as Intel is showing (which isn’t the case)? This is not a rhetorical question, I am putting this out to you guys, and gals, who are really in the business of computers.
All the above is just about the video updates, it says nothing about all the other updates that popped up today in WU, on some peoples’ systems, like the Realtek update MS offered me, and others, as well, which I haven’t investigated yet.

Reply | Quote

“I don’t have any Win10 machines that show them.”

Well Woody, my thinking here is that you may have already installed any drivers that were offered for your system, perhaps without noticing. They seem to come down the same chute with the monthly security roll-ups, the Flash update, and the Malicious software remover.

On the other hand, thanks to your timely tutorial on wushowhide, I have been extra vigilant about updates ever since hopping on board the Win 10 train in July 2016. Only the Windows updates for 1511 have passed through my gates.

Reply | Quote

I am running Windows 10 on an older Sandy Bridge and I don’t get any drivers. The system is 1607 fully patched, including the most recent CU hotfix, KB3213522.
Maybe the drivers were already installed as part of the initial installation and this would be a reason why I don’t get any.
Due to the age of the machine and lack of support for Windows 10 from Dell, I run only Windows supplied drivers and only where there is no other option, I run OEM drivers.
I explained the reason before, Microsoft tends to match their drivers with the Hardware ID which contains DELL ID in addition to the generic one. The only other drivers matching the full ID are only from the laptop manufacturer’s site, DELL in this case.

Reply | Quote

And I would advise gathering as much info as possible before making general recommendations.

There are obviously several different viewpoints regarding driver updates to consider.

I have stated my personal experience and opinions, and as such, they may only apply to my situation. Just thought that the Win 10 info that I observed on two different PC’s was important enough to be shared.

Reply | Quote

It certainly is important. I wish we knew more!

Reply | Quote

“And I’m not running nVidia on my Win 10 machines. Just the on-board Intel HD.”

This is excellent. I didn’t have this luxury and I had to buy a hybrid Intel + NVidia.

You have a generic box and your drivers are normally downloaded from the OEM manufacturer as there is no other good choice.

This is an example of Hardware Id for an older, still supported, Nvidia Card GeForce GT 540M.
PCIVEN_10DE&DEV_0DF4&SUBSYS_050E1028

The suffix 1028 for the SUBSYS is specific to DELL.

Although a driver is usable if it matches only the first part, before the SUBSYS, I prefer to have it fully matched and sometimes to get the latest one you need to use the Microsoft version.

It is complicated and not for everyone to understand.

Reply | Quote

My main machine is an AMD, which seems to be spared the trauma, and my second machine is a Dell XPS-15, which isn’t showing anything. Both are on 1607.

I’m also running two beta machines on Intel hardware, including a Surface Pro 3, but not seeing anything there.

Very frustrating…

Reply | Quote

I sympathize. I mix up so many KB numbers, frequently by transposing single digits, it’s embarrassing. Helps to have a lot of people looking.

Reply | Quote

Correct. But what is less known is that Microsoft Drivers are matching the manufacturer Hardware Id unlike the generic ones from OEM.
I have to say though that the Intel Generic ones are most of the times the same drivers with the manufacturer’s drivers or cover them as well. The Hardware Ids supported are defined in the .inf file associated with any driver.
For other manufacturers, this depends on the actual device.

Reply | Quote

I think the working version is under “C:WindowsINF” and not under DriverStore. The DriverStore one is… a store. Or maybe not?!

Reply | Quote

YUP! I can identify with both of you along with a few other dysfunctionallities. Now how does one spell ”dyslectic, OH Yes, copy and paste….

Reply | Quote

Same with me, on 2 different partitions, one is Insider Fast Ring. the other is 1607 Release Ring which is currently RTM patched. No Drivers being offered on these two from WU at this particular time.

I copy all necessary Driver file to back them up. The earlier offering was easily sucked up from my backups. When I get that far I will let you know if the same thing happens this time.

Best Regards,

Crysta

Reply | Quote

Correct.

In the above examples, oem49.inf and oem51.inf are located in C:Windowsinf

Reply | Quote

I agree with you. I have there is no one way(I wish Microsoft would hear that) to accomplish stability and PC’s are fare from being utility devises like most people seem to think.

Woody, your one of the few people that might be able to find out in the new year????……

Best Regards,

Crysta

Reply | Quote

I’ll keep trying.

Reply | Quote

Just FYI, or for grins … you can look in device manager for driver updates history.

Just double click on a device, then on the device properties page, look at the “Events” tab. You can see when the device was installed or last configured (updated).

For the folks with Intel hardware, you can look under “System devices”, for the chipset and management interface stuff.

I am an Intel purist, so have no idea what the AMD stuff look like…not that there’s anything wrong with it, LOL!

Reply | Quote

Just to add a little more background to my driver updates scenario…

I did a complete disk wipe and clean install of Windows 10 Pro x64, version 1511, at the end of last July using the Microsoft media creation tool.

My hardware is third generation Intel Core, code named “ivy bridge”, so it is still supported on Windows 10.

The initial install provided only Microsoft supplied drivers, but was enough to get started with. I had already downloaded the Win 10 drivers for my Asus motherboard, USB Wi-Fi adapter, PCIe FireWire, FireWire audio interface, etc.

I now do recall that at some point during the Asus motherboard driver install (Intel chipset, Intel MEI, Intel HD graphics), that a warning box popped up that I was installing older drivers than what were already installed.

Since I was using the latest drivers from Asus, I proceeded. It now appears that Microsoft has been banging on my door ever since to apply the “correct version” of my drivers.

So for those of you not seeing these driver updates, perhaps you have already joined the Borg collective

Reply | Quote

@ ch100 & John W ……. We hv to remember that when M$ offered the free Win 10 upgrade to Win 7/8.1 cptr users on 29 July 2015, the OEMs balked n refused to create Win 10 device drivers for these “old” n already-sold OEM Win 7/8.1 cptrs. IOW, the OEMs preferred the Win 7/8.1 cptr users to buy new OEM Win 10 cptrs, instead of taking the free upgrade = more profits for the OEMs.

This resulted in many OEM Win 7/8.1 cptr users ending up with bricked cptrs after opting for the Win 10 upgrade or who were ignorantly or forcefully auto-upgraded by M$ via Windows Update. This was even though M$ had informed them that their Win 7/8.1 cptrs were compatible for the Win 10 upgrade.
……. The boycott by the OEMs also resulted in M$ having to create basic generic Win 10 device drivers for some of the OEM Win 7/8.1 cptrs.
.
So, if u want Win 10, better to buy a new OEM Win 10 cptr bc the OEMs only provide Win 10 device drivers n driver updates for their new cptrs.
……. It’s also better for OEM Win 7/8.1 cptr users to stay on Win 7/8.1 n not upgrade to Win 10 = less device driver headaches.

Reply | Quote

Both W 10 partitions took the Driver Updates from my Driver Backup and are running as they were before(just for the record this is usually reversed since W 8.1 is not as high a priority).

One thing I noticed is that there were about 4 Device locations that would not take the earlier Driver Updates that have now taken these latest ones. Their versions were 10.1.1.13 and Updated to 10.1.1.38 like all the pertinent ones are now.

Woody do you have any idea what that means?

Best Regards,

Crysta

Reply | Quote

@ ch100 & Crysta ……. Fyi, in most of the world, there is still free choice for the people, even though u may think that some of their choices r wrong, eg “hide n forget”.

Reply | Quote

I haven’t a clue. Driver update behavior has always been opaque, but in the past week or so it’s just been bonkers.

Reply | Quote

@Crysta
It may be that Windows has changed the driver model silently as part of the upgrade from 1511 to 1607 or even while installing one of the CUs.

Reply | Quote

@John W
I don’t think anyone can make general recommendations, except for the extremes:

1. Do not install any drivers from MU
or
2. Install whatever comes on MU as it is Microsoft’s business to manage the mess if they create any. There is a variation to this approach, which is: DO NOT install any OPTIONAL drivers from MU (only Recommended and Important, or only Important).

Other than that, everyone’s situation seems to be different and this is something very difficult for Microsoft to manage, unlike Apple, because MacOS and iOS both have to run only on Apple hardware.

Reply | Quote

I think what you are describing is the way it has always been with every Windows upgrade.

Unless you are an computer engineer, the best way to upgrade has always been to get a new computer. Hopefully the new hardware has been tested and certified.

I don’t buy the conspiracy theories. I just think Microsoft is a failed organization.

They have just hit their Wells Fargo moment …

(Anyone remember when Fonzi jumped the shark?)

Reply | Quote

Jump the shark. Yeah, that’s it.

The big problem with buying new to get Win10 – there were so many headaches with the Skylake processor (and thus the Surface Pro 3, Surface Pro 4, and Surface Book) drivers that I’m amazed Microsoft sold any of ’em. Fortunately, it looks like that debacle is behind us – a year later.

Reply | Quote

@John W
I personally don’t like to jump into the consumer mentality promoted by the sales people and buy something new just for the sake of it, unless there is some benefit to be gained.
There is no reason to buy new hardware if the old one can be upgraded with cheap after market components like RAM and SSD (not so cheap, but still a more than worthy upgrade for read performance on steroids). Some tuning may be needed, which is where your statement “Unless you are an computer engineer…” comes into place.

As for what you say “I just think Microsoft is a failed organization” this is more than inaccurate. They just can’t care less about those who do not bring them profit, guess who they are.
Nadella has turned the business around and “made Microsoft great again”.

http://www.afr.com/technology/technology-companies/microsoft/how-satya-nadella-is-making-microsoft-cool-again-and-taking-on-apple-and-amazon-20161118-gssfb1

Reply | Quote

@John W
Very valuable information.
I knew about it, but somehow forgot it.
Just checked my 1607 and found that it was installed (clean) on 10/29/2016 and the 10.1.1.38 drivers were installed on 11/16/2016.
I kept the US date formatting for convenience, we use different formatting here.
I don’t remember when the chipset driver update took place, but it is proof that it worked flawlessly. I don’t use auto-update but I am not paranoid about updates either.
I have an old Sandy Bridge chipset, nicknamed Cougar Point.
https://en.wikipedia.org/wiki/Platform_Controller_Hub#Cougar_Point

Reply | Quote

@ John W ……. U said, …” I think what you are describing is the way it has always been with every Windows upgrade.”
.
.
That was likely not true with Win 8 in 2012…
http://www.zdnet.com/article/installing-windows-8-on-your-old-pc-could-turn-it-into-greased-lightning/
.
I think in 2012, the OEMs cooperated with M$ wrt Win 8.
.
If what u said was true, no one would hv bought the more expensive Retail Win XP/Vista/7/8/8.1 licenses which were supposed to last for 10 years(= EOL) = the cptrs would hv gone thru a few hardware upgrades with OEM devices, eg newer motherboards, HDDs/SSDs, etc.

Reply | Quote

Maybe, Win 7/8.1 cptr users in a holiday mood r more prone to merrily install whatever buggy or rigged updates intentionally dished out by M$.

Reply | Quote

I think it would have been more accurate to express that opinion as “Microsoft has failed the consumer”. As a business entity, it is thriving, but not because of the consumer.

Simply take a look at Microsoft’s own financial report for 2016. https://www.microsoft.com/en-us/Investor/earnings/FY-2016-Q4/press-release-webcast

Their operating income for 12 months, ending June 30, 2016:

Productivity and Business Processes (Office), and Intelligent Cloud (Server, Azure, and Enterprise Mobility), earned them over $23 Billion.

More Personal Computing, which includes Windows, Surface, Phone, Xbox Live, and Search, only earned $4.6 Billion for the same period.

So from a business perspective is Microsoft going to give priority to what we think? Personal Computing Revenue declined by 4% in the 4th quarter. How cool can that be

Reply | Quote

Clearly the OEM’s want to sell more PC’s, and Microsoft wants to sell more upgrade licenses (Well at least until they decided to give away Win 10 for free).

I also remember when that Win 8 article came out

As a desktop builder for more than 15 years, I have learned to research and scrutinize in great detail each generation of PC hardware, to better understand what has been tested and developed on what platform. The Windows and Intel roadmap, etc … I have run Windows 286, 3.1, 95, 98, ME, NT, 2000, XP, 7, 8.1, and 10.

The biggest complaint that I recall hearing from other builders, as well as consumers who attempted upgrades, was in evaluating the driver compatibility requirements for each version of OS, etc.

Maybe the driver path hasn’t been so bad in recent memory, from Win 7 upwards, because the Windows driver model has basically remained the same since Win 7.

But prior to that it was a very messy affair.

The leap from the DOS based Windows (last one was Win98/ME) to the NT based versions(2000/XP), broke nearly every consumer driver in existence.

The leap from XP to Vista (one which I avoided), also brought many hardware uncertainties. I think that Windows 7 finally updated and matured the Vista hardware drivers. So back in those days, it was really recommended that you should buy a Vista ready PC if you wanted to run Vista. Sure you could buy an upgrade, but better know what you are getting into.

In my opinion, the same advice still applies, but the problems may be more subtle. System stability may be an issue, if your drivers are not written and certified for the latest OS. You might need new hardware that has compatible drivers, before an upgrade.

Reply | Quote

Also, regarding driver updates for Windows 10, I don’t believe that they are qualified as either “Optional” or “Recommended”.

They just seem to show up in the same Win 10 update chute along with the security roll-ups

Reply | Quote

Exactly!

Reply | Quote

It may be possible that these are just additional updated drivers/patches for the Intel Management Engine (Components package)?

Aside from that I’m wondering if there is a way to remove these? I don’t have a previous restore point and the updates aren’t listed as a possible uninstall. Usually I could remove KB from command if not listed in the update panel, but these Intel updates provide no ID.

I’ve also noticed that my OS (8.1) is no longer creating system restore points, since after installing 11.6.0.1032, 10.1.2.80 (2 system, 1 usb), Intel updates.

Reply | Quote

Good point. Because of the way Win10 updating works, they’re pushed on through regardless.

Reply | Quote

I’d also like to know how to undo these intel updates. I applied the optional intel update recently and I have some grey-outs happening when multiple flash/3d gaming is running on my pc. The loading wheel on the cursor will constantly turn, clicking anything loading causes it to grey out, and nothing new will open, even task manager. Sometimes the start menu works and if I wait long minutes a shutdown actually might work. More often than not though, I have to press the reset button and just choose start windows normally.

Reply | Quote

Good question. I’ll make this a main post. Gimme an hour.

Reply | Quote

@ Jay & woody ……. Someone here had already mentioned that to uninstall this driver update, u need to go to Device Manager, locate the affected Intel devices(eg that hv the 10.1.2.80 null-drivers installed) n roll-back the drivers.

Reply | Quote

Yep, I tried that, but it looks like the official Intel checker is better. I think.

Reply | Quote

The better solution is to go to the laptop manufacturer and download the supported version if one exists. It should be version 9.x for Windows 7. By installing it and overwriting the newer version when asked it will automatically roll back.
The next better option is to go to Intel site and download the official version from there with the same options. Probably 10.1.1.38 https://downloadcenter.intel.com/download/26330/Intel-Chipset-Device-Software-for-Intel-NUC will cover all preferences for all Intel chipsets 6 series and above and 9.2.0.30 https://downloadcenter.intel.com/download/20019
for older chipsets

But if there is no issue, 10.1.2.80 is just fine.

Reply | Quote

Yes, but they are not auto pushed if they are what used to be Optional in Windows 7.

There is an algorithm documented on one of the Microsoft sites explaining how it works by default, without any additional measures like using WSUS, Group Policy or wushowhide or third-party clients which is actually my preferred method.
It works like this:
– Windows Update will auto push a driver if none exists – this is the equivalent of either Important or Recommended in Windows 7
– If a functional driver does exist and a newer driver is available, it will not be pushed through Windows Update. This is equivalent with Optional in Windows 7. However, if the user manually scans for drivers in Device Manager, the newer driver will be installed automatically. This behaviour can be controlled by settings in Control PanelSystemAdvancedHardware
– There is a third possibility which I think was used with some of the NVidia drivers few times. If a driver is installed and functional but there is either a functional or security bug found, then the driver is getting pushed automatically via Windows Update. This is equivalent to the current Important category, either Security Updates or Critical Updates.

It is not so badly thought, but it may not be implemented correctly sometimes.

Reply | Quote

Woody,

How does that apply to Legacy Intel Hardware like i2600(K) with Cougar?

I personally have never had allot of successful effect with the Intel App. For my NUC I go directly to the Updated Driver Listing on Intel’s Site and download from there(that is what I used to do with my tower too). Intel just doesn’t do Legacy BUT Microsoft does……. Go Figure.

Best Regards,

Crysta

Reply | Quote

So what exactly is “Energy Server Service queencreek”?
C:PROGRAM FILESIntelSURQUEENCREEKesrv_svc.exe

I know it installs alongside the Intel Driver Update Utility, but I could care less for “usage” reporting to Intel. It installs as a automatic running service on boot.

Is this just another useless service to slow down a system and not required to use the utility?

Reply | Quote

It’s called the Intel Energy Checker…

http://www.shouldiblockit.com/esrv_svc.exe-29abfee5112cb16b305b50f9d5098e3a.aspx

Reply | Quote

@Woody:

Everything is becoming so technical that most “general users” have problems relating to any of it.

Since you are in the process of setting up “specific subjects”, I would like to recommend that one be set up for “NON-TECHIES” (or COMPUTER DUMMIES).

In that manner all of the acronyms, etc. that the more experienced users have in their posts would not even be seen.

These specialized programs, many of which are for “Network Admins”, etc. would not be seen. I am utterly “lost” when there are references to these specialized programs which I do not understand.

It is just becoming more and more difficult to even try to follow some of the dialogue because the “average Joe/Jane” does not understand what is being discussed.

Thank you for everything you do, and have done for all of us!!!

Reply | Quote

@jmwoods, esrv_svc.exe is not the Intel Energy Checker… it is a component. The question I asked Woody is what “exactly” is it, which implies what does it do and for what purpose. I came across threads claiming it’s for usage reporting.

Also shouldiblockit.com is not a reliable source for information.

Reply | Quote

You’re welcome…

Reply | Quote

I have only just found this after the update was installed.
[Linx tablet running 8.1]
My engineer admitted defeat after 2 hours.
Cannot even find where it was downloaded or which chip or part of it related too.
Touch screen will not work.
Sound will not work.
Tablet useless.
A moderator or someone needs to urgently feed back for an explanation, repair/patch/update/removal.
This INTEL UPDATE 10.1.1.38 is defective and irreparably damages the system.
If it was possible someone needs to pay.
Therefore an admission or removal or patch not on the cards then.
A very upset long term MS user.
Andy

Reply | Quote

PS.
I did? have restore points.
they were all lost after this update?

It will not restore either.

Reply | Quote

on my dell desktop xps8300 win 7 pro x64 i’m getting offered INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38 as WU optional update. when I select this update and click on “more information” link it just takes me to the Windows 7 help page (https://support.microsoft.com/en-au/products/windows?os=windows-7) which says nothing about this particular update. well done ms, thnx for nothing!

for those still following this post I found some useful info on the intel community forum –
https://communities.intel.com/thread/110057?start=0&tstart=0

Reply | Quote