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

      Designing For TV: Principles, Patterns And Practical Guidance (Part 2)

      September 5, 2025

      Neo4j introduces new graph architecture that allows operational and analytics workloads to be run together

      September 5, 2025

      Beyond the benchmarks: Understanding the coding personalities of different LLMs

      September 5, 2025

      Top 10 Use Cases of Vibe Coding in Large-Scale Node.js Applications

      September 3, 2025

      Building smarter interactions with MCP elicitation: From clunky tool calls to seamless user experiences

      September 4, 2025

      From Zero to MCP: Simplifying AI Integrations with xmcp

      September 4, 2025

      Distribution Release: Linux Mint 22.2

      September 4, 2025

      Coded Smorgasbord: Basically, a Smorgasbord

      September 4, 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

      Drupal 11’s AI Features: What They Actually Mean for Your Team

      September 5, 2025
      Recent

      Drupal 11’s AI Features: What They Actually Mean for Your Team

      September 5, 2025

      Why Data Governance Matters More Than Ever in 2025?

      September 5, 2025

      Perficient Included in the IDC Market Glance for Digital Business Professional Services, 3Q25

      September 5, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      How DevOps Teams Are Redefining Reliability with NixOS and OSTree-Powered Linux

      September 5, 2025
      Recent

      How DevOps Teams Are Redefining Reliability with NixOS and OSTree-Powered Linux

      September 5, 2025

      Distribution Release: Linux Mint 22.2

      September 4, 2025

      ‘Cronos: The New Dawn’ was by far my favorite experience at Gamescom 2025 — Bloober might have cooked an Xbox / PC horror masterpiece

      September 4, 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

    Learning Resources

    How DevOps Teams Are Redefining Reliability with NixOS and OSTree-Powered Linux

    September 5, 2025
    News & Updates

    Distribution Release: Linux Mint 22.2

    September 4, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    Poll: Has YouTube taken its war on ad blockers too far?

    News & Updates

    Critical Viasat Firmware Vulnerability Let Attackers Execute Remote Code

    Security

    Node.js Streams with TypeScript

    Development

    CVE-2025-9797 – ExpressCart Remote Code Injection Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    Highlights

    CVE-2025-5259 – WordPress Minimal Share Buttons Stored Cross-Site Scripting (XSS)

    May 30, 2025

    CVE ID : CVE-2025-5259

    Published : May 30, 2025, 6:15 a.m. | 3 hours, 21 minutes ago

    Description : The Minimal Share Buttons plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘align’ parameter in all versions up to, and including, 1.7.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

    Severity: 6.4 | MEDIUM

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

    Critical UAF Vulnerability Discovered in Ladybird Browser Engine (CVE-2025-47154)

    May 2, 2025

    How to Integrate Tailwind with Electron – With Code Examples

    August 13, 2025

    This Linux distro routes all your traffic through the Tor network – and it’s my new favorite for privacy

    June 23, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

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