Thank you for contacting Intel.
You can find steps to uninstall network software and driver on the website below:
Hope this helps.
Thanks - I in the end did not need to do this. Once I was running with the 1Gb Ethernet connections, I changed the IP address to be another one in the segment (not the original server's IP address). I then re-enabled the x540 connections - one at a time, and initially set the IP address to DHCP. This worked. Then I set it to static and this worked as well. I used the driver from Sep 2015. I did the same for the second X540 connections - and set up the hyper V connection to it - again worked OK.
Windows Update then asked me to update the Driver - Recommended update, and there were 2 FCoE optional updates - I selected Hide updates to eliminate them, and hopefully the next update will not exhibit the same problem.
I updated a server with on motherboard 10Gbit Ethernet today as well - no problems
I have the same issue as described. Server : Dell r720 with 1X Intel X540-T2 + the onboard x540/i350 combo. The server is an Hyper-V 2012 R2 Server (full Windows Datacenter setup)
After the Windows update I lost all connections of the two 10gig ports of my onboard x540/i350. the two i350 gig ports were still running OK. the PCI-E x540-t2 was still running OK also.
And I noticed as described, two FCoE device now in the DM with exclamation mark over them.... I had to do a manual uninstall of them from the DM + a research of new device then I got back my two 10Gig port as NIC not FCoE...... What a flaw from MS + Intel..... Worst is that now the setup of IP addr is a pain. Not to mentionned that I used NIC Teaming with Windows and ajustement of RSS for adapters prots to have CPU affiinity etc. all has to be redone over a running Hyper-V server.... I was very, very angry.......
Anyway now it's back to running state.
After trying to run a normal driver package setup from Intel for the NIC (PROWinx64_V.20.4.1) on that server. I got a cool msg :
I don't have FCoE on that server, in fact I don't have nay FCoE at all in all my stuff.
I gess it is related hum !?!?!?
Installing the mentionned KB is ridiculous as this is a superseeded KB since more then 2 years now.....
Please someone help me to put back this server to it's normal state.
Note, before this episode with Windows update and FCoE device/lost NIC a previous ProWinx64 from Intel was executed with no error from the same server.....