{"id":7479,"date":"2018-10-24T01:12:00","date_gmt":"2018-10-23T23:12:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=7479"},"modified":"2018-10-23T18:15:50","modified_gmt":"2018-10-23T16:15:50","slug":"windows-10-v1809-defender-shows-wrong-time","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/10\/24\/windows-10-v1809-defender-shows-wrong-time\/","title":{"rendered":"Windows 10 V1809: Defender shows wrong time"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/win102.jpg\" width=\"58\" height=\"58\" align=\"left\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/?p=210908\" target=\"_blank\" rel=\"noopener\">German<\/a>]At this point only a short information in case someone is wondering. In Windows 10 October 2018 Update (Version 1809, Build 17763.55), Windows Defender shows a wrong time for signature updates that are in the future. But this should only be a cosmetic issue.<\/p>\n<p><!--more--><\/p>\n<h2>A reader comment and something within my head<\/h2>\n<p>I mention this here within the blog because there was already a query from a German reader. I received an e-mail with the title 'Strange advertisement on Defender' and the blog reader wrote:<\/p>\n<blockquote><p>On the [attached] picture you can see a screenshot of the current Win-Defender with strange times of the update.<\/p>\n<p>The screenshot is from 23.10.2018 15:50 o'clock.<\/p>\n<p>On the picture the update time is already in the future.<\/p>\n<p>Maybe you have an explanation.<\/p><\/blockquote>\n<p>Yes, I had an explanation, because I read several hours before a <a href=\"https:\/\/www.deskmodder.de\/blog\/2018\/10\/22\/die-registrierungsdatenbank-der-konfiguration-ist-beschaedigt-app-fehlermeldung-unter-windows-10-1809\/#comment-84992\" target=\"_blank\" rel=\"noopener\">comment<\/a> of the kind 'Hello, my 1809 runs also almost without errors. Only the Defender time goes two hours ahead'. Normally I would simply have ignored this comments. But it was obviously 'stored' within the back of my head. And when I got the above reader's question, something rang the bell.<\/p>\n<h2>Tried to run a quick test \u2026<\/h2>\n<p>I booted the test machine with Windows 10 V1809 and tried to check in Windows Defender the date and time value. After a few seconds I got the message that the 'Threat service' had been stopped and I was asked if I wanted to restart the service. I did and had to wait 10 to 20 seconds until Defender was operational again. The reason is unknown to me, I haven't seen it like that yet.<\/p>\n<h2>Check for updates<\/h2>\n<p>Then I let Windows Defender search for new updates. These were also found and installed. Then I took the following screenshot, which shows the problem already.<\/p>\n<p><a href=\"https:\/\/i.imgur.com\/CPG401z.jpg\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/i.imgur.com\/CPG401z.jpg\" width=\"608\" height=\"449\" \/><\/a><br \/>\n(<a href=\"https:\/\/i.imgur.com\/CPG401z.jpg\" target=\"_blank\" rel=\"noopener\">Click to zoom<\/a>)<\/p>\n<p>Windows Defender displays an update dated October 23, 2018, at 19:17. However, the time in the taskbar shows the current local time 17:17. Defender's time will therefore advance by 2 hours. If this is only a cosmetic display issue. I don't know, if this will cause trouble with future updates, that's are rejected because of invalid certificates due to the wrong time.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]At this point only a short information in case someone is wondering. In Windows 10 October 2018 Update (Version 1809, Build 17763.55), Windows Defender shows a wrong time for signature updates that are in the future. But this should only &hellip; <a href=\"https:\/\/borncity.com\/win\/2018\/10\/24\/windows-10-v1809-defender-shows-wrong-time\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,2],"tags":[773,47,1604],"class_list":["post-7479","post","type-post","status-publish","format-standard","hentry","category-issue","category-windows","tag-defender","tag-issue","tag-windows-10-v1809"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/7479","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=7479"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/7479\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=7479"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=7479"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=7479"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}