{"id":185,"date":"2026-05-30T23:24:54","date_gmt":"2026-05-31T06:24:54","guid":{"rendered":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/"},"modified":"2026-05-30T23:24:54","modified_gmt":"2026-05-31T06:24:54","slug":"how-to-manage-windows-server-updates","status":"publish","type":"post","link":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/","title":{"rendered":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS"},"content":{"rendered":"<h2>Overview<\/h2>\n<p>Windows updates patch security vulnerabilities, fix bugs, and occasionally introduce new features. On a production server, managing those updates carelessly can cause downtime, driver conflicts, or broken applications. This article covers how to handle Windows Server updates properly \u2014 whether you&#8217;re patching a single VPS manually or rolling out patches across multiple machines using WSUS (Windows Server Update Services).<\/p>\n<p>Most server outages I&#8217;ve seen from updates come down to one thing: updates applied without a maintenance window, without a snapshot, and without knowing what&#8217;s actually being installed. This guide is designed to fix that habit.<\/p>\n<p>It applies to Windows Server 2016, 2019, and 2022. Some PowerShell syntax differs on 2016 \u2014 I&#8217;ll call those out where relevant.<\/p>\n<h2>Prerequisites<\/h2>\n<ul>\n<li>Administrator or Local Administrator access to the Windows Server instance<\/li>\n<li>PowerShell 5.1 or later (built into Windows Server 2016+)<\/li>\n<li>Internet connectivity from the server, or access to a WSUS server on your internal network<\/li>\n<li>A recent backup or snapshot of the server before applying updates \u2014 non-negotiable on production<\/li>\n<li>For WSUS setup: a separate Windows Server instance with at minimum 10 GB free disk space for the update catalogue (40\u201380 GB is more realistic in practice)<\/li>\n<li>Outbound access to <code class=\"\" data-line=\"\">windowsupdate.microsoft.com<\/code> and <code class=\"\" data-line=\"\">update.microsoft.com<\/code> on port 443 if not using WSUS<\/li>\n<\/ul>\n<h2>Method 1: Manual Updates via Windows Update Settings<\/h2>\n<p>This is the right approach for a single server or a quick one-off patch. It&#8217;s straightforward but gives you full visibility over what&#8217;s being installed.<\/p>\n<ol>\n<li>Open <strong>Server Manager<\/strong>, then click <strong>Local Server<\/strong> in the left panel.<\/li>\n<li>Find <strong>Windows Update<\/strong> in the properties panel. Click the linked status text next to it (e.g. &#8220;Not configured&#8221; or &#8220;Last checked&#8230;&#8221;).<\/li>\n<li>In the Windows Update settings window, click <strong>Check for updates<\/strong>.<\/li>\n<li>Review the listed updates before installing. Pay attention to anything marked as a cumulative update or feature update \u2014 those take longer to install and almost always require a reboot.<\/li>\n<li>Click <strong>Install now<\/strong> once you&#8217;re ready. Schedule the reboot for your next maintenance window if prompted.<\/li>\n<\/ol>\n<p>\ud83d\udcdd Note: On Windows Server Core (no GUI), this method isn&#8217;t available. Use PowerShell instead \u2014 see Method 2.<\/p>\n<h2>Method 2: Managing Updates with PowerShell<\/h2>\n<p>PowerShell gives you more control and is essential for Server Core deployments or automation. The <code class=\"\" data-line=\"\">PSWindowsUpdate<\/code> module is the most reliable way to handle this \u2014 it&#8217;s a community module but it&#8217;s been widely used in enterprise environments for years and is actively maintained.<\/p>\n<h3>Step 1: Install the PSWindowsUpdate module<\/h3>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-1\"><code class=\"\" data-line=\"\">Install-Module -Name PSWindowsUpdate -Force -Scope AllUsers\nImport-Module PSWindowsUpdate<\/code><\/pre>\n<\/div>\n<p>\ud83d\udcdd Note: You may need to set your execution policy first. Run <code class=\"\" data-line=\"\">Set-ExecutionPolicy RemoteSigned<\/code> in an elevated PowerShell session if the install fails with a script restriction error.<\/p>\n<h3>Step 2: Check available updates<\/h3>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-2\"><code class=\"\" data-line=\"\">Get-WindowsUpdate<\/code><\/pre>\n<\/div>\n<p>This lists all available updates with their KB numbers, size, and titles. I&#8217;d always run this before installing so you know exactly what&#8217;s queued.<\/p>\n<h3>Step 3: Install all available updates<\/h3>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-3\"><code class=\"\" data-line=\"\">Install-WindowsUpdate -AcceptAll -AutoReboot<\/code><\/pre>\n<\/div>\n<p>\u26a0 Warning: The <code class=\"\" data-line=\"\">-AutoReboot<\/code> flag will reboot the server immediately after updates finish \u2014 without prompting. Only use this during a scheduled maintenance window. Drop that flag if you want to control the reboot manually.<\/p>\n<h3>Step 4: Install only security updates (recommended for production)<\/h3>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-4\"><code class=\"\" data-line=\"\">Install-WindowsUpdate -Category &#039;Security Updates&#039; -AcceptAll -AutoReboot<\/code><\/pre>\n<\/div>\n<p>Limiting updates to security patches reduces the risk of a cumulative update pulling in changes you haven&#8217;t tested. In my experience, this is what most sysadmins do on production boxes \u2014 security patches on a regular cycle, feature\/cumulative updates tested first in staging.<\/p>\n<h3>Step 5: Check update history<\/h3>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-5\"><code class=\"\" data-line=\"\">Get-WUHistory | Select-Object -First 20 | Format-Table Date, Title, Result<\/code><\/pre>\n<\/div>\n<h2>Method 3: Setting Up WSUS for Centralised Patch Management<\/h2>\n<p>If you&#8217;re running multiple Windows servers \u2014 whether on a <a href=\"https:\/\/www.hostandtech.com\/dedicated\/\">Dedicated Server<\/a> environment or across a cluster \u2014 WSUS lets you approve, schedule, and audit updates from a single console. Clients pull updates from your WSUS server instead of hitting Microsoft&#8217;s servers directly, which also reduces outbound bandwidth.<\/p>\n<h3>Step 1: Install the WSUS role<\/h3>\n<p>Run this on the server you want to act as your WSUS host. Replace <code class=\"\" data-line=\"\">D:WSUS<\/code> with your chosen content directory \u2014 make sure the drive has plenty of space.<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-6\"><code class=\"\" data-line=\"\">Install-WindowsFeature -Name UpdateServices -IncludeManagementTools\n&amp; &#039;C:Program FilesUpdate ServicesToolsWsusUtil.exe&#039; postinstall CONTENT_DIR=D:WSUS<\/code><\/pre>\n<\/div>\n<h3>Step 2: Open the WSUS console and run the configuration wizard<\/h3>\n<ol>\n<li>Open <strong>Server Manager \u2192 Tools \u2192 Windows Server Update Services<\/strong>.<\/li>\n<li>The configuration wizard launches automatically on first run. Click through to <strong>Choose Upstream Server<\/strong>.<\/li>\n<li>Select <strong>Synchronize from Microsoft Update<\/strong> unless you have an upstream WSUS in a larger hierarchy.<\/li>\n<li>On the <strong>Choose Products<\/strong> screen, select only the Windows Server versions you&#8217;re actually running. Selecting everything massively inflates disk usage.<\/li>\n<li>On <strong>Choose Classifications<\/strong>, at minimum select <strong>Critical Updates<\/strong> and <strong>Security Updates<\/strong>. Add <strong>Definition Updates<\/strong> if you&#8217;re running Windows Defender on your servers.<\/li>\n<li>Set a synchronisation schedule \u2014 daily at an off-peak time works well for most setups.<\/li>\n<li>Click <strong>Begin Initial Synchronization<\/strong>. This first sync can take several hours depending on how many products you selected.<\/li>\n<\/ol>\n<h3>Step 3: Point client servers at WSUS using Group Policy<\/h3>\n<p>On each client server (or via a GPO applied to an OU), configure the following registry settings. Replace <code class=\"\" data-line=\"\">http:\/\/wsus-server:8530<\/code> with your actual WSUS server hostname and port.<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-7\"><code class=\"\" data-line=\"\">$wsusServer = &quot;http:\/\/wsus-server:8530&quot;\n\nSet-ItemProperty -Path &quot;HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdate&quot; `\n  -Name &quot;WUServer&quot; -Value $wsusServer -Type String\n\nSet-ItemProperty -Path &quot;HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdate&quot; `\n  -Name &quot;WUStatusServer&quot; -Value $wsusServer -Type String\n\nSet-ItemProperty -Path &quot;HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU&quot; `\n  -Name &quot;UseWUServer&quot; -Value 1 -Type DWord\n\nRestart-Service wuauserv<\/code><\/pre>\n<\/div>\n<h3>Step 4: Approve updates in the WSUS console<\/h3>\n<p>WSUS doesn&#8217;t auto-approve updates by default \u2014 you need to explicitly approve them for each computer group. In the WSUS console, go to <strong>Updates \u2192 All Updates<\/strong>, filter by <strong>Unapproved<\/strong>, review the list, right-click and select <strong>Approve<\/strong>. Assign to the relevant computer group and set the deadline.<\/p>\n<p>\ud83d\udcdd Note: Create separate computer groups for staging and production. Approve to staging first, wait a few days, then approve to production. This one habit has saved me from rolling back a broken update more than once.<\/p>\n<h2>Deferring Updates on Windows Server<\/h2>\n<p>If you need to delay a specific update without disabling Windows Update entirely, you can configure deferral periods via Group Policy or registry. On Windows Server 2019 and 2022:<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-8\"><code class=\"\" data-line=\"\"># Defer quality updates by 7 days\nSet-ItemProperty -Path &quot;HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU&quot; `\n  -Name &quot;DeferQualityUpdates&quot; -Value 1 -Type DWord\n\nSet-ItemProperty -Path &quot;HKLM:SOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU&quot; `\n  -Name &quot;DeferQualityUpdatesPeriodInDays&quot; -Value 7 -Type DWord<\/code><\/pre>\n<\/div>\n<p>\u26a0 Warning: Deferring updates is a short-term tool, not a long-term strategy. Servers left unpatched for weeks become a real liability, especially on public-facing infrastructure.<\/p>\n<h2>Common Issues &amp; Troubleshooting<\/h2>\n<h3>Windows Update stuck at 0% or hangs during download<\/h3>\n<p>This is usually a corrupt update cache. The fix is to clear the SoftwareDistribution folder, which forces Windows Update to re-download fresh metadata.<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-9\"><code class=\"\" data-line=\"\">Stop-Service wuauserv\nStop-Service cryptSvc\nStop-Service bits\nRename-Item -Path C:WindowsSoftwareDistribution -NewName SoftwareDistribution.old\nRename-Item -Path C:WindowsSystem32catroot2 -NewName catroot2.old\nStart-Service wuauserv\nStart-Service cryptSvc\nStart-Service bits<\/code><\/pre>\n<\/div>\n<p>After running this, check for updates again. The old folders can be deleted once updates are working.<\/p>\n<h3>Error 0x80072EFE or 0x80072EE2 \u2014 cannot connect to Windows Update<\/h3>\n<p>These are network connectivity errors. Check that the server can reach <code class=\"\" data-line=\"\">windowsupdate.microsoft.com<\/code> on port 443. If you&#8217;re behind a firewall, the outbound rule may be blocking it. Also check that your DNS is resolving correctly \u2014 a misconfigured DNS server is a surprisingly common cause of this on newly provisioned machines.<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-10\"><code class=\"\" data-line=\"\">Test-NetConnection -ComputerName windowsupdate.microsoft.com -Port 443<\/code><\/pre>\n<\/div>\n<h3>WSUS clients not appearing in the console<\/h3>\n<p>After pointing a client at WSUS, it can take up to 15 minutes to check in. If it still doesn&#8217;t appear, force a detection cycle manually on the client:<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-11\"><code class=\"\" data-line=\"\">wuauclt \/detectnow\n# On Windows Server 2016+ this is more reliable:\nUsoClient StartScan<\/code><\/pre>\n<\/div>\n<p>Also double-check the <code class=\"\" data-line=\"\">UseWUServer<\/code> registry value is set to <code class=\"\" data-line=\"\">1<\/code> and that the WSUS service is running on the server.<\/p>\n<h3>Update fails to install and rolls back<\/h3>\n<p>Check the CBS (Component Based Servicing) log for the actual error. It&#8217;s far more useful than the generic Windows Update error code.<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-12\"><code class=\"\" data-line=\"\">Get-Content C:WindowsLogsCBSCBS.log | Select-String &quot;FAIL|ERROR&quot; | Select-Object -Last 50<\/code><\/pre>\n<\/div>\n<p>A common cause is a corrupted system image. Run this before retrying the update:<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-13\"><code class=\"\" data-line=\"\">DISM \/Online \/Cleanup-Image \/RestoreHealth\nsfc \/scannow<\/code><\/pre>\n<\/div>\n<h3>WSUS disk fills up unexpectedly<\/h3>\n<p>WSUS accumulates superseded updates that are no longer needed. Run the built-in cleanup wizard regularly: in the WSUS console go to <strong>Options \u2192 Server Cleanup Wizard<\/strong> and run all cleanup options. On large deployments I&#8217;d schedule this monthly via PowerShell:<\/p>\n<div class=\"ht-code-snippet\"><button class=\"ht-code-snippet__copy\" type=\"button\" aria-label=\"Copy code\"><\/button><span class=\"ht-code-snippet__feedback\">Copied to clipboard<\/span><\/p>\n<pre class=\"ht-code-snippet__code\" id=\"code-block-14\"><code class=\"\" data-line=\"\">Invoke-WsusServerCleanup -CleanupObsoleteUpdates -CleanupUnneededContentFiles -DeclineExpiredUpdates -DeclineSupersededUpdates<\/code><\/pre>\n<\/div>\n<div class=\"ht-faq-section\">\n<h2>Frequently Asked Questions<\/h2>\n<div class=\"ht-faq-item\">\n<h3 class=\"ht-faq-question\">How do I check which updates are installed on Windows Server?<\/h3>\n<div class=\"ht-faq-answer\">\n<p>Open PowerShell and run <code class=\"\" data-line=\"\">Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20<\/code>. This lists the most recently installed KB updates with dates. You can also check via <strong>Settings \u2192 Windows Update \u2192 Update history<\/strong> if the server has a GUI.<\/p>\n<\/div>\n<\/div>\n<div class=\"ht-faq-item\">\n<h3 class=\"ht-faq-question\">Can I disable Windows Update on a production server?<\/h3>\n<div class=\"ht-faq-answer\">\n<p>You can, but you shouldn&#8217;t leave it disabled long-term. It&#8217;s reasonable to pause updates before a critical deployment or during a busy period, but unpatched servers are a serious security risk. Use deferral settings or WSUS approval controls instead of disabling the service outright.<\/p>\n<\/div>\n<\/div>\n<div class=\"ht-faq-item\">\n<h3 class=\"ht-faq-question\">How often should I patch a Windows Server?<\/h3>\n<div class=\"ht-faq-answer\">\n<p>Microsoft releases updates on the second Tuesday of each month (Patch Tuesday). For most production servers, patching within 2\u20134 weeks of release is a reasonable target for security updates. Critical or zero-day patches should be applied as quickly as your testing cycle allows.<\/p>\n<\/div>\n<\/div>\n<div class=\"ht-faq-item\">\n<h3 class=\"ht-faq-question\">What port does WSUS use, and does it need to be open on the firewall?<\/h3>\n<div class=\"ht-faq-answer\">\n<p>WSUS uses port 8530 for HTTP and 8531 for HTTPS by default. Client servers need outbound access to those ports on the WSUS host. The WSUS server itself needs outbound 443 to Microsoft&#8217;s update servers for synchronisation. No inbound ports need to be opened from the internet.<\/p>\n<\/div>\n<\/div>\n<div class=\"ht-faq-item\">\n<h3 class=\"ht-faq-question\">Do I need to restart after every Windows Server update?<\/h3>\n<div class=\"ht-faq-answer\">\n<p>Not always, but most cumulative and security updates require a reboot to fully apply. If you skip the reboot, the update shows as pending and the patched files aren&#8217;t actually in use yet \u2014 meaning you&#8217;re still vulnerable. Schedule reboots during a maintenance window rather than delaying them indefinitely.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Keeping your Windows Server patched is one of those tasks that seems simple until something goes wrong mid-update. This guide walks through manual updates, PowerShell-based patching, and setting up WSUS for centrally managed environments.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[84],"tags":[412,413,244,67,415,414,410,411],"class_list":["post-185","post","type-post","status-publish","format-standard","hentry","category-windows-server","tag-patch-management","tag-powershell","tag-server-maintenance","tag-windows-server","tag-windows-server-updates","tag-windows-server-2022","tag-windows-updates","tag-wsus"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Manage Windows Server Updates: Manual, Automatic, and WSUS<\/title>\n<meta name=\"description\" content=\"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Manage Windows Server Updates: Manual, Automatic, and WSUS\" \/>\n<meta property=\"og:description\" content=\"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/\" \/>\n<meta property=\"og:site_name\" content=\"Host And Tech knowledge base\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/stshostandtech\" \/>\n<meta property=\"article:published_time\" content=\"2026-05-31T06:24:54+00:00\" \/>\n<meta name=\"author\" content=\"admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@stshostandtech\" \/>\n<meta name=\"twitter:site\" content=\"@stshostandtech\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/\"},\"author\":{\"name\":\"admin\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#\\\/schema\\\/person\\\/b6fa79c48ddaba71af32e395c5b017ee\"},\"headline\":\"How to Manage Windows Server Updates: Manual, Automatic, and WSUS\",\"datePublished\":\"2026-05-31T06:24:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/\"},\"wordCount\":1507,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#organization\"},\"keywords\":[\"patch-management\",\"powershell\",\"server maintenance\",\"Windows Server\",\"Windows Server updates\",\"windows-server-2022\",\"windows-updates\",\"wsus\"],\"articleSection\":[\"Windows Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/\",\"url\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/\",\"name\":\"How to Manage Windows Server Updates: Manual, Automatic, and WSUS\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#website\"},\"datePublished\":\"2026-05-31T06:24:54+00:00\",\"description\":\"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/windows-server\\\/how-to-manage-windows-server-updates\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Manage Windows Server Updates: Manual, Automatic, and WSUS\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#website\",\"url\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/\",\"name\":\"Host And Tech knowledge base\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#organization\",\"name\":\"Host And Tech knowledge base\",\"url\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/logo-dark.png\",\"contentUrl\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/logo-dark.png\",\"width\":1134,\"height\":395,\"caption\":\"Host And Tech knowledge base\"},\"image\":{\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/stshostandtech\",\"https:\\\/\\\/x.com\\\/stshostandtech\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/#\\\/schema\\\/person\\\/b6fa79c48ddaba71af32e395c5b017ee\",\"name\":\"admin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g\",\"caption\":\"admin\"},\"sameAs\":[\"https:\\\/\\\/hostandtech.com\\\/kb\"],\"url\":\"https:\\\/\\\/hostandtech.com\\\/kb\\\/author\\\/admin_fjj7qydm\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS","description":"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/","og_locale":"en_US","og_type":"article","og_title":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS","og_description":"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.","og_url":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/","og_site_name":"Host And Tech knowledge base","article_publisher":"https:\/\/www.facebook.com\/stshostandtech","article_published_time":"2026-05-31T06:24:54+00:00","author":"admin","twitter_card":"summary_large_image","twitter_creator":"@stshostandtech","twitter_site":"@stshostandtech","twitter_misc":{"Written by":"admin","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/#article","isPartOf":{"@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/"},"author":{"name":"admin","@id":"https:\/\/hostandtech.com\/kb\/#\/schema\/person\/b6fa79c48ddaba71af32e395c5b017ee"},"headline":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS","datePublished":"2026-05-31T06:24:54+00:00","mainEntityOfPage":{"@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/"},"wordCount":1507,"commentCount":0,"publisher":{"@id":"https:\/\/hostandtech.com\/kb\/#organization"},"keywords":["patch-management","powershell","server maintenance","Windows Server","Windows Server updates","windows-server-2022","windows-updates","wsus"],"articleSection":["Windows Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/","url":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/","name":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS","isPartOf":{"@id":"https:\/\/hostandtech.com\/kb\/#website"},"datePublished":"2026-05-31T06:24:54+00:00","description":"Learn how to manage Windows updates on your server using Windows Update, PowerShell, and WSUS. Covers scheduling, deferral, and common update failures.","breadcrumb":{"@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/hostandtech.com\/kb\/windows-server\/how-to-manage-windows-server-updates\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hostandtech.com\/kb\/"},{"@type":"ListItem","position":2,"name":"How to Manage Windows Server Updates: Manual, Automatic, and WSUS"}]},{"@type":"WebSite","@id":"https:\/\/hostandtech.com\/kb\/#website","url":"https:\/\/hostandtech.com\/kb\/","name":"Host And Tech knowledge base","description":"","publisher":{"@id":"https:\/\/hostandtech.com\/kb\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hostandtech.com\/kb\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/hostandtech.com\/kb\/#organization","name":"Host And Tech knowledge base","url":"https:\/\/hostandtech.com\/kb\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hostandtech.com\/kb\/#\/schema\/logo\/image\/","url":"https:\/\/hostandtech.com\/kb\/wp-content\/uploads\/2026\/05\/logo-dark.png","contentUrl":"https:\/\/hostandtech.com\/kb\/wp-content\/uploads\/2026\/05\/logo-dark.png","width":1134,"height":395,"caption":"Host And Tech knowledge base"},"image":{"@id":"https:\/\/hostandtech.com\/kb\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/stshostandtech","https:\/\/x.com\/stshostandtech"]},{"@type":"Person","@id":"https:\/\/hostandtech.com\/kb\/#\/schema\/person\/b6fa79c48ddaba71af32e395c5b017ee","name":"admin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/aa1edac8bbadb442e059a5b65ad45a3b2e3ce689202373b96e3e567517ae4b39?s=96&d=mm&r=g","caption":"admin"},"sameAs":["https:\/\/hostandtech.com\/kb"],"url":"https:\/\/hostandtech.com\/kb\/author\/admin_fjj7qydm\/"}]}},"_links":{"self":[{"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/posts\/185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/comments?post=185"}],"version-history":[{"count":0,"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/posts\/185\/revisions"}],"wp:attachment":[{"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/media?parent=185"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/categories?post=185"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hostandtech.com\/kb\/wp-json\/wp\/v2\/tags?post=185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}