How to turn a Windows 8.1 machine into a Miracast receiver

[German article]Windows 8.1 (like Android 4.2.2) supports Miracast on capable hardware. Till now Windows 8.1 was only able to stream to Miracast receivers. Now it's possible, to turn your Windows 8.1 machine (if hardware fits) into a Miracast receiver.


I still remember the question, raised in summer 2013 in Microsoft's Answers forums: "So, if upcoming Windows 8.1 supports Miracast, can I use my Surface Pro to receive a screen mirrored from another Windows 8.1 machine?". Well, that question was answered "No, that isn't possible". Windows 8.1 itself doesn't come with a "receiver application" for Miracast at all.

What is Miracast?

Miracast is a vendor independent standard to stream audio and video signals wireless from a Windows 8.1 machine or an Android 4.2.3 device to Miracast receivers. But there is a mandatory hardware support for for Miracast. See this wikipedia article and this Microsoft article for further reading.

Within my (German) blog I've tested many Miracast receiver and also several Windows 8.1 and Android 4.x devices as Miracast sender. A link list (to my German blog articles) is available in the following article.

Hands on: Streamcasting mit DLNA, Miracast, Airplay & Co.

Is Windows 8.1 capable to act as a Miracast receiver?

If hardware supports Miracast, can we use a Windows 8.1 machine as a Miracast receiver? This question was on my agenda since August 2013. Till August 2014 the answer was always "no chance, Windows 8.1 doesn't support Miracast as a receiver".

But August 2014 Update Rollup changes the game. There was one sentence in this Microsoft blog article (and here), that kept my attention:

Miracast Receive – exposes a set of Wi-Fi direct APIs for Independent Hardware Vendor (IHV) drivers or OEM drivers to develop Windows 32-bit applications that run on all supported x86-based or x64-based versions of Windows 8.1, enabling the computer as a Miracast receiver.

Obviously the message was "Microsoft had no plans, to release a Miracast application" – but they added some APIs to allow third party developers enables a Windows 8.1 machine as a Miracast receiver. Since August 2014 I searched the web from time to time for hints of upcoming solutions – till now without success at all.

