Patch Lady – so what’s KB4523786

Topic

New Reply

On a standalone PC that’s never seen Windows autopilot I am getting KB4523786 pushed out if I click on check for updates.   And I have never installed
[See the full post at: Patch Lady – so what’s KB4523786]

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

abbodi86, woody, Great Lake Bunyip, GreatAndPowerfulTech

Reply | Quote

Replies

Hi Susan

This patch is for the underlying TPM chip in computers with dedicated TPM chips and not the actual Windows Autopilot itself.

3 users thanked author for this post.

woody, Great Lake Bunyip, Barry

Reply | Quote

“This patch is for the underlying TPM chip in computers with dedicated TPM chips and not the actual Windows Autopilot itself.”

I have the chip.  Now it makes sense.  Thanks

Reply | Quote

Tell me again, please, why you never click on “check for updates”?  If you have disabled auto updating, but do have the setting “check for updates, but let me decide whether to download and install them”, what’s the harm to occasionally manually check for updates?

 

iPhone 13, 2019 iMac(SSD)

1 user thanked author for this post.

wdburt1

Reply | Quote

Since this thread is about Win10, I assume that’s what you are asking about. If that is the case:

If you click “check for updates” (even if you have the other setting), it initiates the download AND INSTALL of whatever is the latest pending out there.
It’s not really “check for updates,” it’s check for updates and install them.”

4 users thanked author for this post.

Charlie, woody, pmcjr6142, wdburt1

Reply | Quote

Because it doesn’t check for updates, it installs them.  You aren’t in Windows 7 anymore.  10 isn’t Kansas and won’t allow you to “see” what is pending,  Like PK says, it installs.

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

Charlie, woody, pmcjr6142, wdburt1

Reply | Quote

… but… I understand you can still search only, if you do it with PowerShell?

https://gist.github.com/Grimthorr/44727ea8cf5d3df11cf7 has some examples, and last time I experimented with that I got lists of missing updates but didn’t trigger install. Yes, I did stay away from $UpdateSession.CreateUpdateDownloader() and $UpdateSession.CreateUpdateInstaller() …

Oh and would anyone happen to be familiar with https://www.powershellgallery.com/packages/zWindowsUpdate/1.2 ?

Reply | Quote

… begging the question whether this patch was installed (or offered) on any machines other than Win10 version 1903… in spite of what the KB article says.

Reply | Quote

It was installed after I checked for updates on all of my Win 10 Home 1903 machines earlier today, including one that doesn’t have a TPM chip. Now I’m wondering if I should just leave it installed since it seems to be causing no harm, or should I uninstall it?

1 user thanked author for this post.

woody

Reply | Quote

This link may explain it.

https://www.landzdown.com/general-software-news-updates-discussions/windows-10-version-1903-cumulative-update-released-58554/msg201616/?topicseen#msg201616

 

 

1 user thanked author for this post.

woody

Reply | Quote

I received this update for my  Win10 1903 HPHome laptop.  I did not check for updates, it just showed up along with .net updates and I have it paused.

Reply | Quote

I assume you discovered it with wushowhide? (???)

Reply | Quote

I have a standalone PC  (Windows 10 Home Edition) and the patch KB4523786 was automatically offered.  It downloaded and installed.  I later manually uninstalled it and Windows Update did not again offer it.

Reply | Quote

Confirmed over here in Europe. Uninstalling KB4523786 doesn’t offer it via Win Update again.

Reply | Quote

I wonder if MS yanked it overnight?

Reply | Quote

Yes, they did indeed. Nobody who uninstalled it, got it offered back again. Mistakes can happen, but why don’t they communicate this, at least via Twitter? That’s what makes people angry, right?

1 user thanked author for this post.

woody

Reply | Quote

I had to do a search for Windows Autopilot to find out what you folks are talking about. D’OH!

Our WSUS is scheduled to sync after midnight each day and I did not see it in our system so it must have been pulled before the sync overnight. This is why I schedule sync to occur at that time. That way we avoid patches that have issues upon release that are pulled within a matter of hours.

Red Ruffnsore

2 users thanked author for this post.

Bengalensis, woody

Reply | Quote

The link in the AskWoody “More Detail” blurb references an odd URL that won’t resolve or load (http://datascapellc), when the proper URL should be https://www.computerworld.com/article/3448576/microsoft-pushes-then-yanks-rogue-kinda-security-patch-kb-4523786-ostensibly-for-autopilot.html.  Was that detail link due to some rogue modification from a hack?

Reply | Quote

Yes, sorta. The rogue was my fingers, and the hack was myself.

Guilty as charged. Sorry. Changes being made.

1 user thanked author for this post.

jhvance

Reply | Quote

[abbodi86]

They should fix the detection metadata
but, it’s just an update, it will not hurt the sytem, even without Autopilot (or TPM chip, which i believe this update is not for it)

anyway, MS Michael Niehaus is deep in Autopilot and can clarify the situation
https://twitter.com/mniehaus

• This reply was modified 5 years, 5 months ago by abbodi86.

1 user thanked author for this post.

woody

Reply | Quote

anonymous wrote:

Yes, they did indeed. Nobody who uninstalled it, got it offered back again. Mistakes can happen, but why don’t they communicate this, at least via Twitter? That’s what makes people angry, right?

1903 home on the bench had it installed this morning.  it’s still being advertised.

Hey look! Another Feature Update!

You mean I shouldn't click Check for Updates?

Where is the Any key?

Reply | Quote

I wonder how that’s possible. I don’t see it in the Catalog. Maybe it was cached from last night?

Reply | Quote

I enabled my TPM BIOs firmware this morning and TPM is now showing in my device manager under “security devices”.  However, I had received the AutoPilot update notice before it was enabled.  I did not install the KB4523786 update and it no longer shows in my Windows Update screen.   With my experience and the other posts about it here, seems clear MS yanked it.

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

FYI…

A MS employee just now posted this: https://answers.microsoft.com/message/0c272670-11e1-404e-a08b-c7364c7479f9?threadId=2d5fb14c-959c-46db-8c70-1b3ab7f0ee1d

2 users thanked author for this post.

woody, abbodi86

Reply | Quote

Running Win10 Enterprise, build 1809

A few days ago, MS forced install of kb4524148. After that, I get a blue screen update failed with error code 0xc000021a.

I can get back to normal by using

DISM /image:c:\ /cleanup-image /revertrendingactions

But the update gets pushed again every night.

How can I stop this cycle?

PS: installing the Oct 8, 2019 KB4519338 cumulative update cause the same problem

Reply | Quote

WUShowHide is your friend.

cheers, Paul

Reply | Quote

So if this installed should I uninstall it?

Reply | Quote

Only if it’s causing problems.

cheers, Paul

Reply | Quote

Why are you getting old updates?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote