INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80

Topic

New Reply

I’m seeing several reports of this update appearing as Optional, in Windows 7’s Windows Update. INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80 The
[See the full post at: INTEL – System – 8/19/2016 12:00:00 AM – 10.1.2.80]

Reply | Quote

Replies

Lost control.

Reply | Quote

got it yesterday on my Windows 7 64 bit machine, which had WU settings to get updates for windows only. It was listed under optional, I hid it. Wasn’t going to take the risk. I don’t know if it appeared on my Win 7 laptop, didn’t check.

Reply | Quote

Got it yesterday afternoon on my windows 7 desktop, don’t know about my Win 7 laptop. The WU settings were to get updates for Windows only. I hid this strange update, to me it looks like an error on Microsoft’s end, it doesn’t make sense.

Reply | Quote

according to this link, this should be a chipset driver from Intel.

http://www.catalog.update.microsoft.com/Search.aspx?q=8%2F19%2F2016%2010.1.2.80

Reply | Quote

Yet another MS driver for the ever increasing ignore list on Windows 7.

My Tip:
Stick with intel proprietary drivers.

Reply | Quote

I have this in Ireland, no useful info on microsoft link as per usual

Reply | Quote

Checked for updates related to your post on .NET 4.5.2 & found this. No match related to .NET 4.5.2; as for this, if I download anything, it’s either from Intel or ASUS (my OEM). As the song “You’re a Mean One, Mr. Grinch” goes: “I wouldn’t touch you [it] with a 39 and 1/2 foot pole!”

Reply | Quote

Good catch! But not much info – and it doesn’t line up with the Intel listing. Weird.

Reply | Quote

I think this happened in the past with drivers. Probably the driver was on the Microsoft servers long time ago but somebody finally decided to make it visible to Windows Update. It is possible that this driver’s quality was uncertain and only recently it has been decided to be released.
It is certainly not a mistake, just a bit more mystery added to the never ending Windows Update saga to keep us interested over the Christmas season.
Obviously if not affected by a major issue, it can wait few more weeks or not install at all. This is even more true being in the drivers category and Optional.
Not installing drivers is consistent with Group A style of patching, although from my recent experience, drivers published by Microsoft are more stable than the generic ones from the manufacturer, as Windows Update takes in consideration the hardware ID of the machine when making drivers available. The performance may be poorer though for gamers or those sensitive to it.

Reply | Quote

Did you check what this updated driver actually does before choosing to ignore it?

Hardware makers actually DO improve things sometimes, and such improvements are often documented by them.

I certainly don’t suggest installing it in an information vacuum, but perhaps a “wait and see what this really does” tactic would be appropriate.

-Noel

Reply | Quote

I’m following in many footsteps, I’m sure, Googling this version, but there are only the barest of clues out there as to what was done in this particular version. This is all I turned up (from several separate sites):

—

Release Notes:

Purley – Removed support for USB3 controller

Fixed issue with 2016 certification. Previous build was failing 2016 Signed driver test.

—

Removed support? Not exactly what you’d expect of a legitimate driver update.

-Noel

Reply | Quote

Apparently “Purley” is a new enterprise computing platform umbrella…

https://www.techpowerup.com/212854/intels-post-2017-purley-enterprise-platform-detailed

-Noel

Reply | Quote

It’s certainly NOT listed in my optional updates, it’s in with all the other Important updates and already checked.

Unchecking and hiding here.

Reply | Quote

OUCH! Do you have “Give me recommended updates the same way I receive important updates” checked?

Normally I could look it up in the Windows Update list, but it isn’t in there.

Reply | Quote

Re Intel Chipset Device Software v10.1.2.80 WHQL
The update being offered is the latest WHQL certified version of the Intel Chipset INF file package – which is not even on the Intel site yet – which seems a little odd bearing in mind the release date of August 2016.

If Microsoft are going to push these types of update they might at least give it a proper description – “Intel System Driver” is not even the official Intel name for the package – at least the version number was a big clue.

