- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
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.
Link kopiert
- « Vorherige
-
- 1
- 2
- Nächste »
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
This looks like a problem with Google Chrome, if, as in the cases you and I have reported, simply switching to Firefox or Edge fixes it.
RayJM
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
I am also experiencing problems and removing the tool and reinstalling it does not fix the issues
I guess manually downloads are the way again
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
It worked nicely for me.
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
Is the Intel product 32-bit or 64-bit as I only have 64-bit .NET installed
Then again the installer should grab run time components automatically
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
windows_guru,
As I understand it IDSA is installed as a web application. I have the 64-bit .NET installations also. I downloaded IDSA and installed it. Once I had resolved some of my .NET dependencies (see earlier posts), IDSA ran without any problems. The Windows November patch Tuesday updated a couple of my .NET applications, and IDSA continued to run without any issues.
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
I've been trying everything and nothing was working.
I did a search for "intel driver and support error "sorry something went wrong while trying to scan" and saw "often stems from browser settings blocking local network access."
So then I searched "browser settings blocking local network access."
Once I opened chrome, settings, privacy and security, I then clicked view permissions and data stored across sites. Sorted by "Most visited" and scrolled to Intel. Once I expanded that, scrolled down to the end and noticed that "Local Network Access" was blocked. Once I unblocked access, I closed everything and opened Intel driver & Support again and it worked as usual.
So either everyone is blocking access or the program is installing and defaulting to block access.
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
try using the dsa webpage in microsoft edge latest version whatever is available , it will ask permission to access local services allow that and it should work , i was getting trouble in chrome where scan failed but in microsoft edge its working perfectly fine
- Als neu kennzeichnen
- Lesezeichen
- Abonnieren
- Stummschalten
- RSS-Feed abonnieren
- Kennzeichnen
- Anstößigen Inhalt melden
This behavior is very likely tied to the recent .NET updates causing a runtime or registration mismatch with Intel DSA dependencies. DSA relies on specific .NET components for its service layer and scan interface, and updates can occasionally break that linkage.
Here are the most effective steps to resolve it:
1. Repair .NET Runtimes (first step)
Go to Settings → Apps → Installed Apps, locate all Microsoft .NET entries (especially .NET 8, .NET 9, and Desktop Runtime), and run Modify → Repair on each. Reboot afterward.
2. Perform a clean DSA reinstall (important)
A normal uninstall often leaves behind broken state data.
Use the official Intel DSA Uninstaller Tool to fully remove it
Reboot
Install a fresh copy of the latest DSA version
3. Verify DSA services
Run services.msc and ensure:
Intel Driver & Support Assistant services are Running
Startup type is set to Automatic
4. Rule out browser-side issues
Since DSA uses a web-based UI:
Clear browser cache/cookies
Try a different browser
Temporarily disable ad blockers or privacy extensions
5. If still failing
Check Event Viewer → Windows Logs → Application for .NET Runtime errors related to DSA. If present, this points to a corrupted .NET update—running the Microsoft .NET repair tool may be required.
Overall, this doesn’t look like a permanent incompatibility to me, but rather a broken dependency state after the update. Just a suggestion.
- RSS-Feed abonnieren
- Thema als neu kennzeichnen
- Thema als gelesen kennzeichnen
- Diesen Thema für aktuellen Benutzer floaten
- Lesezeichen
- Abonnieren
- Drucker-Anzeigeseite
- « Vorherige
-
- 1
- 2
- Nächste »