If Intel Driver & Support Assistant (DSA) is stuck scanning, displays “Sorry, something went wrong while trying to scan,” will not open, or refuses to install, work through the fixes in this order: restart its Windows services, use a supported browser, grant Local Network Access, check proxy and firewall rules, interpret any error code, then repair or reinstall DSA. Most failures occur because the browser cannot reach DSA’s local service, a security policy blocks that connection, or the installation is damaged.
What Intel Driver & Support Assistant is supposed to do
Intel Driver & Support Assistant is a free Windows application that identifies Intel and some third-party drivers, checks Intel’s catalog for available Intel driver and software updates, and presents support links. Intel says a normal installation, page load, and analysis typically take about three to six minutes; that is an approximate 2025 figure, not a guaranteed maximum.
As an Amazon Associate I earn from qualifying purchases.
DSA is a local application as well as a website. Its browser page communicates with services running on your computer through localhost ports 28385–28389, while the application also needs HTTPS access to Intel’s online endpoints. A browser permission, proxy, firewall, antivirus rule, or stopped Windows service can therefore make an apparently working installation look broken.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →“Intel® Driver & Support Assistant is a free downloadable application for computers running the Microsoft Windows* Operating System.”
Start with the fastest checks
- Allow the initial scan several minutes. An ordinary analysis can take three to six minutes.
- Restart Windows before changing configuration, particularly after Windows Update or another software installation.
- Confirm that the computer is online and that you are using Firefox, Chrome, or Edge. These are Intel’s validated browsers.
- Close every DSA browser tab and any installer window before retrying. A second installer can produce an installation-in-progress error.
Internet Explorer is no longer supported for DSA. If the page is blank or the scan never begins there, switch to a current Firefox, Chrome, or Edge window rather than trying to repair Internet Explorer.
1. Restart the Intel DSA Windows services
The browser cannot scan if DSA’s background services are stopped or hung. Restart both services even when Windows reports that they are already running.
- Press
Win+R, typeservices.msc, and press Enter. - Find Intel DSA Service. Check its status. If it is running, right-click it and choose Restart; if it is stopped, choose Start.
- Find Intel DSA Updater and perform the same Start or Restart action.
- Close the Services window, reopen the Intel DSA page, and start a new scan.
If either service immediately stops, note the exact behavior before reinstalling. A security product, damaged installation files, or a permissions problem may be preventing the service from starting. Also check Windows Update and reboot once more; pending system updates can leave a service or installer in an inconsistent state.
Recommended Free Tools
2. Reset the browser session and extensions
Use a validated browser
Retry in the latest available Firefox, Chrome, or Edge. A browser profile with stale site data or restrictive extensions can block the page’s connection to the local DSA service even though ordinary websites work.
Clear cached site data
- Close all DSA tabs.
- Clear the browser cache and site data for the Intel DSA page using the browser’s privacy or site-settings controls.
- Exit the browser completely, reopen it, and navigate back to DSA.
Temporarily disable blocking extensions
Turn off ad-blocking, script-blocking, and privacy extensions for the DSA page, then rescan. If the scan works, re-enable extensions one at a time to identify the rule that interferes. Keep the exception limited to the DSA page rather than disabling browser protection globally.
3. Enable Local Network Access in Chromium browsers
Intel’s current error guidance associates the generic message “Sorry, something went wrong while trying to scan” with a missing Local Network Access permission in Chrome and other Chromium-based browsers. This permission allows the page to contact DSA’s service on your own computer.
- Open the Intel DSA page in Chrome or another Chromium browser.
- Use the page’s site-information or permissions control to locate Local Network Access.
- Set it to Allow for the DSA page.
- Reload the page and run the scan again.
If the permission prompt was dismissed earlier, open the browser’s site settings for that page and change the saved decision manually. A browser restart after changing the permission can clear a stale connection.
4. Check proxy, VPN, firewall, and antivirus controls
DSA needs two kinds of connectivity: local communication with its Windows service and outbound HTTPS communication with Intel. Enterprise networks often secure both paths separately.
Permit local addresses
- Allow
localhostand127.0.0.1to communicate with the browser and DSA service. - If a proxy is configured, bypass it for local addresses. Sending a localhost request through a corporate proxy can prevent the browser from reaching DSA.
- In Firefox, add local addresses to the browser’s no-proxy list when your organization uses manual proxy settings.
Review security software
Check antivirus, endpoint protection, and host-firewall logs for blocked DSA processes or local-port traffic. Add an allow rule for Intel DSA only if your organization’s policy permits it, then retry. Do not permanently disable protection just to test a scan; if you need a diagnostic test, use your administrator’s approved temporary procedure and restore the protection immediately.
Test a different network
A home connection or phone hotspot can distinguish a local installation problem from a company-network restriction. If DSA works there, give your network administrator the required local addresses and DSA application details rather than repeatedly reinstalling the program.
5. Use the error code to choose the fix
DSA’s numeric codes are more useful than the generic scan message. Match the code exactly; similar-looking codes can have different causes.
| Error | What it indicates | Practical response |
|---|---|---|
0x80072ee7 |
No internet connection or failure resolving the online endpoint | Verify the connection, proxy, DNS, and firewall rules; retry after network access is restored. |
0x80070652 |
Another installation is in progress | Finish or cancel the other installer, restart Windows, and run DSA again. Do not launch multiple DSA installers simultaneously. |
0x80070570 or 0x80070666 |
Missing or corrupt files; Visual C++ redistributable registration or security software can be involved | Close installers, review security-software blocks, restart, and proceed to a clean DSA reinstall if the error returns. |
1633 |
Unsupported platform | Confirm that the Windows edition and architecture meet DSA’s supported environment; an unsupported platform cannot be repaired by repeating the installer. |
4003, 4005, 4008, 4020, or 4027 |
Invalid configuration data | Restart the services, clear the browser session, and reinstall DSA if the configuration error persists. |
4021 |
Invalid configuration folder | Repair or reinstall DSA so it can recreate its configuration folder; ensure the installation and temporary locations are writable. |
6. Repair or reinstall DSA cleanly
Use this stage only after service, browser, permission, and network checks. A reinstall replaces damaged program files; it will not fix a blocked proxy or an unsupported operating system.
- Open Windows Installed apps or Apps & features, locate Intel Driver & Support Assistant, and uninstall it. If Intel’s dedicated uninstaller is available, use that utility.
- Restart Windows after removal.
- Download the latest DSA installer from Intel’s official download page.
- Before running it, confirm that the download location has free disk space and that your account can write to that folder.
- Check that the Windows
Tempfolder exists and is accessible. A locked or unwritable temporary directory can make an otherwise valid installer fail. - Run the installer once, allow it to finish, and wait up to the normal three-to-six-minute installation and loading period before judging the page unresponsive.
- Return to Services and verify that both Intel DSA Service and Intel DSA Updater are running, then open DSA in a validated browser.
If the same file or registration error returns immediately after a clean reinstall, capture the code and consult your administrator or Intel support. Repeating the identical installer without changing permissions, security rules, or disk access is unlikely to help.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When DSA works but finds no driver
A completed scan that reports no supported driver is not necessarily a failure. Intel says this result means it has no Intel driver or software version available for that particular system at that time.
Detection may be unavailable when a component is very old, discontinued, non-Intel, absent from Intel’s database, or supplied through a customized original-equipment-manufacturer package. DSA’s catalog is not a complete inventory of every driver installed on every Windows computer.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteLaptops and tablets
For portable systems, start with the computer manufacturer’s official support page. Manufacturers often modify graphics, wireless, chipset, power-management, or hotkey packages for a specific model. Intel’s packages are generic; installing one over an OEM-customized package can remove model-specific behavior or produce an unsupported combination.
Best Value
Desktop systems and add-in hardware
Check whether the device is actually Intel hardware and whether the system vendor distributes a customized package. If the component is not in Intel’s database, manual installation from the device or system manufacturer may be the only supported route.
Manual installation when DSA is not the right tool
Use Intel’s Download Center when you know the exact product and need to select a driver package yourself. Manual installation is preferable when DSA cannot run, when you need a specific version, or when you must read release notes before changing a production machine.
| Situation | Best next step | Important trade-off |
|---|---|---|
| DSA service or browser connection is broken | Repair local services, permissions, and network rules first | Reinstalling alone does not bypass a blocked localhost connection. |
| DSA reports no supported update | Check the system manufacturer’s driver page or identify the device manually | OEM packages may be safer than generic Intel packages for laptops and tablets. |
| You need a particular Intel release | Install the matching package manually from Intel’s Download Center | You must verify the product, Windows edition, architecture, and release notes yourself. |
| The machine is managed by an organization | Ask IT to approve services, localhost access, proxy bypass, and driver deployment | Local policy may intentionally block automatic driver tools. |
Supported Windows and browser environment
Intel lists support for Windows 7, Windows 8, Windows 8.1, Windows 10, and Windows 11 in both 32-bit and 64-bit editions. DSA does not support multi-session operating systems. Intel validates Firefox, Chrome, and Edge for the web interface.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Requirement | Supported or required condition |
|---|---|
| Operating system | Windows 7, 8, 8.1, 10, or 11, 32-bit or 64-bit |
| Multi-session Windows | Not supported |
| Validated browsers | Firefox, Chrome, and Edge |
| Local communication | Access to localhost ports 28385–28389 |
| Online communication | Working HTTPS access to Intel’s service endpoints |
Windows support listed by Intel describes DSA compatibility, not a promise that every legacy computer or every OEM driver will be detected. Hardware age, vendor customization, and catalog availability still determine what the scan can offer.
Quick Recap
A practical decision path
- Scan never starts: restart both DSA services, use Firefox, Chrome, or Edge, clear site data, and disable blocking extensions for the page.
- Generic scan error in Chrome or another Chromium browser: enable Local Network Access for the DSA page, then reload.
- Works off the company network but not at work: request localhost and
127.0.0.1proxy bypass plus firewall and antivirus approval. - A numeric code appears: apply the matching action in the error table instead of treating every code as an internet problem.
- Installation still fails: uninstall with Intel’s uninstaller, restart, verify disk and Temp-folder permissions, and install the latest package once.
- Scan completes with no update: check the OEM support page or install a precisely matched package manually; that result can be normal.
What not to assume
- A long scan is not automatically a failure during the normal three-to-six-minute window.
- “No supported driver” does not mean DSA is broken.
- A successful internet connection does not prove that localhost ports are reachable.
- A reinstall cannot correct an unsupported platform or an OEM package that is absent from Intel’s database.
- There is no published Intel failure-rate statistic that can predict how common any one of these causes is.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
