[Settings] Text and button colors not rendering correctly

[Kontr3X]

Microsoft PowerToys version

0.49.1-x64

Running as admin

No

Area(s) with issue?

FancyZones

Steps to reproduce

I use an ultrawide-monitor (32:9) with 3840x1080 res.

✔️ Expected Behavior

Text and Images

❌ Actual Behavior

Blank fields.

Only when you click on it, the configuration page appears.

Other Software

No response

[franky920920]

Do this only occurred in the OOBE or the setting page as well?

[Kontr3X]

As far you can see the screenshots above, only on the OOBE page. I have to press the invincible button, that the setting-page appear.

With invincible button i mean the "Einstellungen öffnen" (open settings-button).

When I close the window of PowerToys and reopen it, then it seems the button for "Einstellungen öffnen" are at least visible:

The language is in german.

[franky920920]

cc: @niels9001

[niels9001]

Seems a similar issue: #14743

[Aaron-Junker]

Some icons in PT Run settings don't show up for me. Is this related to this?

[niels9001]

Some icons in PT Run settings don't show up for me. Is this related to this?

Nah, I think that has to do with images stored in a different folder. I think there's a tracking issue for it somewhere :)

[niels9001]

Relevant WinUI issue: microsoft/microsoft-ui-xaml#6344

[franky920920]

@niels9001 so #Tracking-External?

[jaimecbernardo]

Some icons in PT Run settings don't show up for me. Is this related to this?

Actually, I think these are the ones which just recently changed their folder in install (though it's not happening for me).
@Aaron-Junker , could you send a bug report just to check your "installationFolderStructure.txt"? Or just send that file.

[Aaron-Junker]

@jaimecbernardo This is from 0.51.0
installationFolderStructure.txt

[jaimecbernardo]

@jaimecbernardo This is from 0.51.0 installationFolderStructure.txt

@Aaron-Junker
It matches what's expected perfectly. So the issue is not from this.
Thank you.

What you reported might be related to #14828

[crutkas]

Going to close this against #14743 so we have a core tracking issue