As you no doubt already know an Intel System Driver (aka Chipset Driver) is a collection of INF files used by the Windows “Plug and Play” (PnP) system to identify and configure any Intel motherboard/processor hardware that you are using. It is normally only necessary to install an Intel Chipset “driver” package when setting up a new motherboard or CPU – and in most cases reloading a newer version of the Intel Chipset driver package is not recommended.

So unless you have any hardware that is not recognised in Device Manager or has features that are not functioning fully – then it is best to leave well alone.

Reply | Quote

I went to Device Manager and expanded System Devices.

Then, right clicked on “Intel(R) Xeon(R) processor E3 – 1200 v3/4th Gen Core processor DRAM Controller – 0C04” and selected update driver software.

It downloaded and installed a new driver, version 10.1.2.80.

Reply | Quote

U would be right in a normal world, but not in the Ms reality. They lost trust and justifyingly so.

Reply | Quote

All 55 of those downloads from the catalog appear to be identical. All have the same filename and running a hex file compare on a random selection of the downloads proved they were identical.

I have no idea why MS choose to list every variation as a different download – the Intel package applies to all the different OS versions listed and covers a mass of different Intel products from USB chipsets, through motherboard chipsets, to Intel CPU’s. There is only one package.

Reply | Quote

Just read raggansta’s post on the German link. Following is a google translation cleaned up a bit.

Yes, I installed it but it has not actualized and …you can not uninstall it at “installed updates”. (no KB number)

There is also no information available under “further information”

Reply | Quote

Atom platform for Windows Server Nano?

Reply | Quote

I was offered this one today on my i7 Win7 x64 computer. I too found no information on it, the link for more info leading to the default page about WU.

As with all third party (i.e. non-MS updates) I promptly hid it as it was unchecked and optional, and I have no interest in updating my firmware etc in the absence of any issues or other compelling reason to do so. If it ain’t broke, I don’t fix it!

As this update is stated to have been released 4 months ago and I’ve had no issues on that machine since then, it’s reasonable to assume that I don’t need to worry about it a few days before Christmas (which is, of course, a much bigger affair here in the UK than it is in the US)!

Talking of which, I offer Woody and all fellow commenters together with their loved ones the very best for both Christmas and the New Year, and in particular I thank Woody for all his invaluable advice and assistance, and of course for hosting this superb site :)!

I look forward to what 2017 brings, as we move inexorably through the countdown to the ending of official support for Windows 7 (and, more pressingly, pre-version 3 editions of MBAM)!

Reply | Quote

Yes, that’s checked. This is a test machine and I’ve set it up like most people would have it.

Reply | Quote

On my system, the following drivers were brought up from previous versions to version 10.1.2.80 – driver dates 8/19/16, with the Intel Windows Update…

Intel(R) 8 Series/C220 Series PCI Express Root Port #3 – 8C14

Intel(R) 8 Series/C220 Series PCI Express Root Port #4 – 8C16

Intel(R) 8 Series/C220 Series SMBus Controller – 8C22

Intel(R) HM86 LPC Controller – 8C49

I manually updated Intel(R) Xeon(R) processor E3 – 1200 v3/4th Gen Core processor DRAM Controller – 0C04
and Intel(R) 8 Series/C220 Series PCI Express Root Port #1 – 8C10 to the same versions and dates in Device Manager.

Reply | Quote

Intel Chipset INF 10.1.2.77 – 08/03/16 Is Not WHQL and has the chipset type CAT/INF files packaged into Intels SetupChipset.exe stand alone installer.

Intel Chipset INF 10.1.2.80 – 08/19/16 via Windows Update Is WHQL and is packaged as separate chipset type CAT/INF files for install by Windows INF installer.

Viper

Reply | Quote

Thanks!

That explains the big change in file size.

Reply | Quote

Yep, it must’ve come out as a “Recommended” update.

Reply | Quote

HARRRRR!

