This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have worked out that if I correct the birthday dates and anniversary dates either on Outlook.com, Outlook 2010(with outlook connector) or Live mail the following happens.
When synced to my HTC Titan the anniversary dates remain correct, but all of the birthday dates in the "birthday field" on the phone that fall during British summer time (GMT+1)between the 25th of march and 28th of October move forward 1 day? However the birthday dates that are added to the "birthday calendar" remain correct? .
This problem does not affect dates in the Anniversay field only the birthdays!
If I correct the birthday field on my titan for any of the dates that have moved forward one day then when I check back to Outlook.com, Outlook 2010 or Live mail the birthday has moved back one day from the original date!
I do not believe it is a fault with the Titan software, it appears to be with the server setting for birthdays that fall between the daylight saving times in the server.
If I add a test contact to outlook.com with a birthday and anniversary of 24th March 2001 then both dates sync to titan with correct dates, but if I change both dates in outlook.com to the 25/03/2001 then the birthday field on the phone changes to 26/03/2001 but the anniversary field stays at the 24/03/2001. This remains true for every date up till 28/10/2001 when both times become the same again with no offset.
I have checked every time zone and location setting in Outlook.com, PC and my titan and they are all United Kingdom, GMT London etc.
EDIT, Things get worse!
I have just installed Office 365 on my laptop and if i add a birth dat of 09/07/1970 to one of my contacts using the drop down calendar as soon as I save the change Outlook 2013 updates the date to 08/0701970? Outlook 2013 actually takes a day off the correct date which is then reflected in Outlook.com, Live mail etc.
This has got to be a problem with the database on the server!
Organizing and accessing contact information in Outlook.com
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The really weird aspect is that if I enter a meeting in the phone and synchronize, it appears correct in the Outlook calendar.
As already mentioned: When I enter a meeting in Outlook it is shown one day late on the phone.
And further: If I modify the meeting that I entered on the phone in Outlook and synchronize, the phone meeting entry is moved to the day after!!!
Yes, it has something to do with leap year: when event is created before 29th February, it is shown one day later in the phone, if after - appears in correct day.
(using HTC Sync Manager 3.1.64)
4 years later ... the same happens again ?
Now with a HTC smartphone and HTC SyncManager (latest version).
However I noticed that dates after February 29 (note that both 2012 AND 2016 are a leap year) are always correct.
I have the same issue. Including the issue with outlook (latest version with office 365)where one selects the date in the drop-down and the date changes to one less as soon as you save it.
I've had other problems with dates. When bringing over all the contact details from Gmail to Outlook.com, all the birthdays with dates less than 12 swapped the months and dates. So, each time I discover this, I try changing the date to the correct date and then hit the issue of the date being saved as 1 day less!!!!
It's definitely a bug on people.live.com
- if you set a birthday on the iPhone it's correct in Windows 10 but also wrong on people.live.com
maybe Microsoft will fix the bug when windows 10 user start to complain about it (in a few years...)