Microsoft STILL hasn’t acknowledged the bugs in last Friday’s Win10 1903 cumulative update

Topic

New Reply

Last Friday, Microsoft released KB 4512941, the long-anticipated second August cumulative update for Win10 version 1903. Within a few hours, people we
[See the full post at: Microsoft STILL hasn’t acknowledged the bugs in last Friday’s Win10 1903 cumulative update]

2 users thanked author for this post.

geekdom, Fred

Reply | Quote

Replies

[bbearren]

They have re-released it.  Being the Seeker that I am, I just got it a few minutes ago.  I wasn’t having any issues with the first one, none so far with this one either.

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

• This reply was modified 4 years ago by bbearren.
• This reply was modified 4 years ago by bbearren.

2 users thanked author for this post.

doriel, woody

Reply | Quote

Wonder where it came from?

There’s no new version in the Catalog….

Reply | Quote

I’m completely confused.

1 user thanked author for this post.

Fred

Reply | Quote

bbearren, I am also a seeker and did not get a second update. Yet Windows update history shows that I got KB4505903 twice, KB 4507453 twice, and KB4505057 3 times (twice in the same day, once a week later), but this update has not shown up again no matter how many times I check for updates. So I would not assume this was a re-release if it doesn’t show up in the catalog, it’s just Windows update being a bit weird like usual.

Reply | Quote

Just because some update is showing up again does not mean Microsoft re-released it. It’s more likely that something went wrong when seeking for new updates and Microsoft’s update server simply spit out garbage, which happens more often than not these days. It’s also possible that Microsoft changed the underlying meta data to force a re-install because their ‘AI’-driven telemetry was showing some anomalies.

Reply | Quote

[bbearren]

I watched the download progress, watched the installation progress (being curious, as I knew I already had it), watched it complete and announce me “up to date”.

I just ran sfc /scannow, and got this:

I have no duplicate updates other than KB4512941.

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

• This reply was modified 4 years ago by bbearren.
• This reply was modified 4 years ago by bbearren.

Reply | Quote

[Fred]

anonymous wrote:

bbearren, I am also a seeker and did not get a second update. Yet Windows update history shows that I got KB4505903 twice, KB 4507453 twice, and KB4505057 3 times (twice in the same day, once a week later), but this update has not shown up again no matter how many times I check for updates. So I would not assume this was a re-release if it doesn’t show up in the catalog, it’s just Windows update being a bit weird like usual.

I did seek aswell, [KB 4512941 + KB4512508]; 1 processor up to 98%, rollingback didn’t go well;
So I rolled back the systemdrive image from 2 days before…. and guess, those “two updates” [KB 4512941 + KB4512508] were gone. [[??]]
Half a day later there suddenly is this driverupdate: [“Intel – System – 4/11/2018 12:00:00 AM – 1815.12.0.2021”]; no explination what so ever, peculiar….

exiting? no!

* _ the metaverse is poisonous _ *

• This reply was modified 4 years ago by Fred.

Reply | Quote

Half a day later there suddenly is this driverupdate: [“Intel – System – 4/11/2018 12:00:00 AM – 1815.12.0.2021”]; no explination what so ever, peculiar….

Yeah Fred, I think someone fudges the dates on drivers. My realtek driver had been version 9.1.409.2015, released April 9th 2015, for years. And then back in June 2019 suddenly I got version 9.1.410.2015, which was supposedly released April 10th 2015. I think someone must just be incrementing the version numbers and not bothering to put a proper release date.

Funny enough there were no results on google for this version at the time, but googling now it looks like someone asked about it here a week after I got the update.

I bet these updates are a good thing and ensure old drivers continue working on new versions of Windows, but it would be nice if they dated them properly and explained their purpose.

1 user thanked author for this post.

Fred

Reply | Quote

Microsoft confirms high CPU usage bug in latest Windows 10 1903 update

I don’t know about “confirmed” but at least they are investigating.

Reply | Quote

I just now checked for updates and it did not offer me another update. However i did not have any problems with the update when i downloaded it on friday.

 

 

 

Barry
Windows 11 v22H2

Reply | Quote

I think the comment I just read on another forum sums things up rather well:

“We are in 2019 and this is the level of Microsoft incompetence. Unfortunately Microsoft has become too big to fail.”

Fortunately, I’m using Windows Update Blocker to keep this incompetence at bay until it is (hopefully) sorted out.

You never know when MS is going to have another one of those “oops, sorry, we didn’t mean to download and install those updates even though you specifically asked us not to. Won’t happen again, we promise”. (Then rinse and repeat a short time later).

PC1: Gigabyte B560M D2V Motherboard, Intel i5 11400 CPU, 16GB RAM, NVIDIA GeForce GTX 1650 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Professional 22H2 64bit.
PC2: Asus H81M-PLUS Motherboard, Intel i3-4160 CPU, 16GB RAM, NVIDIA GeForce GTX 1050 Graphics Card, 1x Samsung 870 EVO 250GB SSD, 1x Samsung 860 EVO 250GB SSD, Windows 10 Home 22H2 64bit.

1 user thanked author for this post.

Fred

Reply | Quote

Microsoft has just updated MS support article 4512941 Wednesday Sept. 4 to acknowledge the “high CPU usage” problem from SearchUI.exe

1 user thanked author for this post.

woody

Reply | Quote