Quoting Neil Banfield, reply 129
Quoting Mustang Lx 50, reply 127
I'm using Stardock's Start8 to give me back the start button. I'm also using Virtual CD v10 - maybe it does something to explorer since it adds extra options to the right click menu for drive icons. As for Antivirus I'm using Eset 6. Originally I was unable to get WindowBlinds to start but your fix to the settings for wbcore.exe fixed that problem. I found I also had to exclude taskmgr from WindowsBlinds if I wanted it to appear. The UAC popup window also wouldn't appear.
You are not using anything from Comodo too are you?
Mr Banfield,
Ive been using Comodo for years with no problems. They have the best Internet security out there.
I ran into problems with this Beta WB and Comodo, so I uninstalled Comodo I.S. and went to default windows 8 Defender security.
Windowblinds runs fine with it.
HOWEVER, I have now tried Panda Cloud I.S., Avast I.S. and Comodo I.S. ALL of them have problems with Windowblinds.
Hence this is a problem with Windowblinds, not with the security software being used. Fix your software please.
It's rather foolish to force a person to change antivirus software to "fit" your program. 3 out of 4 I've tested have had problems with Windowblinds. I think the faulty party is being presented here.
This is clearly a Stardock problem.
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.
WinCustomize Forums
Stardock Forums
Now I can use it with windowblinds.