Reply | Quote

It’s a one-way trip. Just what I love in a driver.

Reply | Quote

+1

Reply | Quote

Faulty version of the controller which was found later to be faulty? Or it means removed the poorly signed one and replaced with a valid one?

Reply | Quote

This means a chipset driver update.
There was a microcode update for Intel CPUs a while ago which everyone was in doubt about the suitability of the microcode update to be done at the OS level vs BIOS where is was its place.
It may be something similar in this case.

Reply | Quote

In Windows 8.1 I’m seeing 2 updates…

INTEL – System – 1/1/1970 12:00:00 AM – 10.1.2.80
INTEL – System – 9/15/2016 12:00:00 AM – 11.6.0.1032

I have a feeling I haven’t put any Intel drivers on this new box yet, may explain why there’s 2.

The first has the description “INTEL System Driver update released in January 1970”. I wonder when the earlier one this updates was released, hopefully after Intel was founded in 1968

Reply | Quote

HA!

Reply | Quote

From the Intel forum: “It is an INF Update package (what they now call a ‘Chipset Software’ package) and it wiped out my SMBus driver (which is necessary for Intel Desktop Utilities to get DIMM temperatures), replacing it with a dummy entry…”

Reply | Quote

GACK. Do you have a link?

Reply | Quote

Should be able to do aa rollback in Device Manager…

Reply | Quote

Installed it and no issues.

Step 1 – Disk Image.

Step 2 – Update.

Reply | Quote

https://communities.intel.com/thread/109458

Reply | Quote

@alreadybanned, @Woody,

“…and it wiped out my SMBus driver (which is necessary for Intel Desktop Utilities to get DIMM temperatures), replacing it with a dummy entry…”

Then how the hell did it get past MS and end up in WU?? Does MS just put any executable into an update without checking it??

Wow…as John Oliver says, “Just when you think you’re at the bottom…”

Reply | Quote

There’s likely more to the story….

Reply | Quote

Wow. Thanks!

Reply | Quote

You would think so. Not sure which device is involved though.

Reply | Quote

Multiple drivers involved on my system.

See my earlier posts.

Reply | Quote

Yep.

No issues here.

Reply | Quote

Maybe its to wreck old boxes running Win7. A sneaky way for you to give up and buy a new box running Win10 being that the free upgrade push was not the success they were hoping for. Nothing from MS surprises me anymore.

Reply | Quote

@ ch100 ……. U said, …”. drivers published by Microsoft are more stable than the generic ones from the manufacturer, as Windows Update takes in consideration the hardware ID of the machine when making drivers available. ”
.
.
U got that backwards, ie drivers from the manufacturers/OEMs r more stable than those generic ones from M$. Eg …
http://www.ibtimes.co.uk/windows-10-how-fix-nvidia-driver-issues-after-upgrade-1513643
.
Seems another sneaky attempt by M$ to degrade Win 7/8.1 n push their users onto Win 10.
.
.
P S – Windows Install Media created from M$’s iso files contains only basic generic drivers from M$ for the essential devices/components of a cptr(eg the motherboard, HDD/SSD, display/monitor, keyboard n mouse, etc) n may lead to poorer performance, esp for the graphics/video adapter.
……. In such a clean installed Windows system, it is better to update M$’s generic drivers with those better/up-to-date ones from the manufacturers/OEMs website.
.
B4 2012, OEMs, eg Dell, HP, Lenovo, Acer, etc, used to provide free Win 7 Install DVDs that contained all the necessary n up-to-date drivers from the OEMs, n not from M$.

Reply | Quote

@ ch100 ……. Also, this link …
http://www.wisegeek.org/what-is-a-chipset-driver.htm

Reply | Quote

Reading these posts just gave me an “I wonder if” moment. Here is an interesting set of coincidences involving Intel USB 3.0, unsigned drivers, and Intel Bluetooth.