But last weekend everything changed. I was searching the web for another topics (to prepare an article about mirroring Android screens to Windows desktop) – and on page 2 of Google`s search results I stumbled upon this article.


AirServer Universal: Turns your Windows 8.1 machine into a Miracast receiver

Well, on October 31st, 2014, App Dynamics released AirServer Version 3.0.12. AirServer was known to me as an AirPlay receiver for Windows (see Windows per AirServer als AirPlay-Empfänger nutzen). The new 3.x version of this program was rebranded as AirServer Universal. The PC version supports now – beside AirPlay (Apple) – also Miracast on capable Windows 8.1 machines.

App Dynamics developed this extension in cooperation with Intel and Microsoft, to enable Windows 8.1 as a universal mirroring receiver for AirPlay and Miracast. With AirServer Universal you might be able to use a Windows 8.1 machine to show the screens of AirPlay iOS devices (iPhone, iPad) and Miracast devices (Android, Windows 8.1, Windows Phone 8.1) streamed wireless to this Windows machine.

AirServer Universal is available here as a 7 day trial and will be licensed for educational purpopses (8 to 12 US $), for private use (14 $) and for business use (20 $). I've tested it on my Windows 8.1 machine during weekend. The requirements for a Windows 8.1 machine are:

  • The new AirServer Universal can be installed on Windows 8.1 based PC/tablets with latest updates (Windows 8.1 August 2014 Update Rollup is mandatory)
  • The WiFi adapter used on such a machine need Windows 8.1 specific NDIS 6.4 drivers.

This allows many Windows 8.1 machines, including the following:

  • Surface Pro
  • Surface Pro 2
  • Surface Pro 3
  • Intel 7260 based machines

as Miracast receivers. I have used a Akoya S6214T Windows 8.1 Tablet (convertible), that was sold here in Germany by Medion (a Lenovo subsidary). My test scenarios was:

  • Run my Akoya S6214T with Windows 8.1 Update and AirPlay Universal Version 3.0.15 as Miracast receiver.
  • Use a Akoya P2214T Windows 8.1 Slate as Miracast source
  • Use an Android 4.4.4 Nexus 4 Smartphone, an Android 4.4.4 Nexus 7 (2013) Tablet and a Samsung Galaxy S4 with Android 4.4.2 as Miracast source .

Installing AirServer Univeral on my 64-Bit-Windows 8.1 machine was no issue. A setup wizard guided me through the install steps. Here I was asked in a custom setup to select the functionality.

AirPlay was de-selected – which is a good choice. This means, you haven't AirPlay support, but it also means, you haven't to install Bonjour protocol (via iTunes). I always avoid to install iTunes or Bonjour on my productive Windows machines. Missing Bonjour will result in this warning, each time AirServer Universal launches.

But it's easy to close this warning. If somebody use a 7-day-trial, this dialog box is also shown, asking for a key and offering to buy.

Entering a valid license key will hide this dialog box on further program starts. AirServer Universal sits in your taskbars tray – a right click on that icon opens a context menu.

Here are the Settings-page of AirServer Universal, which provides several settings tabs.

As you can see, it's possible to enable AirPlay and/or Miracast as separat services. If a micracast devices tries to connect to AirServer Universal, a popup will be shown in taskbar.

I was able to connect two machines with Windows 8.1 Update without any problem. Here are the two machines (receiver in background, source is a tablet pc in foreground).

Seems genius, and it is genius – you are able to mirror your Windows 8.1 screen with audio and video to a 2nd Windows 8.1 machine. But there are a few pitfalls, as far as I've seen during my tests.

  • I wasn't successful to connect my Android devices (Nexus 4, Nexus 7 (2013), Samsung Galaxy S4) with my Windows 8.1 machine running AirServer Universal. The best what I received, was a message on my Windows 8.1 screen, to type a security code 5555 5555 on my Android device. But I wasn't able to type anything on my Android device, because there was only a Android screen informing me about waiting to connect. I noticed this mis-fit during several Miracast HDMI-receiver tests last year (since then, most vendors updated their firmware, so that I was successful to connect my Android devices to these Miracast HDMI receivers).
  • And during my streaming tests, using a Windows 8.1 machine as source, I've have had each 3 – 4 seconds terrible artefacts on my reciver (as it may be seen in the image below). These flaws are also present, even there was a static screen on my source machine. Streaming a screen with a Youtube video results in video artefacts and also audio stutter.

Although I'm not sure, to blame my hardware for these issues, my feeling is, that it's a software bug (either in AirServer Universal or in Microsoft's API routines). Wi-Fi direct hardware should be fast enough to transport all data (I've never had problems, using this machine as a streaming source for a Miracast HDMI-receiver like a Netgear Push2TV PTV 3000). I tried also to change AirServer Universal settings (I enabled slow network connection option and set the streaming buffer up to 1 second). The artefacts occurs every 3-4 seconds. I also enabled frame rate view – and during tests I recognized, that AirServer Universal receives 59 or 60 frames per second – there was no frame drops.

My conclusion: While AirServer is genius as a AirPlay receiver, I feel, that the developers (or Microsoft) needs to invest further time for improvements. It's partial genius, to have a solution, that enables me to use my Windows 8.1 machines as a Miracast receiver. But in practice I need to be able to connect Android devices as well – and AirServer Universal needs improvement in audio- and video quality. So at least I'm eager to see, what the guys in Island will present in future updates. I guess, AirServer Universal has a great potential to be a great piece of software for streaming enthusiasts.

Cookies blockieren entzieht uns die Finanzierung: Cookie-Einstellungen

Dieser Beitrag wurde unter Streaming, Windows 8.1 veröffentlicht. Setze ein Lesezeichen auf den Permalink.

17 Antworten zu How to turn a Windows 8.1 machine into a Miracast receiver

  1. Thomas Traberg-Larsen sagt:

    I had exactly same problems while testing the trial. Using two different MS Surface Pro 3 machines as server, I did never get a success. Tried both to connect from another Win 8.1 maschine, and several Android devices (Samsung, HTC, Sony tablet) – nothing works :(

  2. Günter Born sagt:

    @Thomas: "I had exactly same problems while testing the trial" means, you see the 5555 5555 on AirServer, but no connection? I was in touch with App Dynamics developers. They recently released an update – so I'm able to connect Windows 8.1 machines, but no Android devices. Maybe they will be shipping a modified version, enabling Android connections – I have to go back in touch with App Dynamics developers for this issue.

    Also: Keep in mind, that third party internet security suites, VPN-software and similar products may cause trouble.

    • Günter Born sagt:

      @Thomas: I got a feedback from App Dynamics developers. Here is, what they have written.

      AirServer should not be running on the source Surface Pro 3 if trying to connect to another Surface Pro 3 running AirServer.
      Although not required, it helps to connect both computers to the same WiFi network before launching AirServer and connecting over Miracast.

      I've tested it with two distinct Windows 8.1 machines (no Surfaces Pro 3).

  3. Günter Born sagt:

    Concerning the "fragmentation" within AirServer display as shown above, it seems that's a mixture auf Miracast design flaw and implementation issues. Some Frames are getting dropped durch UDP transfer – and there is no chance, to receive the missing frames. As a result, you will see some "pixeled" areas in your Miracast view.

  4. Dan V sagt:

    I got this to work reasonably well on my Lenovo laptop running windows 8.1 receiving from my BlackBerry running 10.3.1. I have owned air server for some time for airplay use. The fact they added miracast is just fantastic.

    • Günter Born sagt:

      @Dan: Thx for feedback. The developers from App Dynamics are doing an excellent job. Currently they have to improve things a bit (and I guess, Microsoft need a few things to fix). Android compatibility is (at the moment) just a mess – I can't get 3 distinct Android devices to connect). Here is a list of devices, which I have tested (with a non public version):

      Windows 8.1: Connecting like a champ
      Windows Phone 8.1 (Lumia 635): Connecting like a champ

      Samsung Galaxy S4, Android 4.4.2: Connection failed
      Nexus 4, Android 5.0: Connection failed
      Nexus 7 (2013), Android 5.0: Connection failed

      It seems, that something in Microsofts Miracast API buried deep into Windows 8.1 Update w August Rollup Update doesn't like Android (or Android's Miracast implementation from Google is a mess).

  5. Mark Lipschitz sagt:

    I would like to use a Miracast solution in my office. I have a touchscreen patient note program. I would like to get a Windows 8.1 tablet, Bluetooth keyboard and use a HDMI monitor for Miracast. If I use a Surface 3 for Miracast will the tablet still be able to be connected to the internet via wifi? Thank you.

    • Günter Born sagt:

      @Mark: Miracast is using multiantenna Wi-Fi – which means only approved hardware is Miracast enabled. AFAIK Surface Pro 3 is Miracast enabled. And yes, if you connect your Surface Pro 3 to a Miracast sink (like Netgear Push2TV PTV 3000), you are still able to connect to the Internet via Wi-Fi. In short, the answer to your question is Yes.

  6. Paul Guillory sagt:

    Which Wi-Fi adapter is in your Akoya S6214T?

    • Günter Born sagt:

      @Paul: The Akoya S6214T comes with an Intel (R) Dual Band Wireless AC 3160 Wi-Fi adapter.

      Do you think, Android Miracast connection issues are Adapter related? I would be able to test another USB Wi-Fi adapter. But I've tested the machine (as source) with numerous Micracast HDMI-Receivers. All quality HDMI Miracast receivers did connect like a champ with this machine.

  7. Jayantabasu sagt:

    I have downloaded the latest Microsoft SDK. I am having a Windows 8.1 Laptop. but I am unable to call this API and other Wireless Display Sink APis .I have tried to include Wfdsink.h. I get an error as "cannot open include file ; 'Wfdsink.h'. Where can I get this header file? The Wifidisplay.lib is also missing..
    How can I use the "set of Wi-Fi direct APIs for Independent Hardware Vendor (IHV) drivers or OEM drivers to develop Windows 32-bit applications that run on all supported x86-based or x64-based versions of Windows 8.1, enabling the computer as a Miracast receiver."

    • Günter Born sagt:

      Thanks for your question. Unfortunately, I'm not a developer. So I woould suggest to ask your question within Microsoft's Technet Developer forums. There are many people with sufficient knowlegde. Maybe you will receive an answer.

  8. Greg T sagt:

    Try Mirrors Android devices (Nexus 4, 5, 6, 7(2013), Supported Devices) using Chrome Cast mirroring and Chromebooks + Windows PCs & Surface/ Pro/ 2/ 3) through Google Cast extension on Google Chrome on the device and then initiating Google Cast mirroring.

  9. Jason Yeoman sagt:

    It would be preferable if Airserver with Miracast could be run on a desktop computer that is connected to a projector. It can't be done unless the desktop also has a wifi adapter (even though it's connected to the network via ethernet).

  10. Thuan sagt:

    This helps us much, thank you

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert

Hinweis: Bitte beachtet die Regeln zum Kommentieren im Blog (Erstkommentare und Verlinktes landet in der Moderation, gebe ich alle paar Stunden frei, SEO-Posts/SPAM lösche ich rigoros). Kommentare abseits des Themas bitte unter Diskussion.