Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
7428 Discussions

Wireless-AC 7265 Windows 10 driver problems (18.33.0.2)

KWong21
Beginner
‎06-05-2016 09:27 PM
14,255 Views

Driver version:

18.33.0.2 installed via Intel driver update utility

Driver date:

28th January 2016

Problem description:

1.) Using the "Connect" feature of Windows 10 to Microsoft wireless display adapter doesn't work, tested devices with other Wi-Fi modules, no problem:

https://www.microsoft.com/surface/en-us/accessories/wireless-display-adapter-2 Microsoft Wireless Display Adapter

2.) WiDi doesn't work either, connecting to a WiDi certified receiver: the Microsoft Wirless Display Adapter, same as above.

The Wireless Display Adapter uses Wi-Fi CERTIFIED™ Miracast® technology, so you're not limited to certain apps or content streaming; you can display everything from your device on an HDTV or monitor. The Wireless Display Adapter is also an Intel® Wireless Display (WiDi) certified adapter and works with 2-in-1s and tablet devices with Intel WiDi capability.

3.) Bluetooth mouse stopped working for a while from time to time, for about 10 seconds, and then come back, which never happened before.

Preview file
46 KB
0 Kudos

Link Copied

66 Replies
idata
Employee
‎07-20-2016 10:37 AM
1,872 Views
In response to idata

kenostephen,

 

 

It is important to try this through a clean installation. Please, as soon as you, could you please provide the run-time logs and the logs provide by the https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility Intel® System Support Utility

 

 

The instructions to collect the run-time logs on Windows®10 is on post number 34.

 

Are you part of the same IT team that mrtnjgr is part of?

 

 

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
MJäge
Beginner
‎07-20-2016 10:53 PM
1,872 Views
In response to idata

Hello Aleki,

is there a way to share these logs privately? I don't feel comfortable with putting potentially sensitive log files on a public forum.

And no, kenofstephen and I don't know each other.

Martin

In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎07-20-2016 11:35 PM
1,872 Views
In response to idata

Hi Aleki,

I've tried to uninstall the device and remove its driver and then re-install the driver packge,

however it gave the same result - driver version 18.33.3.2

In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎07-20-2016 11:37 PM
1,872 Views
In response to idata

I don't know Martin...

And please read the release note in the link you sent me, it says 18.33.3.2 for 7265...so no update at all...

Software and drivers:

Intel® PROSet/Wireless WiFi Software (includes Drivers): Wireless_19.0.1_PROSet32_Win10.exe and Wireless_19.0.1_PROSet64_Win10.exe

Note:

Intel® PROSet software version = 19.0.1

  • Driver version = 19.0.1.1 for Windows® 10 for 3168, 18260, 8260, 3165, and 17265 adapters.
  • Driver version = 18.33.3.2 for Windows® 10 for 7265, 3160, and 7260 adapters.
In response to idata
0 Kudos
Copy link
idata
Employee
‎07-21-2016 08:21 AM
1,872 Views
In response to idata

Martin,

 

 

Yes there is a way. Could you please check your private messages?

 

 

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
idata
Employee
‎07-21-2016 08:25 AM
1,872 Views
In response to idata

kenofstephen,

 

 

As soon as you can please send the logs requested so we can take a look.

 

 

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎07-24-2016 08:21 PM
1,872 Views
In response to idata

Hi Aleki,

I replied you before,

1. C:\Users\\AppData\Local\Temp\micl_tmp*.

a. This is actually a directory with a name that starts with micl_tmp. Please zip up the entire directory and send it.

For 1.), such directory doesn't exist in my system, so I couldn't give you anything. I've explained to you last time with almost the same screenshot.

2. C:\temp\WiDiLog_CompatibilityTool*.wdl

This this could be a single file or multiple files ending in .wdl. The tool creates a new log file every time you run it.

For 2.), this has been provided to you last time.

In response to idata
Preview file
104 KB
0 Kudos
Copy link
KWong21
Beginner
‎06-19-2016 11:40 PM
2,243 Views

Preview file
95 KB
0 Kudos
Copy link
KWong21
Beginner
‎07-24-2016 08:32 PM
1,872 Views

