Will stop complaining here.  Does this also mean there will be no more screen shots from users saying look at my desktop?

As long as they are relevant to Beta issues...;)

Any review?  

I'll give you one. WB10.0.2, although a Beta, works beautifully on my laptop. However there seems to be IMO machine specific issues, for want of a better term, or perhaps conflicts with certain programs. I can't say for certain as I'm not seeing it through other's eyes, I can only speak for myself. Read the various comments to get a better idea of how the new Beta is working.  

Update:  I posted yesterday that I was unable to resize Firefox.  The issue is now resolved.  I decided to check my video driver and it was out of date so ran the update and all is well.  If anyone else is having sizing issues or unexplained phenomena, you might want to check that all of your drivers are up to date. 

OK then.  Thanks for everyone's help  

Please contact support here: https://esupport.stardock.com/index.php?/Tickets/Submit 

Hi

Just to help out those that installed beta and with no luck,to tell You that U are not alone..

Have Windows 10 64 bit,installed WB 10 beta,and restarted it,with no luck.It always says something like "It looks like the program is not installed correctly would you like to fix it" . 

Click "Yes" but it does something in background process for few seconds,and nothing,not even a wallpaper works..

Reinstalled it ,tryed again,same thing.. It doesn t work..

Hope they will fix it soon,othervise,what is the use of subscription,when with Windows 10 You can t use any product,or?

Actually yea,what products are compatible with 10?

Here is something you might want to try.  Uninstall WB 10, turn off your security program(s) and try again.  It may or may not help but it's worth a try. 

Neil, I followed this advice and now I can read the right click menus just fine.  Thanks so much for your help and patience!

Will try,thx..

If that doesnt work then -

Please contact support here: https://esupport.stardock.com/index.php?/Tickets/Submit

If you use ESET there are specific instructions you have to follow due to their HIPS feature which breaks WB silently.

Many of the ObjectDesktop apps are now Windows 10 compatible.

Tryed,didn t work..

Guess ticket,but,not sure to submit ticket when it is in beta phase,probably this is why it is in bete phase

Sorry for the delay new user posting limit.

Bitdefender Internet Security 2016. And you are right, that was, in fact, the issue. In the antivirus module there is a setting called Active Threat Control. Disabling that fixed all my issues.

While I am not super happy about disabling parts of my antivirus, I understand the root cause - I'm sure WB is injecting or otherwise modifying the other processes and that is making the AV mad. I'm trying to play with exclusions so I can get it working - am I correct that "c:\program files (x86)\stardock\windowblinds\wbsrv.exe" is responsible for WB operations?

Thanks for your assistance Neil!

fix to trayicon.   updated to the beta 2 and still no fix.  so i just pinned to taskbar.  however it does not show the versions installed like the system tray.  i need the system tray icon wblinds showing at all times and not disappear with updates here and there.

WindowBlinds 10 BETA (005 - Windows 7 Edition) - 64 bit OS

Wblind.dll 2015/12/17 07:45:ll
Wblind64.dll 2015/12/17 07:45:43
Wbsrv.dll 2015/12/02 08:52:18
WB10Config.exe 2015/12/17 07:45:08
Wbload.dll 2015/12/02 08:52:48
Screen.exe 2015/12/02 08:52:27

highly frsutrating system tray refuses to show and i refuse to uninstall once more.  ridiculous, that feature shud not have been removed any at all.

if so, enough complaints have been lodged by users; more so myself. 

Please remember that Windowblinds 10 is still in Beta.

Results will vary...;)

What are the settings to make system tray stay.  As when box is checked until u close window blinds configuration and then reopen, check is off again. 

I am relatively new using the Stardock products and really like what I have seen so far.  My problem is that I am not frustrated by having the icon for WB10 show and stay in the system tray or a few other pesky "bugs", but the fact that so many people seem to not understand that a program that is in beta testing is being tested to find and correct as many bugs as possible before release to the general population. That does mean that there may be and probably will be problems with any beta product.  I have been involved as a beta tester for 4 or 5 years with a software company that markets photo editing software.  I have tested what they call prototype, alpha, and beta products. I never experienced any major problems with any of the products until Windows 10 was introduced and then it seemed that everything went bonkers.  My feeling about all of this complaining, and that's what a lot of the dialogue seems to be, is that one should not be using WB10 beta or any beta software if they are not willing to accept some aggravation every now and again and listen to what is being offered as solutions.  Because of the differences in hardware and software, particularly antivirus software, installed on each individual's PC the solutions offered in some cases will probably not work for all.  The biggest issue I have found in beta testing is that Graphic card drivers and antivirus software cause the most issues generally speaking

I don't mean to offend anyone but this is just MY feelings about beta testing a product.

Great work and a big thank you to Stardock!!

I guess I am strange because I want as few icons as possible in the system tray.  WB is one I definetely don't need in the system tray.  

1.  WB10 interferes with the default Start Menu All Apps display.  see my discussion here:

 https://forums.wincustomize.com/474160/page/1/#3610366

2.  WB 10 does not rememnber the setting to make the icon appear in the system tray.  I check it, close the configuration dialog and when I go back in it's unchecked.

Greg, your number one above does not occur on any of my 6 Win10 rigs. I'd open a support ticket, if I were you. Since you're the only one reporting it, I'm guessing it's on your end, and possibly not a beta bug.