Miracast no longer working on Windows 10 laptopHow to troubleshoot miracast on windows 10 laptop?How...

Extract rows of a table, that include less than x NULLs

How to show a landlord what we have in savings?

How to tell a function to use the default argument values?

Mathematica command that allows it to read my intentions

How do I deal with an unproductive colleague in a small company?

How to prevent "they're falling in love" trope

Arrow those variables!

Why does this cyclic subgroup have only 4 subgroups?

How do conventional missiles fly?

If human space travel is limited by the G force vulnerability, is there a way to counter G forces?

Can the Meissner effect explain very large floating structures?

Intersection Puzzle

Size of subfigure fitting its content (tikzpicture)

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

Is there a hemisphere-neutral way of specifying a season?

Im going to France and my passport expires June 19th

Which is the best way to check return result?

How does a predictive coding aid in lossless compression?

Plagiarism or not?

Can a virus destroy the BIOS of a modern computer?

Ambiguity in the definition of entropy

Is it inappropriate for a student to attend their mentor's dissertation defense?

How do I handle a potential work/personal life conflict as the manager of one of my friends?

Valid term from quadratic sequence?



Miracast no longer working on Windows 10 laptop


How to troubleshoot miracast on windows 10 laptop?How uninstall Win 10 update? (it broke my miracast)Connecting Windows PC to Microsoft Wireless Display Adapter (Miracast)AMD graphic card not working after upgrading to Windows 8.1 on a Dell 3521How to get Miracast working with Sitecom WLA 7100How to connect Anycast M2 Plus RK2928 using Intel WiDi to Windows 7 laptopGraphics card in laptop not workingConnection to 5ghz network has no internet for supporting wireless cardWhat do I need to project my Windows 10 PC screen on my HDTV?Remote desktop (VNC/RDP) VS Miracast/WiDIMiracast connection error after joining ad domainCannot mirror my laptop (windows 10) to Panasonic Smart Viera TV TX-32FS500B













10















I have a Dell Inspiron 17 5748 running Windows 10 1709 (Fall Creators Update). A good year ago I was able to wirelessly duplicate my laptop's screen to a Samsung UE40J6200 TV. I remember having to install an Intel wireless card and the need to install a piece of software called Intel WiDi to make it work.



I didn't use the functionality for a while and have reinstalled Windows 10 on that laptop since. I looked for the WiDi drivers and found that Intel has discontinued the product saying that Windows now has good Miracast support that can be used instead. The additional bonus would be that an Intel wireless card is no longer required.



Unfortunately I haven't been able to use it with this laptop since then. Whenever I put my TV in the "screen mirroring" mode, the laptop is able to see the TV when choosing the function to connect to a wireless display. The laptop seems to be able to connect and usually the TV will show the laptop's display for about 5 seconds before the image either freezes or the connection is dropped.



