BuckoA51

Latest Google Chrome 49.0.2623.87 seems to be crazy broken if you try and skin it with Wind

+1 from me, I much prefer Microsoft's search and won't be using Start10 for this reason.

OK, I understand such things can be difficult to fix though it has been on-going for more than a year, I'm pretty disappointed that we're still waiting for a fix.

It's #MGQ-645-39742

Yes, latest Windowblinds WindowBlinds 8.1 (035 - Windows 8 Edition according to the about, 8.12 according to the installer exe) and latest non-beta Nvidia drivers.

I've had to disable my Windowblinds again, it looks pretty but all this locking up is just a joke on multi-monitor systems. I got a message back from technical support saying there was "no progress" on a fix :(

[quote]On my multi-monitor system, changing the taskbar multiple display settings from Show taskbar buttons on "Main taskbar and taskbar where window is open" to just "Taskbar where window is open" fixed the problem.[/quote] Fancy that, I had to do the opposite! Though perhaps I should try it that way around again, as far from being fixed in the later builds the problem now seems to be getting worse, not better :(

I wouldn't count on it working much longer, Microsoft are overhauling WDDM (and introducing WDDM 2.0) in Windows 10. Chances are it will break completely by the time they push the next preview out and a whole new version will be required for the final build of Windows 10.

To everyone who said/thought I must be crazy/screwing up my computer etc, I just got this from Stardock tech support:- [quote] Matthew, I was finally able to reproduce this with the conditions you have given. I will place an internal ticket to have it looked at. Thanks for the feedback.[/quote] Looks like a fix might be on the way finally [e digicons]^_^[/e]

I have some new information about this problem. Over Christmas I was lucky enough to get a new motherboard, so I finally reinstalled Windows 8. Completely fresh installation I set about updating, reinstalling the apps I use etc and of course one of the first things I installed was Windowblinds to see if the issue was resolved. At first everything seemed fine, then suddenly the problem was back again, completely locked up taskbar until Explorer was restarted. At this point I knew it co

Not fixed for me I'm sorry to say. Not really willing to reinstall my entire OS just for Windowblinds right now as I'm not having problems with anything else.

This is my favourite skin ever, I still use it on my laptop, Windows 8.1 and works great for the most part. (can't get WB working on my desktop any skin but that's another story). I would love to see an update too.

I'll pass thanks, I don't hold out much hope of some random system optimiser magically fixing the problem. For now I've given up on Windowblinds, Stardock Support are as stumped as the rest of us. I will try again next time there's an updated version.

That definitely doesn't work for me, sometimes the start menu won't even open, though most times it does.

I tried switching to one monitor and the problem persisted :( I really love the multiple taskbars though, think I'd rather switch Windowblinds off than lose them. As I type this the taskbar has bugged out again, a real shame as Windows 8 looks so much nicer with Windowblinds applied. Stardock tech support are completely stumped too.

It's not "locking up" for me, I can still move windows, resize, alt tab etc, I just cannot click on the taskbar. Removing WindowBlinds definitely fixes the issue for me. I don't even mind the new tiles in Windows 8 I think they are awesome on tablets, way better than Android or iOS. However I'm running a desktop here so have no need of them.

Nevermind, just had the problem without having loaded VirtualBox this session... *sigh*

Which version of Virtualbox? How long did you run it for? Did you use seamless mode or any feature like that? Did you have guest additions installed in your Windows guest and how were you capturing the cursor? How many monitors do you have? It seems at the moment as if VirtualBox is actually screwing with the mouse pointer, so sometimes Windows thinks I'm not clicking on the taskbar when in fact I am.

Really does seem to be VirtualBox that is aggravating it. No problems for 3 days or more then had the issue again today after starting VirtualBox.

It's the WHQL driver I'm using. [quote]Ran VirtualBox a while ago without any complications[/quote] How long is "a while ago"?, did you use it for long? Which guest OS's?

Ok I am beginning to suspect this might be some sort of conflict with VirtualBox. Do any of you regularly run Virtualbox on your Windowblinds enabled machines? In testing yesterday with minimal startup, there was no problem for a good half a day of computing, then as soon as I started a VM up the problem appeared. I can say for sure that it doesn't always happen when VBox is running and that it has happened when VBox hasn't been running, but I could have started Virtualbox and

[quote]Does your problem persist with every skin you apply?[/quote] Yes every skin [quote]Are you using only windows 8 ready skins?[/quote] A mixture of what comes with the software and those I've downloaded from Wincustomize, not all are Windows 8 ready but some are. [quote]Just something to ponder....MS makes the flight sim 'FSX' ...and

Yes I Googled that same thing myself, I've tried power management settings that didn't help.

[quote]Is the list large ?The event log.Would maybe be an operation hang or similar.[/quote] Yeah aren't event logs on all windows machines really large? In this instance I just don't know what to drill down to. Remember I can still work the PC by alt-tabbing, or even open the Start menu with the Windows key, so it's as if Explorer is still running just not responding to mouse clicks. [quote]Post a screeny, maybe we can help more.A screen of the event log.[/quote]<

[quote]-Well a lifetime of experience that events similar to this may occur if not cleaning your registry, that and the fact that they tend to go away when the registry is working properly. [e digicons]:cylon:[/e] [/quote] My experience has been totally the opposite, never known registry cleaning to cure a problem and back in the XP days when I did do it, caused more problems than it ever fixed. Windows Guru Mark Russinovich even said the same:- "I haven't and never wi