The late Feb “optional, non-security, C/D Week” patch is out but only for Win10 version 1809 and 1709. Win8.1 preview is also out.

Topic

New Reply

I take this as a good sign – that Microsoft’s spending more time on testing the Win10 1903 and 1909 patches, but then again the Win10 1903 and 1909 “o
[See the full post at: The late Feb “optional, non-security, C/D Week” patch is out but only for Win10 version 1809 and 1709. Win8.1 preview is also out.]

1 user thanked author for this post.

Pepsiboy

Reply | Quote

Replies

woody wrote:

I take this as a good sign – that Microsoft’s spending more time on testing the Win10 1903 and 1909 patches, but then again the Win10 1903 and 1909 “o
[See the full post at: The late Feb “optional, non-security, C/D Week” patch is out but only for Win10 version 1809 and 1709. Win8.1 preview is also out.]

Woody,

I got KB4539601, (Preview Monthly Quality Rollup) this morning for my Win7 HP x64 machine. It came in as “Optional”. Of course, I’ll not be installing it.

Dae

Edit: KB number corrected,

1 user thanked author for this post.

woody

Reply | Quote

I assume you’re paying for Extended Security Updates?

Reply | Quote

woody wrote:

I assume you’re paying for Extended Security Updates?

Woody,

NOPE ! ! !  Too limited income. Can’t afford it yet.

Dave

Reply | Quote

Hey woody, I’m on 1809 Home and as of writing this today I’ve been offered only the following updates (detected through wushowhide):
– KB4538156 2020-02 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8;
– KB4494174 2020-01 Update for Windows 10 Version 1809

The Knowledge Base article for KB4494174 states the following:

“Intel Microcode for the following products (CPUs) have been updated.
Updated January 30, 2020 and February 25, 2020
Denverton
Sandy Bridge
Sandy Bridge E, EP
Valley View
Whiskey Lake U”

Am I safe to assume that I can skip this microcode update if my system is not based on any of the above CPUs?

Reply | Quote

I would wait until it affects your CPU.

2 users thanked author for this post.

Berserker79, woody

Reply | Quote

what kind of CPU do you currently have, Berserker79?
use the CPU-Z tool to identify the processor on your computer.

give the KB4494174 update a pass – no need to download & install it yet

I, on the other hand, am using an Intel Sandy Bridge based Dell Inspiron PC (intel core i5-2500) running v1809 that already has the KB4494174 update installed (I manually installed KB4494174 V3 thru the MS Catalog site and not thru WU)

1 user thanked author for this post.

Berserker79

Reply | Quote

Hi EP!

I have a Skylake S CPU (i7-6700K) which I realized is in the (full) list of affected CPUs, albeit it is not one of those in the “Updated January 30, 2020 and February 25, 2020” short list. Unless there is a pressing issue, I’m waiting to install this patch

BTW, I think that what got me confused about this update is that I was under the impression that I had already installed it some time ago. However, it does not show up in the list of installed updates, which leads me to think that I may have installed an earlier version of the corresponding patch for Windows 10 1803 back in September, shortly before I did the update to 1809.

Reply | Quote

I’m on 1809 home(AMD APU based laptop only) and I have not been offered any updates that are optional via the normal route so I’m not worried just yet until some folks do some  KB vetting for that patching.

1809 0nly has a few months more before that feature update forcing occurs and I really hope that when I’m updated to 1909 that most of the issues are fixed. I’ve never been offered 1903 but my laptop is only been booted up for the first time on Feb 12 2020.

I’m on an AMD 3000H series APU so microcode updates are rarer for any Spectre/Meltdown/newer issues unlike my Intel based laptops that run Westmere(Arrandale mobile) through Ivy Bridge mobile Intel core i series processor generations.

Reply | Quote

1903/1909 will be allways delayed behind

Win 8.1 preview patches are ready since patch tuesday, why they delay them?
they don’t want the Win10 group to feel less important? 😀

1 user thanked author for this post.

geekdom

Reply | Quote

Windows 10 Pro ( 1903 ) KB 4497165 Intel microcode update just came down the tube. Wait until Woody gives the okay or is one of those “hide it” updates?

Reply | Quote

Just did read 2171187 post and my CPU ( Skylake ) is not in the list either, so I hid it.

Reply | Quote

I don’t think #2171187 is the whole story. Read kb4497165 applies to version 1903 and 1909. It says there: “This new release includes a microcode update from Intel for the following CPUs”. Skylake D/H/S/Server/U/U23e/W/X/Xeon E3 processors are listed there.

1 user thanked author for this post.

jburk07

Reply | Quote

Yes, I would like to know, too.

