Intel dual band 7260AC for desktop hangs on Windows 10 creator edition with IPv6 enabled

[AKopp]

I was previously running Windows 10 64-bit Anniversary edition 1607 without any problems.

I have an Intel dual band 7260AC for desktop installed with IPv4 and IPv6 enabled, driver version 18.33.6.2 from the wireless proset version 19.50.1

A few days ago, I installed the update to the new Windows 10 Creator edition 1703 and ALL applications, including console programs like 'nslookup' and 'ping', using the wirless network started to become 'not responding' after a few minutes or less.

Once an application 'hung', it could not be terminated from task manager, giving an 'access denied' error when attempting and 'end task'.

If I disabled the Intel 7260AC adapter and using a wired Broadcom ethernet connection, everything worked normally again.

After disabling IPv6 on the Intel 7260AC, the wireless network ALSO worked again without hanging.

Looking at the symptoms, it seems there is a problem with the 18.33.6.2 driver on Windows 10 Creator edition, where an application gets 'hung' inside the system call to the driver, because they can't be terminated anymore.

I didn't see any newer drivers available and was wondering if other people have encountered similar problems or are using a 7260AC adapter with IPv6 enabled normally?

Adri.

[idata]

Hello AdriK, Grimmer1, and hsk,

In order to gather more information in regards to the issue at hand, we would like to review your event logs with the following procedure:

1. Press the Win + R keys to open the Run box, type eventvwr.msc, and select OK.

2. On the left hand panel, under Windows Logs, right click on "System" and choose to "Clear Log...". You may now leave the Event Viewer minimized or closed.4. Reproduce the issue.5. Open Event Viewer again, locate the System logs. Right click and choose to "Save all events as."

Best regards,

Carlos A.

[AKopp]

Hello Carlos,

If I understand you request correctly, you want me to:

- Uninstall the OS supplied driver 17.15.0.5

- Install the latest Intel PROSet/Wireless 19.50.1

- Use the driver 18.33.6.2 from the Intel PROSet/Wireless.

- Clear the System Event Log and wait for the wireless 7260AC to hang

- Save the System Event Log

- Uninstall the faulty driver and revert to the OS supplied driver

Is that correct?

Best regards,

Adri.

[idata]

Hello AdriK,

No need to uninstall the inbox driver, as our version will install right over it. You got everything else spot on.Please know that we're asking this from you in a completely voluntary manner to gather more data. No need to go through all this trouble if you don't want to. We've got our own labs and adapters to test this issue with, but more logs from different systems experiencing the issue always help.Thank you in advance.Best regards,Carlos A.

[JW4]

I would experience the hang up even with the old drivers every once in a while as well but the new ones that would hang more frequently. I have since uninstalled the intel proset/wireless software with the new drivers and all my hanging issues even with old driver have went away. The only intel software I have for the card installed is the bluetooth part. Just some info my laptop is an asus n53sv i7 2670qm, 16gb ram, 500gb samsung ssd evo 850, intel 7260ac revision 2 wireless card. Windows 10 x64 home. I have also tried a clean install with the same issues of hang with wireless card.

This was the last few events from days ago before I uninstalled the intel software days ago.

The \Device\NDMP1 service entered the Intel(R) Dual Band Wireless-AC 7260 state.

Log Name: System

Source: NETwNb64

Date: 5/6/2017 10:34:20 AM

Event ID: 7036

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer:

Description:

The \Device\NDMP1 service entered the Intel(R) Dual Band Wireless-AC 7260 state.

Event Xml:

http://schemas.microsoft.com/win/2004/08/events/event">

7036

4

0

0x80000000000000

3104

System

\Device\NDMP1

Intel(R) Dual Band Wireless-AC 7260

0000080002003800000000007C1B00400000000000000000000000000000000000000000000000005744525608040000

************That would be and event then this would error**************

The Network Setup Service service terminated with the following error:

Network Setup Service is not a valid Win32 application.

Log Name: System

Source: Service Control Manager