On Monday night I was doing some updates on my Lenovo Thinkpad Edge E440 laptop with Win7-64 Pro. This is the laptop where I had the issue with the Intel Bluetooth Drivers conflicting with the WU speedup patch KB3172605. The laptop is an i5 based upon an Intel 8 Series chipset MB.

I did a run of the Lenovo update tool and it showed 3 updates available, Intel Bluetooth Drivers, Intel WiFi Drivers (both noting the KB3172605 in the change log and specifying the order to install them), and a third update for Intel USB 3.0 Drivers. Since I had already resolved the Intel BT driver and Windows Update speedup conflicts, I steered clear of the WiFi and BT packages. I chose to update the USB 3.0 drivers as the laptop would sometimes fail to detect a USB 3.0 thumbdrive. I created a restore point just in case (once burned…)

Installation went OK, but on reboot, I noticed it was slow to install the drivers. Warning #1 – slow to install new device software. Warning #2 – small BT icon failed to appear (similar to WU conflict when I did the KB3172605). BIG WARNING #3 – the Logitech USB wireless mouse would not work at all, nor would the USB 3.0 ports.

Inspection of Device Manager showed an “unknown device”. Process of elimination and a former screenshot of the Device Manager data showed it was the Logitech HiD USB mouse.. Second reboot was the same, however the Action Center showed failure to load unknown device driver – unsigned driver, AND a warning that the wireless LAN was not working.

Did a system restore to the restore point I had created and it was all fixed.

Now this driver package for the Intel USB 3.0 was from Intel via Lenovo, not WU. The drivers were apparently unsigned, and it disabled the USB 3.0 ports and affected a USB mouse as well as Intel Bluetooth.

I just checked WU and my system has not encountered any WU delivered updates related to Intel or USB 3.0. I never use WU for any hardware drivers, I just go the PC or device manufacturer websites.

What was interesting was the unsigned driver did not warn on install, as I have had happen on other machines and other drivers. You could still install them, but it warned of potential problems in advance.

I do not have a server, or a Xeon processor, but I wonder if this coincidental or if it was a bad Intel driver release that slipped into various distribution channels.

Reply | Quote

I think they removed the support of the USB 3 Root Hub for Windows Server installed on Desktop grade hardware. Intel has a history of doing it, in particular with some ATI Graphics Cards.

Reply | Quote

It is Recommended not Optional, but the machine has to have a particular hardware chipset which is desktop grade.
Noel refers to the removal of drivers for a specific USB 3 controller, but that applies only to Server OS installed on cheap desktop hardware, not to Desktop OS.
There is information about uninstalling this chipset driver but I cannot find it right now.

Reply | Quote

Very likely that you are right, at least this is the principle of installing Chipset “drivers”. We should wait a bit longer though to understand better the purpose of this release. It may be simply addressed to those who install new systems and this would be consistent with your post.

Reply | Quote

Is your USB 3 Root Hub still working?

Reply | Quote

Bluetooth anyone? Might be a fix/workaround for the issue in KB3172605?

Reply | Quote

I found the new driver removes the driver for USB 3 Root Hub, but only for Server OS installations. Does it remove the SMBus support for Windows 2008 R2 or Windows 7?

Reply | Quote

For a better understanding of the Intel Chipset Utility, this is good reading
http://www.intel.com/content/www/us/en/support/boards-and-kits/000005835.html

Reply | Quote

This optional update just updates some device ID strings for newer Intel hardware – and it installs “null drivers” without a functions. I’ve published a few further details with my findings/interpreations at:

http://borncity.com/win/2016/12/22/windows-optional-update-intel-system-8192016/

Reply | Quote

so is it safe to install or should i ignore it for now?

“if it ain’t broke don’t fix” ?????

Reply | Quote

Get the 10.1.2.77 from Intel and install with -overall switch.
It is the best of all worlds.

Reply | Quote

10.1.2.77 seems to me to be the good one.
If you have a functional Chipset INf already installed, it is only waste of time to “upgrade”.

