I've done the same with Windows, but I had a unique bug with Storage Spaces and did some debugging to identify driver issues to include with the report. I guess the reason it was fixed was because there was similar feedback without the debugging on the Windows Feedback app and because the blast radius was small. It was just one .sys file, but even then Storage Spaces is relatively contained.

Compare that to any GUI-related issue. Almost every surface has some kind of unsupported/unexpected hooking or reliance on unchanging elements because some company has built a tool that integrates. They've then sold this to Fortune 500s who explode if Windows blows up their tool. This makes the startup cost for fixing many things very expensive.

If you report issues related to higher profile/usage functionality then you are less likely to get traction because:

* They know about the issue already, but it's a really hard to fix for some reason which may not be obvious to you. All stakeholders are not equal in the decision process hence compatibility concerns win in some situations.

* Even if they decide to fix it, a huge amount of effort has to go into scheduling the fix in a release. Some authority may agree to go fix it and everyone is excited. That's just the start of a painful process to implement and test the fix.