APPLIES TO
Any SFU-managed Windows devices
SYMPTOMS
- Appears to show the incorrect time after the November 1, 2026 time zone change.
- The new time zone PCT does not exist.
DIAGNOSTIC STEPS
Check Windows Update History
To visit your Windows update history, Start > Settings > Windows Update > Update History. Look for KB5127648 to see if the time zone update has been installed.
(Windows 10 clients should look for KB5126657)

RESOLUTION PATH(S)
Resolution 1: Check Software Center
If KB5127648 update is missing, check your Software Center to see if the update is pending (for SFU-managed machines). Install and restart your device.
Resolution 2: Check the MECM client
Open the Configuration Manager Properties and view the current version. It should be 5.00.9141.1032.

If it is out of date, proceed to Resolution 3: Do a CCMREPAIR. Do that and cycle back to a policy update.
If your client version is correct, troubleshooting always proceeds with a policy update.
Select the Actions tab and run Machine Policy Retrieval & Evaluation Cycle. Wait a minute for it to run.

Then, select Configurations tab and look at CB - PCT TZ W10 & W11 Oct 2026 and see if it is Compliant. If it is Non-compliant, highlight that configuration and run it by selecting Evaluate.

Resolution 3: Do a CCMREPAIR
If your client version is out of date or the CB is not visible, repair the MECM client install.
Open CMD via Run as Administrator.
If you do not have admin rights on your PC, these steps will need to be performed by IT support staff.
Then, type c:\Windows\CCM\ccmrepair.exe . This will take at least 5 minutes to complete. It will automatically exit upon success.
Repeat Resolution 2 (above) and look for configuration baseline: CB - PCT TZ W10 & W11 Oct 2026 in Configurations Manager Properties.
ESCALATION CRITERIA
If all three resolution fails, you likely have a device health issue that may take more effort to resolve. Service admins have prepared a GPO designed to verify and repair MECM client issues.
Please submit a ticket at Managed Computer Services, clearly indicating:
- Computer name
- AD OUs affected
- OS version (Windows 10 vs 11 for example) (Use “winver” to get the exact Windows build number)