Status
Not open for further replies.

UKAspie

Extraordinary Member
Joined
Feb 8, 2010
Messages
38
I use the Clock App for things like meeting I need to go to, laundry ready (I live in a flat with a shared laundry room two floors below me) and when to take my meds. (I'm older than most of you ...)
A recent (yesterday?) update to the app seems to have stopped it working. I realised the time for an alert had passed, and when I looked at the App that alert had rescheduled for the same time tomorrow.
Is this being looked at, or can we just roll back?
 

Solution

Short answer​

  • There isn’t an official Microsoft notice (as of Sep 6, 2025) about a widespread Clock bug that auto-reschedules missed alarms. Please report it via Feedback Hub so it gets triaged quickly. Press Win+F right after the miss, describe “Clock alarm rescheduled for tomorrow,” and attach a recording/screenshot. (support.microsoft.com)
  • Rolling back a Microsoft Store app to a previous version isn’t supported for end users; the Store only offers the current build. (learn.microsoft.com, answers.microsoft.com)

Quick fixes and checks​

1) Make sure it can notify you
  • Settings > System > Notifications: On, and Clock is allowed (banners + sound). Turn off Do not disturb or add...

Short answer​

  • There isn’t an official Microsoft notice (as of Sep 6, 2025) about a widespread Clock bug that auto-reschedules missed alarms. Please report it via Feedback Hub so it gets triaged quickly. Press Win+F right after the miss, describe “Clock alarm rescheduled for tomorrow,” and attach a recording/screenshot. (support.microsoft.com)
  • Rolling back a Microsoft Store app to a previous version isn’t supported for end users; the Store only offers the current build. (learn.microsoft.com, answers.microsoft.com)

Quick fixes and checks​

1) Make sure it can notify you
  • Settings > System > Notifications: On, and Clock is allowed (banners + sound). Turn off Do not disturb or add Clock to Priority. Also ensure the PC is awake at the alarm time; alarms/toasts don’t show if the device is sleeping. (support.microsoft.com)
2) Repair/Reset the Clock app
3) Reinstall the app
  • Open PowerShell (Admin) and run:
    Get-AppxPackage Microsoft.WindowsAlarms | Remove-AppxPackage
    Then reinstall “Clock” from Microsoft Store (Library > Get updates). (answers.microsoft.com)
4) Sanity test
  • Set a one‑time alarm 2–3 minutes ahead (ensure it isn’t set to repeat daily). Keep the device awake and volume up to confirm it fires. If it still misses and then shows “tomorrow,” capture that via Win+F and submit to Feedback Hub. (support.microsoft.com)

Workarounds (while Microsoft fixes it)​

  • Use Outlook/Calendar or Microsoft To Do reminders for time‑sensitive meds/meetings, since they generate standard notifications independent of the Clock app. And consider a dedicated hardware timer/phone alarm as a temporary safeguard.
If you can, share:
  • Windows version (Settings > System > About), Clock app version (Settings > Apps > Clock > Advanced options), and whether the alarm was set to repeat. Also, was the PC asleep at the time? This will help pinpoint whether it’s a notifications/sleep issue or an app regression.
 

Short answer​

  • There isn’t an official Microsoft notice (as of Sep 6, 2025) about a widespread Clock bug that auto-reschedules missed alarms. Please report it via Feedback Hub so it gets triaged quickly. Press Win+F right after the miss, describe “Clock alarm rescheduled for tomorrow,” and attach a recording/screenshot. (support.microsoft.com)
  • Rolling back a Microsoft Store app to a previous version isn’t supported for end users; the Store only offers the current build. (learn.microsoft.com, answers.microsoft.com)

Quick fixes and checks​

1) Make sure it can notify you
  • Settings > System > Notifications: On, and Clock is allowed (banners + sound). Turn off Do not disturb or add Clock to Priority. Also ensure the PC is awake at the alarm time; alarms/toasts don’t show if the device is sleeping. (support.microsoft.com)
2) Repair/Reset the Clock app
3) Reinstall the app
  • Open PowerShell (Admin) and run:
    Get-AppxPackage Microsoft.WindowsAlarms | Remove-AppxPackage
    Then reinstall “Clock” from Microsoft Store (Library > Get updates). (answers.microsoft.com)
4) Sanity test
  • Set a one‑time alarm 2–3 minutes ahead (ensure it isn’t set to repeat daily). Keep the device awake and volume up to confirm it fires. If it still misses and then shows “tomorrow,” capture that via Win+F and submit to Feedback Hub. (support.microsoft.com)

Workarounds (while Microsoft fixes it)​

  • Use Outlook/Calendar or Microsoft To Do reminders for time‑sensitive meds/meetings, since they generate standard notifications independent of the Clock app. And consider a dedicated hardware timer/phone alarm as a temporary safeguard.
If you can, share:
  • Windows version (Settings > System > About), Clock app version (Settings > Apps > Clock > Advanced options), and whether the alarm was set to repeat. Also, was the PC asleep at the time? This will help pinpoint whether it’s a notifications/sleep issue or an app regression.
Notifications were on and Clock was allowed. The PC was awake. The work-around I used was to set 'Clock'on a second PC that didn't have the problem. It has been fixed in the latest general Windows update.
 

Solution

Great—thanks for the update​

Glad to hear the latest Windows update resolved it. To help others who hit the same issue, could you share:
  • The exact Windows update/KB and install date (Settings > Windows Update > Update history).
  • Your Windows build (press Win+R, type winver).
  • The Clock app version (Settings > Apps > Installed apps > Clock > Advanced options).

Prevent it (and help others) going forward​

  • Turn on Microsoft Store auto-updates: Store > Profile > App settings > Update apps automatically.
  • After cumulative updates, open Microsoft Store > Library > Get updates to pull any app-side fixes.
  • If it resurfaces, capture it with Win+F (Feedback Hub) right after the miss and include the Clock version/build.
If you’re happy with the fix, please mark the thread as Solved so folks can find it quickly.
 

Status
Not open for further replies.
Back
Top