Windows 8.1 Enterprise Update Januari 2016

Support for Windows 7 ended on January 14, 2020 and Windows 8 went out of support on January 12, 2016. Devices running either version of Windows no longer receive security updates. Therefore, if you're using Microsoft 365 on a computer running Windows 7 or Windows 8 and are configured for automatic updates, you'll no longer receive updates for the Office apps, including feature, security, and other quality updates.

Windows 8 was ultimately succeeded by Windows 10 in July 2015. Support for RTM editions of Windows 8 ended on January 12, 2016, and with the exception of Windows Embedded 8 Standard users, all users are required to install the Windows 8.1 update. Mainstream support for the Embedded Standard edition of Windows 8 ended on July 10, 2018, and extended support ends on July 11, 2023.

Windows 8.1 Enterprise Update Januari 2016

DOWNLOAD

In January 2016, Microsoft announced that it would no longer support Windows 8.1 or 7 on devices using Intel's Skylake CPU family effective July 17, 2018, and that all future CPU microarchitectures, as well as Skylake systems after this date, would only be supported on Windows 10. After the deadline, only critical security updates were to be released for users on these platforms.[126][127][128][129] After this new policy faced criticism from users and enterprise customers, Microsoft partially retracted the change and stated that both operating systems would remain supported on Skylake hardware through the end of their Extended support lifecycle. Windows 8.1 remains officially unsupported on all newer CPU families, and neither AMD or Intel will provide official chipset drivers for Windows operating systems other than Windows 10.[130][131] However, in August 2016, Microsoft again extended the Skylake support policy until the end of support for Windows 7 and 8.1 (2020 and 2023, respectively).[132][131]

Microsoft marketed Windows 8.1 as an "update" rather than as a "service pack", as it had done with such revisions on previous versions of Windows.[219] Nonetheless, Microsoft's support lifecycle policy treats Windows 8.1 similarly to previous Windows service packs: upgrading to 8.1 has been required to maintain access to mainstream support and updates after January 12, 2016.[4][220][221] Although Windows 8 RTM is unsupported, Microsoft released an emergency security patch in May 2017 for Windows 8 RTM, as well as other unsupported versions of Windows (including Windows XP and Windows Server 2003), to address a vulnerability that was being leveraged by the WannaCry ransomware attack.[222][223] Updates to apps published on Windows Store after July 1, 2019, are no longer available to Windows 8 RTM users.[224]

As of Jan. 10, 2023, Microsoft will stop issuing security updates for Windows 8.1. (Support for Windows 8 ended seven years earlier, in January 2016.) The Windows 7 Extended Security Update (ESU) program also ends on that date; customers who had paid the ESU subscription price got a three-year extension from the official January 2020 end-of-support date for Windows 7, but the door slams shut once and for all at the start of 2023.

The 10-year upgrade cycle for Windows 10 matters most to customers running Long Term Servicing editions in enterprise deployments. For 2015 and 2016, these were called Long Term Servicing Branch (LTSB); beginning in 2019, the name changed to Long Term Servicing Channel (LTSC). The 2015 and 2016 LTSB releases end support on Oct. 14, 2025, and Oct. 13, 2026, respectively. For Windows 10 Enterprise LTSC 2019, the end date is Jan. 9, 2029. Confusingly, Microsoft does not offer extended support for Windows 10 Enterprise LTSC 2021, which ends support on Jan. 12, 2027.

Large enterprise customers who have custom support agreements with Microsoft and that are willing to pay a very steep price for a Premium Support agreement have, in the past, been allowed to receive custom updates after the official end of support. The last such support agreement for Windows 2000 ended in 2016, more than six years after extended support officially ended, and some large customers with Windows XP and Windows 7 deployment may still be operating under custom support plans, although Microsoft doesn't publicly acknowledge their existence.

KB Articles associated with this update are: KB5008631Affected Versions:Microsoft Exchange Server 2019 Cumulative Update 11Microsoft Exchange Server 2016 Cumulative Update 22Microsoft Exchange Server 2019 Cumulative Update 10Microsoft Exchange Server 2016 Cumulative Update 21Microsoft Exchange Server 2013 Cumulative Update 23QID Detection Logic (authenticated):The QID checks for the version of file Exsetup.exe.ConsequenceSuccessful exploitation allows attackers to execute remote code.SolutionCustomers are advised to refer to KB5008631 for information pertaining to this vulnerability.Patches:The following are links for downloading patches to fix these vulnerabilities:CVE-2022-21846CVE-2022-21855CVE-2022-21969