KB4497165 seems not to be an optional, non-security update, but the MS catalog does not indicate that it is a security update either.

So, what kind of update is KB4497165? Does it update the BIOS? If it is a BIOS update, isn’t it better to get the update from the manufacturer of the device (e.g., DELL I get update notices from DELL specifically for my device, but I have only recently received one notice– to update the Wi-Fi adapter, which I have done.)

Is it safe/advisable to install KB4497165 now? Or should one keep it hidden until MS-Defcon is 3+?

Or should one wait until the manufacturer provides the update? {I know this involves INTEL processors, but presumably INTEL communicates with the device manufacturers and presumably the manufacturer then prepares the updates for its own machines}

Reply | Quote

BIOS(UEFI) updates come from the OEM and Windows 10 like Linux has a OS method as well for shimming in the CPU microcode updates via the OS path regardless of the PC’s/Laptop’s OEM taking the time to do that micro-code patching via a firmware  update.

I’m dual booting Windows 7(EOL)/Linux Mint 19.3 on 3 older Intel core i series CPU based laptops and some of those older laptops are never receiving any firmware updates from their OEMs. So under Windows 7 no Intel micro-code patching can be done via that OS while under Linux Mint I’ve already had new Intel micro-code patches offered with Mint 19.3.  So for online usage I boot them under Mint and 7/7 Pro (EOL) is booted up for offline usage only. I’ve not much choice there as the laptop’s have been declared legacy by their OEMs for years now and that arrangement with Mint still gets the Intel Micro-Code patching via the Linux kernel.

Firmware updates are a big risk on laptops anyways compered to some PCs(motherboards) that ship with dual BIOS(UEFI) options, or even dedicated BIOS/UEFI flashback features where the MB’s BIOS/UEFI can be flashed without a CPU present in the MB’s CPU socket.

Reply | Quote

Did you answer my main questions or not? I can’t tell.

My main questions were: what kind of update is KB4497165? Does it update the BIOS?

My devices are not legacy O/S’s. Win10/Pro version 1909 One is Skylake U and the other is Whiskey Lake U.

Reply | Quote

The microcode patches Windows software. It does not flash a BIOS chip.
I’m not sure of the implications with UEFI. UEFI is different from BIOS.

1 user thanked author for this post.

Reply | Quote

PKCano wrote:

UEFI is different from BIOS

It’s not really.
BIOS is still the software to tie the motherboard chips together so you can run an OS.
UEFI is a different boot mechanism which makes file placement simpler and potentially prevents rootkits if you use secure boot.

cheers, Paul

Reply | Quote

So the microcode patches are s/w on Win and don’t affect (make changes in) the UEFI either?

Reply | Quote

Paul T wrote:

BIOS is still the software to tie the motherboard chips together so you can run an OS. UEFI is a different boot mechanism which makes file placement simpler and potentially prevents rootkits if you use secure boot.

Actually it’s a little more involved than that.  UEFI can support legacy BIOS; legacy BIOS cannot support UEFI.

“BIOS (/ˈbaɪɒs/ BY-oss; an acronym for Basic Input/Output System and also known as the System BIOS, ROM BIOS or PC BIOS) is firmware used to perform hardware initialization during the booting process (power-on startup), and to provide runtime services for operating systems and programs.  The BIOS firmware comes pre-installed on a personal computer’s system board, and it is the first software to run when powered on. The name originates from the Basic Input/Output System used in the CP/M operating system in 1975.  The BIOS originally proprietary to the IBM PC has been reverse engineered by companies looking to create compatible systems. The interface of that original system serves as a de facto standard.

The BIOS in modern PCs initializes and tests the system hardware components, and loads a boot loader from a mass memory device which then initializes an operating system. In the era of DOS, the BIOS provided a hardware abstraction layer for the keyboard, display, and other input/output (I/O) devices that standardized an interface to application programs and the operating system. More recent operating systems do not use the BIOS after loading, instead accessing the hardware components directly.

Most BIOS implementations are specifically designed to work with a particular computer or motherboard model, by interfacing with various devices that make up the complementary system chipset. Originally, BIOS firmware was stored in a ROM chip on the PC motherboard. In modern computer systems, the BIOS contents are stored on flash memory so it can be rewritten without removing the chip from the motherboard. This allows easy, end-user updates to the BIOS firmware so new features can be added or bugs can be fixed, but it also creates a possibility for the computer to become infected with BIOS rootkits. Furthermore, a BIOS upgrade that fails can brick the motherboard permanently, unless the system includes some form of backup for this case.

