Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      The Case For Minimal WordPress Setups: A Contrarian View On Theme Frameworks

      June 6, 2025

      How To Fix Largest Contentful Paint Issues With Subpart Analysis

      June 6, 2025

      How To Prevent WordPress SQL Injection Attacks

      June 6, 2025

      In MCP era API discoverability is now more important than ever

      June 5, 2025

      Black Myth: Wukong is coming to Xbox exactly one year after launching on PlayStation

      June 6, 2025

      Reddit wants to sue Anthropic for stealing its data, but the Claude AI manufacturers vow to “defend ourselves vigorously”

      June 6, 2025

      Satya Nadella says Microsoft makes money every time you use ChatGPT: “Every day that ChatGPT succeeds is a fantastic day”

      June 6, 2025

      Multiple reports suggest a Persona 4 Remake from Atlus will be announced during the Xbox Games Showcase

      June 6, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      TC39 advances numerous proposals at latest meeting

      June 6, 2025
      Recent

      TC39 advances numerous proposals at latest meeting

      June 6, 2025

      TypeBridge – zero ceremony, compile time rpc for client and server com

      June 6, 2025

      Simplify Cloud-Native Development with Quarkus Extensions

      June 6, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      Black Myth: Wukong is coming to Xbox exactly one year after launching on PlayStation

      June 6, 2025
      Recent

      Black Myth: Wukong is coming to Xbox exactly one year after launching on PlayStation

      June 6, 2025

      Reddit wants to sue Anthropic for stealing its data, but the Claude AI manufacturers vow to “defend ourselves vigorously”

      June 6, 2025

      Satya Nadella says Microsoft makes money every time you use ChatGPT: “Every day that ChatGPT succeeds is a fantastic day”

      June 6, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Operating Systems»Microsoft dev explains why Windows taskbar clock with seconds was avoided

    Microsoft dev explains why Windows taskbar clock with seconds was avoided

    June 5, 2025

    Windows 11 finally has an option to display the clock seconds on the taskbar, if you prefer it that way. The option warns that you must be ready for the increase in power consumption associated with it, but is it true? Microsoft dev says the taskbar clock with seconds uses more resources, which is why it was avoided, but it’s not significant anymore.

    A clock with seconds for the taskbar and other places isn’t exactly a new idea for Windows 11 because it’s something you can already do on Windows 10 if you play with the Registry, but there were plans to make that a feature exposed via Settings/Control Panel.

    As spotted by Windows Latest, in a post from April 2025, Raymond Chen, a veteran developer at Microsoft Windows, confirmed that Microsoft had previously tested a version of the Taskbar clock with seconds and also a blinking colon, like we have on digital clocks.

    However, the company removed it because it used extra memory about 4KB, which was a concern back then, since Windows 95 only needed 4MB of RAM to run.

    However, in 2025, memory and computing power don’t seem to be an issue with modern PCs. Then why do Windows 11 devs refrain from adding such a trivial UI object to the taskbar as a default? As per Microsoft, the answer lies in the details.

    Showing seconds means the clock updates every second, which stops the processor from going into full sleep mode. It stays a little more active, which can lead to slightly higher battery use over time. That’s one reason Microsoft didn’t make this feature default.

    Devs still don’t find the idea practical because the clock would stay alive indefinitely. Such a mildly useful feature that obstructs the CPU from entering a low-power state isn’t good for the OS.

    Windows 11 Taskbar Clock does not consume a lot of energy

    show seconds in clock windows 11 24h2

    You must have also noticed the warning in the Settings when you try to enable seconds in the taskbar. But how much power does it actually use?

    In Microsoft’s tests, File Explorer used about 0.4 milliwatts normally. When the taskbar clock was set to show seconds, power use went up to around 5.4 milliwatts. That sounds like a big jump, but it’s still very low.

    For comparison, a laptop screen can use anywhere from 200 to 1100 milliwatts, depending on brightness. So, the extra energy from the clock is tiny next to that.

    Still, the idea of efficiency draws a line between what’s acceptable and what isn’t, and the clock seems to be on the wrong side.

    You don’t have to worry now because at least you have an option to enable it in the settings.

    Windows 11 Clock in Notification Center
    Image Courtesy: WindowsLatest.com

    In addition, you can use the Control Panel’s Date and Time applet to view a clock that shows seconds. You can also do that soon from the Calendar/Notifications flyout.

    The post Microsoft dev explains why Windows taskbar clock with seconds was avoided appeared first on Windows Latest

    Source: Read More 

    windows
    Facebook Twitter Reddit Email Copy Link
    Previous ArticleMastering TypeScript: How Complex Should Your Types Be?
    Next Article Microsoft says get Windows 11, ditch Windows 10 to be on the “right side”

    Related Posts

    News & Updates

    Black Myth: Wukong is coming to Xbox exactly one year after launching on PlayStation

    June 6, 2025
    News & Updates

    Reddit wants to sue Anthropic for stealing its data, but the Claude AI manufacturers vow to “defend ourselves vigorously”

    June 6, 2025
    Leave A Reply Cancel Reply

    Continue Reading

    Transformation-Invariant Learning and Theoretical Guarantees for OOD Generalization

    Development

    The Weather Company enhances MLOps with Amazon SageMaker, AWS CloudFormation, and Amazon CloudWatch

    Development

    Gemini can now watch Google Drive videos for you – including work meetings

    News & Updates

    This Planet Has a Huge Deposit of Diamonds, Says Study

    Artificial Intelligence

    Highlights

    CVE-2025-5283 – Google Chrome libvpx Use-After-Free Heap Corruption Vulnerability

    May 27, 2025

    CVE ID : CVE-2025-5283

    Published : May 27, 2025, 9:15 p.m. | 3 hours, 44 minutes ago

    Description : Use after free in libvpx in Google Chrome prior to 137.0.7151.55 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)

    Severity: 0.0 | NA

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    CVE-2025-44148 – MailEnable Cross Site Scripting (XSS)

    June 3, 2025

    Google Classroom Adds 10 More Languages Starting May 19

    May 21, 2025

    How to securely attach an Apple AirTag to pretty much anything

    May 6, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.