<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Sick and tired of Microsoft - Intel graphics drivers back and forth. in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729713#M147568</link>
    <description>&lt;P&gt;Actually,&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/248335"&gt;@Duxy&lt;/a&gt;,&amp;nbsp;the problem here has nothing to do with iDSA and nothing to do with the standard driver install packages, the problem is Intel setting up bogus installation records in Microsoft's database that associate specific driver releases with specific systems/motherboards/processors. These records cause the bogus downgrades that are performed by Windows Update. This has been a problem for a very, very long time. Intel blames Microsoft for it. Microsoft blames Intel for it.&lt;/P&gt;&lt;P&gt;Leon has pointed to our standard guidance for this issue, namely the use of the Windows Update Show-Hide tool to block the records in the Windows Update database. This is not a perfect solution; I have systems where the downgrade occurs before I have a chance to run the tool. Nothing to do but try again...&lt;/P&gt;&lt;P&gt;And around and around we go...&lt;/P&gt;&lt;P&gt;...S&lt;/P&gt;</description>
    <pubDate>Wed, 10 Dec 2025 21:14:27 GMT</pubDate>
    <dc:creator>n_scott_pearson</dc:creator>
    <dc:date>2025-12-10T21:14:27Z</dc:date>
    <item>
      <title>Sick and tired of Microsoft - Intel graphics drivers back and forth.</title>
      <link>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729641#M147543</link>
      <description>&lt;P&gt;So this is the situation for iGPU's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Microsoft pushes an old 27.xx driver,&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then Intel releases newer drivers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BUT Intel driver install wipes old drivers,&amp;nbsp; EVEN if NO CLEAN INSTALL IS SELLECTED.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And then Microsoft starts pushing the old driver via windows update and replaces the new intel driver again.&lt;/P&gt;&lt;P&gt;AND THIS **bleep** KEEPS GOING BACK AND FORTH EVERY F'in WINDOWS UPDATE CHECK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;FIX YOUR DRIVERS SO THEY DO NOT WIPE OLD DRIVERS IF NOT SELECTED TO DO SO.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is pure harassment by neglect or stupidity. If not planned malice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a not so nice day.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 07:38:57 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729641#M147543</guid>
      <dc:creator>Duxy</dc:creator>
      <dc:date>2025-12-10T07:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: Sick and tired of Microsoft - Intel graphics drivers back and forth.</title>
      <link>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729648#M147546</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/248335"&gt;@Duxy&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Use the solution described in &lt;A href="http://community.intel.com/t5/Graphics/Windows-11-Graphics-Driver/m-p/1729378#M147477" target="_self"&gt;my post here&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Leon&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 08:34:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729648#M147546</guid>
      <dc:creator>LeonWaksman</dc:creator>
      <dc:date>2025-12-10T08:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: Sick and tired of Microsoft - Intel graphics drivers back and forth.</title>
      <link>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729713#M147568</link>
      <description>&lt;P&gt;Actually,&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/248335"&gt;@Duxy&lt;/a&gt;,&amp;nbsp;the problem here has nothing to do with iDSA and nothing to do with the standard driver install packages, the problem is Intel setting up bogus installation records in Microsoft's database that associate specific driver releases with specific systems/motherboards/processors. These records cause the bogus downgrades that are performed by Windows Update. This has been a problem for a very, very long time. Intel blames Microsoft for it. Microsoft blames Intel for it.&lt;/P&gt;&lt;P&gt;Leon has pointed to our standard guidance for this issue, namely the use of the Windows Update Show-Hide tool to block the records in the Windows Update database. This is not a perfect solution; I have systems where the downgrade occurs before I have a chance to run the tool. Nothing to do but try again...&lt;/P&gt;&lt;P&gt;And around and around we go...&lt;/P&gt;&lt;P&gt;...S&lt;/P&gt;</description>
      <pubDate>Wed, 10 Dec 2025 21:14:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Sick-and-tired-of-Microsoft-Intel-graphics-drivers-back-and/m-p/1729713#M147568</guid>
      <dc:creator>n_scott_pearson</dc:creator>
      <dc:date>2025-12-10T21:14:27Z</dc:date>
    </item>
  </channel>
</rss>

