- If you don’t like the default font, you can easily change it using the Windows PowerShell properties.
- It’s hard to say what could be causing this font problem.
- It is also possible that the font is not available for download.
- To fix the font itself, you may have to download and install it again.
- You can also install other fonts, but make sure that they work with PowerShell before you install them.
It may seem strange to use a PowerShell command to change the font size. In the upper left corner of the console, click on the PowerShell icon and select Properties if you don’t like the default font. If you don’t like the default font, you can easily change it.
Currently the PowerShell console only supports Raster Fonts, Lucida Console, and Consolas fonts. While Lucida Console is more functional, I believe Consolas to be better.
I’ve had this problem for a while now, but just today I decided to look into it further. You may have changed the font in PowerShell to Lucida Console, but when you open it, the setting is gone!
The Set-ConsoleFont command is used when you are trying to change the font in the console. You need to import the SetConsoleFont module first.
In Internet Explorer, display all running services in the IEServiceList.ps1 file. Written by Jeffery Hicks at http://jdhitsolutions.blogspot.com.
Shortcuts to scripts configure Lucida Console’s font.
You cannot find the $PSISE cmdlet in the main PowerShell console, so we must use it inside PowerShell ISE to change the font size.
When you open a new Windows PowerShell tab, Windows Terminal uses Consolas as its default font. You can change this to any other system font through Windows 11.
Why is the font not changing in PowerShell
If you have PowerShell 5.0 or later, or PowerShellGet on PowerShell 3 or later, you can install AWSPowerShell from the PowerShell Gallery. If you have PowerShell 5.0 or later, you can use the following command to install and update AWSPowerShell.
Console session settings are applied to shortcut links, rather than universally to the user profile. For example, you can set font, layout, and color in a console by clicking the console icon. If you launch a particular console using a shortcut, these settings are saved in the shortcut you used.
When I encountered this problem, the font worked fine in other applications and PowerShell could use it for the active session as long as I quit the app and restarted it before it could use it again.
If the font is not available for download, it is also possible that it is pre-installed. It is not possible to get these fonts from popular font repositories because they are usually pre-installed. Having access to another Windows 10 PC can allow you to export and install the font. That might work.
The problem now arises: WSL Distro consoles use Unicode UTF-8 codepages instead of OEM codepages, while PowerShell uses OEM codepages. As a result, if you mix commands between bash and PowerShell, powershell.exe will reset the codepage forcefully, which will reset the console to raster font if you don’t set the system to use Unicode UTF-8.
In this case, the SetConsoleFont module is useful. You need to import the module before you can use it. First, copy the module to a local editor. Note that the last line of the module had an unwanted line break when I copied it, so make sure it looks as follows:
How to fix a font that doesn’t change in PowerShell
Click on Properties when you open PowerShell.
If you right-click on the title bar and choose Default or Properties, you can change the font and size in the Font tab of that window.
This will cause PowerShell to forget your changes the next time you open it, so you’ll need to select a different font if the changes you make here don’t count. When you do that, PowerShell remembers them. Any font can be affected by this, so use the one that works.
Before installing another font, ensure that it works with PowerShell.
In order to fix the font itself, it may need to be downloaded and installed again. There is no way to tell what is causing the font issue. During my experience, PowerShell was able to use the font in other applications while I had this problem. It could not use it when I quit and restarted the application.
My solution ended up being to create an Install-Font and Uninstall-Font PowerShell function, based on some plagiarized content from the internet.
Close program and open as usual. Changing font sizes in the console reverts to opening powershell in tiny fonts as soon as it is opened.
You may also not be able to download the font. Most pre-installed fonts cannot be downloaded from popular font repositories. You can export the font from another Windows 10 PC and install it on the system you’re having problems with PowerShell if you have access to another Windows 10 PC.
You can also change the font by running PowerShell with administrator privileges. Although PowerShell doesn’t require administrator rights to customize its appearance, you may have issues with the font, so if you have administrator rights in PowerShell, you must change it.
RECOMMENATION: Click here for help with Windows errors.
Frequently Asked Questions
In the console, right-click the PowerShell icon in the upper-left corner and select Properties, then the Font tab.
The default font options for the PowerShell console are limited to Matrix fonts and Lucida prefix. Matrix fonts are the default fonts, although Lucida Console is an improvement. In my opinion, Console is even better, but it is not listed as an option.
- Go to the home page and select the Run Font dialog box.
- Select the font and font size.
- Select Set Default.
- Select one of the following options: This document only. All documents are based on the normal template.
- Select OK twice.
In Windows 8.1, go to the Start screen and type PowerShell. As a result, right-click on Windows PowerShell and select Run as administrator. Once the window opens on your desktop, right-click the blue icon in the upper left corner and select Properties. On the Font tab, increase the size.
Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog, techquack.com, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.