Reply | Quote

+1 As fp has stated
Microsoft’s opportunity to inject additional code to snoop via their update policy of late.

I have noticed that OEM manufacturers have jumped on the Microsoft snooping bandwagon with graphics cards etc..but, at least you can switch the snooping off with our chosen hardware oem’s.

Reply | Quote

Our PC’s work fine without it.

Reply | Quote

W7 pro 64, hidden the update it looks suspicious.

Reply | Quote

Yep I saw this yesterday on a HP Microserver running Server Essentials 2012R2

Reply | Quote

Seen Gunter Born’s comment.

Ain’t broke, don’t fix.

Reply | Quote

Yep, that nails it. The whole story.

It’s an honor to have you here!

Reply | Quote

Vielen Dank Herr Born

Reply | Quote

I’ve always said when it comes to hardware drivers provided by MS… “if it ain’t broke don’t BREAK it”!

Reply | Quote

HA!

Reply | Quote

FYI this “optional” update just showed up this morning on my Windows 8.1 64-bit system. It was “unchecked”, so I ignored it, for now.

Reply | Quote

I’ve been building computers for over 15 years, and one thing I’ve learned is never let Microsoft update your drivers.

I always get the latest drivers direct from the hardware OEM website, such as Intel, AMD, or nVidia, etc.

After installing the motherboard and other internal components on an Intel based system and after installing Windows, the PC is running on Microsoft supplied generic drivers. The MB chipset, any 3rd party enhanced components, drivers for graphics, network, sound, etc., are not likely running well, if at all, but your system is up and you can finish the job.

The next thing you do is install the correct drivers for your specific hardware obtained from the manufacturer.

The exception here might be when connecting a supported printer or scanner type device where Windows goes out and gets the correct drivers.

Typically when Microsoft suddenly shows up with a system driver, it is because your system matches some generic list. They really don’t know much about your specific PC. To assume they know better than you do, LOL!!!!!!!!!!!!

I have had a few occasions where it was necessary to roll drivers back, or uninstall drivers that were installed by Windows.

Best just to add them to ignore list, and then search your OEM for updates, if they exist. There may be a few cases where you are running older, manufacturer end-of-life hardware and Microsoft is the only store in town. But seriously, then it may be time to get a new system

Reply | Quote

Thanks everyone for the input. The other day, 3 Intel updates showed up in the “important” updates and wasn’t sure if I should install those. I’m not sure how Microsoft decided that they are important to my server(the heart of my AD network!) but I’m really happy I found this thread. I will not install them, at least for now.

Reply | Quote

@ Gunter B ……. Quoting from the link, …”My conclusion: The purpose of these null drivers is, just define device IDs for several components on a main board and show the related „Intel(R)“ branding within device manager. I guess, it’s a kind of placeholder, in case Microsoft ships device driver updates in future.
What I haven’t understood till now: Why the update from August 2016 is released now, in December 2016.”
.
The placeholder may be like a time-bomb which can be triggered by M$ at any time to brick Intel-based Win 7/8.1 cptrs, in order to force them to buy new OEM/Intel Win 10 cptrs.

Reply | Quote

Highly, highly unlikely.

I would say “impossible” except, well, Get Windows 10.

Reply | Quote

+!

Reply | Quote

Are you running the “new” HP Microserver with Intel CPU?

Reply | Quote

@ woody ……. It is a fact that since the release of Win 10 on 29 July 2015, excessively-greedy M$ cannot be trusted, esp by Win 7/8.1 cptr/server users.
……. These Intel-System null-driver updates were created by M$ in Aug 2016 n postponed to Dec 2016. The likely reason being they r “time-bomb or booby-trap” updates. Likely the postponement was bc M$ were in 2-minds about releasing such controversial, “destructive” or “breaking” updates so soon after the 02 Aug 2016 buggy Anniversary Update debacle.

Reply | Quote

Don’t click the red x….take the red pill.

Reply | Quote

