Clock went missing after recent windows 10 update

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.

33,600 views 20 replies +1 Loading…
Reply #2 Top

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

Reply #3 Top

I dont use any additional monitors.

Reply #4 Top

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.

Reply #5 Top

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.

Reply #6 Top

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.

Reply #7 Top

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.
End of 2of3's quote

Thanks for the research 2of3!

Reply #8 Top

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

Reply #10 Top

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

Reply #11 Top

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

It's been driving me nuts too!!

Reply #12 Top

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

Reply #13 Top

Quoting Neil, reply 12

If you update to the WindowBlinds 10.48 beta you should not be having this problem.
End of Neil's quote

Not fixed

Reply #14 Top
Quoting 2of3, reply 13
Quoting Neil Banfield,

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



Not fixed

End of 2of3's quote

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)

Reply #15 Top

Quoting Neil, 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)
End of Neil's quote
Be sure to include what the monitor number is when Windows identifies it and which monitor is set to primary.

Reply #16 Top

Quoting Neil, 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)
End of Neil's quote

 

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:

 

Reply #17 Top
Quoting 2of3, reply 16
Quoting Neil Banfield,

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



 

End of 2of3's quote

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.

Reply #18 Top

Quoting Neil, 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.
End of Neil's quote

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

 

Works perfectly on V10.49 5*

Reply #19 Top
Quoting 2of3, reply 18
Quoting Neil Banfield,

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. :blush:

 

Works perfectly on V10.49 5*

End of 2of3's quote

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.

Reply #20 Top

Quoting Neil, 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.
End of Neil's quote

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