Editing Windows Update (section)

==Clients==
===Windows Update web app===
[[File:Win Update ME.png|thumb|left|The Windows Update web app, version 4, in [[Windows Me]]]]
Windows Update was introduced as a [[web app]] with the launch of [[Windows 98]] and offered additional [[Theme (computing)|desktop themes]], [[Video game|games]], [[device driver]] updates, and optional components such as [[NetMeeting]].<ref>{{cite web|url=http://www.techweb.com/wire/story/win98/TWB19980625S0017|title=Taking Windows 98 For A Test-Drive|last=Gartner|first=John|date=24 August 1995|website=TechWeb|publisher=CMP Net|archive-url=https://web.archive.org/web/19981203021627/http://www.techweb.com/wire/story/win98/TWB19980625S0017|archive-date=3 December 1998
}}</ref> [[Windows 95]] and [[Windows NT 4.0]] were retroactively given the ability to access the Windows Update website and download updates designed for those operating systems, starting with the release of [[Internet Explorer 4]]. The initial focus of Windows Update was free add-ons and new technologies for Windows. Security fixes for [[Outlook Express]], Internet Explorer and other programs appeared later, as did access to beta versions of upcoming Microsoft software, e.g. [[Internet Explorer 5]]. Fixes to Windows 98 to resolve the [[Year 2000 problem]] were distributed using Windows Update in December 1998. Microsoft attributed the sales success of Windows 98 in part to Windows Update.<ref>{{cite press release|url=http://www.microsoft.com/presspass/press/1999/feb99/holislpr.mspx|title=Strong Holiday Sales Make Windows 98 Best-Selling Software of 1998|date=9 February 1999|access-date=2008-07-29|work=PressPass|publisher=[[Microsoft]]|archive-date=6 March 2012|archive-url=https://web.archive.org/web/20120306183421/http://www.microsoft.com/presspass/press/1999/feb99/holislpr.mspx|url-status=live}}</ref>

The Windows Update web app requires either [[Internet Explorer]] or a third-party [[web browser]] that supports the [[ActiveX]] technology. The earliest version of the web app, version 3, does not send any personally identifiable information to Microsoft. Instead, the app downloads a full list of every available update and chooses which one to download and install. But the list grew so large that the performance impact of processing became a concern. Arie Slob, writing for the Windows-help.net newsletter in March 2003, noted that the size of the update list had exceeded {{Nowrap|400 [[Kilobyte|KB]]}}, which caused delays of more than a minute for [[dial-up Internet access|dial-up]] users.<ref name="arieslob">{{cite web|url=http://www.windowsnewsletter.com/html-archive/2003/22mar2003.html|title=Windows Update is Spying on You!|last=Slob|first=Arie|date=March 22, 2003|website=Windows-Help.NET|publisher=InfiniSource|url-status=dead|archive-url=https://web.archive.org/web/20180114020429/http://www.windowsnewsletter.com/html-archive/2003/22mar2003.html|archive-date=January 14, 2018|access-date=September 12, 2019}}</ref> Windows Update v4, released in 2001 in conjunction with [[Windows XP]], changed this. This version of the app makes an inventory of the system's hardware and Microsoft software and sends them to the service, thus offloading the processing burden to Microsoft [[Server (computing)|servers]].<ref name="arieslob" />{{Clear}}

===Critical Update Notification Utility===
[[File:Windows 98 - Critical Update Notification.png|thumb|Screenshot of the Critical Update Notification [[dialog box]] in [[Windows 98]]|alt=]]
''Critical Update Notification Utility'' (initially ''Critical Update Notification Tool'') is a [[background process]] that checks the Windows Update website on a regular schedule for new updates that have been marked as "Critical." It was released shortly after Windows 98.

By default, this check occurs every five minutes, plus when Internet Explorer starts; however, the user could configure the next check to occur only at certain times of the day or on certain days of the week. The tool queries the Microsoft server for a file called "<code>cucif.cab</code>", which contained<!--Not anymore--> a list of all the critical updates released for the operating system. The tool then compares this list with the list of installed updates on its machine and displays an update availability notification. Once the check is executed, any custom schedule defined by the user is reverted to the default. Microsoft stated that this ensures that users receive notification of critical updates in a timely manner.<ref name="cun-kb">{{Cite web |url=https://support.microsoft.com/en-us/help/224420/description-of-the-windows-critical-update-notification-utility |title=Description of the Windows Critical Update Notification utility |date=5 December 2007 |website=Support |publisher=[[Microsoft]] |access-date=22 November 2018 |archive-date=26 July 2020 |archive-url=https://web.archive.org/web/20200726012559/https://support.microsoft.com/en-us/help/224420/description-of-the-windows-critical-update-notification-utility |url-status=live }}</ref>

An analysis done by security researcher [[H. D. Moore]] in early 1999 was critical of this approach, describing it as "horribly inefficient" and susceptible to attacks. In a posting to [[BugTraq]], he explained that, "every single Windows 98 computer that wishes to get an update has to rely on a single host for the security. If that one server got compromised one day, or an attacker cracked the [Microsoft] DNS server again, there could be millions of users installing [[trojan horse (computing)|trojans]] every hour. The scope of this attack is big enough to attract crackers who actually know what they are doing..."<ref>{{Cite web |url=http://seclists.org/bugtraq/1999/Jan/0400.html |title=How the MS Critical Update Notification works... |last=Moore |first=H. D. |date=29 January 1999 |website=BugTraq mailing list archive |via=seclists.org |access-date=30 July 2008 |archive-date=21 June 2009 |archive-url=https://web.archive.org/web/20090621010729/http://seclists.org/bugtraq/1999/Jan/0400.html |url-status=live }}</ref>

Microsoft continued to promote the tool through 1999 and the first half of 2000. Initial releases of [[Windows 2000]] shipped with the tool. The tool did not support Windows 95 and Windows NT 4.0.

===Automatic Updates===
[[File:Winautoupdates.PNG|thumb|Automatic Updates "Restart Required" [[dialog box]] in [[Windows XP]] Service Pack 1|alt=]]
''Automatic Updates'' is the successor of the Critical Update Notification Utility. It was released in 2000, along with [[Windows Me]]. It supports Windows 2000 SP3 as well.

Unlike its predecessor, Automatic Updates can download and install updates. Instead of the five-minute schedule used by its predecessor, Automatic Updates checks the Windows Update servers once a day. After Windows Me is installed, a [[balloon help|notification balloon]] prompts the user to configure the Automatic Updates client. The user can choose from three notification schemes: being notified before downloading the update, being notified before installing the update, or both. If new updates are ready to be installed, the user may install them before turning off the computer. A shield icon will be displayed on the [[Shutdown (computing)|Shutdown]] button during this time.

Windows XP and Windows 2000 SP3 include [[Background Intelligent Transfer Service]], a [[Windows service]] for transferring files in the background without user interaction. As a system component, it is capable of monitoring the user's Internet usage and throttling its own bandwidth usage in order to prioritize user-initiated activities. The Automatic Updates client for these operating systems was updated to use this system service.

Automatic Updates in Windows XP gained notoriety for repeatedly interrupting the user while working on their computer. Every time an update requiring a reboot was installed, Automatic Updates would prompt the user with a dialog box that allowed the user to restart immediately or dismiss the dialog box, which would reappear in ten minutes; a behavior that [[Jeff Atwood]] described as "perhaps the naggiest dialog box ever."<ref name="atwood">{{cite web|url=https://blog.codinghorror.com/xp-automatic-update-nagging/|title=XP Automatic Update Nagging|last=Atwood|first=Jeff|author-link=Jeff Atwood|date=13 May 2005|website=Coding Horror: Programming and Human Factors|access-date=September 12, 2019|archive-date=9 November 2021|archive-url=https://web.archive.org/web/20211109191749/https://blog.codinghorror.com/xp-automatic-update-nagging/|url-status=live}}</ref>

In 2013, it was observed that shortly after the [[Booting|startup process]], Automatic Updates (<code>wuauclt.exe</code>) and Service Host (<code>[[svchost.exe]])</code> in Windows XP would claim 100% of a computer's CPU capacity for extended periods of time (between ten minutes to two hours), making affected computers unusable. According to Woody Leonhart of [[InfoWorld]], early reports of this issue could be seen in [[Microsoft TechNet]] [[Internet forum|forums]] in late May 2013, although Microsoft first received a large number of complaints about this issue in September 2013. The cause was an [[exponential algorithm]] in the evaluation of superseded updates, which had grown large over the decade following the release of Windows XP. Microsoft's attempts to fix the issue in October, November and December proved futile, causing the issue to be escalated to the top priority.<ref>{{Cite web|url=https://arstechnica.com/information-technology/2013/12/exponential-algorithm-making-windows-xp-miserable-could-be-fixed/|title=Exponential algorithm making Windows XP miserable could be fixed|last=Bright|first=Peter|date=December 16, 2013|website=[[Ars Technica]]|publisher=[[Condé Nast]]|access-date=September 12, 2019|archive-date=6 May 2021|archive-url=https://web.archive.org/web/20210506000837/https://arstechnica.com/information-technology/2013/12/exponential-algorithm-making-windows-xp-miserable-could-be-fixed/|url-status=live}}</ref><ref>{{Cite web|url=https://www.infoworld.com/article/2609615/microsoft-promises-to-fix-windows-xp-svchost-redlining--as-soon-as-possible-.html|title=Microsoft promises to fix Windows XP SVCHOST redlining 'as soon as possible'|last=Leonhard|first=Woody|date=December 16, 2013|website=[[InfoWorld]]|publisher=[[IDG]]|access-date=September 12, 2019|archive-date=30 March 2019|archive-url=https://web.archive.org/web/20190330032404/https://www.infoworld.com/article/2609615/microsoft-promises-to-fix-windows-xp-svchost-redlining--as-soon-as-possible-.html|url-status=live}}</ref>

===Windows Update Agent===
[[File:Windows Update Restart Vista.png|thumb|Revised restart [[dialog box]] in [[Windows Vista]]|alt=]]
Starting with [[Windows Vista]] and [[Windows Server 2008]], ''Windows Update Agent'' replaces both the Windows Update web app and the Automatic Updates client.<ref>{{Cite web|url=https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-version|title=How to update the Windows Update Agent to the latest version|date=6 June 2017|website=Support|publisher=[[Microsoft]]|access-date=22 November 2018|archive-date=4 September 2020|archive-url=https://web.archive.org/web/20200904183049/https://support.microsoft.com/en-us/help/949104/how-to-update-the-windows-update-agent-to-the-latest-version|url-status=live}}</ref><ref>{{Cite web|url=https://technet.microsoft.com/en-us/library/cc735627(v=ws.10).aspx|title=Windows Update Agent|date=13 December 2007|website=[[Microsoft TechNet|TechNet]]|publisher=[[Microsoft]]|access-date=22 November 2018|archive-date=14 January 2018|archive-url=https://web.archive.org/web/20180114073712/https://technet.microsoft.com/en-us/library/cc735627(v=ws.10).aspx|url-status=live}}</ref> It is in charge of downloading and installing software update from Windows Update, as well as the on-premises servers of [[Windows Server Update Services|Windows Server Updates Services]] or [[System Center Configuration Manager]].<ref>{{Cite web|url=https://technet.microsoft.com/en-us/library/bb932139.aspx|title=How to Install the Windows Update Agent on Client Computers|date=2007|website=[[Microsoft TechNet|TechNet]]|publisher=[[Microsoft]]|access-date=22 November 2018|archive-date=11 October 2018|archive-url=https://web.archive.org/web/20181011053744/https://technet.microsoft.com/en-us/library/bb932139.aspx|url-status=live}}</ref><ref>{{Cite web|url=http://searchwindowsserver.techtarget.com/definition/Microsoft-Windows-Update-Agent|title=Microsoft Windows Update Agent|last=Rouse|first=Margaret|date=May 2014|website=TechTarget|access-date=22 November 2018|archive-date=27 January 2021|archive-url=https://web.archive.org/web/20210127080207/https://searchwindowsserver.techtarget.com/definition/Microsoft-Windows-Update-Agent|url-status=live}}</ref>

Windows Update Agent can be managed through a [[Control Panel (Windows)|Control Panel]] applet, as well as [[Group Policy]], [[Microsoft Intune]] and [[Windows PowerShell]]. It can also be set to automatically download and install both ''important'' and ''recommended'' updates. In prior versions of Windows, such updates were only available through the Windows Update website. Additionally, Windows Update in Windows Vista supports downloading [[Windows Ultimate Extras]], optional software for Windows Vista Ultimate Edition.

Unlike Automatic Updates in Windows XP, Windows Update Agent in Windows Vista and Windows 7 allows the user to postpone the mandatory restart (required for the update process to complete) for up to four hours. The revised dialog box that prompts for the restart appears under other windows, instead of on top of them. However, standard user accounts only have 15 minutes to respond to this dialog box. This was changed with [[Windows 8]]: Users have 3 days (72 hours) before the computer reboots automatically after installing automatic updates that require a reboot. Windows 8 also consolidates the restart requests for non-critical updates into just one per month. Additionally, the login screen notifies them of the restart requirements.<ref>{{cite web |last=Savov |first=Vlad |url=https://www.theverge.com/2011/11/15/2563251/windows-8-update-restart-consolidation |title=Windows 8 auto-update will consolidate restarts into one per month, give you three days to do it |website=[[The Verge]] |publisher=[[Vox Media]] |date=15 November 2011 |access-date=22 November 2018 |archive-date=29 August 2021 |archive-url=https://web.archive.org/web/20210829051505/https://www.theverge.com/2011/11/15/2563251/windows-8-update-restart-consolidation |url-status=live }}</ref>

Windows Update Agent makes use of the [[Transactional NTFS]] feature introduced with Windows Vista to apply updates to Windows system files. This feature helps Windows recover cleanly in the event of an unexpected failure, as file changes are committed [[atomicity (database systems)|atomically]].<ref name="filecab">{{cite web |title=NTFS Beta Chat Transcript (July 12, 2006) |url=https://blogs.technet.microsoft.com/filecab/2006/09/20/ntfs-beta-chat-transcript-july-12-2006/ |date=12 July 2006 |work=Storage at Microsoft |publisher=Microsoft |access-date=22 November 2018 |archive-date=20 April 2019 |archive-url=https://web.archive.org/web/20190420233542/https://blogs.technet.microsoft.com/filecab/2006/09/20/ntfs-beta-chat-transcript-july-12-2006/ |url-status=live }}</ref>

Since [[Windows 8]], the Windows Update is able to offers device firmware updates, for example [[UEFI]].

[[Windows 10]] contains major changes to Windows Update Agent operations; it no longer allows the manual, selective installation of updates. All updates, regardless of type (this includes hardware drivers), are downloaded and installed automatically, and users are only given the option to choose whether their system would reboot automatically to install updates when the system is inactive or be notified to schedule a reboot.<ref name=cnet-scheduleupdate>{{cite web|title=Windows 10 lets you schedule Windows Update restarts|url=http://www.cnet.com/how-to/windows-10-lets-you-schedule-windows-update-restarts/|website=CNET|access-date=4 August 2015|archive-date=19 February 2015|archive-url=https://web.archive.org/web/20150219130153/http://www.cnet.com/how-to/windows-10-lets-you-schedule-windows-update-restarts/|url-status=live}}</ref><ref name=crn-updates>{{cite web|title=Did Microsoft Just Backtrack On Forced Updates For Windows 10?|url=http://www.crn.com/news/applications-os/300077576/did-microsoft-just-backtrack-on-forced-updates-for-windows-10.htm|website=CRN.com|date=27 July 2015|access-date=4 August 2015|archive-date=28 July 2015|archive-url=https://web.archive.org/web/20150728071222/http://www.crn.com/news/applications-os/300077576/did-microsoft-just-backtrack-on-forced-updates-for-windows-10.htm|url-status=live}}</ref> Microsoft offers a diagnostic tool that can be used to hide troublesome device drivers and prevent them from being reinstalled, but only after they had already been installed and then uninstalled without rebooting the system.<ref name=iw-nvidiadriver>{{cite web|title=On the road to Windows 10: Nvidia driver tests KB 3073930 patch blocker|url=http://www.infoworld.com/article/2952996/microsoft-windows/on-the-road-to-windows-10-botched-nvidia-driver-tests-kb-3073930-patch-blocker.html|website=InfoWorld|date=27 July 2015|access-date=31 July 2015|archive-date=20 June 2017|archive-url=https://web.archive.org/web/20170620044549/http://www.infoworld.com/article/2952996/microsoft-windows/on-the-road-to-windows-10-botched-nvidia-driver-tests-kb-3073930-patch-blocker.html|url-status=live}}</ref><ref name=iw-3073930>{{cite web|title=On the road to Windows 10: Problems with forced updates and KB 3073930|url=http://www.infoworld.com/article/2951214/microsoft-windows/on-the-road-to-windows-10-problems-with-forced-updates-and-kb-3073930.html|website=InfoWorld|date=22 July 2015|access-date=31 July 2015|archive-date=20 June 2017|archive-url=https://web.archive.org/web/20170620052143/http://www.infoworld.com/article/2951214/microsoft-windows/on-the-road-to-windows-10-problems-with-forced-updates-and-kb-3073930.html|url-status=live}}</ref>

Windows Update Agent on Windows 10 supports [[peer-to-peer]] distribution of updates; by default, systems' [[bandwidth (computing)|bandwidth]] is used to distribute previously downloaded updates to other users, in combination with Microsoft servers. Users may optionally change Windows Update to only perform peer-to-peer updates within their [[local area network]].<ref name=pcw-peertopeer>{{cite web|title=How to stop Windows 10 from using your PC's bandwidth to update strangers' systems|url=http://www.pcworld.com/article/2955491/windows/how-to-stop-windows-10-from-using-your-pcs-bandwidth-to-update-strangers-systems.html|website=PC World|publisher=IDG|access-date=4 August 2015|archive-date=5 August 2015|archive-url=https://web.archive.org/web/20150805145115/http://www.pcworld.com/article/2955491/windows/how-to-stop-windows-10-from-using-your-pcs-bandwidth-to-update-strangers-systems.html|url-status=live}}</ref>

Windows 10 also introduced cumulative updates. For example, if Microsoft released updates KB00001 in July, KB00002 in August, and KB00003 in September, Microsoft would release cumulative update KB00004, which packs KB00001, KB00002, and KB00003 together. Installing KB00004 will also install KB00001, KB00002 and KB00003, mitigating the need for multiple restarts and reducing the number of downloads needed. KB00004 may also include other fixes with their own KB number that were not separately released.<ref>{{Cite web |url=https://support.microsoft.com/en-us/help/4133604/ |title=User can't log on to a POP/IMAP account by using NTLM authentication in Exchange Server 2013 |quote=To resolve this issue, install Cumulative Update 21 |access-date=24 March 2020 |archive-date=10 February 2021 |archive-url=https://web.archive.org/web/20210210014628/https://support.microsoft.com/en-us/topic/user-can-t-log-on-to-a-pop-imap-account-by-using-ntlm-authentication-in-exchange-server-2013-22c7f67d-87a5-75d2-501e-82cdc21f94b9 |url-status=live }}</ref> A disadvantage of cumulative updates is that downloading and installing updates that fix individual problems is no longer possible. KB stands for knowledge base, as in [[Microsoft Knowledge Base]].

===Windows Update for Business===
''Windows Update for Business'' is a term for a set of features in the [[Windows 10 editions|Pro, Enterprise and Education editions of Windows 10]], intended to ease the administration of Windows across organizations. It enables IT pros to:<ref name="WUfB1">{{Cite web|last=Hammoudi|first=Samir|date=15 November 2015|title=Windows Update for Business explained|url=https://blogs.msdn.microsoft.com/beanexpert/2015/11/15/windows-update-for-business-explained/|url-status=dead|website=beanexpert|publisher=[[Microsoft]]|access-date=14 January 2018|archive-date=19 April 2019|archive-url=https://web.archive.org/web/20190419173000/https://blogs.msdn.microsoft.com/beanexpert/2015/11/15/windows-update-for-business-explained/}}</ref><ref name="WUfB2">{{Cite web|last=Azzarello|first=Pat|date=10 May 2017|title=What is Windows Update for Business?|url=https://blogs.technet.microsoft.com/windowsitpro/2017/05/10/what-is-windows-update-for-business/|url-status=dead|archive-url=https://web.archive.org/web/20180611031330/https://blogs.technet.microsoft.com/windowsitpro/2017/05/10/what-is-windows-update-for-business/|archive-date=11 June 2018|website=Windows for IT Pros|publisher=[[Microsoft]]|quote=Windows Update for Business is intended for machines running Windows 10 or later, and Windows 10 Education, Professional, or Enterprise editions managed in organizations.|access-date=14 January 2018}}</ref><ref name="WUfB3">{{Cite web |url=https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb |title=Deploy updates using Windows Update for Business |last1=Halfin |first1=Danni |last2=Brower |first2=Nick |date=13 October 2017 |website=Microsoft Docs |publisher=[[Microsoft]] |last3=Lich |first3=Brian |last4=Poggemeyer |first4=Liza |access-date=22 November 2018 |archive-date=22 October 2021 |archive-url=https://web.archive.org/web/20211022191359/https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb |url-status=live }}</ref>
* Switch between the standard and the deferred [[Windows 10 editions#Release branches|release branches of Windows 10]]. This feature has since been removed as Microsoft retired the deferred branch.<ref>{{Cite web|title=Microsoft changes Windows Update for Business options - gHacks Tech News|url=https://www.ghacks.net/2019/02/15/microsoft-changes-windows-update-for-business-options/|access-date=2020-11-03|website=www.ghacks.net|date=15 February 2019|archive-date=6 October 2021|archive-url=https://web.archive.org/web/20211006091519/https://www.ghacks.net/2019/02/15/microsoft-changes-windows-update-for-business-options/|url-status=live}}</ref>
* Defer automatic installation of ordinary updates for 30 days. Starting with Windows 10 version 20H1, this feature is more difficult to access.<ref name=":0">{{Cite web|title=Microsoft removes Setting to defer feature updates from Windows 10 version 2004 - gHacks Tech News|url=https://www.ghacks.net/2020/06/25/microsoft-removes-setting-to-defer-feature-updates-from-windows-10-version-2004/|access-date=2020-11-03|website=www.ghacks.net|date=25 June 2020|archive-date=27 August 2021|archive-url=https://web.archive.org/web/20210827220048/https://www.ghacks.net/2020/06/25/microsoft-removes-setting-to-defer-feature-updates-from-windows-10-version-2004/|url-status=live}}</ref>
* Defer automatic installation of Windows upgrades (a.k.a. "feature updates") for 365 days. Starting with Windows 10 version 20H1, these updates are no longer automatically offered.<ref name=":0" />

These features were added in Windows 10 version 1511.<ref name="WUfB-EdBott">{{cite web|last1=Bott|first1=Ed|title=How to take control of Windows 10 updates and upgrades (even if you don't own a business)|url=https://www.zdnet.com/article/how-to-take-control-of-windows-10-updates-and-upgrades-even-if-you-dont-own-a-business/|website=[[ZDNet]]|publisher=[[CBS Interactive]]|date=17 January 2018|access-date=22 November 2018|archive-date=12 November 2021|archive-url=https://web.archive.org/web/20211112005437/https://www.zdnet.com/article/how-to-take-control-of-windows-10-updates-and-upgrades-even-if-you-dont-own-a-business/|url-status=live}}</ref> They are intended for large organizations with many computers, so they can logically group their computers for gradual deployment. Microsoft recommends a small set of pilot computers to receive the updates almost immediately, while the set of most critical computers receives them after every other group has done so, and has experienced their effects.<ref>{{cite web|last1=Halfin|first1=Danni|last2=Lich|first2=Brian|title=Build deployment rings for Windows 10 updates|url=https://docs.microsoft.com/en-us/windows/deployment/update/waas-deployment-rings-windows-10-updates|website=Microsoft Docs|publisher=[[Microsoft]]|date=27 July 2017|access-date=22 November 2018|archive-date=24 May 2021|archive-url=https://web.archive.org/web/20210524234443/https://docs.microsoft.com/en-us/windows/deployment/update/waas-deployment-rings-windows-10-updates|url-status=live}}</ref>

Other Microsoft update management solutions, such as [[Windows Server Update Services]] or [[System Center Configuration Manager]], do not override Windows Update for Business. Rather, they force Windows 10 into the "dual scan mode". his can cause confusion for administrators who do not comprehend the full ramifications of the dual scan mode.<ref>{{cite web|last1=Rasheed|first1=Shadab|title=Why WSUS and SCCM managed clients are reaching out to Microsoft Online|url=https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/|website=Windows Server Blog|publisher=[[Microsoft]]|date=9 January 2017|access-date=22 November 2018|archive-date=14 January 2018|archive-url=https://web.archive.org/web/20180114184020/https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/|url-status=live}}</ref>