I decided to hide these updates. All is very suspicious. This is exactly the attack. The only question is, whether this is absolutely a malicious attack or (as it was said above) it some kind of MS empowerment.
I do not need this any way.
Thank you for this topic.
By the way, these updates are already two updates: the second one (which is similar as first but has another date) has come today.

Reply | Quote

I don’t think so. We’re starting to see several other, similar updates. I don’t know why MS decided to ship them now, but it looks like they’re trying to cover all sorts of hardware configurations.

Reply | Quote

on my win update, i’m seeing an extra intel update in addition to the one described here.
is anyone else getting this?

intel – system – 3/13/2016 12:00:00 AM – 11.0.0.1010

Reply | Quote

Yes – I see that one now as well.

Intel – System – 3/13/2016 12:00:00 AM – 11.0.0.1010

Download size: 3.0 MB

You may need to restart your computer for this update to take effect.

Update type: Optional

Intel System driver update released in March 2016

More information:
http://sysdev.microsoft.com/support/default.aspx

Help and Support:
http://support.microsoft.com/select/?target=hub

Reply | Quote

I’m willing to say impossible
but some just love to embrace the conspiracy theories

Reply | Quote

That update was for the case that you hid the previous update. MS is nervous because the Windows 10 adoption rate is too low. They know they need to break Windows 7 for untechnical people to force migration. This update is their second attempt after the previous august 16 update.

MS Windows is slowly becoming a joke.

Reply | Quote

@ SuspiciousMS

+10

Reply | Quote

PLS DONT DESTROY!

Reply | Quote

It’s because nobody wants there **** DRM and forced updates.

Reply | Quote

This also showed up in my December Update:
Intel – System – 3/13/2016 12:00:00 AM – 11.0.0.1010

Download size: 3.0 MB

You may need to restart your computer for this update to take effect.

Update type: Optional

Intel System driver update released in March 2016

More information:
http://sysdev.microsoft.com/support/default.aspx

Help and Support:
http://support.microsoft.com/select/?target=hub

Do I trust it? NO WAY!!

I won’t install it – if it ain’t broke, it doesn’t need fixin’.

Reply | Quote

The Intel Chipset drivers never contained drivers.

Here is an article describing what the chipset drivers do.

Full article link:
http://www.win-raid.com/t895f42-Intel-Chipset-Device-quot-Drivers-quot-INF-files.html

Preliminary Notes regarding Intel’s Chipset “Drivers”

The “Intel(R) Chipset Device Software” (formerly named “Intel(R) INF Update Utility”) seems to be the most overestimated “driverpack” for Intel Chipset system:
Only a minority of the Intel Chipset users know, that the on-board Intel Chipset devices are working fine without any “Intel(R) Chipset Device Software”. In various Forums you can read the advice to install the “latest Intel Chipset Drivers” as first and much important step after the installation of any Windows Operating System. Otherwise the users will never get a stable and performant system.

The reality is quite different:

Although the Device Manager shows the information files as “drivers”, the “Intel(R) Chipset Device Software” doesn’t contain any real driver (= .SYS file), but just textmode (= .INF) files, which
a) let the OS know, that for the related Intel Chipset Device a driver is neither needed nor available and
b) gives the user the information, that the related device is an Intel one.
None of the Windows Operating Systems needs the .INF files for a proper functionality.
The Intel Chipset “drivers” don’t have any impact on the performance of a system.

If you don’t believe me, please read >this< official statement from Intel regarding the importance and the function of the "Intel(R) Chipset Device Software".
Here is the summary:

Zitat von Intel

The Intel Chipset Software Installation Utility is not a driver and does not include drivers.
The Intel Chipset Software Installation Utility gives the product name for the piece of hardware. This information allows the operating system to display the correct name for that piece of hardware in Device Manager.

My conclusions:

