Intel® Driver & Support Assistant now requiring local network access?

[50shadesofblue]

Why is Intel® Driver & Support Assistant (DSA) now requiring local network access to function?  This seems out of scope for the tool and a bit invasive.  If I decline, the tool does not work or scan my PC.

[Hmmmm]

Totally concur with this. Seems excessive.

[KennethB_Intel]

Hello 50shadesofblue,

Thank you for reaching out to the Intel Community Forum. I understand your concern regarding the Intel® Driver & Support Assistant (DSA) now requiring local network access, and I am here to assist you.

To better understand and address this issue, could you please provide the following details:

• What operating system and version are you currently using?
• Were there any recent changes or installations before this issue happened?

We will wait for your response so we can further assist you.

Best regards,

Kenneth B.

Intel Customer Support Technician

[EdHB]

Hi, Kenneth. This seems to be a well-known concern to people. Has Intel offered any reasonable explanation for what seems to be an overly permissive permissions change request?

If there is a compelling reason, please let us know.

In either case, will you please provide clear directions how we can revert back to1995 and locate and manually install driver updates? (Ok, maybe a bit too much, but on the surface, this seems like egregious overreach!)

[50shadesofblue]

Thank you.

- Operating system: Windows 11 Home - Version 25H2 (fully updated).

- Intel DSA started requesting network access after it auto updated to the latest release.  It's Intel® Driver & Support Assistant version 25.4.36.6.  No other installation changes.

[CraigB]

Any update on this topic?  Why does Intel need to poke around a user's local network to determine what drivers they need?

[VonM_Intel]

Hello 50shadesofblue,

Thank you for posting in our Community. The behavior you’re seeing started appearing in the latest releases, as DSA requires enhanced local service communication and secure component validation in order to perform accurate scans. Still, it’s absolutely valid to question why this permission is needed, and I appreciate you raising the point.

To help me review this further, I'd like to clarify a few additional details.

1. If you temporarily allow network access, does the scan complete normally afterwards?

2. Are you using any third‑party antivirus or firewall tools that might be blocking or modifying DSA’s local service communication?

I want to make sure the tool behaves transparently and securely on your system. Once I have these details, I’ll be able to provide clearer guidance and next steps.

Thank you again for bringing this to our attention.

@CraigB @EdHB @Hmmmm, I empathize with your situation and the issue you are facing. However, I kindly request that you create a new thread for your case. This will allow us to focus on your specific problem and provide you with better assistance.

Best regards,

Von M.

Intel Customer Support Technician

[50shadesofblue]

1. Yes - if I allow network access, the scan completes successfully and the tool works (I can see my installed drivers and update history).  However, after I go back and turn off network access, the tool is not able to complete a scan and shows an error message:

2. No, I am not using any third-party antivirus or security programs aside from what is already built into Windows.

[Jay_Bower]

There's no chance, no chance, I am allowing the assistant to scan my network. The assistant is now worthless.

[EdHB]

Hi, @VonM_Intel. Thanks for the reply. Speaking for myself, there is no need to start a new thread. This is a change in behavior that several of us have experienced. In other words, I think if you can answer the OPs questions, you'll answer all (or many) of ours.

Specifically:

1. Was this an intentional change by Intel?

2. If so, why?

3. What is DSA actually doing with this additional permission?

4. How can I keep my system up-to-date without giving this permission?

@50shadesofblue, if you feel my comments are off topic, I'll gladly start a separate thread. I'm adding to your question because I think we all have the same questions.

Thank you all!

Ed

[EdHB]

Intel, why is it talking so long to answer these simple questions? By nature, I don't like to be accusatory, but getting answers to these simple - and very obvious questions - should take about a minute.

I can't help but feel Intel's lack of response and clarity means you're hiding something or simply hoping that these questions go away. 

Please be helpful and honest. Please respond. You shouldn't need the lawyers to answer these!

[WhyYouDoThis]

Never ceases to amaze me, are these mods actually people or bots at this point. The script they follow lends no benefit to the conversation or provide beneficial insight into the question(s) at hand. 

There is no reason for a machine scan tool to demand local network visibility. Absolutely zero. Period. There are serious security implications here, and I am shocked that this mandatory requirement received the necessary approvals to go live. This should be changed ASAP.

Two thumbs down. 

[Spk]

Completely agree. There's no way we'll allow DSA access to the local network.

Instead, we're removing it from all our machines and will revert to manually checking/applying driver updates. Thanks Intel.

[SANEguy]

This is sad and excessive. Our organization will be removing DSA from our systems and maintain driver updates on a case-by-case and as-needed basis.

[AlHill]

Make sure, when installing the graphics driver, that you customize the install and deselect IDSA.  Intel enables it be default, so you always have this garbage idsa installed.

Doc (not an Intel employee or contractor)
[CoPilot is a virus]