1 of 1 people found this helpful
We understand that you're having issues accessing certain sites after installing the Windows® 10 Creators Update.
Normally, we would recommend reinstalling your drivers and applying our recommended settings. However, we noticed that you're using the Intel® Centrino® Wireless-N 1030. This adapter has discontinued and is altogether not compatible with Windows® 10.
In this case, our main recommendation will be to return to a supported operating system. We understand that your adapter was (and is) currently working, however it must be doing so by using the generic drivers included with Windows*. This is not ideal, as issues such as the ones that you're experiencing are very much expected, and future update releases could possibly increase the compatibility gap.
- Supported Operating Systems for Intel® Wireless Products.
- Customer Support Options for Discontinued Intel® Wireless Products.
Thanks for the reply Carlos. Yes, I am currently using the Windows generic drivers although I did try using other driver/application packages from both Dell and yourselves (for W7 and W8.1). They appear to install OK and showed correctly in device manager displaying the new driver reference. Sadly all seemed to give the same basic problem that I am experiencing.
OK, its not a total disaster as much of the time everything is OK, and even using a different browser is OK.
Appreciate your insight on this... I'll probably hold out and work around this for the time being until I see what bug fixes MS come up with.
Just a little more info on this...
For curiosity I tried a clean x86 installation with everything configured identically to the x64. Results were the same however following last weeks Windows Updates (a new cumulative) I have not experienced any issues at all. There was info from MS mentioning:
Addressed an issue where Microsoft Edge users in networking environments that do not fully support the TCP Fast Open standard may have problems connecting to some websites. Users can re-enable TCP Fast Open in about:flags.
Whether that or some other bug fixes addressed the issue I can't say... other than the fact all is now good and has been for almost a week.
Thanks for sharing this update with us. This information should be very helpful to the community.
We'll check in on other similar threads to see if this new set of updates helped with their problem as well.