Cumulative Updates - March 10th 2020

Sumit 44,226 Reputation points Volunteer Moderator
2020-03-11T02:05:33+00:00

Changelog for Cumulative updates released on March 10th, 2020 are as under:

  1. Windows 10 1903 and 1909~~: KB4540673~~ (OS Builds 18362.719)
  2. Windows 10 version 1809: KB4538461(OS Build 17763.1098)*

For Windows 10 1903/1909, It is recommended to install servicing stack update KB4541338 before installing the cumulative updates.

Direct Download links

Servicing Stack Update KB4541338 for Windows 10 1903 and 1909


Update 12/03/2020

KB4551762 is now available for Windows 10 version 1903 and version 1909 that jumps the build number to 18362.720 and 18363.720. See this for more information.

32-bit MSU file of the update is available here and 64-bit is available here.

Windows 10 update history

https://support.microsoft.com/en-in/help/4529964/windows-10-update-history

Windows 10 release dashboard

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903

 Follow @WindowsUpdate to find out when new content is published to the release information dashboard.

*Support for Windows 10, version 1809 ends May 12th 2020.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

384 answers

Sort by: Oldest
  1. Anonymous
    2020-03-15T14:23:44+00:00

    i need open my incredimail

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-03-15T15:07:34+00:00

    What has changed is that Microsoft, in order to "save money", has utilized Microsoft Insider volunteers to do most or all of the Q/A for Windows and Updates, and has fired or retired their entire Q/A staff, which used to occupy a vast space with dozens of professional software Q/A engineers. That's the long and the short of it. The software is now junk. For my relatively minor problem - for which I was able to find a workaround - I have checked and rechecked to make sure that I don't have any corruption or virus. It's all exactly as Microsoft thinks it should be: broken.

    I'm a retired software engineer, and I have never seen this kind of irresponsibility in software except for fly-by-night vendors. Microsoft is now in that category.

    Regards

    Jon

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-03-15T15:29:05+00:00

    You will need to get a Windows 10 installation disk to fix this, boot from the DVD and click on Command Prompt.

    Copy the entire C drive to a backup drive using the xcopy command. Quoting an article on the subject: "Type xcopy c:\ f:\ /s /e /h /i /c /y and press Enter to copy all the files and subdirectories (including any empty subdirectories, any system or hidden files) from drive C to drive F.

    Article: https://www.ubackup.com/clone/clone-hard-drive-command-prompt-8523.html

    Than, reboot again from DVD, and select Repair, and hope and pray that the Repair option does the right thing.

    If it doesn't work, reboot using the DVD yet again, and re-install Windows 10. The backup drive has all of your personal data.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-03-15T15:52:03+00:00

    Dear Microsoft Team,

    I'm so happy that you have created and prioritized this update. Your fabulous intelligent update system has made its own decision to install it. And it has not asked a single question. This update showed me how miserable my activities and business were. I had a whole hour for meditation in front of this blue screen. Than you once again for breaking all my plans today. They are nonsense comparing to super important update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-03-15T15:58:48+00:00

    Which drive you have reffered to as backup here.

    Is it the corrupted C drive.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments