This behavior matches a recent Clock app change, not a local repair issue. In Clock version 11.2605.9.0, timers were updated so that after reaching zero, they continue counting up as negative time such as -00:27:31. The same release also fixed an issue where the "timer finished" notification did not appear when the timer was started from the widget.
Based on that:
- The reverse counting is expected behavior in newer builds of the Clock app.
- If the missing alert happens only when starting the timer from the widget, that was a known issue and was fixed in version 11.2605.9.0.
- Since Repair, Reset, and reinstall did not help, that is consistent with this being an app-version behavior rather than a corrupted installation.
- If the problem continues, file feedback through Feedback Hub (
WIN + F) under Apps > Clock.
If the timer is being started inside the Clock app itself rather than from the widget, the available information only confirms the new overrun counting behavior and the widget-notification fix.
References: