#Startallback trial reset skin#

No, hiding away the start menu skin as if it wasn't designed and packaged all as one 'Windowblinds' skin. The reality is that all GUI modifiers are specifically designed to modify the standard/default Windows GUI, not something already altered by a third party. What's causing it? Perhaps a poorly written bit of coding in 'Startisback++'. If you want an explanation of why you have an issue - it's your poor choice of incompatible software when an actual compatible alternative exists. Your use of a third party shell modification 'took away' the WB functionality. Should I also give you 5 dollars to re-enable the other half of my windowblind skin you took away? Is there anyone willing to assist me in understanding the nature of this issue and working out an actual solution, rather than just telling me to 'restart at checkpoint'? I'm willing to learn. Please, help.ĮDIT: It seems I should have been clearer. I know it's not the most severe problem, but it's driving me nuts. So far I uninstalled Startisback, reinstalled WindowBlinds, loaded a restore point, Uninstalled windowblinds, restarted, reinstalled windowblinds, ran system file checker and finally am posting here.

Immediately, I saw that the skinned start button from my WindowBlinds theme (Loyalty is Sensuality) was being cut off at the top and bottom of the taskbar, where it previously extended above it. As this was not an option I uninstall Startisback. The sole reason didn't work for me was that it insisted I either use the default windows start button, one of their default alternatives, or specify a custom one, when all I wanted was for it to do nothing at all with the button so WindowBlinds can do it's thing. With a few options in mind, I began by installing the Startisback++ Trial for Windows 10.

This morning I started looking into using an alternative start menu.

Startallback trial reset