However, I've found another log which might show the problem:

FIRST:

I got this failed log yesterday:

14:10:12:048,[t:0x3d24] : RequestBustoLoadVAD - LoadVad:Unplug failed: 0x57

[L=3][M=SmartAgent][F=enum_bus.cpp: 520]

14:10:12:048,[t:0x3d24] : Closing VAD BUS Driver handle [L=7][M=SmartAgent][F=enum_bus.cpp: 562]

14:10:12:048,[t:0x3d24] : MS: End VAD Unload [L=6][M=SmartAgent][F=enum_bus.cpp: 114]

14:10:12:049,[t:0x3d24] : LoadVAD VAD Unload: Failed [L=3][M=SmartAgent][F=enum_bus.cpp: 118]

14:10:12:049,[t:0x3d24] : <<[LoadVAD] [L=7][M=SmartAgent][F=enum_bus.cpp: 93]

10:12:57:215,[t:0x408c] : Log Server started by C:\Program Files\Intel Corporation\Intel WiDi\WiDiApp.exe [L=6][M=LogServer][F=LogServer.cpp: 224]

10:12:57:217,[t:0x408c] : Logger started [L=6][M=WIDIAPP][F=App.xaml.cs: 137]

10:12:57:222,[t:0x408c] : CWiDiSmartAgentClassFactory::CWiDiSmartAgentClassFactory - DLL ref count = 1 [L=7][M=SmartAgent][F=ClassFactory.cpp: 44]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::AddRef - new ref count = 1 [L=7][M=SmartAgent][F=ClassFactory.cpp: 60]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface [L=7][M=SmartAgent][F=ClassFactory.cpp: 81]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface - Client QIed for IClassFactory [L=7][M=SmartAgent][F=ClassFactory.cpp: 102]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::AddRef - new ref count = 2 [L=7][M=SmartAgent][F=ClassFactory.cpp: 60]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::Release - new ref count = 1 [L=7][M=SmartAgent][F=ClassFactory.cpp: 69]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::AddRef - new ref count = 2 [L=7][M=SmartAgent][F=ClassFactory.cpp: 60]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::Release - new ref count = 1 [L=7][M=SmartAgent][F=ClassFactory.cpp: 69]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface [L=7][M=SmartAgent][F=ClassFactory.cpp: 81]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface - Client QIed for IClassFactory [L=7][M=SmartAgent][F=ClassFactory.cpp: 102]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::AddRef - new ref count = 2 [L=7][M=SmartAgent][F=ClassFactory.cpp: 60]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::Release - new ref count = 1 [L=7][M=SmartAgent][F=ClassFactory.cpp: 69]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface [L=7][M=SmartAgent][F=ClassFactory.cpp: 81]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::QueryInterface - Client QIed for unsupported interface [L=7][M=SmartAgent][F=ClassFactory.cpp: 107]

10:12:57:223,[t:0x408c] : CWiDiSmartAgentClassFactory::CreateInstance [L=7][M=SmartAgent][F=ClassFactory.cpp: 131]

10:12:57:225,[t:0x408c] : >>[CUIBCServer::CUIBCServer] [L=7][M=UIBCserver][F=UIBCServer.cpp: 31]

10:12:57:225,[t:0x408c] : <<[CUIBCServer::CUIBCServer] [L=7][M=UIBCserver][F=UIBCServer.cpp: 31]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - Installed WiDi found: C:\Program Files\Intel Corporation\Intel WiDi [L=7][M=SmartAgent][F=PlatformReport.cpp: 407]

10:12:57:226,[t:0x408c] : GetFileVersion C:\Program Files\Intel Corporation\Intel WiDi\WiDiSmartAgent.dll Version 6.0.66.0 [L=7][M=SmartAgent][F=PlatformReport.cpp: 261]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - Installed WiDiSmartAgent version: 6.0.66.0 [L=7][M=SmartAgent][F=PlatformReport.cpp: 410]

