How to get the Windows 10 2022 Update version 22H2 Win Update

Page 4 of 12 FirstFirst ... 23456 ... LastLast

  1. Posts : 1,463
    Windows 10 Pro 22H2 64 bit
       #30

    I just got it through WU. Took 2 min and am now on 22H2 19045.2130.

    Jim
      My Computer


  2. Posts : 919
    Windows 10 Pro 64bit 22H2 19045.3324
       #31

    antares said:
    Why do some people get version 2132 and others 2130? I'm in the 2130 club
    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
      My Computers


  3. Posts : 802
    Windows 10 Home x64
       #32

    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:

    How to get the Windows 10 2022 Update version 22H2-untitled.png

    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...
      My Computers


  4. Posts : 23,499
    Win 10 Home ♦♦♦19045.4412 (x64) [22H2]
       #33

    krzemien said:
    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:

    How to get the Windows 10 2022 Update version 22H2-untitled.png

    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...


    As mentioned in the post just above yours... you can now get .2132 as well.
      My Computer


  5. Posts : 359
    Windows 10x64 Pro
       #34

    Farvatten said:
    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
    That link only applies to 21H2 to 22H2 upgrade. This one is to convert 22H2 2130 to 22H2 2132

    So what additional updates does 2132 bring as compared to 2130? And why does WU not deliver 2132 directly?
      My Computer


  6. Posts : 919
    Windows 10 Pro 64bit 22H2 19045.3324
       #35

    antares said:
    That link only applies to 21H2 to 22H2 upgrade. This one is to convert 22H2 2130 to 22H2 2132

    So what additional updates does 2132 bring as compared to 2130? And why does WU not deliver 2132 directly?
    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
      My Computers


  7. Posts : 802
    Windows 10 Home x64
       #36

    Ghot said:
    As mentioned in the post just above yours... you can now get .2132 as well.
    That's not the problem and I know that.

    What I meant was the alleged installation date which is not correct - see highlighted in the screenshot I provided.
      My Computers


  8. Posts : 23,499
    Win 10 Home ♦♦♦19045.4412 (x64) [22H2]
       #37

    krzemien said:
    That's not the problem and I know that.

    What I meant was the alleged installation date which is not correct - see highlighted in the screenshot I provided.


    Did you by any chance do an In-Place upgrade in Oct 2020?

    I installed Windows 10 in May 2020, but in July 2020 I did an In-Place upgrade...

    How to get the Windows 10 2022 Update version 22H2-image1.png


    In-Place upgrade, Repair install, re-Install... will change the install date.
      My Computer


  9. Posts : 15,507
    Windows10
       #38

    OldMainframeGuy said:
    I just installed 22H2. The dearth of information on what's actually in this version is amazing.
    Here's the definitive list:

    We changed an Outer Mongolia emoji which impacted Cornish language users - enjoy!
      My Computer


  10. Posts : 23,499
    Win 10 Home ♦♦♦19045.4412 (x64) [22H2]
       #39

    cereberus said:
    Here's the definitive list:

    We changed an Outer Mongolia emoji which impacted Cornish language users - enjoy!


      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:35.
Find Us




Windows 10 Forums