The installation of any "Intel(R) Chipset Device Software" or their included INF files is only useful, if the Device Manager shows a yellow mark at an Intel (VEN_8086) device with a "missing driver".
Since the newest Windows Operating systems are able to detect and to name by their own all Intel chipset devices, which were on the market at the release of the OS, there is usually no need at all and no benefit for the users to install or update the Intel chipset device INF files (often named by mistake "Intel chipset drivers").
Only users with a brandnew Intel chipset (from 8-Series up for Windows 7, from 9-Series up for Windows 8/8.1) or a very old Windows OS should install the latest suitable *.INF files for their specific Intel Chipset Devices to get rid from the "missing driver" message within the Device Manager.
Forcing the installation of a not required or already present Intel Chipset Device INF file (e.g. by using the " -overall" command) doesn't make any sense, but will blow up the user's registry and the Windowsinf folder with garbage (unused resp. unusable oemxx.inf files). Furthermore the forced installation of unusable drivers generally may overwrite actually in use other drivers and can cause degraded performance or a lack of features.

Reply | Quote

@ Jstar …….
.
A++1

Reply | Quote

In fact this package is useful as the article says, to identify correctly the devices in Device Manager and not only if they show a yellow mark. Windows places generic labels on the devices affected by this package and the best drivers may not be installed, only “generic” ones with basic functionality.
It is Optional though, and users should treat this package in the same way like they would treat the other Optional Windows patches.
The technically minded people generally install them, because they are interested in the additional functionality provided, while the others generally don’t, because … well, it is much easier to complain and look for imaginary issues than to use the same amount of time to learn something new.

Reply | Quote

I hid the original optional Intel update described here, but in device Manager I updated drivers to a number of items in System.

Now, Windows Update is offering the optional update INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38

Shall hide this one also. Amazing that there are no descriptions or explanations, except here at Ask Woody.

Reply | Quote

There’s never any reason to hide any updates.

Take a look here: https://www.askwoody.com/2016/bottom-line-dont-install-the-intel-system-8192016-120000-am-10-1-2-80-patch/#comment-112247

The situation is much more complex. I’d like to dig deeper, if there’s additional info.

Reply | Quote

I have installed the update on server 2012 and 2012R2 with no problems.

I run all the updates because if I MS for tech then they say “fully update windows then call me back”.

it is true that some updates have broken things but overall the updates are needed.

Reply | Quote

Why do you think the updates are needed? I assume you installed the 8/19/2016 version.

Reply | Quote

To be honest I have been on the phone with MS so many times over the years that I just keep my servers and workstations fully updated.
I would say that 90% of the servers and workstations that I have taken over or created have benefited greatly from this in terms of speed and availability.

Reply | Quote

Also, I don’t know what it is for. I tend to error on the other side of your guys thoughts…

Reply | Quote

Fair enough. Wish I could figure out what they’re supposed to do…

Reply | Quote

Same

Reply | Quote

Hi, I honestly don’t know how I get here but I installed this optional controlers assuming it was something necessary (it was not) and now I have continuous blue screen and my laptop shuts down and restarts. I figured it out it was when I installed the following drivers:

Intel – System – 3/13/2016 12:00:00 AM – 11.0.0.1010

INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38

INTEL – System – 10/3/2016 12:00:00 AM – 10.1.1.38

The three of them. When I go to my device manager and search for new updates or something it appears the blue restart screen and now I’m wondering, is there anyone who knows how to uninstall these drivers?

I have tried to restore the system to a restore point but as I recently formatted my laptop, there were none. I would love to know if someone can help me to unistall them or do something about them. I’m thinking about reformat again which sounds a bit like not a good idea.

Thank you in advance.

Reply | Quote

Hmmm… Let’s separate out the symptoms.

When you start your machine, you’re able to get Win7 going, yes? (I assume because you mention getting into Device Manager.) When go you go into Device Manager, what precisely triggers the Blue Screen?

Reply | Quote

Thanks for answering, okay. I have win8 and yes, I can get to my desktop