Unified Extensible Firmware Interface (UEFI) is a successor to the legacy PC BIOS, aiming to address its technical shortcomings.”

“The Unified Extensible Firmware Interface (UEFI) is a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the legacy Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers, with most UEFI firmware implementations providing support for legacy BIOS services. UEFI can support remote diagnostics and repair of computers, even with no operating system installed.

Intel developed the original Extensible Firmware Interface (EFI) specifications. Some of the EFI’s practices and data formats mirror those of Microsoft Windows.  In 2005, UEFI deprecated EFI 1.10 (the final release of EFI). The Unified EFI Forum is the industry body that manages the UEFI specifications throughout.

The interface defined by the EFI specification includes data tables that contain platform information, and boot and runtime services that are available to the OS loader and OS. UEFI firmware provides several technical advantages over a traditional BIOS system:

Ability to use large disks partitions (over 2 TB) with a GUID Partition Table (GPT)
CPU-independent architecture
CPU-independent drivers
Flexible pre-OS environment, including network capability
Modular design
Backward and forward compatibility”

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

Microcode patches are runtime changes to the BIOS to mitigate CPU issues. If the PC manufacturer provides them they are done as a firmware update.

UEFI can be changed from the OS, e.g. to update secure boot certificates (KB4524244) or change the boot order for recovery (Hold Shift when you click shut down in Windows).

cheers, Paul

Reply | Quote

Microcode patches are runtime changes to the BIOS to mitigate CPU issues. If the PC manufacturer provides them, they are done as a firmware update.

Is this an either-or statement? In other words, if one has already performed the OEM’s firmware update (like 6 months ago), then one does not have to do this recent microcode patch that is a runtime change to the BIOS (BIOS mode is UEFI)?

I ask because DELL’s advisory about INTEL-SA-00233 is to be sure you have the listed BIOS or higher, be sure you are up-to-date with the CU patches, and be sure to apply the applicable OS patch, which is required to mitigate these Intel-SA-00233 related vulnerabilities.

As I read this, it sounds like you have to do both: have the firmware update AND run the OS patch.

Reply | Quote

I don’t know the logic but expect that Windows microcode updates check the CPU code version before patching.

cheers, Paul

1 user thanked author for this post.

Reply | Quote

I repeat, it’s a little more involved than that.  Have a look at

Adventures with UEFI

Converting a re-build from MBR to GPT

Backing into a dual boot in UEFI

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We were all once "Average Users". We all have our own reasons for doing the things that we do with our systems, we don't need anyone's approval, and we don't all have to do the same things.

Computer Specs

Reply | Quote

Only the Laptop’s/PC’s OEM that built the device can provide the BIOS/UEFI(Firmware) update and one has to use the OEM’s provided software/mechanism and specific device’s firmware for flashing ones UEFI/BIOS firmware onto that specialized motherboard chip. And on laptops that’s requiring that the laptop remain plugged in and on mains power and if the power is disrupted  and the BIOS/Flash update becomes corrupted then that laptop can be effectively bricked and needing a trip to the OEM’s regional repair center or authorized repair provider if closer.

Now both the Old BIOS(Legacy firmware method) and UEFI(Uniform Extendable Firmware Interface)  are both Firmware(Software and data tables) that’s flashed onto a special chip on the device’s motherboard. so I do not think that MS’s KBs are made use of to my knowledge to push out OEM firmware updates to flash one’s specific device/motherboard UEFI/BIOS chip.

These Intel/Whatever CPU/processor microcode updates can be delivered via what is referred to as a non firmware based microcode “Shim” where that can be done via the OS via a startup Shimmed in  microcode patch. And Linux has offered that method for eons and only under Windows 10 is that OS based easy to accomplish “Shim” method made available for Windows users. And that’s very useful to have in the absence of any OEM provided firmware update that may be a long time coming, if ever, on older OEM PC/Laptop hardware that’s mostly been declared as legacy and out of support by the OEM that manufactured the computer.

It’s better to have the device’s firmware flashed with the proper Intel microcode update but in reality the OEMs are not as forthcoming with the firmware once Intel/Others make  the microcode available for the OEM’s to integrate into their respective firmware updates.

Really after all these Spectre/Meltdown hardware side channel vulnerabilities came in to the public eye and required excessive amounts of firmware flashing there really needs to be laptops that come with dual UEFI(BIOS) chips and some redundancy there as well should a flash process go wrong.

