Default font too 'blocky' compared to Win7

So I recently got a new computer I built myself. Having to for a couple reasons finally make the jump to Win10....there's just so many issues I have but a bit one is that the system font just doesn't want to work right.
It's mainly numbers -- text seems to be fine but the numbers are very blocky and very much don't even fit right with the rest. This affects some programs more than others, but notably Windows Explorer and the tab bar on my browser, as well as the RSS feed(Waterfox) which I've attached small pics of. Especially in the last one it's very clear how out of place the numbers are.

My font is Segoe UI. I *like* that font and want to keep it. For sure I was using it on Win7. As far as I can tell I have fonts at default -- I've changed and reverted this a number of times already. What's especially puzzling is trying to see if maybe I had it at 'Semibold' previously, I tried changing it to that, but somehow this makes everything in Italics....which makes zero sense. I even tried overwriting my old font files from my old install and that did nothing. I can't see how the font files would be borked -- this is a clean Win10 install (on version 2004), not even an upgrade.
I also have tried with ClearType both on and off and this doesn't change things.

Now the main difference from my old setup is that I have a DVI ---> HDMI converter, since my graphics card has no DVI input. I was in fact using a TV temporarily while waiting for this and the font issues weren't there (though there were other ones). I suppose it may just be that my monitor is old, but it seems odd that it was working fine in Win7.

If anyone has any ideas I'd be extremely grateful.

I don't want to flame but did you actually real the post? I said I tried changing the font multiple times, and that I want the default one....just back to how it looked in Win7.

TerraEpon said:

If anyone has any ideas I'd be extremely grateful.

@Try3 gave you an idea.

You don't sound too grateful, dude.

Note that not everything that works in Windows 7 works in Windows 10, or works at all.

Check for updated drivers for the graphics card.

OldNavyGuy said:

@Try3 gave you an idea.

You don't sound too grateful, dude.

Well considering I already said I tried that...

And then the next person replies with basically the same thing. Are users here bots or something?

Well the biggest thing is I'm not trying to change the font away from Segoe UI. But I did try changing it both manually and with the program called 'Winaero Tweaker' which as far as I can tell does the exact same registry change just automatically.

The strangest thing, which I forgot to mention in my post, is that the preview fonts for Segoe UI look fine in the previews. I've attached a pic of this....doesn't have that 'blocky' look at all. This is why I think there's sometimes wonky going on *on top of, again, the fact that if I change it to 'Segoe UI Semibold' it changes to italic (as well as if I change it to a couple others that I forget) -- making me think the font files themselves are somehow bad but I'm at a loss on how to fix them.

TerraEpon said:

Well considering I already said I tried that...

And then the next person replies with basically the same thing. Are users here bots or something?

You're pretty mouthy...especially for a newbie.

If no one else tries to help you, don't be surprised.

OldNavyGuy said:

You're pretty mouthy...especially for a newbie.

If no one else tries to help you, don't be surprised.

Well, being templated -- twice, at that -- for something I already said I did is pretty dehumanizing.
And this whole thing is /extremely/ fruterating already. I just spend a lot of money on a new rig and all of a sudden I have a much worse experience, and any attempts at trying to find a solution don't get me /anywhere/ because any reference to fxing the font bring up either Cleartype or changing the font altogether.

At least it'd be nice to know if people can at least see the problem I'm having? Pic #5 in the first post makes it especially vivid.

(Oh and yes, you did give a valid idea -- checking graphics drivers. They are updated so far as I know)