{"id":10032,"date":"2026-11-17T22:57:35","date_gmt":"2026-11-17T22:57:35","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=10032"},"modified":"2026-11-17T22:57:36","modified_gmt":"2026-11-17T22:57:36","slug":"fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm","title":{"rendered":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The problem<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>RDP and the websites didn&#8217;t respond.<\/li>\n\n\n\n<li>The Azure portal showed the VM as Running, but its provisioning state was stuck at Updating, and the guest agent wasn&#8217;t reporting.<\/li>\n\n\n\n<li>Two restarts and a stop\/start (deallocate) didn&#8217;t help.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Step 1: Look at the console, not the network<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When an Azure VM won&#8217;t answer, the first stop is Boot diagnostics. The screenshot showed:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">? Working on updates 98%<br>? Don&#8217;t turn off your PC. This will take a while.<br>? Your PC will restart several times.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Get-AzVMBootDiagnosticsData -ResourceGroupName -Name -Windows -LocalPath C:\\Temp\\bootdiag<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The activity log showed the upgrade had started around 11:30 AM. By evening it had been at 98% for roughly nine hour<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Step 3: Read the upgrade logs from a rescue VM<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can&#8217;t read the logs on a VM that won&#8217;t boot, so we:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Created a managed disk from the snapshot.<\/li>\n\n\n\n<li>Built a temporary rescue VM (Server 2022, no public IP, same subnet).<\/li>\n\n\n\n<li>Attached the disk copy as a data disk.<\/li>\n\n\n\n<li>Used Azure Run Command to bring the disk online, give it a drive letter, and read the logs. We never had to log in to the rescue VM.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">$copy = New-AzDisk -ResourceGroupName -DiskName &#8216;-OS-repaircopy&#8217; `<br>-Disk (New-AzDiskConfig -Location -CreateOption Copy -SourceResourceId $snap.Id -SkuName StandardSSD_LRS)<\/p>\n\n\n\n<h1 class=\"wp-block-heading\"><\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Invoke-AzVMRunCommand -ResourceGroupName -VMName -CommandId RunPowerShellScript -ScriptPath .\\inspect.ps1<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">? Tip: the attached volume may come up without a drive letter. Check Get-Partition and assign one with Set-Partition -NewDriveLetter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What the disk told us<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The registry on the disk already reported Windows Server 2022 Datacenter, build 20348. The upgrade had switched over to the new OS.<\/li>\n\n\n\n<li>C:\\Windows.old existed, holding the previous 2016 install.<\/li>\n\n\n\n<li>C:\\Windows\\Panther\\setupact.log showed every upgrade step as executed (migration, security, OOBE, services) except the last one:<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Operation (executed): Start suspended services<br>Operation (remaining): Cleanup Windows.old at end<br>Executing operation: Cleanup Windows.old at end<br>CSimpleCleanup::DoExecute: Will remove path: C:\\Windows.old\\Windows<br>VERBOSE: Path \\?\\C:\\Windows.old\\Windows has no exceptions, trying a straight delete<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The log ended there, on every boot.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">setuperr.log was full of errors, but they were the usual non-fatal migration noise (plugin load failures, GAC assembly errors and so on), not the cause.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Root cause<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The upgrade had actually finished. Setup was hanging on its final cleanup step: deleting C:\\Windows.old\\Windows. That folder turned out to contain:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">? 1,004,868 files in 111,920 folders: 95 GB<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Setup deletes this one file at a time on a single thread, during first boot, on a Standard SSD. It wasn&#8217;t finishing, and every restart went back into the same step.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Step 4: Delete the folder offline, in parallel<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To test the fix without risk, we made a second disk copy from the snapshot and attached it to a second rescue VM. We also temporarily switched that disk to Premium SSD (detach, change SKU, reattach) for higher IOPS during the delete.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of a normal delete, we used robocopy to mirror an empty folder over the target:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">$empty = &#8216;C:\\emptydir&#8217;<br>New-Item -ItemType Directory -Force $empty | Out-Null<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">robocopy $empty &#8216;G:\\Windows.old\\Windows&#8217; \/MIR \/B \/XJ \/R:0 \/W:0 \/MT:64 \/NFL \/NDL \/NP \/NJH<br>cmd \/c rd \/s \/q &#8216;G:\\Windows.old\\Windows&#8217;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">??????????????????????????????????????????????????????????????????????????????????????????????????<br>? Switch ? Why ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<br>? \/MIR ? Makes the target match the empty source, which deletes everything in it ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<br>? \/B ? Backup mode: gets past TrustedInstaller-owned ACLs without hours of takeown\/icacls ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<br>? \/XJ ? Skips junction points, so it can&#8217;t get caught in a junction loop ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<br>? \/MT:64 ? 64 parallel threads instead of Setup&#8217;s one ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<br>? \/R:0 \/W:0 ? No retries or waits on stubborn files ?<br>??????????????????????????????????????????????????????????????????????????????????????????????????<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We ran chkdsk \/scan against the volume first to rule out filesystem corruption.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Result: the full 95 GB \/ 1 million-file tree was gone in 45 minutes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10032","post","type-post","status-publish","format-standard","hentry","category-research"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn&#039;t respond. The Azure portal showed the VM\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"paris\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Welcome to Pariswells.com |\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com\" \/>\n\t\t<meta property=\"og:description\" content=\"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn&#039;t respond. The Azure portal showed the VM\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-17T22:57:35+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-17T22:57:36+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com\" \/>\n\t\t<meta name=\"twitter:description\" content=\"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn&#039;t respond. The Azure portal showed the VM\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#article\",\"name\":\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \\u201cWorking on updates 98%\\u201d on an Azure VM | Welcome to Pariswells.com\",\"headline\":\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM\",\"author\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/author\\\/paris#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#organization\"},\"datePublished\":\"2026-11-17T22:57:35+00:00\",\"dateModified\":\"2026-11-17T22:57:36+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage\"},\"articleSection\":\"Research\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/category\\\/research#listItem\",\"name\":\"Research\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/category\\\/research#listItem\",\"position\":2,\"name\":\"Research\",\"item\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/category\\\/research\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#listItem\",\"name\":\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#listItem\",\"position\":3,\"name\":\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/category\\\/research#listItem\",\"name\":\"Research\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#organization\",\"name\":\"Welcome to Pariswells.com\",\"url\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/author\\\/paris#author\",\"url\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/author\\\/paris\",\"name\":\"paris\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/93b8ee3f592ac401167f870452bd82d43de80152cd3524e2853403658ada9984?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"paris\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage\",\"url\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm\",\"name\":\"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \\u201cWorking on updates 98%\\u201d on an Azure VM | Welcome to Pariswells.com\",\"description\":\"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\\\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn't respond. The Azure portal showed the VM\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/research\\\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/author\\\/paris#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/author\\\/paris#author\"},\"datePublished\":\"2026-11-17T22:57:35+00:00\",\"dateModified\":\"2026-11-17T22:57:36+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/\",\"name\":\"Welcome to Pariswells.com\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/pariswells.com\\\/blog\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com","description":"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn't respond. The Azure portal showed the VM","canonical_url":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#article","name":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com","headline":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM","author":{"@id":"https:\/\/pariswells.com\/blog\/author\/paris#author"},"publisher":{"@id":"https:\/\/pariswells.com\/blog\/#organization"},"datePublished":"2026-11-17T22:57:35+00:00","dateModified":"2026-11-17T22:57:36+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage"},"isPartOf":{"@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage"},"articleSection":"Research"},{"@type":"BreadcrumbList","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/#listItem","position":1,"name":"Home","item":"https:\/\/pariswells.com\/blog\/","nextItem":{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/category\/research#listItem","name":"Research"}},{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/category\/research#listItem","position":2,"name":"Research","item":"https:\/\/pariswells.com\/blog\/category\/research","nextItem":{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#listItem","name":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM"},"previousItem":{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#listItem","position":3,"name":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM","previousItem":{"@type":"ListItem","@id":"https:\/\/pariswells.com\/blog\/category\/research#listItem","name":"Research"}}]},{"@type":"Organization","@id":"https:\/\/pariswells.com\/blog\/#organization","name":"Welcome to Pariswells.com","url":"https:\/\/pariswells.com\/blog\/"},{"@type":"Person","@id":"https:\/\/pariswells.com\/blog\/author\/paris#author","url":"https:\/\/pariswells.com\/blog\/author\/paris","name":"paris","image":{"@type":"ImageObject","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/93b8ee3f592ac401167f870452bd82d43de80152cd3524e2853403658ada9984?s=96&d=mm&r=g","width":96,"height":96,"caption":"paris"}},{"@type":"WebPage","@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#webpage","url":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm","name":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com","description":"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn't respond. The Azure portal showed the VM","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/pariswells.com\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm#breadcrumblist"},"author":{"@id":"https:\/\/pariswells.com\/blog\/author\/paris#author"},"creator":{"@id":"https:\/\/pariswells.com\/blog\/author\/paris#author"},"datePublished":"2026-11-17T22:57:35+00:00","dateModified":"2026-11-17T22:57:36+00:00"},{"@type":"WebSite","@id":"https:\/\/pariswells.com\/blog\/#website","url":"https:\/\/pariswells.com\/blog\/","name":"Welcome to Pariswells.com","inLanguage":"en-US","publisher":{"@id":"https:\/\/pariswells.com\/blog\/#organization"}}]},"og:locale":"en_US","og:site_name":"Welcome to Pariswells.com |","og:type":"article","og:title":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com","og:description":"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn't respond. The Azure portal showed the VM","og:url":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm","article:published_time":"2026-11-17T22:57:35+00:00","article:modified_time":"2026-11-17T22:57:36+00:00","twitter:card":"summary","twitter:title":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM | Welcome to Pariswells.com","twitter:description":"The problem We did an in-place upgrade of an Azure VM from Windows Server 2016 Datacenter to Windows Server 2022. The VM ran IIS (an HTTP\/HTTPS site plus a line-of-business app on a custom port). After the upgrade the server never came back: RDP and the websites didn't respond. The Azure portal showed the VM"},"aioseo_meta_data":{"post_id":"10032","title":null,"description":null,"keywords":null,"keyphrases":{"focus":{"keyphrase":"","score":0,"analysis":{"keyphraseInTitle":{"score":0,"maxScore":9,"error":1}}},"additional":[]},"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","location":null,"local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-11-17 22:54:39","updated":"2026-11-17 22:57:36","primary_term":null,"seo_analyzer_scan_date":null,"focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/pariswells.com\/blog\/\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/pariswells.com\/blog\/category\/research\" title=\"Research\">Research<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">\u00bb<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tFixing a Windows Server 2016 ? 2022 in-place upgrade stuck at \u201cWorking on updates 98%\u201d on an Azure VM\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/pariswells.com\/blog\/"},{"label":"Research","link":"https:\/\/pariswells.com\/blog\/category\/research"},{"label":"Fixing a Windows Server 2016 ? 2022 in-place upgrade stuck at &#8220;Working on updates 98%&#8221; on an Azure VM","link":"https:\/\/pariswells.com\/blog\/research\/fixing-a-windows-server-2016-%e2%86%92-2022-in-place-upgrade-stuck-at-working-on-updates-98-on-an-azure-vm"}],"_links":{"self":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/10032","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/comments?post=10032"}],"version-history":[{"count":1,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/10032\/revisions"}],"predecessor-version":[{"id":10033,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/posts\/10032\/revisions\/10033"}],"wp:attachment":[{"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/media?parent=10032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/categories?post=10032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pariswells.com\/blog\/wp-json\/wp\/v2\/tags?post=10032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}