It actually disappears again when No Taskbar button is showing ( If no window or app is open)

I would say, Basically, if you get "Insidian" or one of my latest skins to function then any skins startbutton will work.

Bump...ish

Updated to latest start11 beta/wb11 rc1. Start button still being cut off on many skins under windows 11.

why dont they ever update the things people actually complain about? rather they update things no one even notices were updated lol

Everything in this update was asked for by the users. Simplex specifically has been very helpful in pointing out issues that need addressed. They ask/report them in a proper manner and does not complain or criticize.

SimplexDesigns is an exemplary member. Both JanOscar and I test his skins and enjoy interacting with him as well. I'm really glad you've noticed him as well as I've seen in Sean's comments, too.

I think TPScroggins has explained things eloquently ...;)

ahh ok, my bad i was reading previous comments that neone6 wrote, and his issues were with start11 not windowblinds. so my apologies. but i jusst updated to windowblinds 11.02 cant really say i noticed anything different other than i think a classic skin was added.

Windowblinds is never "updated" just to add a skin.  Point releases have changes which deal with issues properly raised and subsequently addressed...;)

great, ill see how everything runs after a few days.. seems to be working nicely at the moment.. hopefully no out of the blue windows/explorer crashes.. i know that issue is manily a iconpackager problem, but coulda been a windowblinds helping the cause also.

Updated Start11 and the only setting that works is having the Start Button centered. If I set it left in any way the button vanishes.

Hello,
Sorry to hear you are having issues. Please include details on your system so we can try to reproduce the issue. Windows 10 or 11? full version number too please.

Thanks
Basj,
Stardock Community Assistant.

c242 whenever u apply an iconpackager theme it crashes windows completely and makes explorer restart, and when it restarts the start menu button goes missing and u cant bring the start button back until u restart ur PC.. but if u try and apply another iconpackager theme, it will crash it again and ull have to reboot ur pc again.. u didnt know this?

All I know is, it restarts explorer on purpose to clear the iconcache.

yes, it does that.. but when it restarts explorer it makes the start menu button completely disappear. and the only way to get it back is to reboot ur pc.. the same thing will happen every time u apply an iconpackage..

Not for me and I am on an insider build.

wierd, im on windows 10 because windows 11 is complete shit and i wont use it.. it never happened before, but soon as i updated to windowsblinds 11 and start 11, obviously never updated iconpackager because there is no update.. that started happening. number of other people reported the same thing, so idunno if the new apps conflict with the old iconpackager.. not sure, but its a HUGE pain in the rear...

it only happens on this pc im on now which has windowblinds 11 and start11 on it.. my other 2 pcs wich i didnt update and they still have windowblinds 10.89 and start10 on them.. iconpackager works perfectly fine on those.. it seems to only not work with the new windowblinds11 and start11

"Windows 11 is complete shit"

Not for all. I like it more than that inconsistent tiles mess. The more since 22H2.

i only used it when it first came out, i bought a gaming laptop and it had it on there.. i thought it was crap.. so i installed windows 10 over it and havent tried it since, back then tho none of the stardock programs were windows11 ready yet, that was another major reason i downgraded, perhaps now its better.. is the DPI scaling complete crap like it is on windows 10? i mean u can get it the way u want it on windows 10 just have to use a few programs and install that windows dpi fix.. u still gotta do that on windows 11?

Guys, your discussion (comments #40-48) has nothing to do with neone6's reason for posting this thread. Put simply, you're hijacking it. 

Please start your own thread if you wish to continue.

Sorry Doc and neone, You are right of course.