{"id":106046,"date":"2021-12-21T07:00:00","date_gmt":"2021-12-21T15:00:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/oldnewthing\/?p=106046"},"modified":"2021-12-17T21:18:29","modified_gmt":"2021-12-18T05:18:29","slug":"20211221-00","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20211221-00\/?p=106046","title":{"rendered":"You thought Windows drivers from 2006 were old, wait&#8217;ll you see the Intel drivers from 1968!"},"content":{"rendered":"<p>Some time ago, I noted that <a href=\"https:\/\/devblogs.microsoft.com\/oldnewthing\/20170208-00\/?p=95395\"> all Windows drivers are dated June 21, 2006<\/a>. This is a date hack so that the Windows-provided driver is always treated as the driver of last resort, taking a back seat to any manufacturer-provided drivers, which will have a more recent date.<\/p>\n<p>The Intel drivers use the same trick, but <a href=\"https:\/\/downloadmirror.intel.com\/29227\/eng\/Readme_Public.txt\"> they go even further back<\/a>:<\/p>\n<blockquote class=\"q\">\n<p>Note: Intel(R) Chipset Device Software uses an unusual date for the devices it is targeting. The date 07\/18\/1968 is symbolic &#8211; Intel was founded that day. The reason this date is used is to lower the rank of Intel(R) Chipset Device Software.<\/p>\n<p>This is necessary because it&#8217;s a supporting utility that should not overwrite any other drivers. Updating Intel(R) Chipset Device Software is not needed &#8211; do not worry if you don&#8217;t have the latest version.<\/p>\n<\/blockquote>\n<p><b>Related reading<\/b>: <a href=\"https:\/\/devblogs.microsoft.com\/oldnewthing\/20160209-00\/?p=93002\"> Why do the Windows 10 Phone built-in wallpaper images have a timestamp of April 4, 1975<\/a>?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It&#8217;s the same driver date hack, just even more extreme.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[104],"class_list":["post-106046","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-tipssupport"],"acf":[],"blog_post_summary":"<p>It&#8217;s the same driver date hack, just even more extreme.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106046","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=106046"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/106046\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=106046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=106046"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=106046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}