I uninstalled Chrome App, deleted all files under Users\AppData folder and reinstalled it. But nothing changed.

On Mac I can only set EET (Eastern European Time) for locations in Turkey which is wrong. But Chrome is clearly pulling from the OS, and I would expect Windows to do the same. Yet this bug indicates it is not.

Test team, could you confirm the Windows behavior. Note the need for a patch to fix the timezone information. https://support.microsoft.com/en-us/kb/3192321

The correct timezone for Turkey is UTC+3 for all dates. That is, there is no Daylight Savings Time.

If wrong, we need to consider patching M-55 stable because I do not think we have another update coming before Jan 6.

Tested this issue on Windows 10 with chrome version #55.0.2883.87 

These are the steps i followed 

1. Changed the country and timezone to turkey and Istanbul (+0300)
2. The mentioned url in the comment #3 is only update for Win 7,8 and Win 2K8, 2K12
2. Installed the latest update on windows 10 i.e KB 3213522 and restarted the machine

Observed that the chrome is still considering the daylight saving settings displaying "Fri Jan 06 2017 20:45:00 GMT+0400 (Turkey Daylight Time)". 
Please look into the attached screen-cast and let us know your observations

Deleted: Issue 677130.mp4 3.4 MB

	Issue 677130.mp4 3.4 MB View Download

You are right, fix number of w10 is KB3213522. 
I have just looked into the attached screen-cast. This is exactly our problem.
I hope you will release a patch soon.

Here are adjustment rule list after installing KB3213522:
I think that chrome doesn't check start and finish date of the last rule (rule number 7). The First Friday of January at 00:00 is 06.01.2017

Turkey Standard Time Adjustment rules
   Adjustment rule #1
      Start Date: 1 Jan 0001 Monday
      End Date: 31 December 2010 Friday
      Time Change: 1:00 hours
      Annual Start: The Last Sunday of March at 03:00
      Annual End: The Last Sunday of October at 04:00
   Adjustment rule #2
      Start Date: 1 Jan 2011 Saturday
      End Date: 31 December 2011 Saturday
      Time Change: 1:00 hours
      Annual Start: The Last Monday of March at 03:00
      Annual End: The Last Sunday of October at 04:00
   Adjustment rule #3
      Start Date: 1 Jan 2012 Sunday
      End Date: 31 December 2012 Monday
      Time Change: 1:00 hours
      Annual Start: The Last Sunday of March at 03:00
      Annual End: The Last Sunday of October at 04:00
   Adjustment rule #4
      Start Date: 1 Jan 2013 Tuesday
      End Date: 31 December 2013 Tuesday
      Time Change: 1:00 hours
      Annual Start: The Last Sunday of March at 03:00
      Annual End: The Last Sunday of October at 04:00
   Adjustment rule #5
      Start Date: 1 Jan 2014 Wednesday
      End Date: 31 December 2014 Wednesday
      Time Change: 1:00 hours
      Annual Start: The Last Monday of March at 03:00
      Annual End: The Last Sunday of October at 04:00
   Adjustment rule #6
      Start Date: 1 Jan 2015 Thursday
      End Date: 31 December 2015 Thursday
      Time Change: 1:00 hours
      Annual Start: The Last Sunday of March at 03:00
      Annual End: The Second Sunday of November at 04:00
   Adjustment rule #7
      Start Date: 1 Jan 2016 Friday
      End Date: 31 December 2016 Saturday
      Time Change: -1:00 hours
      Annual Start: The First Friday of Jan at 00:00
      Annual End: The Last Sunday of March at 03:00

Additional Information: 
IE 11.576.14393.0 and IE Edge 38.14393.0.0 are creating Date object as expected.

new Date('2017-01-06T16:45:08')
[date] Fri Jan 06 2017 16:45:08 GMT+0300 (Turkey Standard Time)

Additional Information 2:
We evaluated the case with MS support team. As they told us, hotfix doesn't cover all usage possibilities. They suggested a registry change workaround which is untrusted for us. When you change current date as 02.01.2017 and test again, you will see everything works fine with Chrome.
Fyi

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]