The Motherboard makers that sale COTS MB parts to the home system build it yourself market already offer motherboards with dual UEFI/BIOS options and less worry if a firmware update  goes wrong as there’s that other firmware chip that’s flashed with  working  firmware to fall back on. Some Motherboards offer what is called BIOS(UEFI) flashback capability and the end user able to store the firmware update on a USB stick and that MB can flash its firmware chip without even needing a CPU present in the MB’s CPU socket. There are motherboards out there that if the PC fails to properly post using one UEFI/BIOS chip will automatically fall beak to the other UEFI/BIOS chip and boot up from there and let the end user(Over-clockers mostly) try all sorts of custom configurations in their UEFI/BIOS settings and get more performance that way.

 

1 user thanked author for this post.

Reply | Quote

@KYKaren

The KB4497165 patch simply updates the mcupdate_GenuineIntel.dll file – nothing more, nothing less

Reply | Quote

@kykaren

The KB4497165 patch simply updates the mcupdate_GenuineIntel.dll file – nothing more, nothing less

And what does that mean – i.e., what does this .dll do? I already have the correct firmware, so is this .dll update needed, too? Or not?

Reply | Quote

That DLL contains all known Intel microcode updates; when your system boots, microcode updates that apply to your specific processor family are loaded from this file. It is possible (likely?) that you’ll receive updates to this file (and to the one for AMD processors) when they do not apply to your specific processor.

If the code in the DLL doesn’t apply to your processor, it will not be loaded at boot time.

2 users thanked author for this post.

Eckis Redux

Reply | Quote

I’ve been reading the above about KB 4497165 and am wondering if one even needs this update? CPU-Z is reading my CPU as Skylake only without all the other letters and numbers that are listed after Skylake in the KB article. Can someone shed some light on this ?

Reply | Quote

UPDATE:    I read where if you don’t keep up to date on the chip set updates they can impact your regular monthly updates. So I went ahead and tried to install the update and its telling me I’m already up to date, so that answers my question that I had. The chip set update is obviously not the right one for my PC, otherwise it would have installed. This was through Window Update.

Reply | Quote

I doubt a lack of BIOS / hardware updates will make any difference to Windows updates.

Do you have a link to where you read that it does?

cheers, Paul

Reply | Quote

[hansR]

KB 4497165 is offered. why?

Ryzen 5 2600X, NVidia Geforce GTX 1050 TI;

Winver: 1903 (18362.657)

Hid it …

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

• This reply was modified 3 years, 7 months ago by hansR.

Reply | Quote

Information is here:
https://support.microsoft.com/en-us/help/4497165/kb4497165-intel-microcode-updates

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

You read my HW list? This is a AMD CPU …

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

Reply | Quote

hansR wrote:

You read my HW list? This is a AMD CPU …

According to Microsoft the type CPU you use doesn’t matter.

Reply | Quote

Alex5723 wrote:

hansR wrote:

You read my HW list? This is a AMD CPU …

According to Microsoft the type CPU you use doesn’t matter.

According to Microsoft: Install this update for the listed processors only.

 

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

Reply | Quote

[Alex5723]

hansR wrote:

Alex5723 wrote:

hansR wrote:

You read my HW list? This is a AMD CPU …

According to Microsoft the type CPU you use doesn’t matter.

According to Microsoft: Install this update for the listed processors only.

 

According to Microsoft Windows Home users don’t have a say in this matter and 90% don’t read Microsoft’s blogs..and anyway they don’t know what type/version of CPU they use.

• This reply was modified 3 years, 7 months ago by Alex5723.

Reply | Quote

By the Way: KB 4497165 is not offered to my HP Notebook with Intel Core i7–8565U (Whiskey Lake-U, CPU-ID 00806EB). Which you can find here https://support.microsoft.com/en-us/help/4497165/kb4497165-intel-microcode-updates

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

Reply | Quote

KB4497165 is being offer to MY i7-8565 (Whiskey Lake U), a Dell Inspiron 5482 2-in-1. According to a DELL advisory about INTEL-SA-00233, you have to have the correct/latest BIOS (they call it BIOS, but System Information says the BIOS mode is UEFI) in addition to applying the OS patch for fixing those INTEL-SA-00233 CVE threats.

By the way, the MS catalog listed KB4497165 yesterday, but it’s not there today.

1 user thanked author for this post.

woody

Reply | Quote

The MS Catalog seems to me crazy, you can’t find anything when looking for a KB or patch, it doesn’t show any research.

Reply | Quote

If you know the update number, type the number without the “KB” in the search box.
If you want February patches type in “2020-02”
You can add search elements with the “+” – example 2020-02 + Cumulative

1 user thanked author for this post.

woody

Reply | Quote

I’ve tried, it doesn’t work (in portuguese)

Reply | Quote

Both KB4494174 and KB4497165 have gone missing in the Microsoft Update Catalog:

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

woody

