Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, June 17, 2016 2:30 AM | 1 vote
Hi,
I have deployed a customised image of Windows 10.0.10586 using Microsoft System Center Configuration Manager to a Dell Latitude E7450, and it is now showing that the "Wi-Fi Driver" does not support "Wireless Display".
Display Adapter: Intel HD Graphics 5500
Wireless Adapter: Intel Dual Band Wireless-AC 7265
I've installed the latest version of the driver from Dell's web site, Network_Driver_PX32H_WN32_18.40.0.9_A19, and that hasn't changed anything.
I've grabbed a second Dell Latitude E7450 and performed a clean install of Windows 10.0.10586, and straight away that show's that it does support Wireless Display, even with the default wireless driver. I've then updated the driver as above and it continues to report as supported.
As part of my troubleshooting, I've removed the Graphics and Network drivers with the delete driver option ticked, which hasn't resolved the issue.
The only difference I've seen so far is the on the machine where wireless display is not working the "Microsoft Wi-Fi Direct Virtual Adapter" is showing in device manager as "Not Connected (Code 45)".
netsh wlan sho d output below:
Custom W10 Image
Interface name: Wi-Fi
Driver : Intel(R) Dual Band Wireless-AC 7265
Vendor : Intel Corporation
Provider : Intel
Date : 25/02/2016
Version : 18.40.0.9
INF file : C:\WINDOWS\INF\oem152.inf
Files : 2 total
C:\WINDOWS\system32\DRIVERS\Netwtw04.sys
C:\WINDOWS\system32\DRIVERS\Netwfw04.dat
Type : Native Wi-Fi Driver
Radio types supported : 802.11b 802.11g 802.11n 802.11a 802.11ac
FIPS 140-2 mode supported : Yes
802.11w Management Frame Protection supported : Yes
Hosted network supported : No
Authentication and cipher supported in infrastructure mode:
Open None
Open WEP-40bit
Open WEP-104bit
Open WEP
WPA-Enterprise TKIP
WPA-Enterprise CCMP
WPA-Personal TKIP
WPA-Personal CCMP
WPA2-Enterprise TKIP
WPA2-Enterprise CCMP
WPA2-Personal TKIP
WPA2-Personal CCMP
Open Vendor defined
Vendor defined Vendor defined
IHV service present : Yes
IHV adapter OUI : [00 80 86], type: [00]
IHV extensibility DLL path: C:\WINDOWS\System32\IWMSSvc.dll
IHV UI extensibility ClSID: {1bf6cb2d-2ae0-4879-a7aa-a75834fbd0e3}
IHV diagnostics CLSID : {00000000-0000-0000-0000-000000000000}
** Wireless Display Supported: No (Graphics Driver: Yes, Wi-Fi Driver: No)**
Clean W10 Image
Interface name: Wi-Fi
Driver : Intel(R) Dual Band Wireless-AC 7265
Vendor : Intel Corporation
Provider : Intel
Date : 25/02/2016
Version : 18.40.0.9
INF file : C:\Windows\INF\oem23.inf
Files : 2 total
C:\Windows\system32\DRIVERS\Netwtw04.sys
C:\Windows\system32\DRIVERS\Netwfw04.dat
Type : Native Wi-Fi Driver
Radio types supported : 802.11b 802.11g 802.11n 802.11a 802.11ac
FIPS 140-2 mode supported : Yes
802.11w Management Frame Protection supported : Yes
Hosted network supported : No
Authentication and cipher supported in infrastructure mode:
Open None
Open WEP-40bit
Open WEP-104bit
Open WEP
WPA-Enterprise TKIP
WPA-Enterprise CCMP
WPA-Personal TKIP
WPA-Personal CCMP
WPA2-Enterprise TKIP
WPA2-Enterprise CCMP
WPA2-Personal TKIP
WPA2-Personal CCMP
Open Vendor defined
Vendor defined Vendor defined
IHV service present : Yes
IHV adapter OUI : [00 80 86], type: [00]
IHV extensibility DLL path: C:\Windows\System32\IWMSSvc.dll
IHV UI extensibility ClSID: {1bf6cb2d-2ae0-4879-a7aa-a75834fbd0e3}
IHV diagnostics CLSID : {00000000-0000-0000-0000-000000000000}
** Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)**
What am I missing, why isn't the custom image supporting Wireless Display???
During my testing of removing drivers, the Microsoft Wi-Fi Direct Virtual Adapter device has been removed altogether, how can i re-add this device?
All replies (3)
Tuesday, July 5, 2016 3:05 AM ✅Answered | 1 vote
Turns out it was a policy setting.
Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) Policies
"The policy we were using to configure our wireless for our production network was an "XP" policy. I recreated the connection policy as a "Policy for Windows Vista and Later Releases".
The setting to pay attention to is on the "Network Permissions" tab: "Don't allow Wi-Fi Direct groups". selecting that option prevents the machine from connecting to Wi-Fi Direct devices such as the Miracast."
Monday, June 20, 2016 8:15 AM
Hi,
Make sure you also installed WiDi utility:
**File Name: **Network_Utility_16R05_WN32_6.0.40.0_A00.EXE
Importance: Recommended
Description: Update Package for Microsoft® Windows® (121.84 MB)
Release Date: 29 Jul 2015
Version: 6.0.40.0 ,A00
Last Updated: 16 Oct 2015
Download Add to My Download List-#1
Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact [email protected]
Wednesday, November 22, 2017 5:28 PM | 1 vote
I have this same issue, and every article I can find suggests this was the issue and I did have an XP policy, but after converting it to a Vista or later policy and changing the "don't allow Wi-Fi direct groups" to not be set I still have the same issue. It appears that the group policy isn't blocking computers from using Wi-Fi direct anymore, but it didn't allow Wi-Fi direct on computers that had the old group policy applied at one time.
For example, I can disjoin a computer from our domain and it will start working, but if I add it back to the domain it will continue working! In other words the group policy isn't breaking this feature for computers anymore, but it also isn't fixing computers that were previously broken...
Anyone know what regkey or how to force the setting to "allow" rather than "not deny"?