<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Powershell on Tobias Theel | Senior Software Engineer</title><link>https://blog.noobygames.de/tags/powershell/</link><description>Recent content in Powershell on Tobias Theel | Senior Software Engineer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.noobygames.de/tags/powershell/index.xml" rel="self" type="application/rss+xml"/><item><title>Windows 11 Still Defaults to PowerShell 5.1 — And Why That's a Problem</title><link>https://blog.noobygames.de/blog/upgrade-powershell-7/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://blog.noobygames.de/blog/upgrade-powershell-7/</guid><description>&lt;p&gt;Windows 11 is a modern operating system. Its terminal, however, defaults to a shell from 2016.&lt;/p&gt;
&lt;p&gt;When you open PowerShell on a fresh Windows 11 install, you get &lt;strong&gt;Windows PowerShell 5.1&lt;/strong&gt; — a version built on the old .NET Framework 4.x, permanently frozen in time, and officially in &lt;a href="https://learn.microsoft.com/en-us/powershell/scripting/powershell-support-lifecycle"&gt;maintenance mode&lt;/a&gt; since 2018. Microsoft has not added features to it since then and will not.&lt;/p&gt;
&lt;p&gt;I ran into this the hard way when setting up &lt;a href="https://ohmyposh.dev"&gt;Oh My Posh&lt;/a&gt; on a fresh machine — a prompt customization framework that promises beautiful, informative terminal prompts. On PowerShell 5.1, it either threw errors or rendered garbled symbols:&lt;/p&gt;</description></item></channel></rss>