Intel Driver & Support Assistant No Longer Working

[TechDude]

My install of the Intel Driver & Support Assistant was working without issue on my Windows 11 laptop until my latest Windows updates.  The updates consisted of security updates for .NET 8.0.21 and .NET 9.0.10 as well as an update for .NET Framework 3.5 and 4.8.1.  Now the Intel DSA scans and scans and then reports it has problems.  Could the Intel DSA be incompatible with these .NET updates?

I tried all the troubleshooting steps I could find but not success.

[n_scott_pearson]

I concur. It is definitely broken. Seeing it across a number of (otherwise) up-to-date systems. I have tried reinstallation, etc. without  success.

...S

[RSmith52]

My system was working fine using Win11-24H2 but after updating to 25H2 the driver scan runs and runs until it finally times out and stops.  I tried all of the posted "fixes" from a Google search but no success as well.

[DavidLegion1]

I also have the same issues that everyone else has. I have gone as far as running the program in administrative mode, uninstall and reinstall and repair to no avail. I also feel like that the latest updates for Windows 11 on October 14, 2025 is causing the issues with Intel DSA. I have one PC that I have paused updates for the past several weeks and Intel DSA is working fine. 

[RSmith52]

Update:  I have my Intel software working again.  This is long, first some background.  On Patch Tuesday I ran all of the Windows updates offered by WU (my system is a Win 11 24H2 OS).  I did NOT run the Intel software that day.  That night, I ran the upgrade from 24H2 to 25H2 and followed that with the offered Patch Tuesday updates for 25H2.  This morning, I ran the Intel software on my system and found the constant scanning error.  That was followed by my posting to this site earlier today.

I had another system here that I had run the original Patch Tuesday updates on (24H2) but I never did the 25H2 update to that system.  I tested the Intel software on that system, and it worked normally.

Since the updates offered by WU can be determined by the specific software previously installed on a given system, I compared the 2 systems relative to .NET versions installed and then made sure that broken system had at LEAST the same versions as the working system.  I also rolled my original system back to 24H2 while I tested these combinations of drivers.

Here is the WORKING system list - from Control Panel “Programs and Features”:

Microsoft .NET Runtime 8.0.21  x64

Microsoft ASP.NET Core 8.0.21 Shared Framework  x86

Windows Desktop Runtime 8.0.21  x86

Windows Desktop Runtime 8.0.21  x64

Windows Desktop Runtime 9.0.10  x64

The BROKEN system now has those same 5 versions above PLUS this list:

Microsoft .NET Runtime 8.0.14  x64

Microsoft ASP.NET Core 8.0.14 Shared Framework  x86

Windows Desktop Runtime 8.0.14  x86

The working system list represents a minimum mix of drivers that allowed my 2nd system to work, and the broken system (now a working system) list represents additional drivers that still allow the 1st system to work with the Intel software.

So that’s my experience tonight.  My “broken” system is back to being a 24H2 system with working Intel software.  I hope this gives the other 3 posters some clues to get their systems working again.  As for me, I’m not in any hurry to move forward to 25H2 tonight.

RS

[Davers]

Thanks for that. Removed all 8.0.14 instances and installed 8.0.21 versions and all working as normal again.
Saved me a lot of mucking around.

[50shadesofblue]

Interesting.  I have the same issues now with IDSA on two separate laptops since installing the 10/14 Windows Updates.  These are modern machines with Ultra 7 155H processors. Some things to note though:

- My devices were both already on Windows 11 version 25H2, and IDSA worked fine.  So I don't think it's 25H2 that's the problem, just something with this past Tuesday's (10/14) patches.

- I checked and I don't have any of those 8.0.14 version Runtime or Shared Framework versions installed.  Here's what I have in Control Panel with IDSA being broken.

[Mox]

You're not alone, here the same, I found this thread precisely by searching some reports about this issue: "Sorry, something went wrong while trying to scan.".

[RSmith52]

50shadesofblue,

This whole thing is a puzzle, and I hope that someone from Intel will post with exactly which of these drivers and versions are required.  You might try installing the 2 Shared Framework x86 drivers that I installed above, you can always delete then later.  You can get the drivers at:

Download .NET 8.0 (Linux, macOS, and Windows) | .NET

Make sure that you uninstall the Intel software, then reinstall before testing.

RS