<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrade on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</title><link>https://pwsh.in/tags/upgrade/</link><description>Recent content in Upgrade on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 15:37:51 +0530</lastBuildDate><atom:link href="https://pwsh.in/tags/upgrade/index.xml" rel="self" type="application/rss+xml"/><item><title>SetupDiag: A Wintel Admin's Guide to Diagnosing In-Place Upgrade Failures</title><link>https://pwsh.in/posts/setupdiag-migration-guide/</link><pubDate>Tue, 21 Jul 2026 15:37:51 +0530</pubDate><guid>https://pwsh.in/posts/setupdiag-migration-guide/</guid><description>&lt;h2 id="why-this-tool-exists">Why this tool exists&lt;/h2>
&lt;p>Think of an in-place OS upgrade like renovating a house while people are still living in it. Windows Setup has to migrate settings, drivers, and applications from the old structure into the new one without tearing anything down first. When the renovation stalls, Setup usually just tells you &amp;ldquo;it failed&amp;rdquo; with a cryptic code like &lt;code>0xC1900101-0x20017&lt;/code> — it doesn&amp;rsquo;t tell you &lt;em>which wall&lt;/em> it got stuck on.&lt;/p></description></item></channel></rss>