Dears, please see the screenshort for Intel® Driver & Support Assistant
scan issue, for those days when I click intel driver & support assistant, the icon shows that I have 2softwear need to updat, but when the tool open the browser it shows that it can't scan my computer, may something wrong when system start to scan. and lots of user talk about this issue in China, we all have same issue. so I'm worry about if the assistant softwear have some issue. I'm already update the lasted version of Intel® Driver & Support Assistant (ver. 22.214.171.124) but also doesn't work. so could you pelase help to solve it? looking for your feedback. Thanks in advance.
Hi this problem was raised also in this thread https://forums.intel.com/s/question/0D50P00004WFZg3SAH/intel-dsa-scan-failed-on-my-hades-canyon-nuci... . So bookmark this thread and wait for Intel response. From your post I assume that you are not located in China?
I'm almost sure it's not a NUC issue, since I tried my Acer at home and my HP at my office, all of them have the same issue.
But I also think it's not only a connection issue from China, something seems not right from DSA itself.
I'm not a network expert, I'm not sure why the connection issue still persists even I tried V*P*N or I used proxy setting in Internet Option, theoretically, the connection should be initiated from the proxy server, right? My proxy server is in Finland, the connection should not be blocked.
@BSkib Enough of this. You have made your rude comments multiple times already. Continuing to do so serves no purpose. There are rules of conduct here.
If you have a specific issue with IDSA, other than your meaningless criticism, post your issue and it will be dealt with.
Hello @HWang63 ,
Please verify that you have the Intel Management Engine Interface Driver installed and so, the Chipset Software (Driver). Those drivers should be installed manually. Since you didn't describe your computer/board model, I can't give you the correct link.
Right, I can see. The System Device part in your NUC, looks similar to my NUC8i7HVK (see the attached image). So, the problem is caused by something else.