I don't know why, it seems that explorer.exe gets some different bitmap, or it gets it from somewhere else etc. Also, while this worked fine at 96 and 120 (100% and 125%) DPI, the Windows 10 orb is still shown at 144 (150%) DPI.This scenario is not that uncommon - laptop computers are sometimes docked at a desk and undocked and taken on the go. If the user changes the DPI of the monitor, the Windows 10 orb will show. Only running it at startup means that it modifies the bitmap only for the DPI that was used at startup.There are 2 things that I think need to be taken care of: I tried the code that you provided, and while it generally worked, we still have to iron some things out. Thanks for the contribution and for letting me know about it. That's great, a lot of people also asked about this recently, so the timing is great. UPD: a pre-built binary for those interested, execute it at your own risk: StartButtonReplacement.zipīeta Was this translation helpful? Give feedback. It needs Explorer to be restarted after executing or to be executed before Explorer is started, so i think it would fit ExplorerPatcher since it injects into Explorer process and I think it can execute some code before taskbar is loaded. I've also found a program which replaces Start Button via hooking uxstyles API, but I think it's out of scope of the project.
The program works like StartAllBack "Colorize everything with accent color" option - it gets theme bitmap handle and modifies the bitmap, so it does not need to patch the msstyles file. it has accent color on hover, changes its color to dark when changing taskbar theme to light).
I think that the current Start Button, which remains unchanged since Windows 10, looks out of place, so I've developed a very little application which replaces it - it is based on the fact that Start Button icon is stored in TaskbarPearl section of Win32 styles and behave exactly like Windows 10 Start Button behaved (e.g.