KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 Win Update

IronZorg89 said:

Then again, I suppose you already have the answer to your question since @Bree in post # 86 of this thread:
Windows 10 Insider Preview Dev Build 20279.1 (fe_release) - Dec. 14
has pointed out that it doesn't take an update for the fix to be applied....

Probably worth repeating here as it is directly relevant to this thread.

It's not necessarily an update, one that changes the installed files. If it is just a configuration setting that's needed, then that can be changed without applying any update that would be listed in update history.

One example is the banner at the top of Settings can be turned on or of remotely by Microsoft. Another was Start's 'expanding flyout' for Power, etc. that officially first appeared with 1909, that was A/B tested by Microsoft with it appearing on a few select 1903 machine, one of mine included.

And Microsoft's cryptic wording of the resolution in post #1 suggests that is the case here.

This issue is resolved and should now be prevented automatically on non-managed devices. Please note that it can take up to 24 hours for the resolution to propagate to non-managed devices. Restarting your device might help the resolution apply to your device faster.

A 'non-managed device' means you and me, retail machines updated by Windows Update.

Bree said:

Probably worth repeating here as it is directly relevant to this thread.

It's not necessarily an update, one that changes the installed files. If it is just a configuration setting that's needed, then that can be changed without applying any update that would be listed in update history.

One example is the banner at the top of Settings can be turned on or of remotely by Microsoft. Another was Start's 'expanding flyout' for Power, etc. that officially first appeared with 1909, that was A/B tested by Microsoft with it appearing on a few select 1903 machine, one of mine included.

And Microsoft's cryptic wording of the resolution in post #1 suggests that is the case here.



A 'non-managed device' means you and me, retail machines updated by Windows Update.

Thx for making things clearer for all of us. As usual if one is ever tempted to run chkdsk /f, make sure to have a just-in-case system image backup in order to play it safe.

Try3 said:

I have no idea what this means....

It means, as I explained in post #84 of the thread IronZorg89 gave a link for, and again in post #400 of this thread, that apparently no new files were needed to fix this bug, just a change in how they were configured to run.

Microsoft can issue configuration changes through Windows Update as easily as they can push updates, and this seems to be how they've resolved this one. A configuration change, such as the one that put the banner at the top of Settings, does not get recorded in Update History as it doesn't update any system files.

Try3 said:

IronZorg89,

Lindemann's question -

Your reply -


So your reply should have been, "I don't know.", instead of wasting people's time chasing down links.


I have no idea what this means.

Denis

I am not wasting your time; I was just trying to help. This quote is from first page of this thread and "added on 12/20":

This issue is resolved and should now be prevented automatically on non-managed devices. Please note that it can take up to 24 hours for the resolution to propagate to non-managed devices. Restarting your device might help the resolution apply to your device faster.

And @Bree has also already mentioned it. It seems that you want an update, but there is none. Like I said before you can always try to see if you encounter the issue at hand by running chkdsk /f , but making sure to have a system image backup before.

So apparently this means there is such a thing as magic - namely that Microsoft issued a fix for a bad problem that applied itself to my system at a time unknown to me and by a method unknown to me and it left no traces detectable by me and therefore I am to believe the problem is fixed even though there is no evidence whatsoever that shows a fix has happened.

Stuxnet anyone?

bbinnard said:

So apparently this means there is such a thing as magic - namely that Microsoft issued a fix for a bad problem that applied itself to my system at a time unknown to me and by a method unknown to me and it left no traces detectable by me....

Basically, yes.

This policy setting determines the level that Microsoft can experiment with the product to study user preferences or device behavior.

https://docs.microsoft.com/en-us/win...xperimentation

See your: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\System\AllowExperimentation