The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

    Mastodon

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,969 other subscribers
«
»

Powershell 4.0 hates Lucida Console and switches to raster fonts

Posted by jpluimers on 2016/07/25

PowerShell 4.0 is madly in love with "English (United States)"

PowerShell 4.0 is madly in love with “English (United States)”

A long time ago I started writing up my blog post like this in March 2015 when I bumped into this the first time when upgrading from PowerShell 2 to PowerShell 4:

It seems there is no real workaround:

Good and not so good news: after reading the below linked posts, this is what works:

  • PowerShell 4 and up works fine with any [Wayback] Lucida Console size (including 12) and boldness
    • only when the “Language for non-Unicode programs” is set to “English (United States)”.
  • PowerShell 4 works fine with [Wayback] Consolas on any size and boldness
    • for any “Language for non-Unicode programs”

So if you’re like me and switch between “Dutch (Netherlands)” and “English (Ireland)” a lot (both use the EURO as currency, but have distinct enough other locale settings to cover a lot of European stuff) then you need to get used to the Consolas font.

Source:

Edit 20210930: a possible solution

I need to fire up some old systems having PowerShell v3 or v4 on them to test the below possible solution.

Digging for [Wayback/Archive.is] “806286/powershell-4-console-font-issue” – Google Search and [Wayback/Archive.is] “746647/console-host-does-not-allow-font-adjustment-in-v3” – Google Search, I found [Wayback/Archive.is] [Forum FAQ]Solution for Windows PowerShell console font issue when changing system locale

Solution

To resolve this problem, please follow the steps below:

  1. Access to the path below to find the shortcut of Windows PowerShell: %systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools.
  2. Right click Windows PowerShell and choose Properties.
  3. Switch to Options, check if Current code page list there, if that it is, choose 437 (OEM-United States) and click Apply. Maybe you will encounter an Access Deniedpop-up as the following picture.  Then you need take ownership of current PowerShell File, switch to Security Tab and obtain full control permission for current User Account. Note: if Current code page was not list there, just leave alone Options settings and switch to Font Tab. 
  4. Switch to Font Tab, choose the font you wished to use, click Apply.
  5. After the above settings, current Windows PowerShell console font should works as you wished.

Applies to

  • Windows PowerShell 3.0
  • Windows PowerShell 4.0

–jeroen

This entry was posted on 2016/07/25 at 12:00 and is filed under CommandLine, Development, Font, Lucida Console, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

«
»
 
%d bloggers like this: