KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237 Win Update

Page 2 of 20 FirstFirst 123412 ... LastLast

  1. Posts : 1,248
    Windows 10 Pro (Build 19043.1110)
       #10

    rockfan13 said:
    It's done now anyways. But do you think I should post this there anyways?
    If you mean you solved your problem, you might want to mark your OP 'solved', and/or tell how you solved it. If it seems a problem that others might have, you might want to post a heads-up on the General Support forum.
      My Computer


  2. Posts : 50,055
    Windows 10 Home 64bit 21H1 and insider builds
       #11

    RingTailCoon said:
    OK, this little dumbass here, download was stuck on 6 %, so I downloaded and installed it via the catalogue. Not knowing that the installation in the background already was running!!! Sooooo....... I downloaded the SAME update at the SAME time! So after a while I quitted the one dowloaded from the catalogue and I left the one in the Windows Update-screen running after a while.

    And now all is happily updated... one hour later than usual!

    And why am I already on 21H2? I only installed the enablement package... Or was THIS update 21H2?
    The enablement package updates you from 21H1 to 21H2.
      My Computer


  3. Posts : 2,450
    Windows 10 Pro x64
       #12

    Quick update (9 min). SFC found and fixed corrupt files. No other problems, so far.

    KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-19043.1237.png
      My Computer


  4. Posts : 201
    Windows 10 2004 Home
       #13

    sgage said:
    I think you might want to start a thread in the General Support subforum. It isn't really appropriate here.
    I just deleted that post now.

    - - - Updated - - -

    The whole update went fine.
      My Computer


  5. Posts : 1,750
    Windows 10 HOME 64-BIT
       #14

    kado897 said:
    The enablement package updates you from 21H1 to 21H2.
    Well now, that one was then a verrrrrrry small update. As I recall a matter of 5 minutes!
      My Computer


  6. Posts : 2,557
    Windows 10 pro x64-bit
       #15

    Done and dusted. And this was not for 21h2 as someone has asked above. There is a way to get 21H2 and there won't be any great features in it as MS is leaning toward Win 11. If one really wants to jump to 21H2 right now, there is a way:

    How to upgrade Windows 10 version 21H1 to 21H2 right now (KB5003791) - gHacks Tech News

    In the meantime, this PT went fine and nothing to report yet.

    KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-winver-after-installing-kb5005565.png
      My Computers


  7. Posts : 624
    Windows 11 Pro (x64)(v23H2)(Build 22631.3447)
       #16

    installed now and working fine...
    so far..

    EDIT:
    Still waiting for the Enablement Package to land on my PC through Windows update...
      My Computers


  8. Posts : 1,750
    Windows 10 HOME 64-BIT
       #17

    IronZorg89 said:
    Done and dusted. And this was not for 21h2 as someone has asked above. There is a way to get 21H2 and there won't be any great features in it as MS is leaning toward Win 11. If one really wants to jump to 21H2 right now, there is a way:

    How to upgrade Windows 10 version 21H1 to 21H2 right now (KB5003791) - gHacks Tech News

    In the meantime, this PT went fine and nothing to report yet.

    KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-winver-after-installing-kb5005565.png
    You were sayin'...? KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-untitled-2.jpg
      My Computer


  9. Posts : 2
    Windows 10 21H1
       #18

    Here is more: Windows 10 KB5005565 & KB5005566 cumulative updates released

    This cumulative update comes with the following highlighted fixes:

    • Addresses an issue that causes PowerShell to create an infinite number of child directories. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding.
    • Updates a rare condition that causes Bluetooth headsets to only work for voice calls.
    • Updates an issue that provides the wrong Furigana result when you cancel the Japanese reconversion.
    • Updates an issue that resets syncing for Microsoft OneDrive to “Known folders only” after you install a Windows update.
    • Updates an issue that prevents audio headsets that connect to a device using USB from working if the device has certain third-party audio drivers.
    • Updates an issue with resizing images that might produce flickering and residual line artifacts.
    • Updates an issue that prevents you from typing any words in the username box during the out-of-box experience (OOBE) process. This issue occurs when you use the Chinese Input Method Editor (IME).
    • Updates an issue with copying and pasting a text box into Office 365 apps. If you use an IME, you won’t be able to insert text into the text box.
    • Updates an issue that might cause your device to stop working when making a touch input gesture. This issue occurs if you bring more fingers into contact with the touchpad or screen during the middle of the gesture.
    • Updates an issue that might cause an external monitor to display a black screen after Hibernation. This issue might occur when the external monitor connects to a docking station using a certain hardware interface.
    • Updates an issue that resets the brightness for standard dynamic range (SDR) content on high-dynamic range (HDR) monitors. This occurs after you restart your device or reconnect to the device remotely.


    Windows 10 version 1909 is getting KB5005566 with identical fixes.
    Nothing more about printnightmare, nothing about mshtml/ActiveX.
      My Computer


  10. Posts : 238
    Windows 10 Home x64
       #19

    RingTailCoon said:
    You were sayin'...? KB5005565 Windows 10 2004 19041.1237, 20H2 19042.1237, 21H1 19043.1237-untitled-2.jpg
    Interesting. It's still 21H1 for me after the update.

    Did you install anything else?
      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 16:44.
Find Us




Windows 10 Forums