I've tested with all the skins that are included, sucha as sublime and precision, as well as other third party skins.

Why does the text then become like that, glowy and unreadable when its suppose to be White and clear? What do i ned to change in Classic Shell startmenu settings? I can't find the problem for this.

I've tried all skins for Classic Shell i could find. Specially worse with "Metro glass skin for win 8" skin, and all skins that are "glassy."

Only skins that works with the menus and skins is Windows Aero which i understand disables WB 7.91.

I've also just tried "startisback" and that Cuts off the whole start menu and only search at buttom that is visable. When i disable WB the menu works.

It's the same with included skins as well as other skins.

So something weird is going on and i don't know how to fix it then.

Having investigated those AV apps, I was unable to find any issues with WB and Panda Cloud IS other than a mistake at their end with using system colours combined with a fixed dark background colour.  This means certain colour schemes would make some text in their app less readable, but that would happen with those same colours with or without WB.  I did however run into a long list of bugs in their app from just 5 mins usage and have let them know.

With Avast AV there appears to be an issue with the dialogs becoming smaller than expected until moved and I believe this is due to an interaction between their custom skinned dialogs and WB and we will look to fix this.  No other issues were found and WB skins just fine with it running.

Comodo is a totally different case and has massively different issues involving rendering a machine effectively unusable even when Comodo is disabled (but not uninstalled) when WindowBlinds is installed.  This is why for the time being I would recommend strongly against the use of WindowBlinds on a machine with Comodo installed on it at least if it is 64 bit (I believe 32 bit works just fine).  Should you install WB on such a machine you can always resolve the issue by booting to safe mode and uninstalling WB.

The problem with Antivirus packages is they are designed to intentionally break Windows functionality and while it is true that some bad apps use that functionality, it is also true the functionality was put in the OS for a good reason and there are legitimate uses for it.  If this were not the case Microsoft would have removed the functionality from the OS long ago.

The problem with ESET and WindowBlinds was ESET actively breaking Windows functionality in the name of security and not telling the user about it.  Thankfully they offer a method for the user to whitelist an application and they have been very receptive to whitelisting it in the global definitions and therefore allowing our mutual customers to have a good experience.

Symantec will typically whitelist applications too so you can avoid the WS.Reputation issue (a pain for all software developers), though we have had a report today that they may have messed this up with a recent update for Start8.

Anyway with Antivirus the more secure it is, the more false positives you get.  The ultimate AV would not allow anything unsigned to run (so locked down like Windows RT apps, iOS apps etc) but customers would find that limiting.  AV companies try to find the best balance, but sometimes their apps still break things.

If you have encountered problems I would ask that you report specifics as that's the point of this beta test.  If you are unable / unwilling to do this then I recommend that you do not install beta software.

I should stress that I have not installed WB with those AV apps running and it is possible they break WB by blocking the installation of files, but if that were to be the case it would be a problem with the AV app not WindowBlinds.

As a general message to everyone reading this thread, if you have an issue please do make sure to report it with details as assuming other people will report it just results in things not being addressed in the final version as it could well be a specific combination of software that triggers some issue.

Another issue in which the the text in a non-full screen window goes blurry. Notice the "Type:" below the name of each program.

Screenshot:

http://imageshack.us/f/96/stardock6.png/

Tried it out again with several other themes such as Precision, Win 8 Metro and Arsenic. All produced the same results using the default explorer background provided by the theme. This however, does not happen when the window is maximized. 

EDIT: Encountered another issue while choosing wallpapers in "Personalize". Lines at the side of the frames disappears. Only happens when the window is not maximized. This issue happened on every theme I tried including Win 8 Metro.

Link:

http://imageshack.us/f/832/stardock7.png/

EDIT 2: After messing around with several other themes, it seems that not only the "Type" text is affected, but also the "Date Modified" and "Size" text are respectively affected as well. Something which I have discovered is that these text are somehow semi-transparent in which its text is affected by whats behind the window. I tried playing a video file behind the window and I have found out that the text is unreadable as the movie plays. Nevertheless, the clarity of the text is perfectly clear while the window is behind a black background, and completely unreadable behind a white background.

You have turned on the explorer backgrounds feature.

Go to the settings and reset the transparency levels.

The problems with transparent text issues using any explorer background with applied transparency is certainly NOT a new bug. It is bad enough to render the entire option unusable. Is there any hope of a fix for this other than not using the feature?

There is an issue which is in both v7.9 and v7.91:  http://grab.by/napO
There is a blank app (sometimes more than one), it can be dragged on the bar, it shows the quickbar of recently closed program and sometimes it has 1x1 window in the center of the screen. It doesn't show up in Task Manager, so I don't know which window that is.

Started happening since WB 7.9 installation,

My system specs:

Windows 8 Pro x64
8Gb RAM,
nVidia GT555 1Gb
Core i7, 2400MHz,

I have Start8, Decor8, WB 7.91, Fences2, ObjectDock, ModernMix installed.

We have actually done further development on the conflict between WB and Comodo AV and are reasonably confident in saying the next beta update of WindowBlinds will not conflict with Comodo.  The problem appeared to have been linked to the MoveWindow api call and their hooking of it.  I am unsure why they hook this call, or why this remains hooked even when Comodo is disabled, but WB did not expect this to be the case.

I will make sure someone checks with Avast already running and then installing WB as I know nothing like that showed up with some AV testing today that the QA department were working on.

That is more a function of DeskScapes (where the options are available)

Again I say thank you!

Security for me is most important and your taking time in this area to insure compatibility is most appreciated. You have made me a customer for some time to come. 

Kudos to you and your team.

I uninstalled Outpost Pro firewall and suddenly the 64bit applications started working. As well, the desktop didn't go totally empty and black. So I think there's a problem between WindowBlinds and Outpost Pro.

This latest 7.95 beta fixed all my problems with WindowBlinds and Outpost Firewall Pro 8.0.  Everything just works with no exclusions needed. Excellent job Stardock!