Home | Recent Posts New Topic
typ656
typ656
Join Date 08/2016
+1

Clock went missing after recent windows 10 update

August 8, 2016 12:02:59 PM from Stardock ForumsStardock Forums

Font of the clock and date is randomly going black or clock is missing completely. Can I do something about it ? It occurs on every style.

windowblinds
Locked Post +1 Karma
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
neomadin
typ656
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #1 August 8, 2016 12:09:37 PM
from Stardock ForumsStardock Forums

Do you have more than one monitor?

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
DrJBHL
Join Date 04/2002
+4222
Reply #2 August 8, 2016 12:10:20 PM
from WinCustomize ForumsWinCustomize Forums

I believe that will require the dev to fix Windowblinds to fix that.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
typ656
Join Date 08/2016
+1
Reply #3 August 8, 2016 2:17:14 PM
from Stardock ForumsStardock Forums

I dont use any additional monitors.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
2of3
Join Date 10/2006
+816
Reply #4 August 8, 2016 6:20:53 PM
from WinCustomize ForumsWinCustomize Forums

This is an issue I reported in another thread. It looks like Windowblinds is borrowing the tray clock text settings from the taskbar button text setting.

The reason it turns black is probably because most skins have black/dark text on the taskbar buttons.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Nerius
Join Date 09/2008
+2
Reply #5 August 8, 2016 9:23:00 PM
from Stardock ForumsStardock Forums

I have the same problem. Driving me crazy i can't fix the skin to change the Clock. Skinstudio doesn't obey, or the skin doesn't and can't change the font ,size or color of the Clock in taskbar. Also fluctuate back and forth both in White and blue. (suppose to be constant White color) Also date is visable now when it suppose to only show the Clock and not the date when using small taskbar as i Always have it on. Somethings are messed up on the Anniversay update.

This problems didn't exist on former win 10 1511 10586 version which worked perfect with the skins.

 I only have one monitor.

taskbar button text setting yes i tried that to but Clock won't change in the skins atleast for me.

 

Hope this gets fixed soon.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Uvah
Join Date 05/2006
+874
Reply #6 August 9, 2016 5:54:15 AM
from WinCustomize ForumsWinCustomize Forums

Aside from the clock issue I have yet to see the ghost icon on ObjectDock. Before the update I was closing it over a dozen times a day. One ill possibly cured but others pop up to replace it. Go figure.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
ZubaZ
Join Date 11/2001
+917 sdemployee
Reply #7 August 9, 2016 8:26:47 AM
from Stardock ForumsStardock Forums

Quoting 2of3,
reply 4

This is an issue I reported in another thread. It looks like Windowblinds is borrowing the tray clock text settings from the taskbar button text setting.

The reason it turns black is probably because most skins have black/dark text on the taskbar buttons.

Thanks for the research 2of3!

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
typ656
Join Date 08/2016
+1
Reply #8 August 18, 2016 8:01:44 PM
from Stardock ForumsStardock Forums

Can you fix it or its a bigger issue than it seems to be ?

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
valentin1282
Join Date 03/2011
0
Reply #9 August 31, 2016 7:58:03 PM
from Stardock ForumsStardock Forums

Same problem here:   Goes ON and OFF  (ECHO skin)

clock bug

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
theAnton81
Join Date 05/2006
+1
Reply #10 October 23, 2016 10:46:13 AM
from Stardock ForumsStardock Forums

Any update on this issue? It is extremely annoying.. :/

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
happyboy7
Join Date 11/2008
+10
Reply #11 October 23, 2016 1:25:17 PM
from WinCustomize ForumsWinCustomize Forums

I'm so glad that it's not just me with this problem!!

It's been driving me nuts too!!

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #12 October 24, 2016 6:39:02 AM
from Stardock ForumsStardock Forums

If you update to the WindowBlinds 10.48 beta you should not be having this problem.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
2of3
Join Date 10/2006
+816
Reply #13 October 24, 2016 3:59:27 PM
from WinCustomize ForumsWinCustomize Forums

Quoting Neil Banfield,
reply 12

If you update to the WindowBlinds 10.48 beta you should not be having this problem.

Not fixed

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #14 October 24, 2016 6:14:26 PM
from Stardock ForumsStardock Forums

Quoting 2of3,
reply 13

Quoting Neil Banfield,
reply 12

If you update to the WindowBlinds 10.48 beta you should not be having this problem.



Not fixed

It should no longer be a problem on the primary taskbar.  If you are having issues please do provide screenshots and additional information as this was specifically addressed and fixed (the underlying issue is a bug in the OS itself)

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
ZubaZ
Join Date 11/2001
+917 sdemployee
Reply #15 October 25, 2016 8:07:51 AM
from Stardock ForumsStardock Forums

