Y2k issue with outlook

Question

In scheduling an appointment in 2030 with 2 digits, it schedules for 1930

Answer 1

Y2K is set up correctly under settings but outlook defaults to 2029

Answer 2

Outlook is interpreting the two-digit year using the Windows/.NET two‑digit year rule, so 30 is being mapped to 1930 instead of 2030.

Key behavior from the platform:

• Windows and .NET use a cutoff value (TwoDigitYearMax) to expand two‑digit years.
• With the current default of 2049, two‑digit years 00–49 are interpreted as 2000–2049, and 50–99 are interpreted as 1950–1999.
• If the cutoff is still set to 2029 (older default or policy), then 00–29 become 2000–2029 and 30–99 become 1930–1999.

That means when entering a date like 01/01/30 in an environment where the cutoff is 2029, Outlook (via Windows date handling) expands it to 01/01/1930, which matches the behavior described.

To avoid this issue when scheduling for 2030:

1. Always enter a four‑digit year (for example, 01/01/2030 instead of 01/01/30).
2. Avoid using two‑digit years in date fields, as they are ambiguous and their interpretation can change over time.

If control over Windows policy is available, an administrator can adjust the two‑digit year cutoff via the Y2K policy so that the environment uses a later cutoff (for example, 2049). However, even with such a change, using four‑digit years is strongly recommended for reliability.

---

References:

• Troubleshoot date and time issues in model-driven apps
• How Excel works with two-digit year numbers
• Policy CSP - ADMX_Globalization
• TwoDigitYearMax default is 2049