Startisback++ Broke my Start Button

Why didn't you use Stardocks "Start 10 " for the startbutton & Start menu as that is made for use WITH Windowblinds and made by the same company as Windowblinds ?   

Next time try products where you bought WB from,Start10 is fully compatible with it. 

I would suggest at this point that you save your data and do a system reset. This reinstalls Windows 10 and is fast and easy.

Then, use Start10 in the future.

Also, go to your stardock account and deregister any Stardock programs before doing the reset, so you won't have problems activating after the reset.

For the same reason you don't install exclusively Microsoft programs in windows, genius. There's actually no point to this further sentence, I just felt like wasting some of your time, as well. thanks for the memories, jackarse. 

Quoting twistedbard327, reply 4

For the same reason you don't install exclusively Microsoft programs in windows, genius. There's actually no point to this further sentence, I just felt like wasting some of your time, as well. thanks for the memories, jackarse. 

Wow, someone is very rude. 

That's okay. I forgive him. He prob'ly thought he was helping. 

He was helping. Start 10 is made to work with WindowBlinds, Startisback and some of the other start menus don't work well with WindowBlinds.

Oh if your wondering you can use Startisback start buttons with Start 10.

Have you tried installing Start 10? It may override old setting made by Startisback.

(And namecalling is SO 9th grade. Grow up, Dude.)

I've just now downloaded the skin and installed it on Win10.  Based on your image and my playing with it, it seems like your Win10 taskbar settings are set to "Use small tasbar buttons", at least that's how I can reproduce the look in your "in practice" image.  If it's "on", try turning that option "off".

Also, the original screenshot would have been made in Win7, on Win10 even with large taskbar icons the top and the bottom of the button are slightly cut off, that's not really unusual.

See if that takes care of it.

I appreciate an actual thought, thank you. I did try start10, to no avail. I suppose at this point I should see if I can't identify exactly what startisback actually changed. Maybe I'll get into the skin studio and see if any clues to how the start button/taskbar skins interact. honestly, annoyance aside, it's an intriguing issue. I'm grown up, man. And as a grown-up, I reserve the right to be a dick. I exercise that right sparingly. This guy took the time to ask me why i didn't just use start10 in the first place, as if it was some kind of a bad decision. I had no reason to expect this problem. All he was doing was telling me what he thinks I should have done, in a snarky question. Why didn't I? 'Cause I didn't have to.

[Just in case you didn't see my post #9. looks like you may have "leap-frogged" around it, timing on these posts can be tricky.]

Quoting RedneckDude, reply 12

Quoting twistedbard327,

reply 6

That's okay. I forgive him. He prob'ly thought he was helping. 

I think Lightstar meant you, twistedbard327.    

Oh, I was still just being a smartass. 

On Stardock's sites there IS NO "right to be a dick", reserved or otherwise.

Using Start10 and the suggestion to 'Use Start10' is the correct solution to your 'problem'.

Third party Shell modifications WILL have varying success, and as such won't be directly supported.

Stardock's software is designed to be directly compatible with the OS for which it/they are intended, and obviously to be compatible with each other.

Does nobody get that my problem isn't what I did? It's what happened as a result. I'm just trying to deal with a software issue, not get life advice. I'm not here whining, "why is this happening to me?" I gave a pretty clear picture of a technical issue, literally, in fact, and my alleged "solution" is to not have had the problem in the first place? But hey, at least Stardock was able to clear up that I should always use Stardock products with my Stardock products. Should I also give you 5 dollars to re-enable the other half of my windowblind skin you took away? Man, I'm just drowning in good ideas today.

Your use of a third party shell modification 'took away' the WB functionality. Stardock didn't.

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.

What's causing it?  Perhaps a poorly written bit of coding in "Startisback++"....;)

The reality is that all GUI modifiers are specifically designed to modify the standard/default Windows GUI [shell], not something already altered [or even hacked] by a third party.

No, hiding away the start menu skin as if it wasn't designed and packaged all as one "Windowblinds" skin. I've expected all along that I'd end up with start10, but as it stands, I, in no way, can afford 5 dollars right now. (judge me, I couldn't care less) I'm a huge fan of stardocks suite of customization tools. But all of that aside, It's starting to amuse me that I haven't managed to convey this clearly yet. I don't need an abstract, "whadya gonna do?", explanation, I'm not going to be convinced that I made some kind of mistake looking into my options. I'm not angry at the world or microsoft or stardock or anybody else about what happened. I only ever wanted to find out if i could glean some insight into why and/or how, in this very specific instance, I am experiencing the originally stated set of circumstances, as it pertains to the functionality of the GUI, so that I might manage to devise a real solution. 

You chose incompatible software.

If two programs are likely to affect the same GUI components they almost always WILL conflict with 'interesting' results.

The ONLY fix is for the developer of one...or other....or both programs to resolve the conflict.

Chances are that will never happen as:-

1. - Stardock already has a compatible alternative to this other proggy.

2. The other proggy is probably unaware/oblivious of Windowblinds and/or doesn't care either way...;)

Bottom line is...

"Real solution" use Start10. [you know....what was actually suggested in reply #1]...;)

::sigh::

You are barking the wrong tree. Go to Startisback++ for supports,it borked somethings which Windowblinds cannot handle rightly.