I select (translated from Spanish) “Search for changes in hardware” and then it appear the blue screen. that’s it. It also happens when I disconnect the battery charger.

Reply | Quote

Unless you know how to collect a memory dump of the BSOD, you can bet on 2 things.
– Graphics card driver is the main suspect
– Faulty RAM can cause those issues, but more likely freezes than BSOD

I suggest the following:
Uninstall any Graphics Driver either from Programs and Features or from Device Manager, including deleting drivers. Use only basic Microsoft driver and try to reproduce the problem.
If the problem still exists, run a memory checker, Windows has a built-in one, but it is worth trying memtest http://www.memtest86.com/
running for few hours.

If you are on Windows 8 (and not 8.1) as it appears from your post, upgrade to Windows 8.1. Fully patch your system and include all non-optional drivers if they are presented. However install drivers last, after you install all Windows patches, Important, Recommended and Optional (except drivers and those with Preview in title).

Reply | Quote

Sounds like a good diagnosis to me.

Reply | Quote

From an elevated (Run as Administrator) Command prompt, run the following…

sfc /SCANNOW

If it find errors it cannot fix, download and run SFCFix by niemiro from Sysnative…

http://www.majorgeeks.com/files/details/sfcfix.html

Reply | Quote

If SFCFix fails, follow the steps in Shawn Brink’s tutorial on EightForums for using DISM to repair corruption…

https://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

Reply | Quote

Oh my, Hi everyone! Thanks for the overwhelming support, I will be applying some of these steps as soon as I start the next day, for now I’m sleepy and expecting to have a goodnight.

So again, thank you all for the support and I will be updating tomorrow.

Best wishes.

Reply | Quote

Hi, thank you for your suggestion. I’m applying it right now unistalling all Graphics Driver both Intel and NVIDIA. I’m not really a fan of W8.1 it would be nice if you could give me more info about what you’re saying about ‘Fully patch your system and include all non-optional drivers if they are presented. However install drivers last, after you install all Windows patches, Important, Recommended and Optional (except drivers and those with Preview in title).’ This last sentence. You mean that by installing W8.1 I automatically fully patch my system. Please help.

Thanks again.

Reply | Quote

You mean that by installing W8.1 I automatically fully patch my system? *

Reply | Quote

UPDATE: Okay, with the first sentence of your suggestion my problem was solved! YAY Now, without installing W8.1 all is good, my questions are: now should I update the drivers I’ve uninstalled? I have VAIO so, there’s an option to update drives through the VAIO Update interface. Should I update them now?

And my other question is: I have now those drives of Intel that got me into all of this, how I unistall them? Because I already tried to remove them through Installed Updates but they do not appear figurative. I honestly don’t want them in my laptop. I would love to know if they can be unistalled and how. I thought that uninstalling the Intel driver they would go away but they didn’t.

So, thank you so much primarily for assisting me in this crazy mess. I will wait for your response to proceed to make any movement.

Thanks alot.

Reply | Quote

@Cristian
I see that you are not a regular reader here.

First thing first: Windows 8 does not officially exist any more like Windows XP. If you don’t upgrade to Windows 8.1, nobody will be able to help you and Microsoft Support would hang up.
The official and free way to continue using Windows 8 based on the original licence is to upgrade to Windows 8.1 from the Store. If you have an ISO image to do a cleaner upgrade is even better.
Once you have Windows 8.1 you need to install everything coming on Windows Update, less drivers and everything means EVERYTHING. Only then you are in a supported scenario.

Reply | Quote

New comment on Intel forum posted Feb 15th.

https://communities.intel.com/message/454035#454035

Contains this tidbit ….

Intel® Chipset Device Software Update Through Microsoft Windows* Update Overwrites Existing Device Drivers Causing Loss of Functionality (SMBus)

http://www.intel.com/content/www/us/en/support/software/chipset-software/000023446.html

Windows 10 Pro 22H2

5 users thanked author for this post.

walker, satrow, woody, ch100, PKCano

Reply | Quote