Following KBs are covered in this detection:KB5008876 for Windows 10, version 1903 and later, Windows 10 LTSB, Windows 10 version 1903 and later, KB5008877 for Windows 10, Windows 10 LTSB, Windows Server 2016 KB5008879 for Windows 10, version 1903 and laterKB5008880 for Windows 11KB5008882 for Microsoft Server operating system-21H2KB5009546 for Windows Server 2016, Windows 10 LTSBKB5009585 for Windows 10 LTSBKB5009711 for Windows 7, Windows Server 2008 R2, Windows Embedded Standard 7KB5009712 for Windows 8 Embedded, Windows Server 2012KB5009713 for Windows 8.1, Windows Server 2012 R2KB5009714 for Windows Server 2008KB5009718 for Windows Server 2019, Windows 10, Windows 10 LTSB, Windows Server 2019KB5009719 for Windows Server 2008 R2 and Windows 7KB5009720 for Windows 8 Embedded and Windows Server 2012 KB5009721 for Windows RT 8.1 ,Windows Server 2012 R2, Windows 8.1KB5009722 for Windows Server 2008This security update is rated Important for supported versions of Microsoft .NET Framework..NET Framework 3.5, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 and 4.8QID Detection Logic (Authenticated):- Checks for vulnerable version of System.web.dll for .Net FrameworkConsequenceSuccessful exploitation allows attacker to cause denial of service vulnerability.SolutionCustomers are advised to refer to CVE-2022-21911 for more details pertaining to this vulnerability.Patches:The following are links for downloading patches to fix these vulnerabilities:CVE-2022-21911

When you are using an Microsoft 365 (formerly Office 365) installation or a Click-to-Run installation of Office 2013, Office 2016, Office 2019, and Office 2021, then the updates will not be offered via Windows Update but will be installed automatically. Depending on your installation source, you can manually check for updates from within any Office application or the Microsoft Store on Windows 10 and Windows 11.

My 2016 Forest seems to not be affected- no 1074 lsass.exe crash system events. However, my 2019 Forest did. uninstalling the kb5009557 took forever (30 minutes like mentioned above) to get past the 100% updates please wait on reboot but during that time, all authentications worked. I was finally able to check the update history and it is no longer on them. Servers are faster, too since the lsass.exe is not taking full CPU.

- Support removed for Windows 7 and Server 2008(R2) since Microsoft discontinued support for it on January 14th, 2020- Support removed for Microsoft Security Essentials, Windows 7 Defender, Service Packs, Remote Desktop Client and Silverlight (download switches /includemsse and /excludesp, update switches /instmsse, /instmssl and /updatetsc)- Support removed for Windows 10 version 1703 since Microsoft discontinued support for it on October 8th, 2019- Split Windows 10 download into version specific parts- Included complete rewrite of the Linux scripts version 1.19 (Special thanks to H. Buhrmester)- March 2020 updates added to 'security only' lists for Windows 8.1 and Server 2012 / 2012 R2 (x86/x64) systems- Included improved XSLT filter for the determination of dynamic Office updates by Product Id rather than ProductFamily Id (Special thanks to H. Buhrmester)- Replaced superseded November 2019 Servicing stack update (kb4523200) by March 2020 Servicing stack update (kb4540721) for Windows 10 Version 1507 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4520724) by March 2020 Servicing stack update (kb4540723) for Windows 10 Version 1607 and Windows Server 2016 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523202) by March 2020 Servicing stack update (kb4541731) for Windows 10 Version 1709 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523203) by March 2020 Servicing stack update (kb4540724) for Windows 10 Version 1803 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523204) by March 2020 Servicing stack update (kb4539571) for Windows 10 Version 1809 and Windows Server 2019 (Thanks to "aker")- Replaced superseded February 2020 Servicing stack update (kb4538674) by March 2020 Servicing stack update (kb4541338) for Windows 10 Version 1903 and 1909 (Thanks to "aker")- Fix: Invalid --no-check-certificate option for Aria2 download utility (Thanks to "negg", "Dalai", "hbuhrmester" and "Gerby")- Fix: Wget utility didn't any longer download root certificates properly due to user agent aware responses from microsoft.com (Thanks to "aker")- Fix: Adjusted installation sequence to have root certificate packages installed before all all others (Thanks to "aker")

- Included complete rewrite of the Linux scripts version 1.19 (Special thanks to H. Buhrmester)- March 2020 updates added to 'security only' lists for Windows 8.1 and Server 2012 / 2012 R2 (x86/x64) systems- Included improved XSLT filter for the determination of dynamic Office updates by Product Id rather than ProductFamily Id (Special thanks to H. Buhrmester)- Replaced superseded November 2019 Servicing stack update (kb4523200) by March 2020 Servicing stack update (kb4540721) for Windows 10 Version 1507 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4520724) by March 2020 Servicing stack update (kb4540723) for Windows 10 Version 1607 and Windows Server 2016 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523201) by March 2020 Servicing stack update (kb4540722) for Windows 10 Version 1703 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523202) by March 2020 Servicing stack update (kb4541731) for Windows 10 Version 1709 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523203) by March 2020 Servicing stack update (kb4540724) for Windows 10 Version 1803 (Thanks to "aker")- Replaced superseded November 2019 Servicing stack update (kb4523204) by March 2020 Servicing stack update (kb4539571) for Windows 10 Version 1809 and Windows Server 2019 (Thanks to "aker")- Replaced superseded February 2020 Servicing stack update (kb4538674) by March 2020 Servicing stack update (kb4541338) for Windows 10 Version 1903 and 1909 (Thanks to "aker")- Fix: Invalid --no-check-certificate option for Aria2 download utility (Thanks to "negg", "Dalai", "hbuhrmester" and "Gerby")- Fix: Wget utility didn't any longer download root certificates properly due to user agent aware responses from microsoft.com (Thanks to "aker")- Fix: Adjusted installation sequence to have root certificate packages installed before all all others (Thanks to "aker") 2ff7e9595c