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.

Hello,

I have an Inspiron i5577 with AC-3165 w/BT. For a long time now, sometimes when I rewind a video on Firefox or Chrome, on any website, with a fresh Windows 10 installation, the video and audio becomes choppy. Imagine looking at a video that only plays 1 Frame Per Second. It plays for quarter of a second, stops, plays again, stops, etc. Once the stutter begins, every sound played through other sources such as local MP3 or Windows notification sound also stutter.

If I rewind videos on a local MP4 file it never starts stuttering. It never starts stuttering with wired earphones. The stutter is always initiated when changing a video playback position on the browser. The more frequently I change the position, the more likely it stutters. Sometimes it stutters only for a second after rewinding but continues to play. When this initial one-time stutter happens, it always starts stuttering permanently after subsequent rewinding. Rewind once - it stutters once but plays fine. Rewind again - it stutters forever.

I have tested it with two BT headsets manufactured by different companies, as well as on two web browsers. The problem is with the Bluetooth adapter or drivers.

I have followed Mr. Carlos A.'s advice to reinstall WiFi and BT adapters but that hasn't solved it-3165 Bluetooth cuts of minus of a second that affects all devices connected. Dell Inspiron 7000 17" on W10. I've done… (tried Dell's WiFi/BT drivers too).

To temporarily fix the problem I disable and re-enable the BT adapter. The BT headphone automatically pairs and it plays fine after the reset. Sometimes the stutter happens multiple times in 10 minutes, sometimes once an hour. It makes media consumption through BT highly unpleasant.

I've attached Intel System utility log to this thread with a hope that someone can help troubleshoot it. I'm willing to go through technical steps. Thanks in advance!

EDIT:  Here is a more detailed look at the problem. Open a YouTube video and play. Click on a rewind bar to skip ahead. Do it again. It starts stuttering. Click on Windows 10 notification button (bottom-right corner of taskbar) and from the action panel click on the Bluetooth card twice to disable and re-enable. Once the Bluetooth is disabled, what surprises me is that the video automatically stops. If I try to rewind the video while BT is being reset, it won't play. The video starts playing automatically on its own once the BT finishes resetting and pairs the BT headset. As soon as its automatically paired the video resumes with a proper sound.

Hi there

     We are trying to deploy a new wireless profile using TLS and Machine Certificates settings. However, our users cannot import these profiles without running the Intel Proset apps as an administrator. The apps will hang in the process. Dropping the exported profile into the AutoImport also failed. The autoimport log stated that "this settings is only available to administrators......" Had anyone ran into this problem? Thanks

Hello,

on my Dell Vostro 1520 (GM45-Chipset, no whitelisting as far as I know) both drivers (Bluetooth and Wireless) for the N2230-Card could be installed successfully without any error message under Win 7 32bit.

Bluetooth works fine without any issues.

Wifi doesn't work at all. "N2230" is listed as a network device, but marked yellow (could not be started, Code 10)

OS installation is fresh, new and clean. The current original intel driver is the first and only one installed for the N2230 (no driver provided by Dell, not integrated as OEM)

There are no other issues in the device manager.

Bios version is newest - A08.

Unfortunetely I don't have another compatible laptop to test the card in another environment.

What can I do?

Regards

I am using Lenovo ThinkPad T570. It was working well about 1 month ago. Suddenly it stopped working. I tried all advice given in thread wigig error 0x1010 but nothing worked. The latest version (WiDock_3.0.53144) is installed on my PC. Please advice!

Since January my wifi adapter is disabled intermittently. Sometimes it comes back on after I try a few things like reinstalling drivers but this happens randomly. On device manager the adapter is disabled with error code 45.

Details:

- Dell inspiron 13 laptop 7000 series, service tag (DSJZ2C2)

- Windows 10

- proset wireless software version 20.40.0, driver version 19.51.11.2

What I have tried:

- uninstall and clean install of driver, at first repairing proset installation worked too. Also tried the driver version not packaged as proSet...that didn't help either. 

- dell factory reset and tried previous Bios versions, rolling back on windows updates (the adapter was detected only briefly and stopped after the next restart)

- also tried system restore to a point in time where I did have wifi, this helped initially but then I ran into a BSOD situation when I tried an earlier system restore to get it working again.

- network reset, didn't make a difference

I am out of options now and can only access internet through my ethernet connection which is not ideal. I would appreciate any help or suggestions!

I recently updated my ISP from 250Mbps to 1Gbps.

Mobile devices are now achieving 300+Mbps connections using speedtest.net

My Dell Inspiron 15 7000 Gaming laptop is only achieving 131.49Mbps, which is about the same as prior to the ISP and modem update.

I have updated to the latest intel drivers. I have enabled U-APSD support. There are no device priorities configured in the ISP modem.

Here is the netsh wlan show interface:

netsh wlan show interface

There is 1 interface on the system:

    Name                   : Wi-Fi

    Description            : Intel(R) Dual Band Wireless-AC 3165

    GUID                   : 654901e8-f155-481a-8ea2-f619835a9070

    Physical address       : f8:34:41:2b:1a:ab

    State                  : connected

    SSID                   : Munzee

    BSSID                  : a8:9f:ec:22:6c:8d

    Network type           : Infrastructure

    Radio type             : 802.11ac

    Authentication         : WPA2-Personal

    Cipher                 : CCMP

    Connection mode        : Auto Connect

    Channel                : 48

    Receive rate (Mbps)    : 351

    Transmit rate (Mbps)   : 351

    Signal                 : 99%

    Profile                : Munzee

    Hosted network status  : Not available

I am attaching the latest SSU scan.

I have tried to enable driver event logging in the PRO/SET admin tools (v20.40.0), but cannot get the Wireless Event Viewer to start. Apparently this tool is no longer supported in Windows 10? If I need to log driver events for my Dual Band Wireless-AC 8260, which tool should I use?

I am using Manjaro KDE with the 4.14.34-1-MANJARO kernel. I also have Windows 10 dual booted.

When I connect to my the internet via WiFi, I get speeds like 4kBps with ocassional timeouts in speedtest.net.

Heres the info of lshw:

*-network

    description: Wireless interface

    product: Intel Corporation

    vendor: Intel Corporation

    physical id: 0

    bus info: pci@0000:03:00.0

    logical name: wlp3s0

    version: 10

    serial: a0:af:bd:a3:ff:02

    width: 64 bits

    clock: 33MHz

    capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless

    configuration: broadcast=yes driver=iwlwifi driverversion=4.14.34-1-MANJARO firmware=29.610311.0 ip=192.168.1.102 latency=0 link=yes multicast=yes wireless=IEEE 802.11

    resources: irq:131 memory:b4000000-b4001fff

   

As you can see I have the firmware v29. So the fw is updated.

When I switch back to windows I get my full speed (1 mBps) so windows is unaffected.

I tried running another distro (Ubuntu 17.10) from a LiveUSB and there too the speeds are tremendously slow.

Now if I connect my phone to the same wifi, and use USB thethering to connect my laptop to the internet, the speed is what I expect (1mBps) which I think confirms that it is probably the linux driver thats having trouble.

My laptop is the Acer Aspire A515-51G having the 8th gen Intel i5.

I have also tried switching to another router and the speed is still slow. (~4kBps)

It's really frustrating to have to usb thether my phone every time I use the internet so I can even browse smoothly.

please tell me how can I go about solving this.. because on windows I have NO problems whatsoever. It's only linux distros causing issues.

Edit: Even pinging to my router is unrealisticly slow

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.

64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=4.60 ms

64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=1.47 ms

64 bytes from 192.168.1.1: icmp_seq=6 ttl=255 time=3.04 ms

64 bytes from 192.168.1.1: icmp_seq=7 ttl=255 time=1.43 ms

64 bytes from 192.168.1.1: icmp_seq=18 ttl=255 time=68.5 ms

64 bytes from 192.168.1.1: icmp_seq=19 ttl=255 time=2.46 ms

64 bytes from 192.168.1.1: icmp_seq=20 ttl=255 time=2.09 ms

64 bytes from 192.168.1.1: icmp_seq=21 ttl=255 time=1.98 ms

64 bytes from 192.168.1.1: icmp_seq=22 ttl=255 time=1.49 ms

64 bytes from 192.168.1.1: icmp_seq=23 ttl=255 time=1.48 ms

64 bytes from 192.168.1.1: icmp_seq=24 ttl=255 time=1.31 ms

64 bytes from 192.168.1.1: icmp_seq=25 ttl=255 time=1.43 ms

64 bytes from 192.168.1.1: icmp_seq=26 ttl=255 time=1.43 ms

64 bytes from 192.168.1.1: icmp_seq=32 ttl=255 time=63.3 ms

64 bytes from 192.168.1.1: icmp_seq=33 ttl=255 time=2.10 ms

64 bytes from 192.168.1.1: icmp_seq=34 ttl=255 time=1.28 ms

64 bytes from 192.168.1.1: icmp_seq=35 ttl=255 time=1.75 ms

64 bytes from 192.168.1.1: icmp_seq=36 ttl=255 time=1.13 ms

^C

--- 192.168.1.1 ping statistics ---

36 packets transmitted, 18 received, 50% packet loss, time 35276ms

rtt min/avg/max/mdev = 1.137/9.023/68.543/20.155 ms

Just see the delay and packet loss

Message was edited by: Rushab Shah

need proper settings and congiguration

I have just purchased a new X470 motherboard that features a built in Intel 9260, but upon installing the drivers I have disocdisco that it doesn't work properly. It will work for a split second then cut out, depending on the driver (Intel website or Gigabyte website) will BSOD with irql_not_less_or_equal from netwtw06. The event viewer spews out "network adapter returned a wrong value " then an attempt to reset the adapter. Are the latest drivers not compatible with Ryzen?

Hi I recently got an Intel Dual Band Wireless-AC 8265 and ever since I have used it my ping randomly spikes to 300-800 every now and then. eg

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=84ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=894ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=748ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=46ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=351ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=337ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=14ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=8ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=501ms TTL=51

Reply from 216.58.203.100: bytes=32 time=13ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=802ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=10ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=329ms TTL=51

Reply from 216.58.203.100: bytes=32 time=11ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=12ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=668ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=7ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=5ms TTL=51

Reply from 216.58.203.100: bytes=32 time=9ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Reply from 216.58.203.100: bytes=32 time=6ms TTL=51

Ping statistics for 216.58.203.100:

    Packets: Sent = 143, Received = 143, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 5ms, Maximum = 894ms, Average = 40ms

I have tried messing around with the adapter settings, I've uninstalled and reinstalled the drivers, I've downloaded the WLAN Optimizer to turn streaming mode on to stop scans for other networks and I've also tried the ScanWhenAssociated method in the registry. If anyone knows anything I can do I'd appreciate it.

Thanks

Installation Error - Intel PROSet Wireless Link Adapter Driver

My computer is trying to install software that keeps coming up with errors. Also restart and try again the installation runs again on error.

How do I get rid of the mistake?

I am trying to connect to two wireless networks simultaneously on one computer using two Dual Band Wireless-AC 8260 chipset PCI cards. Device manager shows that the driver for one card loads, but the second card returns a Code 31 error. ("This device is not working properly because Windows cannot load the drivers required for this device.") Is there a way to resolve this issue, or do I need to purchase a card with chips from one of Intel's competitors so that I don't need to load two copies of the same driver. Environment is as follows:

HP Compaq Elite 8200 CMT

Intel(R) Core(TM) i5 2400 CPU @ 3.10 GHz

Windows 7 Professional Service Pack 1 (64 bit)

Gigabyte WB-11ac dual band PCI card (Dual Band Wireless-AC 8260 chipset), Bluetooth connected via motherboard USB port and operational

ASUS PCE-AC55BT dual band PCI card (Dual Band Wireless-AC 8260 chipset), Bluetooth not connected to motherboard

Driver version 19.10.11.2

Thanks for any help you might be able to provide.

Hello team,

Apparently the current card Intel DB-AC 7260 which is installed in one of our industrial computers would connect only to A standard. If I Enable only G standard, the card does not see any network even though AP has A/B/G and N enabled. However, my cell phone and laptops around me, connect to N standard to the same AP with no issue.

These are the things I tried to do so far:

1. Changed antenna rubber dock 2.4GHz for flat 5GHz
2. Changed a port on the card from port 1 to 2 and back – no difference
3. Enabled only G standard for 802.11 a/b/g together with N standard for 802.11 n/ac – problems, cannot see any network
4. Enabled only A standard for 802.11 a/b/g together with N standard for 802.11 n/ac – got connection but unstable, ping jumps from 1ms to 300-400ms

Here are some screen shots of the problems:

I need to mentioned, unit hasn’t been moved around at all, it's placed on the desk.

Once Wireless mode is enabled on a/g standard together with N standard, with 2.4GHz rubber dock antenna, it connects again to A standard and pings are not stable. The signal jumps from 99% down to 79% and back to 99%.

If I connect flat 5GHz antenna, the card does not switch to N standard but stays on A – ping is stable.

here is the proof I have a latest drivers installed:

Thanks for the support!

thanks,

CommunityAdminintel_admin@

@

Intel Wireless Advanced-N 6230 possui driver para windows 10 64 bit?

I desperately need the driver for the Intel N 1030 Dual Band Wireless Adapter, which neither Dell nor Intel supports anymore. I find it very odd that there IS A DRIVER for the SINGLE Band N 1030 at Intel Support, updated August 2017. Why no Dual Band?