10:12:57:226,[t:0x408c] : GetFileVersion C:\Program Files\Intel Corporation\Intel WiDi\WiDiApp.exe Version 6.0.749.0 [L=7][M=SmartAgent][F=PlatformReport.cpp: 261]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - Installed WiDiApp version: 6.0.749.0 [L=7][M=SmartAgent][F=PlatformReport.cpp: 413]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - PDL VERSION_STRING = 6.0.66.0 [L=7][M=SmartAgent][F=PlatformReport.cpp: 416]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - PDL WIDI_COMPANY_NAME = Intel Corporation [L=7][M=SmartAgent][F=PlatformReport.cpp: 417]

10:12:57:226,[t:0x408c] : LOGWiDiVersion - PDL WIDI_COPYRIGHT_STRING = Copyright © 2010-2015, Intel Corporation. All rights reserved. [L=7][M=SmartAgent][F=PlatformReport.cpp: 418]

10:12:57:226,[t:0x408c] : getInstalledIUMVersion - IUM not installed [L=7][M=SmartAgent][F=PlatformReport.cpp: 392]

SECOND:

Can't connect to Microsoft Wireless Display adapter, with this log looping forever:

11:26:51:993,[t:0x2bb0] : >>[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:26:51:993,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - Number of WLAN interfaces = 1 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3133]

11:26:51:993,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - WLAN Interface Name[0] = Intel(R) Dual Band Wireless-AC 7265 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3146]

11:26:51:993,[t:0x2bb0] : <<[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:26:52:630,[t:0x37ec] : WlanTestNotification Handler : non msm message received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3258]

11:26:52:631,[t:0x37ec] : WlanTestNotification Handler : non msm message received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3258]

11:26:54:631,[t:0x2bb0] : >>[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:26:54:631,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - Number of WLAN interfaces = 1 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3133]

11:26:54:631,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - WLAN Interface Name[0] = Intel(R) Dual Band Wireless-AC 7265 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3146]

11:26:54:631,[t:0x2bb0] : <<[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:26:57:849,[t:0x37ec] : WlanTestNotification Handler : non msm message received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3258]

11:26:57:849,[t:0x37ec] : WlanTestNotification Handler : non msm message received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3258]

11:26:59:854,[t:0x2bb0] : >>[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:26:59:854,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - Number of WLAN interfaces = 1 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3133]

11:26:59:854,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - WLAN Interface Name[0] = Intel(R) Dual Band Wireless-AC 7265 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3146]

11:26:59:854,[t:0x2bb0] : <<[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:27:06:098,[t:0x37ec] : WlanTestNotification Handler : wlan_notification_acm_scan_complete received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3290]

11:27:08:100,[t:0x2bb0] : >>[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:27:08:100,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - Number of WLAN interfaces = 1 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3133]

11:27:08:100,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - WLAN Interface Name[0] = Intel(R) Dual Band Wireless-AC 7265 [L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3146]

