Having mouse problems with some Screens in Win 10 1809

When I bring up settings or other Microsoft windows I cannot access the top of the window to close etc.  It is not the case when I use the Microsoft defaul theme.

37,877 views 44 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

 

AzDude
Stardock Community Assistant

Reply #2 Top

I have this too, but I only have problems with Edge the other apps work. You have to unload WB for it to work.

Reply #3 Top

Hello,

Sorry to hear you are having trouble.

When I bring up settings or other Microsoft windows I cannot access the top of the window to close etc.  It is not the case when I use the Microsoft defaul theme.
End of quote

It is a known issue with the mass release of the Windows October update - it should only be with UWP apps (calendar, calculator, etc).

We are working on a fix - thank you for your patience. 

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #4 Top

Yo, guys! Aside from the abovementioned issue with UWP apps not responsive for windows controls, I have another weird issue also - no status bar in Windows File Explorer (see this screen - http://joxi.ru/EA4ZOkPTwqPn9m) with applying theme ("Cascade: in my case), while in the default state with no skin it works just fine. Is it also the issue with WB which will be fixed or skin problem maybe?

Reply #5 Top

Quoting serega_m, reply 4

Yo, guys! Aside from the abovementioned issue with UWP apps not responsive for windows controls, I have another weird issue also - no status bar in Windows File Explorer (see this screen - http://joxi.ru/EA4ZOkPTwqPn9m) with applying theme ("Cascade: in my case), while in the default state with no skin it works just fine. Is it also the issue with WB which will be fixed or skin problem maybe?
End of serega_m's quote

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #6 Top

Quoting serega_m, reply 4

- no status bar in Windows File Explorer
End of serega_m's quote

It is showing for me here on 10.71 - Ill test on .65.:

EDIT: Ok, I see it on .65 but its fixed on an early internal.  Ill make note.

Reply #7 Top

Well, my version is WindowBlinds 10.65 (048 - Windows 10 Edition) - 64 bit OS.

Dunno about betas as I am not participant :)

Reply #8 Top

WindowBlinds 10.65 (048 - Windows 10 Edition) Windows 10 X64 version 1809 here.

Reply #9 Top

Thanks I will keep an eye on it.

Reply #10 Top

Right clicking the title bar and selecting close or alt-f4 works to close the windows.

Reply #11 Top

Thanks for tip. Right clicking on the Title bar works. A good work around until it's fixed.

 

Reply #12 Top

I’m using windows default theme on dark mode until it’s fixed. I really like the dark mode. 

Reply #13 Top

I don't perceive this as a mouse problem.  If it were a mouse problem, then there would be trouble with clicks, erratic tracking, etc.  This is a problem with WB 10.71 and Windows 10 v1809 as I have mentioned in other threads.  Going back to WB v10.65 will probably fix these issues.

Reply #14 Top

Quoting r_pinkard, reply 13
 Going back to WB v10.65 will probably fix these issues.
End of r_pinkard's quote

Nope, I'm using it and still does it. StarDock is aware of it and is in the process of fixing it. I'll wait.

Reply #15 Top

I am waiting too. I am with these bugs too. I'm waiting the fix release the more quickly possible. I buy a few days ago the my Object Desktop license and I want use it.

Reply #17 Top

This is not primarily a mouse problem, but a skinning problem. Settings / UWP programs and Edge browsers seem to have no skins, but this is not true. The skins are only invisible in the background. The focus for closing etc. Buttons are also in the background.

If you play something with the mouse pointer, you hit the buttons in the background sometime and can press them, whereupon the function is also executed.

Hopefully there will be a patch soon!

Windows 10 x64 1809  and WindowBlinds 10.71 (051 - Windows 10 Edition) - 64 bit OS

the  no status bar in Windows File Explorer bug i have too.

 

*************

Going back to WB v10.65 will probably fix these issues.

*************

No, it doesn´t.

 

Greetings

serra.avatar

 

Translated with www.DeepL.com/Translator

Reply #18 Top

As mentioned before Stardock's Dev is currently working to fix the problem. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Thank you.

Basj

Stardock Community Assistant.

Reply #19 Top

Can they send an email to everyone when a fix is released? Instead of keeping an eye on this thread. Maybe the check for updates option in WB will suffice.

Reply #20 Top

Quoting PapaBravo, reply 19

Can they send an email to everyone when a fix is released? Instead of keeping an eye on this thread. Maybe the check for updates option in WB will suffice.
End of PapaBravo's quote

When a New release is ready there will be a notice and a download release posted

for all who want it .

Reply #21 Top

...This is not primarily a mouse problem, but a skinning problem. Settings / UWP programs and Edge browsers seem to have no skins...

 

Yes, I'm seeing these same issues.  10.65 seems to fix the problem with the Settings screen, but the Edge browser buttons are still not getting skinned.  But then, who uses Edge anyway (...just kidding).  I hope these issues can get fixed in the next release soon.

Reply #23 Top

Over the last 2 days, I re-installed Windows 10 1803 from the beginning.  Pure torture!  Re-installed Windowblinds v10.65.  I am not seeing any of the issues with skinning associated with Windows 10 v1809.  Edge skins O.K. Setting screens don't skin, but the buttons work normally.  For that matter, Office apps don't skin, but the buttons work O.K.

Technically, Microsoft is encouraging users to roll-back or re-install to v1803 until the issues associated with the v1809 are solved.  The trouble with a fouled upgrade is that it erodes trust in Microsoft.  Even if they release a v1810 upgrade, do I trust the upgrade?  For now, I'm not too sure...

But if it ain't broke, I'm not gonna fix (or change it) for now.

Reply #24 Top

I have a question...

These issues affect a few people. What is the platform/processor/video hardware of the people affected?

I was affected. In my machine I have all the issues reported here.

My machine is:

- Windows 10 v1809 x64 bit, updated from v1803.

- My drivers is all updated to the last versions.

- Platform/processor/video hardware: AMD A320 chipset; Ryzen 1500X processor; AMD RX570 video hardware with 4GB RAM; 16GB RAM on motherboard.

 

I will test in my laptop, that is Intel platform/processor/video hardware in this week.

Reply #25 Top

Quoting algatelli, reply 22

Patience?????????????????????

6 days!!!!!!!!

We are waiting...
End of algatelli's quote

StarDock can't fix it until Microsoft fixes their problem.