Quoting Neil Banfield,
reply 14

It should no longer be a problem on the primary taskbar.  If you are having issues please do provide screenshots and additional information as this was specifically addressed and fixed (the underlying issue is a bug in the OS itself)
Be sure to include what the monitor number is when Windows identifies it and which monitor is set to primary.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
2of3
Join Date 10/2006
+816
Reply #16 October 26, 2016 4:12:29 PM
from WinCustomize ForumsWinCustomize Forums

Quoting Neil Banfield,
reply 14

It should no longer be a problem on the primary taskbar.  If you are having issues please do provide screenshots and additional information as this was specifically addressed and fixed (the underlying issue is a bug in the OS itself)

 

First my info: This is a ASUS ROG laptop with no external monitors.

WB config:

Windows 10 Home (14393.rs1_release_inmarket.161004-2338)
WindowBlinds 10 (015 - Windows 10 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                   2016/06/30 18:57:23
        Wblind64.dll                 2016/06/30 18:57:44
        Wbsrv.dll                    2016/03/04 15:54:32
        WB10Config.exe               2016/10/18 14:10:26
        Wbload.dll                   2016/06/30 22:45:18
        Screen10.exe                 2016/09/12 19:04:17

I'm also running the latest Start10 (v 1.5)

Tested on this skin: https://www.wincustomize.com/explore/windowblinds/7407/ This is one of my own skins so I know that the clock text should be white.

Screenys:

 

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #17 October 26, 2016 5:58:39 PM
from Stardock ForumsStardock Forums

Quoting 2of3,
reply 16

Quoting Neil Banfield,
reply 14

It should no longer be a problem on the primary taskbar.  If you are having issues please do provide screenshots and additional information as this was specifically addressed and fixed (the underlying issue is a bug in the OS itself)



 

First my info: This is a ASUS ROG laptop with no external monitors.

WB config:

Windows 10 Home (14393.rs1_release_inmarket.161004-2338)
WindowBlinds 10 (015 - Windows 10 Edition) - 64 bit OS

Window titlebar blur features are enabled on this operating system

        Wblind.dll                   2016/06/30 18:57:23
        Wblind64.dll                 2016/06/30 18:57:44
        Wbsrv.dll                    2016/03/04 15:54:32
        WB10Config.exe               2016/10/18 14:10:26
        Wbload.dll                   2016/06/30 22:45:18
        Screen10.exe                 2016/09/12 19:04:17

I'm also running the latest Start10 (v 1.5)

Tested on this skin: https://www.wincustomize.com/explore/windowblinds/7407/ This is one of my own skins so I know that the clock text should be white.

Screenys:

Reduced 81%
Original 467 x 540



 

You are clearly not using the beta update of WindowBlinds.  As stated before you need WindowBlinds 10.4.8 or higher installed.  You have 10.0.7 which is a different thing entirely.

If you have installed the beta I am going to guess you didn't follow the instruction to uninstall your existing WB version, reboot and then install the latest version.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
2of3
Join Date 10/2006
+816
Reply #18 October 27, 2016 10:38:13 AM
from WinCustomize ForumsWinCustomize Forums

Quoting Neil Banfield,
reply 17

If you have installed the beta I am going to guess you didn't follow the instruction to uninstall your existing WB version, reboot and then install the latest version.

You are quite right, of course. What a stupid rookie mistake! I apologize for wasting everyone's time.

 

Works perfectly on V10.49

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #19 October 27, 2016 10:49:15 AM
from Stardock ForumsStardock Forums

Quoting 2of3,
reply 18

Quoting Neil Banfield,
reply 17

If you have installed the beta I am going to guess you didn't follow the instruction to uninstall your existing WB version, reboot and then install the latest version.



You are quite right, of course. What a stupid rookie mistake! I apologize for wasting everyone's time.

 

Works perfectly on V10.49

Good to hear.  I think we need to make the installer force the uninstall / reboot.  For some reason on some computers locked files do not get replaced.

Reason for Karma (Optional)
Successfully updated karma reason!
typ656
2of3
Join Date 10/2006
+816
Reply #20 October 27, 2016 11:02:09 AM
from WinCustomize ForumsWinCustomize Forums

Quoting Neil Banfield,
reply 19

Good to hear. I think we need to make the installer force the uninstall / reboot. For some reason on some computers locked files do not get replaced.

Sounds good. Didn't impulse do that for you, or is that wishful thinking?

Reason for Karma (Optional)
Successfully updated karma reason!
Stardock Forums v        Server Load Time:   Page Render Time: