Your Symbol Device Library should not show footprints for generic symbols. Note this edit originally omitted because I assumed the topic was regarding the R the OP posted.
Often, any number of different footprints can be assigned to a symbol.
Maybe you had assigned a footprint to a symbol in a project. If that is the case, then every time you copy that symbol in a project, that symbol will have the same footprint.
That is not true. The footprint preview in the symbol selection works normally.
However, not all schematic symbols have a footprint attached by default. There can be many different footprints for a humble resistor. Both SMT and THT, and from very tiny to big power resistors. For the generic symbols, KiCad does not have any default footprint, and this forces you to always assign a footprint to it.
For reference, this is the same thing on my linux box. You can see all the default footprints there. It worked before on windows, but suddenly stopped.
Oops, that is a detail I missed. But somehow I doubt it is windows related. I think the list is generated depending on the “keywords” section of the symbol. You can load it in the symbol editor and then: "Symbol Editor / File / Symbol Properties**
I installed Kicad 6 to try and reproduce it. And now I can’t reproduce it in 7.0 again. I’ve no idea what happened. Reinstalling 7 didn’t work, but apparently installing 6 made 7 work.
This thread title is wrong. Default footprints are one to one for symbols and don’t get used with the generic symbols in “Device”
The OP is referring to filtered footprints
The issue returned today. It seems to happen intermittently. Sometimes it fixes itself when I restart, but other times not. Is there a way to get debug info from kicad?
Find and post your exact version by opening Kicad, then Help > About Kicad > top RH corner click “Copy Version Info” then Right click > Paste directly into a post you open in this forum.
ok, with v7.0.9 the issue linked by @RaptorUK is resolved, so this is something else. Sadly I can’t reproduce it (windows10), so we have to wait for other confirmations or you have to open a gitlab issue yourself.