How to Change the Time on Your Computer (Windows, Mac & More)
Your computer's clock affects more than just the time display in the corner of your screen. It touches file timestamps, calendar events, security certificates, and even how your browser verifies encrypted connections. Knowing how to adjust it — and understanding why it sometimes drifts or shows the wrong time — is basic system literacy worth having.
Why Your Computer's Clock Matters
Most people notice the time is wrong when a meeting reminder fires at the wrong moment or a downloaded file shows a future timestamp. But the clock runs deeper than that.
SSL/TLS certificates — the technology behind the padlock in your browser — are time-sensitive. If your system clock is significantly off, websites may appear broken or untrusted. Kerberos authentication, used in corporate networks, typically tolerates only a five-minute time skew before refusing to grant access. Even syncing files with cloud services like Dropbox or OneDrive can produce conflicts when your local time doesn't match server time.
So adjusting your clock isn't just cosmetic — it can resolve genuine functional problems.
How to Change the Time on Windows
Windows 10 and Windows 11
- Right-click the clock in the taskbar (bottom-right corner).
- Select Adjust date/time.
- Toggle Set time automatically off if you want to set it manually.
- Click Change under "Set the date and time manually" and enter the correct values.
Alternatively, you can re-enable Set time automatically and click Sync now — this forces a fresh pull from Microsoft's time servers and is usually the fastest fix when your clock has drifted.
To change your time zone, look for the time zone dropdown on the same settings page. This is separate from the manual time entry, and getting your time zone right is often all that's needed.
Changing Time in Windows Settings vs. Control Panel
Older guides reference the Control Panel route (Control Panel → Clock and Region → Date and Time). This still works on Windows 10 and 11 but is the legacy path. Both routes write to the same system setting.
🕐 Note for domain-joined PCs: On computers managed by a company or school, the time is typically controlled by the network's domain controller. Manual changes may be overridden automatically, and you may not have permission to adjust the clock at all.
How to Change the Time on a Mac
- Click the Apple menu (top-left) and go to System Settings (macOS Ventura and later) or System Preferences (earlier versions).
- Select General → Date & Time (Ventura+) or just Date & Time.
- To set the time manually, turn off Set time and date automatically.
- Enter the correct date and time in the fields provided.
macOS uses NTP (Network Time Protocol) by default, syncing against Apple's own time servers. If you're re-enabling automatic sync, make sure your internet connection is active and simply toggle the setting back on.
Changing the Time Zone on Mac
In the same Date & Time panel, there's a time zone section. You can let macOS detect your location automatically, or you can set it manually by clicking the map or typing a city name.
Changing the Time on Linux
The approach varies by distribution, but the most universal method uses the terminal:
sudo timedatectl set-time "2025-06-15 14:30:00" To check your current time settings:
timedatectl status To set a time zone:
sudo timedatectl set-timezone America/New_York Most desktop Linux environments (GNOME, KDE) also offer a graphical Date & Time settings panel that works similarly to Windows and macOS — right-click the clock or navigate through system settings.
Why Computers Keep the Wrong Time
Understanding the cause helps you apply the right fix.
| Cause | What Happens | Fix |
|---|---|---|
| Dead CMOS battery | Clock resets to a default date after every shutdown | Replace the small coin cell battery on the motherboard |
| Time zone mismatch | Clock shows correct UTC time but wrong local time | Change time zone, not the time itself |
| NTP sync disabled or failing | Clock drifts gradually over days or weeks | Re-enable automatic sync |
| Dual-booting with Linux | Windows and Linux interpret the hardware clock differently | Configure one OS to use UTC consistently |
| Domain/network policy | Changes are overwritten by network admin settings | Adjust on the server side, or contact IT |
Automatic Sync vs. Manual Time Setting
Automatic time sync (NTP) is almost always preferable for everyday use. Your OS pings time servers — Apple, Microsoft, or public pools like pool.ntp.org — and corrects drift without your involvement. It's accurate to within milliseconds and requires no manual effort.
Manual time setting is useful in specific situations: isolated lab machines, devices that never connect to the internet, or troubleshooting scenarios where you need to test behavior at a specific date and time. It's not recommended as a permanent setup for internet-connected devices because drift is inevitable without automatic correction.
The Variables That Determine Your Specific Situation 🔧
Changing your computer's time sounds like a single task, but the right approach depends on several things that vary from one setup to the next:
- Operating system and version — the menus and commands differ across Windows 10, Windows 11, macOS Monterey, macOS Ventura, and Linux distributions.
- Whether the machine is network-managed — corporate or school computers often have time controlled by policy, removing the option entirely from the local user.
- Hardware age — older machines may have failing CMOS batteries, making any manual or automatic fix temporary until the hardware is addressed.
- Dual-boot configurations — running two operating systems on one machine introduces a known hardware clock conflict that requires a deliberate workaround rather than just resetting the time in one OS.
- The actual cause of the wrong time — a dead battery, a wrong time zone, and a disabled NTP sync all look like the same problem on screen but each needs a different solution.
The steps above cover the most common paths, but which one applies — and whether it will stick — comes down to your specific machine, how it's managed, and what's actually causing the clock to be wrong.