11:27:08:100,[t:0x2bb0] : <<[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:27:10:705,[t:0x37ec] : WlanTestNotification Handler : wlan_notification_acm_scan_complete received

[L=6][M=SmartAgent][F=WiDiSmartAgent.cpp: 3290]

11:27:12:694,[t:0x2bb0] : >>[CWiDiSmartAgent::CheckWlanSwitch] [L=7][M=SmartAgent][F=WiDiSmartAgent.cpp: 3119]

11:27:12:694,[t:0x2bb0] : CWiDiSmartAgent::CheckWlanSwitch - Number of WLAN interfaces = 1 [L=6][M...

0 Kudos
Copy link
KWong21
Beginner
‎07-24-2016 11:18 PM
1,872 Views

I wouldn't say it's the adapter's problem since it works perfectly fine with my MacBook with Windows 10 installed.

Firmware of the Microsoft Wireless Adapter V2 is the latest.

Preview file
1286 KB
0 Kudos
Copy link
idata
Employee
‎07-25-2016 01:14 PM
1,872 Views
In response to KWong21

kenofstephen,

 

 

As we have informed before. It may be related to compatibility with the NUC you have informed previously. We are going to take a look at the logs and will get back to you soon.

 

 

Best regards,

 

Aleki
In response to KWong21
0 Kudos
Copy link
KWong21
Beginner
‎07-25-2016 11:58 PM
1,872 Views
In response to idata

I believe Intel Broadwell-U is a very, very, very common platform.

In response to idata
0 Kudos
Copy link
idata
Employee
‎07-26-2016 03:24 PM
1,872 Views
In response to idata

knofstphen,

 

 

The http://ark.intel.com/products/85214/Intel-Core-i7-5500U-Processor-4M-Cache-up-to-3_00-GHz Intel® Core™ i7-5500U Processor is compatible with Intel® WiDi as well as the Intel® Wireless Adapter you have. Other users have confirmed that these devices work well with Intel® WiDi and Miracast*. Please engage Gigabyte* and order to obtain additional support.

 

 

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎07-27-2016 01:21 AM
1,872 Views
In response to idata

I did as per your request before, they replied me their platform support WiDi and tested OK with the Intel AC3165 card.

So, it's not the platform issue.

In response to idata
0 Kudos
Copy link
idata
Employee
‎07-27-2016 02:31 PM
1,872 Views
In response to idata

kenofstephen,

We are going to engage additional resources to help you with whatever is within our reach. In order to do so, we need you to send us the most recent following logs considering the driver update you did recently. Please send us as an independent file (attachment) here.

1. Run-time logs

 

The WiDi compatibility tool creates 2 sets of log files. They are located in different directories.

 

1. C:\Users\\AppData\Local\Temp\micl_tmp*.

 

a. This is actually a directory with a name that starts with micl_tmp. Please zip up the entire directory and send it.

 

2. C:\temp\WiDiLog_CompatibilityTool*.wdl

 

This this could be a single file or multiple files ending in .wdl. The tool creates a new log file every time you run it.

3. SSU Logs

 

Use this tool to collect this information: https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility Intel® System Support Utility

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎08-01-2016 01:05 AM
1,872 Views
In response to idata

I replied you above with screenshot showing you that the said folder doesn't even exist!

Why don't you believe me?

In response to idata
0 Kudos
Copy link
idata
Employee
‎08-01-2016 08:49 AM
1,872 Views
In response to idata

kenofstephen,

If the folder for the runtime logs is not available, please don't worry, just send us the logs generated by the SSU and send us here. If possible run the http://www.intel.com/content/www/us/en/support/emerging-technologies/000014931.html Intel® WiDi Compatibility Tool and send us the information it will provide you as well.

Best regards,

 

Aleki
In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎08-07-2016 09:06 PM
1,872 Views
In response to idata

Hi Aleki,

I'm reporting back that after updated Windows 10 to the Anniversary Edition (Version 1607),

the wireless connection works 100% fine.

Maybe Microsoft fixed something with you guys, anyway, thanks.

Regards,

Ken

In response to idata
0 Kudos
Copy link
idata
Employee
‎08-08-2016 04:13 PM
1,843 Views
In response to idata

Hello kenofstephen,

 

 

We are glad to know that your system is working fine now.

 

 

The latest Windows® 10 update contains changes for its built-in Miracast* functionality that impact Intel® WiDi. As a result, Intel® WiDi is no longer required (and actually is incompatible with the new Windows® version).

 

 

The OS Miracast* functionality will continue to be used to connect with wireless display receivers.

 

 

Regards,

 

 

Jonathan.
In response to idata
0 Kudos
Copy link
KWong21
Beginner
‎08-08-2016 10:59 PM
1,843 Views
In response to idata

Hi Aleki,

But I'm still seeing this pop up message when connected?

And I saw this:

http://www.intel.com/content/www/us/en/architecture-and-technology/widi-pro-widi-discontinued-notice.html Intel® WiDi and Intel® Pro WiDi Applications Discontinued Notice

In response to idata
Preview file
12 KB
0 Kudos
Copy link
idata
Employee
‎08-09-2016 04:32 PM
1,843 Views
In response to idata

Hello,

 

 

You can remove Intel® WiDi from Windows Control Panel, Uninstall Programs.

 

The message will stop after this.
In response to idata
0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.