Windows 10: Microsoft Update on Feb 7, 2021

On Feb 7, 2021 Microsoft update took almost 2 hours. Now when I'm on the computer I get a pop up box "not responding" about 5 to 6 times a day.

:)

 

Microsoft January 2021 Security Updates

January 2021 Security Updates




The January 2021 security release consists of security updates for the following software:

• Microsoft Windows
• Microsoft Edge (EdgeHTML-based)
• Microsoft Office and Microsoft Office Services and Web Apps
• Microsoft Windows Codecs Library
• Visual Studio
• SQL Server
• Microsoft Malware Protection Engine
• .NET Core
• .NET Repository
• ASP .NET
• Azure

Please note the following information regarding the security updates:

• CVE-2020-0689 has been re-released. For further information see Security update for Secure Boot DBX: January 12, 2021.
• For information regarding enabling Windows 10, version 1909 features, please see Windows 10, version 1909 delivery options. Note that Windows 10, versions 1903 and 1909 share a common core operating system with an identical set of system files. They will also share the same security update KBs.
• Windows 10 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The updates are available via the Microsoft Update Catalog.
• For information on lifecycle and support dates for Windows 10 operating systems, please see Windows Lifecycle Facts Sheet.
• A list of the latest servicing stack updates for each operating system can be found in ADV990001. This list will be updated whenever a new servicing stack update is released. It is important to install the latest servicing stack update.
• Updates for Windows RT 8.1 and Microsoft Office RT software are only available via Windows Update.
• In addition to security changes for the vulnerabilities, updates include defense-in-depth updates to help improve security-related features.
• Customers running Windows 7, Windows Server 2008 R2, or Windows Server 2008 need to purchase the Extended Security Update to continue receiving security updates. See 4522133 for more information.

The following CVEs have FAQs with additional information. Please note that this is not a complete list of CVEs for this release.

• CVE-2020-26870
• CVE-2021-1636
• CVE-2021-1637
• CVE-2021-1643
• CVE-2021-1644
• CVE-2021-1645
• CVE-2021-1647
• CVE-2021-1648
• CVE-2021-1656
• CVE-2021-1663
• CVE-2021-1669
• CVE-2021-1670
• CVE-2021-1672
• CVE-2021-1676
• CVE-2021-1677
• CVE-2021-1694
• CVE-2021-1696
• CVE-2021-1699
• CVE-2021-1707
• CVE-2021-1708
• CVE-2021-1711
• CVE-2021-1713
• CVE-2021-1714
• CVE-2021-1715
• CVE-2021-1716
• CVE-2021-1725

Known Issues


The following KBs contain information about known issues with the security updates. For a complete list of security update KBs, please see 20210112. For more information about Windows Known Issues, please see Windows message center (links to currently-supported versions of Windows are in the left pane).


KB Article Applies To
4598229 Windows 10, Version 1903, Windows Server, Version 1903, Windows 10, Version 1909, Windows Server, Version 1909
4598230 Windows 10, Version 1809, Windows Server 2019
4598242 Windows 10, Version 2004, Windows Server, Version 2004, Windows 10, Version 20H2, Windows Server, Version 20H2
4598275 Windows 8.1, Windows Server 2012 R2 (Security-only update)
4598278 Windows Server 2012 (Monthly Rollup)
4598279 Windows 7, Windows Server 2008 R2 (Monthly Rollup)
4598285 Windows 8.1, Windows Server 2012 R2 (Monthly Rollup)
4598287 Windows Server 2008 (Security-only update)
4598288 Windows Server 2008 (Monthly Rollup)
4598289 Windows 7, Windows Server 2008 R2 (Security-only update)
4598297 Windows Server 2012 (Security-only update)


January 2021 Security Updates - Release Notes - Security Update Guide - Microsoft

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer

 

Microsoft to Test Windows 7 Update System

Having propagated Windows 7 RC to a sizable amount of users, Microsoft has created an ideal environment to test the operating system's update system. To test it, Microsoft will release up to ten mock updates this week, starting from Tuesday. The updates do not affect the system in any way, except that they are used by Microsoft to test how the update system itself is able to deal with the various kinds of updates to the OS and its components, in various scenarios generated by people's different hardware configurations and software environments.

These however, won't be the first updates Windows 7 RC received so far. On May 7, Microsoft released a critical-update that fixes an important stability issue with the 32-bit version of Windows 7 RC. Most mock-updates will install automatically. A certain mock-update will also test a notification feature. This particular update will not install automatically, but rather the user will be prompted to install it (which is what is being tested). To decline from testing the updates, users must toggle Automatic Updates to a setting other than what the OS recommends. Under the hood, the mock-updates simply replace system files with their exact duplicates that are downloaded, hence the system isn't affected in any way. Tests such as these will help Microsoft come up with a much more stable OS when it finally releases.

Sources: WindowsTeamBlog, PC World