font on visual studio "find symbol results" window

This is how I fix it in VS2008, I assume the same would apply to 2010.

1. Open Tools -> Options -> Expand Environment -> Fonts and Colors
2. Click "Use Defaults"
3. Click OK

This restores it every time for me, no idea why it suddenly changes either.

None of the answers thus far worked for me. Mr Anderson's looked good except I just wanted the default font, not a custom one and he noted the settings file was nearly empty to begin with so I felt the fix should involve removing settings somewhere, not adding more. What worked was choosing Tools > Options... > Environment > Fonts and Colors. Then in the "Show Settings For:" drop down, I picked "Environment Font". It was set to Automatic. I changed it to a random one (Academy Engraved LTE) and hit the OK button to apply it. This changed fonts all over VS including in the Find Symbols Results window. I changed it back to Automatic and the font and icons went back to normal.

For complete accuracy's sake, at the point that I did this, I had already restored VS to my most recently backed up settings, and then to the default settings before trying this. I'm guessing it would work without those steps but since it changes to the funky font on its own, I don't know how to test it.

I found that the following seems to work:

1. Go to Tools -> Options -> Environment > Fonts and Colours
2. Choose Show settings for: [All Text Tool Windows]
3. For Display items: Plain Text, click the Bold checkbox and click OK
4. Do the same again, but untick the Bold checkbox to revert it.
5. If it doesn't change immediately, try restarting Visual Studio

Mind you, Find Symbol Results isn't really a text window, so maybe setting and resetting any font will work. I don't know.

I found someone on MSDN who had a similar issue.

I couldn't believe this would fix it, but I went to Personalization, and changed the theme to Windows 7 Basic, and back to my own Aero theme, and the Find Symbol Results went back to a nice font.

I don't know how this could fix the issue, but it worked for me...