Jul 25 2022 07:10 AM - edited Jul 25 2022 07:23 AM
Is it just me or does the Recommended Section of the Start Menu still show blank icons for files? This issue has been there for quite a while now.
Rebuilding the icon cache did not help. SFC /scannow did not show any corruptions. It's a clean install of Windows 11 21H2.
Jul 25 2022 08:02 AM
Jul 25 2022 12:30 PM - edited Jul 25 2022 12:31 PM
Jul 26 2022 09:06 AM
Jul 31 2022 05:01 PM
This has been happening since day one of Windows 11 for me. No way around it. It's random and even a "repair reinstall/upgrade/in place upgrade" doesn't fix it. Along with rebuilding the icon cache. Definitely a bug. I'm surprised this is one of the few very first mentions of it actually. I honestly don't use the "recommended" area so I would just assume disable that portion. I go back and forth with some end users of mine I administer by installing StartIsBack to hide all the crappy bugs with the startmenu since Win11 arrived and my customers insist on having Win11. Some machines such as mine that I do lots of testing etc with I don't install much and tonight I just decided to look around to see who else has this same very issue and laugh that I actually found a hit while investigating this bug more. 🙂 Anyways, so yeah anyone else who comes across this thread. Don't waste your time with all the recommended fixes. Just a waste of time. I've been down the same road as you even more so probably with how many users I admin.
Aug 05 2022 05:39 AM
Thanks for the confirmation. I sent a feedback to MS and they said the following
Thank you for your feedback! We included a fix for this issue with Build 22504, now available in the Dev Channel: https://aka.ms/wip22504 But please let us know if you continue to experience any issues.
UPDATE: This is also now available in the Beta Channel with Build 22581: https://aka.ms/wip22581
However, build 22504 was released in november 2021. Is it possible that all this time this specific fix is still in the Insider builds and not yet released to the stable releases
Dec 04 2022 10:12 AM
Dec 04 2022 10:42 AM
I still have this issue on 22H2. I previously got an answer in the Feedback Hub that it got fixed but apparently it's not. No idea how hard it is to fix this.
Jan 28 2023 04:37 AM
Feb 14 2023 03:50 PM
Feb 22 2023 12:57 PM - edited Feb 22 2023 12:58 PM
Thanks for the help guys. It's shocking we must fix this by workarounds while a simple fix by MS should've solved this a long time ago.