Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

This is a trivial problem, but it annoys me that I can't get to the bottom of it:

I'm running Windows 8, Powershell version 3.0. By right-clicking on the title bar I can go into the Properties and change the font, size, background colour etc without any problems.

After closing and restarting Powershell, all of the changes I've made stick except that if I've set the font to Lucida Console then on reopening I get the Raster font.

(Note that all of the above applies to when I run Powershell as Administrator.)


  • If I set the font to Lucida, then it switches to Lucida for the remainder of the session.
  • If I set the font to anything other than Lucida, then it stays as that after closing and reopening.
  • If I alter the window sizes or text colours or anything else, the changes persist after reopening.
  • The only thing that goes wrong is that if I set the font to Lucida, it switches to 'Raster fonts' when I reopen.
  • But cmd and powershell ISE don't have this problem - only the powershell console.

Can anyone suggest what might be going wrong?

(One observation I've made is that upon re-opening Powershell after setting the font to Lucida, at first the width of the window is what it would be if the font were Lucida, but then after a second, it widens slightly to accommodate the raster font.)

share|improve this question
Maybe the Lucida font file is corrupt? –  aphoria Jan 19 '13 at 12:55
For me on Windows 7 it only happens with font size 12 -- size 14 or 10 work like expected (I didn't try them all). –  user208900 Mar 20 '13 at 11:46
This has been logged with Microsoft Connect - connect.microsoft.com/PowerShell/feedback/details/806286/… –  Ben Foster Dec 23 '13 at 11:03

5 Answers 5

This guy had the problem as well. His solution worked for me too:

However, my shell in Windows 7 refused to save the setting and insisted on changing back to Raster Fonts when I re-opened PowerShell. It worked fine with Consolas, but I wanted Lucida

The Workaround: Select a font size other than 12 points.

share|improve this answer
Yep, seems to be only 12pts that has the issue for me. Setting 11pts or 13pts is persisted across sessions. –  Tom Sep 20 '13 at 2:21
Since I upgraded from Windows 8 to Windows 8.1, I can't keep the font to Lucida. I tried several different font sizes. At least Consolas works. –  bouvierr Oct 23 '13 at 2:22
I experienced the same on Windows 8.1. If I tried to use Lucida my changes were persisted. Consolas however worked fine. This only seemed to affect Powershell as I did not have the same issue with the normal command prompt. –  Ben Foster Dec 23 '13 at 10:40

I've found this behavior before, even with Windows 7. Try this - open a PowerShell window in admin mode (right click the icon open as administrator), change the font and close the window. Now open a PowerShell window with normal user rights and your changes should stick.

share|improve this answer
I'm on Windows 8.1 and this doesn't work for me. –  bouvierr Feb 22 '14 at 19:21
@bouvierr just tested on Windows 8.1, works for me, other solution didn't –  Sammaye Apr 5 '14 at 13:33
this also works for me on win8.1 but only for basic powershell link. If I run github shell I now get a powershell with huge raster font instead of console or lucida font (before I got github shell with default small raster font). –  arberg Feb 12 at 13:04

I too had this problem and I just fixed it by changing the system locale of my Windows installation English (United States). Swedish was apparently no supported with Lucide Console in PowerShell prompt. No idea why, but I blogged briefly about it here: http://www.meadow.se/wordpress/setting-the-font-of-a-powershell-console-to-lucida-console-wont-work/

Hope this helps.

share|improve this answer
This did the trick for me too. I have an english uk windows with my locale set to dutch. When I changed the locale to en-us it was fixed. –  albertjan Apr 28 at 11:39

1) Check which code page you are using
I found the used current code page is not UTF-8 (65001). You can find the current code page in properties -> Options. OR, you can found it by using 'chcp' command

2) Change the code page to UTF-8
using command 'chcp 65001'

3) Change other font
you can use other font by change the powershell propertes

share|improve this answer

Very odd, I can't replicate, even on Win8/PS3. This guy seems to be experiencing the same issue as you, so there must be something to it.

When you change the font, it writes the changes back to the .lnk file used to launch PowerShell when you click OK. To see what file that is, right-click the icon you are launching with and look at the General tab, Location: field. Does its last mod time correspond to when you change the font? Does the change show in the properties of the shortcut? How about if you make the change and then set the .lnk to read-only?

share|improve this answer
Also, according to the Workarounds tab here, depending on your language, Lucida 12pt may not be available. –  charleswj81 Jan 25 '13 at 7:51
Whats strange is that I have the issue in PS, but not in cmd.exe –  Svend Jul 22 '13 at 13:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.