New
#30
I just got it through WU. Took 2 min and am now on 22H2 19045.2130.
Jim
I just got it through WU. Took 2 min and am now on 22H2 19045.2130.
Jim
They've applied the out of band *.msu update that came in earlier in the morning.
KB5020435 Windows 10 19042.2132, 19043.2132, 19044.2132
Was not aware of this happening now - kind-of missed this post earlier.
So when I booted up in the morning, there was nothing in Updates section. I expected this to be the case.
But after I (purposefully) rebooted PC half an hour ago or so, 22H2 Upgrade section appeared.
5-10 minutes later I'm @ 22H2, but for the life of me can't see any difference...
Also, I'm on 19045.2130, and interestingly:
Really? This PC was shipped with 1607 release on-board and I kept it upgraded ever since - so would have expected different date in there: 01/03/2017 or so rather than the one matching 20H2 deployment.
Moot point but still...
I'm pretty sure the link I posted is to the 21H2 patch that came in the morning before 22H2 was released at 10:00AM PST.
If you used it to manually patch before 22H2, then you were already at 2132 when you went from 21H2 to 22H2 otherwise you'd stay at the 2130 which was 21H2's latest build number. The changes will eventually be incorporated into the next CU.
The link you posted is the same manual patch to 2132 if you'd already upgraded to 22H2 first.
According to the release notes it's an emergency patch for a problem that only affected a small group of users:
It addresses an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”.
Last edited by Farvatten; 19 Oct 2022 at 19:27. Reason: Correct Build Numbers