Reply | Quote

That’s right @geekdoom, the same with me.

Reply | Quote

That does not bode well.

Reply | Quote

I’m checking other updates in the Microsoft Update Catalog; the problem may be with the Microsoft Update Catalog.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

I have also done this and what you write is confirmed.

1 user thanked author for this post.

geekdom

Reply | Quote

One more test 4532693 for the road:

KB4532693 is not found either. Really?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

KB4532693 was one I tried on two different devices and it wouldn’t come up, either, no matter how many times I tried. I did have success with KB4532938 twice, but then later no success.

I’ve also had success with KB3188744, a really old patch from October 2016, last updated May 30/31, 2017.

Reply | Quote

In the MS Catalog I typed in about 10 KBs. I got KB4532938 to come up twice, on separate occasions, but it wouldn’t appear at other times. None of the others I tried came up at all, no matter how many times I tried.

This happened on two different devices, both using the Firefox browser.

Reply | Quote

yep, as I noted in #217172. I noticed it for 4494174, too, but didn’t think to mention it, since the patch being offered to me is/was 4497165, which I have hidden, since I don’t know what to do with it.

Reply | Quote

The patches seem to be back on the Catalog this morning (Feb 26). KB4497165 and KB4532693 both show up.

1 user thanked author for this post.

woody

Reply | Quote

… and they’ve been changed. The catalog says they were updated Feb 25.

Looks like it’s a metadata change. See this Tenforums post.

Reply | Quote

When I saw the patches were missing, I clicked the “not helpful” button then put in the comment field that KB12345 (or whatever) is missing. I did not actually think they would read it and correct the situation, but maybe they did. Not all KB patches were missing but 2020-02 seeming to be missing.

Reply | Quote

I’m still puzzled:
Dell (My laptop in an Inspiron 7580) says there’s new BIOS in ‘March 2020’.

What is not clear to me is whether I need to load KB4497165 in addition to the coming BIOS update or not. And if I do load the KB, will there be any negative effect after the BIOS is updated?

(Thanks to @Paul_T who pointed me to this topic.)

Dell Inspiron 7580 i7 16GB Win 10 pro 22H2 (19045.3208), Microsoft 365 Version 2307 (16626.20068)

Reply | Quote

[WCHS]

This may be helpful from DELL – 00233. Inspiron 7580 is on the list – you may already have the correct BIOS (UEFI). It says there to also apply the applicable OS update.

• This reply was modified 3 years, 7 months ago by WCHS.

Reply | Quote

Thanks @KYKaren,

Dell say a new BIOS will be released in March – Version 1.10.0.

Dell Inspiron 7580 i7 16GB Win 10 pro 22H2 (19045.3208), Microsoft 365 Version 2307 (16626.20068)

Reply | Quote

No update today for 1909

Reply | Quote

see my comment below

Reply | Quote

KB4535996 update for 1903/1909 recently released Feb. 27, 2PM pacific local time:
https://support.microsoft.com/en-us/help/4535996/windows-10-update-kb4535996

Note – if anybody thinks the KB4535996 update will “fix” those broken “user profile” bugs, they will be in for a big disappointment

Reply | Quote

Also released today KB4537572 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM and Windows 10, version 1909 and Windows Server, version 1909. Saw it just now 6:00 EST. Read about it here. Fixes some crashes.

Reply | Quote

The new Microsoft patch schedule is that there is no schedule.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Windows 1909 Test Beta
February 27, 2020
Windows Update Queue

• 2020-02 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4537572)
  This not an optional update.
  This update installed without error and rebooted as instructed without error.
• 2020-02 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4535996)
  This is an optional update.
  This update installed without error and rebooted as instructed without error.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

2 users thanked author for this post.

jburk07

Reply | Quote

I revived 2 new CU updates kb4532693 and kb4535996. not sure why there were 2. also a Windows defender update and the .NET update.

All installed with no problems. this brings me up to version 18363.693

 

Barry
Windows 11 v22H2

1 user thanked author for this post.

jburk07

Reply | Quote

Paul T wrote:

but expect that Windows microcode updates check the CPU code version before patching.

Microsoft should have done that before sending microcode patches to the wrong CPUs, like installing Intel microcode on AMD PCs….

Reply | Quote

It’s probably much easier to send an update with database and detection logic for all CPUs, then only apply the updates when required, thus it turns up on most PCs.

cheers, Paul

Reply | Quote

Paul T wrote:

It’s probably much easier to send an update with database and detection logic for all CPUs, then only apply the updates when required, thus it turns up on most PCs.

cheers, Paul

If so what is the telemetry good for ?

Reply | Quote