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

Welp, nothing broke. I'm gonna restart once again... just to check.


/edit

Everything seems OK.

Ghot said:

Welp, nothing broke. I'm gonna restart once again... just to check.


/edit

Everything seems OK.

You're lucky. It's Windows Russian Roulette and doesn't affect all installations.

steve108 said:

You're lucky. It's Windows Russian Roulette and doesn't affect all installations.

Yeah, I know. But I also think a lot of us are over-reacting, somewhat. I know I was.
With a full OS image backup... any of us can test for ourselves.

I had a MR backup from the 19th. Didn't have to use it.

By the same token, I'm not gonna sit here and KEEP running chkdsk c: /f over and over either.

I ran it once, and it came up with no problems, and the reboot, and a 2nd reboot, worked... without issue.




On a side note, the 500GB SSD (2.5") that holds my OS, is only about 7 months old.
SAMSUNG 860 EVO Series 2.5" 500GB SATA III MLC Internal SSD - Newegg.com

I also don't have my drive set up........ normally.
I don't know if that makes a difference or not.

Try3 said:

I am only assuming that my new version of AutoChk is a fixed version because the MS announcement quoted by Brink was in the past tense so could only have referred to a CU that had already been issued i.e. KB4586853 CU {Build 1904*.662} or the later KB4592438 CU {Build 1904*.685}.

I have checked an old image as well so I can confirm that the previous KB4586786 CU had also altered AutoChk.exe.

What I have no info about is whether any particular version of AutoChk.exe. can be regarded as the 'fixed' version that does not run the risk of harming the system. I was only reassured about the subject because the MS announcement quoted by Brink was in the past tense and so could be taken to refer to a CU that had already been issued.

I was being illogical.
- MS's announcement explicitly links it to KB4592438 CU so my 10th December AutoChk.exe, installed by that CU, must be the non-fixed version.
- But I have no subsequent updates [installed or available].
So I must still be susceptible to the problem.

I'm just going to wait for the next CU & keep my fingers crossed.

Denis

IronZorg89 said:

See this post # 84 (please read it thoroughly) in this link:

Windows 10 Insider Preview Dev Build 20279.1 (fe_release) - Dec. 14

Did you really mean #84? Neither it nor the TechRadar article it refers to identify the update that fixed it.

Denis