We understand you're having issues sharing your display wirelessly using Miracast* ever since updating your OS to the Fall Creators Update.
Please keep in mind that while our adapter supports Miracast*, this feature does not receive direct support from our end. However, we will do our best to help you troubleshoot and hopefully identify the source of the problem.
In order to better assist you, we would like to get the following:
- Please generate an Intel® System Support Utility report.
- Download and run the Intel® System Support Utility.
- Select to scan "everything," and run the scan while connected to your wireless network (if possible).
- Choose next one more time to save the report.
- Please share your Dxdiag report.
- In the search box on the taskbar, type DXDIAG and run it. This will open the DirectX Diagnostic Tool.
- At the bottom of the window, select "Save All Information..."
- Please save both reports and attach them to your reply.
Note: To enable attachments, make sure to switch to the advanced editor while replying.
We look forward to hearing back from you.
- Please generate an Intel® System Support Utility report.
Thank you for providing the reports requested. Not to worry, we didn't need any of the things you may have sanitized, only your system configuration, driver versions, and such.
Based on these logs, it seems the problem may have to do with your graphics driver:
We can recommend trying the latest system specific driver provided by your computer manufacturer, they seem to have posted one specially for Windows® 10 Fall Creators Update (RS3). Although it may be worth mentioning that this seems to be a version older than the one you have currently installed (I could be wrong, not my area).
NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.
You may also update your Intel® HD Graphics 630, although this may have no effect on this particular issue.
Please let us know if this helps.
Please note your 'correct answer' is NOT the correct answer.
The Radeon gfx is never touched when Mircast is used, FYI. It's ONLY using the Intel Wireless and Intel graphics chipsets. I went ahead and updated to the latest AMD Radeon drivers as the new releases were out, but as expected, no change.
According to the Intel website and auto update utility, everything is up to date.
According to Microsoft, Windows is up to date (an update even applied over the weekend).
While I see how easy it would be to default to AMD being the issue with Miracast supported not being indicated let me reiterate again that MIRACAST DOES NOT TOUCH THE AMD DISCRETE GRAPHICS ON THIS SYSTEM.
Can Intel please verify that the AC 7265 and Intel 630 graphics drivers are actually up to date? Have you checked with Microsoft to ensure that there aren't and recent changes (and considering again that this issue started with updates in December specifically) that Intel needs to get on board with in this case?
We understand your frustration. However, please remember that Miracast* is not our product, and has no direct support from Intel®. In this case, your computer manufacturer should be your primary source of support.
Upon further review, we noticed that both the SSU and the DxDiag reports show that you're currently using Windows® 10 RS2 (Creators Update, build 15063, version 1703), not Fall Creators Update (build 16299, version 1709). Could you please confirm, or update your OS to the latest build and let us know if the issue persists?
Also, do you have any other Miracast* capable PCs you could try to connect to your TV and/or the MS Display Adapter to confirm they aren't the problem?
I know it may seem unlikely that two separate devices are having issues, but this is how troubleshooting goes.
As an extra mile, I've managed to secure a test laptop from HP* which also uses the Intel® Dual Band Wireless-AC 7265 as your all in one. This system already had a newer version of Windows* than the one shown in the logs you've shared, so I'm currently reinstalling the OS to match the same build that you're using and should be able to test it by tomorrow. We don't have Samsung* TV nor a Microsoft* Display Adapter, but we do have a Miracast* receiver which should be close enough for us to validate or discard driver issues.
We'll post an update on this as soon as we can.
Apologies if I was cranky.
I definitely appreciate that extra mile.
Good to know it's not something with the wireless chipset then.
Hmmm. I'm trying to get a hold of HP tech support, but looks they may be running a skeleton crew this week. Waited from about 8am until 6:45pm before someone picked up. Forgot I had the chat window open and came back in this morning and saw they suggested rolling back Windows for testing, LOL. We know it works before the December patches get applied, so it's sort of a moot point.
It's possibly the fall creators update fixes something. Some of that is eeking into the business channel which is what we are on. I may try doing the FCU tomorrow on one of the desktops to see how it goes. If it fixes something that'd be great.
Oh don't worry, nothing to apologize for.
You're correct. Looking further into this issue I found that your discreet graphics driver doesn't support Miracast*, because as you mentioned, it doesn't need to. That should not affect your ability to cast your screen.
The overall takeaway from your DxDiag log is that your system does support Miracast* with High-bandwidth Digital Content Protection (HDCP). Meaning it should work.
In our lab we had no issues connecting to our wireless display with Windows® Creators Update (RS2), nor Fall Creators Update (RS3).
You may need to check to see if there is a Group Policy or Firewall Rule that may preventing your system from sharing your display. While looking for the exact steps, I ran into an article covering this completely (you may need to copy and paste the URL if the link is still blocked by our WIP-whitelist): http://fmtrout.com/resolving-issues-with-miracast-in-windows-10-on-a-domain/
Note: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there.
Let us know if any of this helps resolve the issue.
This is great news, we're very glad to hear.
If the update doesn't fix the other systems, don't hesitate to let us know.