Reply #1 from Stardock Forums Top

We need to know more to try and help you:

  • Windows version
  • Windowblinds version
  • Are you using any other software/tweaks/registry hacks to customize your PC
Reply #2 from Stardock Forums Top

From your screenshot, it appears you are using Classic Shell. Does the problem go away if you uninstall Classic Shell?

Sins of a Solar Empire: Rebellion
Reply #3 from Stardock Forums Top

Quoting JanOscar, reply 1

We need to know more to try and help you:

    • Windows version
    • Windowblinds version
    • Are you using any other software/tweaks/registry hacks to customize your PC
End of JanOscar's quote

 

Only have Classic Shell installed along with WindowBlinds.  Before that, created and applied a custom desktop theme for Windows 10.  No other software/tweaks/registry hacks.  Both Classic Shell and WindowBlinds need to work.  The Windows 10 "start menu" is an absolute disorganized mess.

 

Reply #4 from Stardock Forums Top

Quoting JanOscar, reply 2

From your screenshot, it appears you are using Classic Shell. Does the problem go away if you uninstall Classic Shell?
End of JanOscar's quote

If I exit Classic Shell to the Windows 10 start menu, the problem persists.  To test the uninstall, I would like to use a virgin Windows 10 VM that has neither Classic Shell nor WindowBlinds installed.  I'd then install WindowBlinds alone and see if the problem persists.  How would that work regarding the WindowBlinds license?

 

Reply #5 from Stardock Forums Top

I believe it still 5 activation for Windowblinds 10. Try it first, if it does not activate you will need to deactivate the old activation first use this guide: https://forums.stardock.com/486311/accounts-and-activation-support-faq#deactivateproduct

Thank you,

Basj,
Stardock Community Assistant

Reply #6 from Stardock Forums Top

Quoting basj, reply 5

I believe it still 5 activation for Windowblinds 10. Try it first, if it does not activate you will need to deactivate the old activation first use this guide: https://forums.stardock.com/486311/accounts-and-activation-support-faq#deactivateproduct

Thank you,

Basj,
Stardock Community Assistant
End of basj's quote

When deactivating the old activation(s), if there is more than one activation, can I choose which activation to deactivate?  If that can be done, then I could activate the VM I'm going to test and then deactivate it once I'm done, since I'm going to delete that VM anyways.

Reply #7 from Stardock Forums Top

Have you look at the link I given you? I believe it is quite clear in there. Note the picture that show "PCName"

Thank you,

Basj,
Stardock Community Assistant

Reply #8 from Stardock Forums Top

Quoting xode0000, reply 4

Quoting JanOscar,

reply 2

From your screenshot, it appears you are using Classic Shell. Does the problem go away if you uninstall Classic Shell?


If I exit Classic Shell to the Windows 10 start menu, the problem persists.  To test the uninstall, I would like to use a virgin Windows 10 VM that has neither Classic Shell nor WindowBlinds installed.  I'd then install WindowBlinds alone and see if the problem persists...

End of xode0000's quote

Installing WindowBlinds on a virgin Windows 10 VM that has never had Classic Shell installed does not get rid of the problem.  Further, the problem is present no matter what skin I use.  Turning off Windows 10 DWM enhancements using control panel as follows does not get rid of the problem:

 

 

The following greatly mitigates the problem: