quick launch and pinned icons are now blank since update

[auggie2023]

Before reporting your issue

• I have confirmed that this issue does not happen when ExplorerPatcher is not installed
• I do not have "register as shell extension" enabled
• I have tried my best to check existing issues

Repro ExplorerPatcher versions

version 26100.4946.69.6
running on Windows 11 build 26200.8246

Repro Windows Versions

Windows 11 pro 25h2 build 26200.8246

3rd party tweak software installed

none

Describe the bug

just started happening after automatic update to current version. I can get the icon to show up by clicking on the blank quick launch button icons but as soon as reboot/restart/log off it goes back to blank icon. the icon pinned to taskbar remains blank regardless. Tried to change icon's to another icon in properties but still goes back to blank after reboot/restart/logoff etc.
Windows update did update multiple items at same time: 026-04 Security Update (KB5083769) (26200.8246) and

Windows Malicious Software Removal Tool x64 - v5.140 (KB890830)

No new software added or changed prior to bug showing up.

Expected outcome

tried to fix by changing icons

Actual outcome

after clicking on icon actual icon image shows but only while system running. goes back to blank after reboot/restart/shutdown/ and log off.

Additional info

No response

Crash Dumps

No response

Media

No response

[auggie2023]

[carterscottm]

Can confirm, just updated W11 to 26200.8246 and am seeing blank quick launch icons as well.

[pyrates999]

Did you try openning up task manager and kill explorer.exe and then run task manager again and run explorer.exe?

[auggie2023]

yes. Did not resolve the issue.

[Git4Mon]

Can Confirm also.

[Alkerion]

Just create a new toolbar, problem solved this way on my side.

[Aadpaling]

Can confirm. Creating a new toolbar is not a real solution, because it affects the built in "quick launch" bar.

[Alkerion]

Can confirm. Creating a new toolbar is not a real solution, because it affects the built in "quick launch" bar.

Not sure to understand where the problem is as in my case this workaround works perfectly for me.

Why do you still use the deprecated QL bar ?

[Aadpaling]

Can confirm. Creating a new toolbar is not a real solution, because it affects the built in "quick launch" bar.

Not sure to understand where the problem is as in my case this workaround works perfectly for me.

Why do you still use the deprecated QL bar ?

Well, why do we use ExplorerPatcher at all right, to get things the way they were. #nochanges
Would appreciate a fix to the issue :)

[Alkerion]

Can confirm. Creating a new toolbar is not a real solution, because it affects the built in "quick launch" bar.

Not sure to understand where the problem is as in my case this workaround works perfectly for me.
Why do you still use the deprecated QL bar ?

Well, why do we use ExplorerPatcher at all right, to get things the way they were. #nochanges Would appreciate a fix to the issue :)

Post a picture of your issue as my trick works 100% for me and a friend of mine.

[WORF84]

For me the option to create a new toolbar disappeared after the update.
Uninstalling and reinstalling doesn't help.

[lorensfrank-del]

Same here

[nskmda]

Me too

first thought it was the latest Win11 update but... probably it's a combination of both. ☹️

if it helps... the icons of the shortcuts in the folder (quick launch) also disappeared.
and some of the icons reappear after I launch the app by clicking on it...

[carterscottm]

if it helps... the icons of the shortcuts in the folder (quick launch) also disappeared. and some of the icons reappear after I launch the app by clicking on it...

I noticed this as well. I made a copy of my quick launch folder and noticed that when browsing it, the icons showes up normally. I then deleted the original quick launch folder and renamed the copy to match the original name. After restarting ExplorerPatcher, the icos show up normally in the QL toolbar again.

[Alkerion]

I've just created a new toolbad and moved my shortcuts inside, it fixed the issue.