Suddenly, after six or seven years, I'm having a problem with Windows throwing Code 52 in Device Manager which refuses to install it. (Code 52: "Windows cannot verify the digital signature for the driverS required for this device. A recent hardware or software change [SUCH AS WINDOWS UPDATE???] might have installed a file that signed incorrectly or is damaged or that might be malicious software from an unknown source.")

I imagine the problem has to do with Windows security updates since this error started after an update.

I ran DriverEasy, which tried to install what it thinks ought to work and got BSOD. I tried it again, ready with camera this time for the BSOD, but it installed ok. Except that Windows says driver isn't for my system. It was version 15.something. My version, dated August 2011, is 14.2.0.10. It has worked since October 2011, when I got it with my Dell Inspiron N7110.

If you can help me out by providing access to the original driver (assuming its digital signature will be recognized by Windows) I'd be grateful.

Or if you can suggest how to get Windows to recognize as "legal" the digital signature that's been there for 6.5 years, that would be all around better.

I tried installing the driver from Intel Support for SINGLE Band N 1030 but it failed.

NOTE: I found detailed instructions about how to change WIndows to ignore problems with driver signatures, but the OS is Windows Home Premium--NOT Professional. It does not have much along the lines of admin capabilities--gpedit.msc is missing.

The only workaround I can find is to press F8 during boot and select the option that allows unsigned drivers. I have to remember to do this every time I reboot. But I hate to open this door to possible malicious drivers being installed. So a terrible workaround, but without it, I have no wireless.

Dave Slomer

Hello,

I have an Inspiron i5577 with AC-3165 w/BT. For a long time now, sometimes when I rewind a video on Firefox or Chrome, on any website, with a fresh Windows 10 installation, the video and audio becomes choppy. Imagine looking at a video that only plays 1 Frame Per Second. It plays for quarter of a second, stops, plays again, stops, etc. Once the stutter begins, every sound played through other sources such as local MP3 or Windows notification sound also stutter.

If I rewind videos on a local MP4 file it never starts stuttering. It never starts stuttering with wired earphones. The stutter is always initiated when changing a video playback position on the browser. The more frequently I change the position, the more likely it stutters. Sometimes it stutters only for a second after rewinding but continues to play. When this initial one-time stutter happens, it always starts stuttering permanently after subsequent rewinding. Rewind once - it stutters once but plays fine. Rewind again - it stutters forever.

I have tested it with two BT headsets manufactured by different companies, as well as on two web browsers. The problem is with the Bluetooth adapter or drivers.

I have followed Mr. Carlos A.'s advice to reinstall WiFi and BT adapters but that hasn't solved it-3165 Bluetooth cuts of minus of a second that affects all devices connected. Dell Inspiron 7000 17" on W10. I've done… (tried Dell's WiFi/BT drivers too).

To temporarily fix the problem I disable and re-enable the BT adapter. The BT headphone automatically pairs and it plays fine after the reset. Sometimes the stutter happens multiple times in 10 minutes, sometimes once an hour. It makes media consumption through BT highly unpleasant.

I've attached Intel System utility log to this thread with a hope that someone can help troubleshoot it. I'm willing to go through technical steps. Thanks in advance!

EDIT:  Here is a more detailed look at the problem. Open a YouTube video and play. Click on a rewind bar to skip ahead. Do it again. It starts stuttering. Click on Windows 10 notification button (bottom-right corner of taskbar) and from the action panel click on the Bluetooth card twice to disable and re-enable. Once the Bluetooth is disabled, what surprises me is that the video automatically stops. If I try to rewind the video while BT is being reset, it won't play. The video starts playing automatically on its own once the BT finishes resetting and pairs the BT headset. As soon as its automatically paired the video resumes with a proper sound.

Since the most recent Microsoft update, my bluetooth has not been working. In "Devices" and under "Bluetooth", the message says that, "bluetooth is turned off." When I try to turn it on, I get this message

This device cannot start. (Code 10)

STATUS_DEVICE_POWER_FAILURE

I've tried multiple troubleshooting methods, uninstalling and reinstalling, and even downloaded the Intel Driver and Support Assistant Installer and am still having this issue.

Hi there

     We are trying to deploy a new wireless profile using TLS and Machine Certificates settings. However, our users cannot import these profiles without running the Intel Proset apps as an administrator. The apps will hang in the process. Dropping the exported profile into the AutoImport also failed. The autoimport log stated that "this settings is only available to administrators......" Had anyone ran into this problem? Thanks