Cumulative Update KB4345421 Windows 10 v1803 Build 17134.167 - July 16

hana0 said:

I only check for updates manually, and still didn't get it



If you were referring to the microcode update, can you please check if your CPU is on the list.

https://support.microsoft.com/en-us/...windows-server

I checked and my 4790k isn't on the list.

Bree said:

Waiting for Microsoft to provide a microcode update is the second-best way to get updated microcode. The preferred solution is to get an updated bios from your OEM that will include the updated microcode. Have you checked to see if one is available?

Asus seems to be more lazy than Microsoft , my last bios built date is 01/jan/2018 and in the site Asus claims it to be on 02/mar/2018., although my laptop is not that old.

The reason Intel and Microsoft release microcode updates cause it is easier and quicker than bios releases.

I do check for bios update regularly as well

If it wasn't for this forum, I'd miss all the non-patch-Tuesday updates. These odd updates never arrive automatically. Have to perform a manual check.

This one installed without a hitch on the 2 P.C.'s in our home. Though it looks like it's directed primarily towards enterprise deployments?

hana0 said:

Why would I hate it? I would love to be up to date!

Intel does update microcode for Linux regularly, but unfortunately Microsoft will update it only for major security vulnerability.

Download Linux* Processor Microcode Data File

Open a support thread with the laptop manufacturer and post the links to the security advisory and the microcode update. I'm fortunate that my desktop has a BIOS I can edit manually (but to be fair Gigabyte are great with the support they will send a modded BIOS), however my laptop manufacturer is on the "not so great" list with very patchy support.

I did briefly own a modern Dell and I got an email from them saying the UEFI update had been released and it was an urgent update.

SSB mitigation does require the new July MCUs but why would MS include OS support and not revise the standalones or even send them via WU?

winactive said:

Open a support thread with the laptop manufacturer and post the links to the security advisory and the microcode update. I'm fortunate that my desktop has a BIOS I can edit manually (but to be fair Gigabyte are great with the support they will send a modded BIOS), however my laptop manufacturer is on the "not so great" list with very patchy support.

I did briefly own a modern Dell and I got an email from them saying the UEFI update had been released and it was an urgent update.

SSB mitigation does require the new July MCUs but why would MS include OS support and not revise the standalones or even send them via WU?

Guys! you really miss my point from the questions.

I don't need the last microcode, or I don't need to install the last windows update. I am happy with the last version released from Microsoft.

my question is that I am not getting them automatically in windows update, and I have to install the packages manually!

From the Microsoft website, how to get the microcode update:

How to obtain and install the update
Method 1: Windows Update
To download and install this update, go to Settings > Update & Security > Windows Update and then select Check for updates. If Windows Update says your device is up to date, you have all the updates that are currently available.

Is it just me who has to install the packages manually?

hana0 said:

Is it just me who has to install the packages manually?

This is the issue I've been struggling with for some time now. The last cum. installed automatically, but the ones prior to that did not and had to be triggered via WU in Settings. Task Manager on my system is actively kicking off the sih task, but it's not getting this latest update. WU in Settings checks every evening (sometime after 8:00PM) but has yet to get a hit for this 07/16/18 cum. I would bet that if I had WU check for updates in Settings, I'd get this cum. I obviously don't understand the automatic update process yet.

hana0 said:

Guys! you really miss my point from the questions.

I don't need the last microcode, or I don't need to install the last windows update. I am happy with the last version released from Microsoft.

my question is that I am not getting them automatically in windows update, and I have to install the packages manually!

From the Microsoft website, how to get the microcode update:

Is it just me who has to install the packages manually?

jamis said:

This is the issue I've been struggling with for some time now. The last cum. installed automatically, but the ones prior to that did not and had to be triggered via WU in Settings. Task Manager on my system is actively kicking off the sih task, but it's not getting this latest update. WU in Settings checks every evening (sometime after 8:00PM) but has yet to get a hit for this 07/16/18 cum. I would bet that if I had WU check for updates in Settings, I'd get this cum. I obviously don't understand the automatic update process yet.

You do know they are staged and applied in order of need? The .167 release is a bugfix of .165 build. It's really not essential unless you have the explicit issue in the patch notes.

It might be your machine is not on a fast update track (depends how often it's used, or whether updates are scheduled or postponed or not restarted after completion).

Also, manual install of some patches has been known to break the automatic installation, I guess via some corruption or mismatch in the service stack. These last two cumulatives; the standalone advice is to install the SSU before the full CU. I don't know if you did this because if you just install the update without reading the notes then you might have missed that.

winactive said:

You do know they are staged and applied in order of need? The .167 release is a bugfix of .165 build. It's really not essential unless you have the explicit issue in the patch notes.

It might be your machine is not on a fast update track (depends how often it's used, or whether updates are scheduled or postponed or not restarted after completion).

Also, manual install of some patches has been known to break the automatic installation, I guess via some corruption or mismatch in the service stack. These last two cumulatives; the standalone advice is to install the SSU before the full CU. I don't know if you did this because if you just install the update without reading the notes then you might have missed that.

Let me ask you a direct question! If you didn't manually update Intel microcode, can you please tell me what is the version of the file mcupdate_GenuineIntel.dll ?

hana0 said:

Let me ask you a direct question! If you didn't manually update Intel microcode, can you please tell me what is the version of the file mcupdate_GenuineIntel.dll ?

10.0.17134.1 the patched one is 10.0.17134.48

It isn't in the file manifest for that cumulative either.