What I have tried so far:




  • Updated wireless card drivers to latest version

  • Updated graphics card drivers to the latest version on the Dell website

  • Updated graphics card drivers to the latest version from Intel (using a manual installation option because apparently Dell blocks the installation of the generic Intel drivers now)

  • Tried a different Windows 10 machine (a Cherrytrail tablet with a Realtek wireless card. This works fine although the tablet doesn't have the latest Windows updates)

  • Tried a Windows 10 Mobile device. This works fine.

  • Verified that the driver and hardware supports a wireless display using dxdiag (using these instructions: How to check if your PC supports Miracast

  • Verified that the system supports a wireless display using an alternate method (netsh wlan sho d command in a command prompt)

  • Connected laptop and TV to my 2.4GHz wireless network instead of having the laptop on the 5GHz network and the TV connected with a wire (this shouldn't matter as Miracast uses WiFi Direct)


I'm now at my wits end as to what I can try next. Google tells me many people complain about Miracast being broken after certain Windows 10 updates but there is never a definite solution available.



The relevant hardware:




  • Core i5 5200U with Intel HD Graphics 5500

  • Intel AC7265 wireless card

  • Samsung UE40J6200 TV

  • Wireless network running on my provider's router (5GHz 802.11AC with a 40MHz wide channel on free channels, 2.4GHz 802.11N with a 20MHz channel and having interference from neighbor's access points)










share|improve this question

























  • Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

    – harrymc
    Feb 21 '18 at 15:55











  • @harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

    – AdmiralFreebee
    Feb 21 '18 at 21:25











  • If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

    – harrymc
    Feb 21 '18 at 21:29











  • @harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

    – AdmiralFreebee
    Feb 22 '18 at 9:39











  • What is your graphics card ?

    – harrymc
    Feb 23 '18 at 12:10
















10















I have a Dell Inspiron 17 5748 running Windows 10 1709 (Fall Creators Update). A good year ago I was able to wirelessly duplicate my laptop's screen to a Samsung UE40J6200 TV. I remember having to install an Intel wireless card and the need to install a piece of software called Intel WiDi to make it work.



I didn't use the functionality for a while and have reinstalled Windows 10 on that laptop since. I looked for the WiDi drivers and found that Intel has discontinued the product saying that Windows now has good Miracast support that can be used instead. The additional bonus would be that an Intel wireless card is no longer required.



Unfortunately I haven't been able to use it with this laptop since then. Whenever I put my TV in the "screen mirroring" mode, the laptop is able to see the TV when choosing the function to connect to a wireless display. The laptop seems to be able to connect and usually the TV will show the laptop's display for about 5 seconds before the image either freezes or the connection is dropped.



What I have tried so far:




  • Updated wireless card drivers to latest version

  • Updated graphics card drivers to the latest version on the Dell website

  • Updated graphics card drivers to the latest version from Intel (using a manual installation option because apparently Dell blocks the installation of the generic Intel drivers now)

  • Tried a different Windows 10 machine (a Cherrytrail tablet with a Realtek wireless card. This works fine although the tablet doesn't have the latest Windows updates)

  • Tried a Windows 10 Mobile device. This works fine.

  • Verified that the driver and hardware supports a wireless display using dxdiag (using these instructions: How to check if your PC supports Miracast

  • Verified that the system supports a wireless display using an alternate method (netsh wlan sho d command in a command prompt)

  • Connected laptop and TV to my 2.4GHz wireless network instead of having the laptop on the 5GHz network and the TV connected with a wire (this shouldn't matter as Miracast uses WiFi Direct)


I'm now at my wits end as to what I can try next. Google tells me many people complain about Miracast being broken after certain Windows 10 updates but there is never a definite solution available.



The relevant hardware:




  • Core i5 5200U with Intel HD Graphics 5500

  • Intel AC7265 wireless card

  • Samsung UE40J6200 TV

  • Wireless network running on my provider's router (5GHz 802.11AC with a 40MHz wide channel on free channels, 2.4GHz 802.11N with a 20MHz channel and having interference from neighbor's access points)










share|improve this question

























  • Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

    – harrymc
    Feb 21 '18 at 15:55











  • @harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

    – AdmiralFreebee
    Feb 21 '18 at 21:25











  • If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

    – harrymc
    Feb 21 '18 at 21:29











  • @harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

    – AdmiralFreebee
    Feb 22 '18 at 9:39











  • What is your graphics card ?

    – harrymc
    Feb 23 '18 at 12:10














10












10








10


1






I have a Dell Inspiron 17 5748 running Windows 10 1709 (Fall Creators Update). A good year ago I was able to wirelessly duplicate my laptop's screen to a Samsung UE40J6200 TV. I remember having to install an Intel wireless card and the need to install a piece of software called Intel WiDi to make it work.



I didn't use the functionality for a while and have reinstalled Windows 10 on that laptop since. I looked for the WiDi drivers and found that Intel has discontinued the product saying that Windows now has good Miracast support that can be used instead. The additional bonus would be that an Intel wireless card is no longer required.



Unfortunately I haven't been able to use it with this laptop since then. Whenever I put my TV in the "screen mirroring" mode, the laptop is able to see the TV when choosing the function to connect to a wireless display. The laptop seems to be able to connect and usually the TV will show the laptop's display for about 5 seconds before the image either freezes or the connection is dropped.



What I have tried so far:




  • Updated wireless card drivers to latest version

  • Updated graphics card drivers to the latest version on the Dell website

  • Updated graphics card drivers to the latest version from Intel (using a manual installation option because apparently Dell blocks the installation of the generic Intel drivers now)

  • Tried a different Windows 10 machine (a Cherrytrail tablet with a Realtek wireless card. This works fine although the tablet doesn't have the latest Windows updates)

  • Tried a Windows 10 Mobile device. This works fine.

  • Verified that the driver and hardware supports a wireless display using dxdiag (using these instructions: How to check if your PC supports Miracast

  • Verified that the system supports a wireless display using an alternate method (netsh wlan sho d command in a command prompt)

  • Connected laptop and TV to my 2.4GHz wireless network instead of having the laptop on the 5GHz network and the TV connected with a wire (this shouldn't matter as Miracast uses WiFi Direct)


I'm now at my wits end as to what I can try next. Google tells me many people complain about Miracast being broken after certain Windows 10 updates but there is never a definite solution available.



The relevant hardware:




  • Core i5 5200U with Intel HD Graphics 5500

  • Intel AC7265 wireless card

  • Samsung UE40J6200 TV

  • Wireless network running on my provider's router (5GHz 802.11AC with a 40MHz wide channel on free channels, 2.4GHz 802.11N with a 20MHz channel and having interference from neighbor's access points)










share|improve this question
















I have a Dell Inspiron 17 5748 running Windows 10 1709 (Fall Creators Update). A good year ago I was able to wirelessly duplicate my laptop's screen to a Samsung UE40J6200 TV. I remember having to install an Intel wireless card and the need to install a piece of software called Intel WiDi to make it work.



I didn't use the functionality for a while and have reinstalled Windows 10 on that laptop since. I looked for the WiDi drivers and found that Intel has discontinued the product saying that Windows now has good Miracast support that can be used instead. The additional bonus would be that an Intel wireless card is no longer required.



Unfortunately I haven't been able to use it with this laptop since then. Whenever I put my TV in the "screen mirroring" mode, the laptop is able to see the TV when choosing the function to connect to a wireless display. The laptop seems to be able to connect and usually the TV will show the laptop's display for about 5 seconds before the image either freezes or the connection is dropped.



What I have tried so far:




  • Updated wireless card drivers to latest version

  • Updated graphics card drivers to the latest version on the Dell website

  • Updated graphics card drivers to the latest version from Intel (using a manual installation option because apparently Dell blocks the installation of the generic Intel drivers now)

  • Tried a different Windows 10 machine (a Cherrytrail tablet with a Realtek wireless card. This works fine although the tablet doesn't have the latest Windows updates)

  • Tried a Windows 10 Mobile device. This works fine.

  • Verified that the driver and hardware supports a wireless display using dxdiag (using these instructions: How to check if your PC supports Miracast

  • Verified that the system supports a wireless display using an alternate method (netsh wlan sho d command in a command prompt)

  • Connected laptop and TV to my 2.4GHz wireless network instead of having the laptop on the 5GHz network and the TV connected with a wire (this shouldn't matter as Miracast uses WiFi Direct)


I'm now at my wits end as to what I can try next. Google tells me many people complain about Miracast being broken after certain Windows 10 updates but there is never a definite solution available.



The relevant hardware:




  • Core i5 5200U with Intel HD Graphics 5500

  • Intel AC7265 wireless card

  • Samsung UE40J6200 TV

  • Wireless network running on my provider's router (5GHz 802.11AC with a 40MHz wide channel on free channels, 2.4GHz 802.11N with a 20MHz channel and having interference from neighbor's access points)







windows-10 drivers miracast






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 21 '18 at 9:58







AdmiralFreebee

















asked Feb 3 '18 at 20:15









AdmiralFreebeeAdmiralFreebee

468213




468213













  • Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

    – harrymc
    Feb 21 '18 at 15:55











  • @harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

    – AdmiralFreebee
    Feb 21 '18 at 21:25











  • If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

    – harrymc
    Feb 21 '18 at 21:29











  • @harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

    – AdmiralFreebee
    Feb 22 '18 at 9:39











  • What is your graphics card ?

    – harrymc
    Feb 23 '18 at 12:10



















  • Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

    – harrymc
    Feb 21 '18 at 15:55











  • @harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

    – AdmiralFreebee
    Feb 21 '18 at 21:25











  • If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

    – harrymc
    Feb 21 '18 at 21:29











  • @harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

    – AdmiralFreebee
    Feb 22 '18 at 9:39











  • What is your graphics card ?

    – harrymc
    Feb 23 '18 at 12:10

















Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

– harrymc
Feb 21 '18 at 15:55





Try : (1) Turn Firewall Defender off, and If this works then create a firewall rule. (2) Right-click the desktop / Display settings / Scroll to Projecting to this PC, and change "Setting: Windows PC's and Phones can project: Available everywhere on secure networks" to "Available everywhere".

– harrymc
Feb 21 '18 at 15:55













@harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

– AdmiralFreebee
Feb 21 '18 at 21:25





@harrymc I have tried your suggestion but the problem seems to have worsened in the meanwhile. The computer no longer even finds the TV when searching for wireless displays. Turning off the firewall or changing the projection settings did not help.

– AdmiralFreebee
Feb 21 '18 at 21:25













If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

– harrymc
Feb 21 '18 at 21:29





If you are experiencing a degradation, this becomes another problem. If you can, try to see what happens when booting in Safe mode with Networking (if it applies). Check the system with sfc /scannow. Do several deep antivirus scans.

– harrymc
Feb 21 '18 at 21:29













@harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

– AdmiralFreebee
Feb 22 '18 at 9:39





@harrymc Projecting to a wireless display doesn't work in safe mode as it relies on the graphics card's driver support. I have checked the system although I don't expect a relation between malware and this problem. Miracast also works only intermittently on my Windows 10 tablet where it varies between working well and not seeing the TV at all.

– AdmiralFreebee
Feb 22 '18 at 9:39













What is your graphics card ?

– harrymc
Feb 23 '18 at 12:10





What is your graphics card ?

– harrymc
Feb 23 '18 at 12:10










4 Answers
4






active

oldest

votes


















3





+50









The problem might be drivers or BIOS. You may find these at :




  • The firmware of the TV at the Samsung site,
    where the latest is apparently
    version 1510.4
    from 2017.09.26. The TV can also update itself if connected to the Internet.


  • The latest Dell drivers and BIOS for your motherboard at the page of
    Support for Inspiron 5748 - Drivers & downloads​


  • The latest
    Intel drivers.


  • You may also verify in Device Manager the make of the driver of the
    Miracast device and search for an update.



If all your drivers and firmware are up to date but the problem persists,
the problem is then with Windows 10 version 1709,
and you will have to wait for Microsoft to fix it.
I don't recommend downgrading to an earlier version of Windows,
as some have advocated, because of security concerns,
and also because Windows will update itself automatically back to version
1709.






share|improve this answer





















  • 1





    Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

    – AdmiralFreebee
    Feb 27 '18 at 8:29



















0














this is what I did to get miracast to work.
go to all settings-system-shared experience.
turn on nearby sharing so your computer can find the tv.
turn off nearby sharing then use connect to connect to the tv.






share|improve this answer































    -1














    For me the issue was resolved by manually setting the interface metric for IPv4 and IPv6 to high numbers (100 and 99) for the Microsoft Wi-Fi Direct Virtual Adapter and the Palo Alto Networks Global Protect (PANGP VPN) connection. I have Windows 10 build 1803, updated display drivers, wi-fi drivers, BIOS, docking station firmware, etc... (I tried many many things before resolving this).



    Windows Settings->Network & Internet->Status->Change adpater options



    For me, the Miracast display connection was called "Local Area Connection 2", and the PANGP connection was called "Ethernet 2". Right click on the one that represents your Miracast connection, select Properties, highlight Internet Protocal Version 4 (TCP/IPv4) and select properties, click on Advanced, unselect Automatic Metric and type 100 in the Interface Metric box. Click Ok twice, then do the same thing for Internet Protocol Version 6 (TCP/IPv6). I did the same for PANGP, but used the number 99 - for no real good reason, just saying what worked - other numbers probably will work...



    Review the ifIndex and InterfaceMetric for all connections by opening a Administrator Powershell terminal (Windows key-X then select "Windows Powershell (Admin)"). Type "Get-NetIPInterface".






    share|improve this answer































      -1














      tl:dr



      This happens because your Smart TV is not getting assigned an (or correct) address via the WI-Fi Direct connection.



      Solution



      You need to manually set up an IP(v4) address on the Wi-Fi Direct interface/adapter





      Having faced the same issue, I did a quick but thorough investigation on this issue, and I too did the majority of troubleshooting steps you did. The question which I had successfully led me to the solution: Why is is I can project the screen only using my android device but not my PC (running Windows)?



      I did a comparison on all prerequisites that were needed for a successful connection (i.e wireless chipset support, operating system support, and driver support) and realised I had overlooked one simple thing - the actual connection protocol i.e (wi-fi direct):



      An IP address must be setup manually on the interface used to miracast,in this case the Microsoft Wi-Fi Direct Virtual Adapter (similar to WIDI driver)



      In Android this is done automatically;




      the WiFiP2pMangerclass (provides the API for managing Wi-Fi
      peer-to-peer connectivity) assigns IP address to every Group Owner
      which is 192.168.49.1, and uses the 192.168.49.0/24 pool in DHCP to
      assign addresses to devices that join the Group Owner.




      Simply go to Network connections and click properties of the Wi-fi direct virtual adapter and input IP address and subnet:



      enter image description here



      enter image description here



      If your miracast software is not working properly you can get the MicrosoftWireless Display Adapter on Windows store which enhances funtionality of the adapter or perhaps has some patches of some sort:



      enter image description here






      share|improve this answer
























      • Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

        – xavier_fakerat
        1 hour ago














      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1291753%2fmiracast-no-longer-working-on-windows-10-laptop%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3





      +50









      The problem might be drivers or BIOS. You may find these at :




      • The firmware of the TV at the Samsung site,
        where the latest is apparently
        version 1510.4
        from 2017.09.26. The TV can also update itself if connected to the Internet.


      • The latest Dell drivers and BIOS for your motherboard at the page of
        Support for Inspiron 5748 - Drivers & downloads​


      • The latest
        Intel drivers.


      • You may also verify in Device Manager the make of the driver of the
        Miracast device and search for an update.



      If all your drivers and firmware are up to date but the problem persists,
      the problem is then with Windows 10 version 1709,
      and you will have to wait for Microsoft to fix it.
      I don't recommend downgrading to an earlier version of Windows,
      as some have advocated, because of security concerns,
      and also because Windows will update itself automatically back to version
      1709.






      share|improve this answer





















      • 1





        Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

        – AdmiralFreebee
        Feb 27 '18 at 8:29
















      3





      +50









      The problem might be drivers or BIOS. You may find these at :




      • The firmware of the TV at the Samsung site,
        where the latest is apparently
        version 1510.4
        from 2017.09.26. The TV can also update itself if connected to the Internet.


      • The latest Dell drivers and BIOS for your motherboard at the page of
        Support for Inspiron 5748 - Drivers & downloads​


      • The latest
        Intel drivers.


      • You may also verify in Device Manager the make of the driver of the
        Miracast device and search for an update.



      If all your drivers and firmware are up to date but the problem persists,
      the problem is then with Windows 10 version 1709,
      and you will have to wait for Microsoft to fix it.
      I don't recommend downgrading to an earlier version of Windows,
      as some have advocated, because of security concerns,
      and also because Windows will update itself automatically back to version
      1709.






      share|improve this answer





















      • 1





        Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

        – AdmiralFreebee
        Feb 27 '18 at 8:29














      3





      +50







      3





      +50



      3




      +50





      The problem might be drivers or BIOS. You may find these at :




      • The firmware of the TV at the Samsung site,
        where the latest is apparently
        version 1510.4
        from 2017.09.26. The TV can also update itself if connected to the Internet.


      • The latest Dell drivers and BIOS for your motherboard at the page of
        Support for Inspiron 5748 - Drivers & downloads​


      • The latest
        Intel drivers.


      • You may also verify in Device Manager the make of the driver of the
        Miracast device and search for an update.



      If all your drivers and firmware are up to date but the problem persists,
      the problem is then with Windows 10 version 1709,
      and you will have to wait for Microsoft to fix it.
      I don't recommend downgrading to an earlier version of Windows,
      as some have advocated, because of security concerns,
      and also because Windows will update itself automatically back to version
      1709.






      share|improve this answer















      The problem might be drivers or BIOS. You may find these at :




      • The firmware of the TV at the Samsung site,
        where the latest is apparently
        version 1510.4
        from 2017.09.26. The TV can also update itself if connected to the Internet.


      • The latest Dell drivers and BIOS for your motherboard at the page of
        Support for Inspiron 5748 - Drivers & downloads​


      • The latest
        Intel drivers.


      • You may also verify in Device Manager the make of the driver of the
        Miracast device and search for an update.



      If all your drivers and firmware are up to date but the problem persists,
      the problem is then with Windows 10 version 1709,
      and you will have to wait for Microsoft to fix it.
      I don't recommend downgrading to an earlier version of Windows,
      as some have advocated, because of security concerns,
      and also because Windows will update itself automatically back to version
      1709.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Feb 27 '18 at 9:11

























      answered Feb 27 '18 at 7:10









      harrymcharrymc

      264k14273582




      264k14273582








      • 1





        Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

        – AdmiralFreebee
        Feb 27 '18 at 8:29














      • 1





        Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

        – AdmiralFreebee
        Feb 27 '18 at 8:29








      1




      1





      Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

      – AdmiralFreebee
      Feb 27 '18 at 8:29





      Have tried everything including the TV firmware update which I did last night. I was up half the night trying different settings but alas... Appreciate your efforts and going to select this answer as correct. It indeed seems to be a Windows 10 issue and I agree not to downgrade for Miracast support.

      – AdmiralFreebee
      Feb 27 '18 at 8:29













      0














      this is what I did to get miracast to work.
      go to all settings-system-shared experience.
      turn on nearby sharing so your computer can find the tv.
      turn off nearby sharing then use connect to connect to the tv.






      share|improve this answer




























        0














        this is what I did to get miracast to work.
        go to all settings-system-shared experience.
        turn on nearby sharing so your computer can find the tv.
        turn off nearby sharing then use connect to connect to the tv.






        share|improve this answer


























          0












          0








          0







          this is what I did to get miracast to work.
          go to all settings-system-shared experience.
          turn on nearby sharing so your computer can find the tv.
          turn off nearby sharing then use connect to connect to the tv.






          share|improve this answer













          this is what I did to get miracast to work.
          go to all settings-system-shared experience.
          turn on nearby sharing so your computer can find the tv.
          turn off nearby sharing then use connect to connect to the tv.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 5 '18 at 6:55









          joe kingjoe king

          1




          1























              -1














              For me the issue was resolved by manually setting the interface metric for IPv4 and IPv6 to high numbers (100 and 99) for the Microsoft Wi-Fi Direct Virtual Adapter and the Palo Alto Networks Global Protect (PANGP VPN) connection. I have Windows 10 build 1803, updated display drivers, wi-fi drivers, BIOS, docking station firmware, etc... (I tried many many things before resolving this).



              Windows Settings->Network & Internet->Status->Change adpater options



              For me, the Miracast display connection was called "Local Area Connection 2", and the PANGP connection was called "Ethernet 2". Right click on the one that represents your Miracast connection, select Properties, highlight Internet Protocal Version 4 (TCP/IPv4) and select properties, click on Advanced, unselect Automatic Metric and type 100 in the Interface Metric box. Click Ok twice, then do the same thing for Internet Protocol Version 6 (TCP/IPv6). I did the same for PANGP, but used the number 99 - for no real good reason, just saying what worked - other numbers probably will work...



              Review the ifIndex and InterfaceMetric for all connections by opening a Administrator Powershell terminal (Windows key-X then select "Windows Powershell (Admin)"). Type "Get-NetIPInterface".






              share|improve this answer




























                -1














                For me the issue was resolved by manually setting the interface metric for IPv4 and IPv6 to high numbers (100 and 99) for the Microsoft Wi-Fi Direct Virtual Adapter and the Palo Alto Networks Global Protect (PANGP VPN) connection. I have Windows 10 build 1803, updated display drivers, wi-fi drivers, BIOS, docking station firmware, etc... (I tried many many things before resolving this).



                Windows Settings->Network & Internet->Status->Change adpater options



                For me, the Miracast display connection was called "Local Area Connection 2", and the PANGP connection was called "Ethernet 2". Right click on the one that represents your Miracast connection, select Properties, highlight Internet Protocal Version 4 (TCP/IPv4) and select properties, click on Advanced, unselect Automatic Metric and type 100 in the Interface Metric box. Click Ok twice, then do the same thing for Internet Protocol Version 6 (TCP/IPv6). I did the same for PANGP, but used the number 99 - for no real good reason, just saying what worked - other numbers probably will work...



                Review the ifIndex and InterfaceMetric for all connections by opening a Administrator Powershell terminal (Windows key-X then select "Windows Powershell (Admin)"). Type "Get-NetIPInterface".






                share|improve this answer


























                  -1












                  -1








                  -1







                  For me the issue was resolved by manually setting the interface metric for IPv4 and IPv6 to high numbers (100 and 99) for the Microsoft Wi-Fi Direct Virtual Adapter and the Palo Alto Networks Global Protect (PANGP VPN) connection. I have Windows 10 build 1803, updated display drivers, wi-fi drivers, BIOS, docking station firmware, etc... (I tried many many things before resolving this).



                  Windows Settings->Network & Internet->Status->Change adpater options



                  For me, the Miracast display connection was called "Local Area Connection 2", and the PANGP connection was called "Ethernet 2". Right click on the one that represents your Miracast connection, select Properties, highlight Internet Protocal Version 4 (TCP/IPv4) and select properties, click on Advanced, unselect Automatic Metric and type 100 in the Interface Metric box. Click Ok twice, then do the same thing for Internet Protocol Version 6 (TCP/IPv6). I did the same for PANGP, but used the number 99 - for no real good reason, just saying what worked - other numbers probably will work...



                  Review the ifIndex and InterfaceMetric for all connections by opening a Administrator Powershell terminal (Windows key-X then select "Windows Powershell (Admin)"). Type "Get-NetIPInterface".






                  share|improve this answer













                  For me the issue was resolved by manually setting the interface metric for IPv4 and IPv6 to high numbers (100 and 99) for the Microsoft Wi-Fi Direct Virtual Adapter and the Palo Alto Networks Global Protect (PANGP VPN) connection. I have Windows 10 build 1803, updated display drivers, wi-fi drivers, BIOS, docking station firmware, etc... (I tried many many things before resolving this).



                  Windows Settings->Network & Internet->Status->Change adpater options



                  For me, the Miracast display connection was called "Local Area Connection 2", and the PANGP connection was called "Ethernet 2". Right click on the one that represents your Miracast connection, select Properties, highlight Internet Protocal Version 4 (TCP/IPv4) and select properties, click on Advanced, unselect Automatic Metric and type 100 in the Interface Metric box. Click Ok twice, then do the same thing for Internet Protocol Version 6 (TCP/IPv6). I did the same for PANGP, but used the number 99 - for no real good reason, just saying what worked - other numbers probably will work...



                  Review the ifIndex and InterfaceMetric for all connections by opening a Administrator Powershell terminal (Windows key-X then select "Windows Powershell (Admin)"). Type "Get-NetIPInterface".







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 1 '18 at 21:58









                  Galen StansellGalen Stansell

                  1




                  1























                      -1














                      tl:dr



                      This happens because your Smart TV is not getting assigned an (or correct) address via the WI-Fi Direct connection.



                      Solution



                      You need to manually set up an IP(v4) address on the Wi-Fi Direct interface/adapter





                      Having faced the same issue, I did a quick but thorough investigation on this issue, and I too did the majority of troubleshooting steps you did. The question which I had successfully led me to the solution: Why is is I can project the screen only using my android device but not my PC (running Windows)?



                      I did a comparison on all prerequisites that were needed for a successful connection (i.e wireless chipset support, operating system support, and driver support) and realised I had overlooked one simple thing - the actual connection protocol i.e (wi-fi direct):



                      An IP address must be setup manually on the interface used to miracast,in this case the Microsoft Wi-Fi Direct Virtual Adapter (similar to WIDI driver)



                      In Android this is done automatically;




                      the WiFiP2pMangerclass (provides the API for managing Wi-Fi
                      peer-to-peer connectivity) assigns IP address to every Group Owner
                      which is 192.168.49.1, and uses the 192.168.49.0/24 pool in DHCP to
                      assign addresses to devices that join the Group Owner.




                      Simply go to Network connections and click properties of the Wi-fi direct virtual adapter and input IP address and subnet:



                      enter image description here



                      enter image description here



                      If your miracast software is not working properly you can get the MicrosoftWireless Display Adapter on Windows store which enhances funtionality of the adapter or perhaps has some patches of some sort:



                      enter image description here






                      share|improve this answer
























                      • Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                        – xavier_fakerat
                        1 hour ago


















                      -1














                      tl:dr



                      This happens because your Smart TV is not getting assigned an (or correct) address via the WI-Fi Direct connection.



                      Solution



                      You need to manually set up an IP(v4) address on the Wi-Fi Direct interface/adapter





                      Having faced the same issue, I did a quick but thorough investigation on this issue, and I too did the majority of troubleshooting steps you did. The question which I had successfully led me to the solution: Why is is I can project the screen only using my android device but not my PC (running Windows)?



                      I did a comparison on all prerequisites that were needed for a successful connection (i.e wireless chipset support, operating system support, and driver support) and realised I had overlooked one simple thing - the actual connection protocol i.e (wi-fi direct):



                      An IP address must be setup manually on the interface used to miracast,in this case the Microsoft Wi-Fi Direct Virtual Adapter (similar to WIDI driver)



                      In Android this is done automatically;




                      the WiFiP2pMangerclass (provides the API for managing Wi-Fi
                      peer-to-peer connectivity) assigns IP address to every Group Owner
                      which is 192.168.49.1, and uses the 192.168.49.0/24 pool in DHCP to
                      assign addresses to devices that join the Group Owner.




                      Simply go to Network connections and click properties of the Wi-fi direct virtual adapter and input IP address and subnet:



                      enter image description here



                      enter image description here



                      If your miracast software is not working properly you can get the MicrosoftWireless Display Adapter on Windows store which enhances funtionality of the adapter or perhaps has some patches of some sort:



                      enter image description here






                      share|improve this answer
























                      • Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                        – xavier_fakerat
                        1 hour ago
















                      -1












                      -1








                      -1







                      tl:dr



                      This happens because your Smart TV is not getting assigned an (or correct) address via the WI-Fi Direct connection.



                      Solution



                      You need to manually set up an IP(v4) address on the Wi-Fi Direct interface/adapter





                      Having faced the same issue, I did a quick but thorough investigation on this issue, and I too did the majority of troubleshooting steps you did. The question which I had successfully led me to the solution: Why is is I can project the screen only using my android device but not my PC (running Windows)?



                      I did a comparison on all prerequisites that were needed for a successful connection (i.e wireless chipset support, operating system support, and driver support) and realised I had overlooked one simple thing - the actual connection protocol i.e (wi-fi direct):



                      An IP address must be setup manually on the interface used to miracast,in this case the Microsoft Wi-Fi Direct Virtual Adapter (similar to WIDI driver)



                      In Android this is done automatically;




                      the WiFiP2pMangerclass (provides the API for managing Wi-Fi
                      peer-to-peer connectivity) assigns IP address to every Group Owner
                      which is 192.168.49.1, and uses the 192.168.49.0/24 pool in DHCP to
                      assign addresses to devices that join the Group Owner.




                      Simply go to Network connections and click properties of the Wi-fi direct virtual adapter and input IP address and subnet:



                      enter image description here



                      enter image description here



                      If your miracast software is not working properly you can get the MicrosoftWireless Display Adapter on Windows store which enhances funtionality of the adapter or perhaps has some patches of some sort:



                      enter image description here






                      share|improve this answer













                      tl:dr



                      This happens because your Smart TV is not getting assigned an (or correct) address via the WI-Fi Direct connection.



                      Solution



                      You need to manually set up an IP(v4) address on the Wi-Fi Direct interface/adapter





                      Having faced the same issue, I did a quick but thorough investigation on this issue, and I too did the majority of troubleshooting steps you did. The question which I had successfully led me to the solution: Why is is I can project the screen only using my android device but not my PC (running Windows)?



                      I did a comparison on all prerequisites that were needed for a successful connection (i.e wireless chipset support, operating system support, and driver support) and realised I had overlooked one simple thing - the actual connection protocol i.e (wi-fi direct):



                      An IP address must be setup manually on the interface used to miracast,in this case the Microsoft Wi-Fi Direct Virtual Adapter (similar to WIDI driver)



                      In Android this is done automatically;




                      the WiFiP2pMangerclass (provides the API for managing Wi-Fi
                      peer-to-peer connectivity) assigns IP address to every Group Owner
                      which is 192.168.49.1, and uses the 192.168.49.0/24 pool in DHCP to
                      assign addresses to devices that join the Group Owner.




                      Simply go to Network connections and click properties of the Wi-fi direct virtual adapter and input IP address and subnet:



                      enter image description here



                      enter image description here



                      If your miracast software is not working properly you can get the MicrosoftWireless Display Adapter on Windows store which enhances funtionality of the adapter or perhaps has some patches of some sort:



                      enter image description here







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 1 hour ago









                      xavier_fakeratxavier_fakerat

                      1,9591522




                      1,9591522













                      • Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                        – xavier_fakerat
                        1 hour ago





















                      • Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                        – xavier_fakerat
                        1 hour ago



















                      Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                      – xavier_fakerat
                      1 hour ago







                      Downvoters! this surely works tried it myself. Anyway not worried by fake medals/points just helping out a guy in need of help with this solution

                      – xavier_fakerat
                      1 hour ago




















                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1291753%2fmiracast-no-longer-working-on-windows-10-laptop%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Cannot install PyQt5 The Next CEO of Stack OverflowCannot install tcpreplay 3.4.4cannot...

                      Kapp-Putsch Acontecimentos | Outros artigos | Menu de navegação

                      Why did early computer designers eschew integers? The Next CEO of Stack OverflowWhat register...