Last Icon In Start Menu Icon Group Not Aligning Properly

Icon Does Not Go Below Previous Icon, It Goes Beside It

Hello All!

I have a slight issue with my Start8 screen.

 

I currently have Start8 set to show a "Large" start menu using "Windows 8 style." I have created several groups to organize my start menu icons. The issue I am seeing is that for some reason the very last icon in a group doesn't go below the 2nd to last icon. Instead it makes a whole new column. So instead of my group looking square it looks like a square with an icon sticking out to the side.

 

Easier to show you than to try and describe it. Here is a picture:

 

Start8 Start Menu Icon Sticking Out

 

As you can see in the picture where I drew the red arrows the last icon went to the right rather than below the previous icon.

 

Is this a Windows 8 issue or an issue with Start 8? Is there anything I can do to fix it?

 

I know it's kind-of trivial but I like things to be neat. :)

 

Thank you.

 

*UPDATE* - I just changed my settings in Start8 to show a "Full screen" start menu rather than a "Large" start menu and the problem is a bit different. There is no longer just one icon protruding to the right. The icon group has been re-organized and now the last two columns are more filled up but they are still not doing what I would think they would do. That is, I would think they would fill up an entire column then start adding icons to the next column so that every column is the same height except the last one.

 

Here is a picture of what it looks like now:

 

Start8 Start Menu Even But Not Complete Columns

 

 

2,193 views 2 replies
Reply #1 Top

This would be a Windows issue rather that Start8 as when in that mode the menu is simply the Windows one resized down.  We are not responsible for the actual rendering of it.

Reply #2 Top

Quoting Neil, reply 1

This would be a Windows issue rather that Start8 as when in that mode the menu is simply the Windows one resized down.  We are not responsible for the actual rendering of it.
End of Neil's quote

 

I should have known it wouldn't be Stardock causing the issue! :)