arno1971 arno1971

Windowblinds Service causes Context-menu problem

▼

Windowblinds Service causes Context-menu problem

Windows Context-menu

from Stardock Forums

The lowest part of my file/folder context-menu

Hi,

For years I have a strange problem with my file/folder context-menu in Windows 10 (my most recent build: 20H2, build 19042.804, but I already had this problem in Windows 7, and even in earlier Window versions). 

I never knew what caused it, and kind of accepted it, but I got more and more annoyed, so I decided to ask help in the Windows tech forum a few days ago.

With some help (extensive problem solving in/with clean boot mode, with disabling/enabling Services and Startup items, via msconfig, System configuration), I was finally able to pin-point the problem.

This is the problem:

When you have a really long file/folder context-menu in Windows, that doesn't fit the screen, as I do, and you have to scroll down for the lowest items, then the text of these items is completely scrambled (SEE SCREENSHOT), as if more than 1 text is displayed at the same time on every line of the context-menu.

If the Windowblind service is DISabled (via clean boot, and consecutive normal boot, with the Windowblind service disabled), and all other services and startup items are ENabled then the lowest items of the context-menu are displayed completely normal. I tried all other combinations of Services and Startup items, but was not able to replicate the problem then. It only occurs with the Windowblinds service enabled.

So, I think this is a Windowblinds bug?

 

Best,

Arnoud

60,954 views 31 replies
Reply #26 from Stardock Forums Top

Quoting Yellow99, reply 25

Since even basj was able to reproduce it on his computer (see postings above)
End of Yellow99's quote

Yes, but only with another Shell - Total Commander

Quoting sdRohan, reply 24

Quoting basj,reply 16
I need to scale my display to 150% to saw it happened on Total Commander in my system
End of sdRohan's quote

WB should only be expected to function as expected with the Windows Explorer shell.

Sean Drohan
Stardock Support Manager

Reply #27 from Stardock Forums Top

Hi I am the OP, and I am still having the problem, although I performed all the steps suggested bu Basj, espec. the clean boot etc., but the problem persists anyway. Luckily I can make the lowest items somewhat visible by scrolling back in upper direction, but this shouldn't be the way to go. If you can find a new, more structural solution that would be great.

Best,

Arnoud

Siege of Centauri
Reply #28 from Stardock Forums Top

Okay... just to prove you Stardock guys wrong, I made a simple mini-program with Visual Studio Express that does nothing but creating a large menu with 100 entries... as it seems, if you use the newer 'MenuStrip' menu, all works normally, but if you use the older 'MainMenu' menu (as a lot of older programs do), then the error occurs.

Please download it and test for yourself: LargeMenu.exe

 

Reply #29 from Stardock Forums Top

Quoting Yellow99, reply 28

LargeMenu.exe
End of Yellow99's quote

So... anyone tried it out yet?  Do you see the problem?  Don't worry, it's not a virus, a Stardock forum is really not the place where one can expect huge download numbers. ;)

Reply #30 from Stardock Forums Top

Admittedly, scrolling menus are something WB doesn't handle very well. That said, they are exceptionally rare (and honestly bad UI); menus that big should have submenus (as Windows Explorer does).

It has been noted internally, however.

Thanks for the feedback. 

Sean Drohan
Stardock Support Manager

Reply #31 from Stardock Forums Top

Quoting sdRohan, reply 30

Admittedly, scrolling menus are something WB doesn't handle very well. That said, they are exceptionally rare (and honestly bad UI); menus that big should have submenus (as Windows Explorer does).
End of sdRohan's quote

Well, you can't just say "Our software is fine, it's the OTHER software developers who should adapt their stuff"... large scrolling menus do exist, e.g. in WinVice (C64 Emulator), or in GIMP (free paint program).  So it would be nice if you could check what causes this problem...

Just my opinion.