Date: 5/6/2017 10:34:20 AM

Event ID: 7023

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

The Network Setup Service service terminated with the following error:

Network Setup Service is not a valid Win32 application.

Event Xml:

http://schemas.microsoft.com/win/2004/08/events/event">

7023

0

2

0

0

0x8080000000000000

3105

System

Network Setup Service

%%193

4E0065007400530065007400750070005300760063000000

[KAlle]

Same problem here.

Even with old 17.15.05 version driver.

Asus N551 almost unusable like this.

Please help!!

[idata]

Hello KlaasA,

We're currently investigating which change in the Creators Update is causing this issue. There is no official fix available yet.If possible, please perform the following procedure:1. Press the Win + R keys to open the Run box, type eventvwr.msc, and select OK.2. On the left hand panel, under Windows Logs, right click on "System" and choose to "Clear Log...". You may now leave the Event Viewer minimized or closed.4. Reproduce the issue.5. Open Event Viewer again, locate the System logs. Right click and choose to "Save all events as."You can then share your logs with us by switching over to the advanced editor mode. Once a solution is available we will share it on this thread.Best regards,Carlos A.

[KAlle]

-System-Provider[ Name] AFD-EventID16002[ Qualifiers] 32768Level3Task0Keywords0x80000000000000-TimeCreated[ SystemTime] 2017-05-10T15:50:04.232751100ZEventRecordID3662ChannelSystemComputerNotebook-KlaasSecurity-EventData\Device\Afd<td nowrap="nowrap" style="f...

[idata]

Hello,

Thank you for sharing these logs.We should have an update on this issue sometime next week.Best regards,Carlos A.

[idata]

Hello everyone,

As always, it's important to make sure that your computer has the latest set of Windows* updates installed. You may also want to make sure you have our recommended wireless connectivity settings in place.There's a new wireless driver release that came online today. This new driver is certified to work with the Creators Update:- https://downloadcenter.intel.com/download/26782/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10-?v=t Intel® PROSet/Wireless Software and Drivers for Windows® 10* Version: 19.60.0Please update to this new driver and let us know if your issue has now been resolved.Best regards,Carlos A.

[HKim49]

I found that version in beta over a week ago. Are you sure this new version patches the problem? I'm not authorized to mess around with our production machines. It would help if you had a release note.

[idata]

Hello hsk,

We do not currently provide release notes with our Intel PROSet Wireless Software, otherwise we would be glad to share these with you.Best regards,Carlos A.

[JW4]

Nope drivers and software still giving issues. While it no longer will hang the browser, it will only resolve the host once then it wont go to any other pages. When you try to shut down the pc it wont fully power off and I have to do a hard reset. I am now getting a bunch of UDP socket with local port errors. I only copied a few of them as it just keeps changing ports but same error. To get it working again with no issues I cant just switch drivers in the system device to older ones or I still have issues. The working fix as of now is I uninstall intels software then go back to older drivers all issues go away. If I keep the intel software in even with old drivers I will have issues once in a while.

Here is some of my system log when issue was happening.

- http://schemas.microsoft.com/win/2004/08/events/event http://schemas.microsoft.com/win/2004/08/events/event">

-

10001

0

4

0

0

0x4000000000000000

4507

System

1

-

C:\WINDOWS\System32\IWMSSvc.dll

- http://schemas.microsoft.com/win/2004/08/events/event http://schemas.microsoft.com/win/2004/08/events/event">

-

16002

3

0

0x80000000000000

4510

System

1

-

\Device\Afd

UDP

59323

2364

000000000400300000000000823E0080000000000000000000000000000000000000000000000000

- http://schemas.microsoft.com/win/2004/08/events/event http://schemas.microsoft.com/win/2004/08/events/event">

-

16002

3

0

0x80000000000000

4514

System

1

-

\Device\Afd

UDP

54299

2364

000000000400300000000000823E0080000000000000000000000000000000000000000000000000

[idata]

Hello Grimmer1,

Thanks for the update. We will look into this and report back to you.Best regards,Carlos A.

[idata]

Hello Grimmer1,

Would it be possible for you to clear your logs, reproduce the issue and then share your even log file with us (whole file, not the data only)?It may also be important for you to engage Microsoft* in regards to this issue, as it may be rooted in your OS, not our drivers.Best regards,Carlos A.

[AKopp]

Hello Carlos,

I installed the new PROSet/Wireless 19.60.0 and instally the new driver seemed to perform well.

With the old driver from PROSet/Wireless 19.50.1, the network would hang within minutes.

With the new driver, it's better, but it still hangs after 1-2 hours.

Here are some related events:

- <</span>Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event">

- <</span>System> <</span>Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <</span>EventID Qualifiers="49152">7034</</span>EventID> <</span>Version>0</</span>Version> <</span>Level>2</</span>Level> <</span>Task>0</</span>Task> <</span>Opcode>0</</span>Opcode> <</span>Keywords>0x8080000000000000</</span>Keywords> <</span>TimeCreated SystemTime="2017-05-18T19:39:20.981726100Z" /> <</span>EventRecordID>15852</</span>EventRecordID> <</span>Correlation /> <</span>Execution ProcessID="944" ThreadID="10964" /> <</span>Channel>System</</span>Channel> <div style="margin-left: 1em; t...

[idata]

Hello AdriK,

Please clear your system event logs, reproduce the issue and share the whole event log file so that our engineers may take a better look at what happens before, during, and after the issue presents itself.

Once you've saved your log to a file, you'll simply need to switch over to the advanced editor to enable attachments. You may need to compress this file before hand.

If the file is still too large to attach, please let us know so that we may send you an email to which you can reply with the attachment.

Best regards,

Carlos A.

[JW4]

Prolly should have included the part where i uninstall intels software and it goes back to old drivers.

[idata]

Hello all (AdriK, Grimmer1, emaildrose, KlaasA

This seems to be an OS-Sided issue.

Please try the following steps suggested by Microsoft* Support (I've added screenshots as attachments for reference):

1. Open a Command Prompt using administrator privileges (Right click on the start menu, select "Command Prompt (admin)" from the list)

2. Start powershell session by writing in "powershell" and pressing enter.3. Find your adapter's name: Get-NetAdapter4. Note your adapter's name (mine is: Wi-Fi)5. View your current Receive Segment Coalescing (RSC) settings, mostly for reference: get-adapterrsc6. Disable RSC: disable-netadapterrsc -name Wi-Fi (or your adapter name from step 3, if it's more than one work, use quotations, ie "wi-fi 2").7. Make sure changes have been made: get-netadapter rsc (everything should say "false" now).

Do let us know if the issue is resolved by this.

Best regards,

Carlos A.

[BSala2]

disabling RSC mitigated the WiFi issue on all affected devices with Intel as well as other manufacturers' adapters. It appears to be an OS issue - not Intel.

[JW4]

About that fix...when i type in the get-netadapterrsc command I dont get anything back. I tried to just type in disable command and error. Any clue??

[idata]

Hello Grimmer1,

That's odd, if you're on Creator's Update the Get-NetAdapter cmdlet should work like it did in my example. As an alternative you can try their second suggested method, lowering the Maximum Transmission Unit from 1500 (or default) to 1400:

1. Open a Command Prompt using administrator privileges (Right click on the start menu, select "Command Prompt (admin)" from the list)

2. Find your adapter's name: netsh interface ipv4 show subinterfaces3. Note your adapter's name under Interface, mine is Wi-Fi.4. Set your Maximum Transmission Unit (MTU) size to 1400: netsh interface ipv4 subinterface Wi-Fi mtu=1400 store=persistent - Note: If your adapter name has more than one word, you will need to write it in quotations. For example: "Wi-Fi 2" or "Wireless Network Connection".5. You should receive an output stating "Ok." after which you may close your command prompt and test your adapter.

See attachments for reference.

Best regards,

Carlos A.