With Windows 8.1, we are introducing wireless display developed on the Wi-Fi Alliance (WFA) Miracast wireless display specification, so you can now wirelessly project to a big screen without fussing with proprietary technologies, network access, and different display cables and adapters. Wireless display is available in new Windows 8.1 PCs – laptops, tablets, and all-in-ones -- allowing you to display your full Windows 8.1 experience (up to 1080p) to large wireless display-enabled screens at home and work.
What can you do with it
Although it can be handy to turn your device into what is essentially a touch-screen remote control for watching online videos, we knew the potential was there to do a lot more when you wirelessly project your Windows device to the big screen.
In Windows 8.1, wireless display is a great way to share anything you do on Windows with friends and family in the living room, with colleagues in the conference room, and with students in the classroom. It lets you share experiences like shopping on Amazon or eBay, checking out 360-degree panoramas of vacation destinations in Bing Travel , solving puzzles in Disney Fairies with the kids, enjoying photos from a class field trip on SkyDrive, or exploring the solar system with your classroom with the World Wide Telescope. Of course, you can also use it for watching movies and videos through your favorite services like Netflix, Xbox Video and YouTube.
Wireless display puts Windows 8.1 on your big screen.
With wireless display in Windows 8.1, you can duplicate your main display or extend your display, giving you two independent screens (multi-monitor). Duplicating the display takes what you have on the local screen of your device and shows it on the big screen. Extending your display allows you, for instance, to use Microsoft PowerPoint to show a presentation in Presenter View, where the local screen shows you your speaker notes, next slide, and slide controls, while the wireless display shows the audience your full-screen presentation. Great for when you want to come from behind the podium, while keeping your notes and controls in the palm of your hand.
What you need
When you use wireless display, you have a source and a receiver: your Windows 8.1 device is the source, while your TV or projector is the receiver. If your display already has Miracast support, you are ready to go. If not, Miracast adapters provide an economical way to add wireless display to your existing TV or projector.
Wireless display works on new Windows 8.1 wireless PCs. This includes Surface 2 and Surface Pro 2, Nokia Lumia 2520, and Intel Atom Generation 3 (“Bay Trail”) and Intel Core Generation 4 (“Haswell”) systems. Some PC manufacturers have also added wireless display to some of their systems that originally shipped with Windows 8. This includes the Surface Pro and many systems based on Intel Core Generation 3 (“Ivy Bridge”) and Intel Wi-Fi. Be sure to check for updates from Windows Update and from your PC manufacturer, including driver updates listed as Optional, when determining whether your PC manufacturer has made wireless display available on your upgraded Windows 8 device.
As I mentioned earlier, we built wireless display on the Miracast industry-standard specification, which the industry based on widely adopted standards such as 802.11n, Wi-Fi Direct, and H.264/MPEG-4 AVC. We believe working with the industry and using industry standards allows broader adoption and interoperability by source devices (e.g., laptops, tablets and phones) and receivers (TVs, projectors, streaming players), and over time allows the standard to advance beyond any one company’s interests.
How to use it
We worked with several Miracast receivers during Windows 8.1 development. Notable among these are the ActionTec ScreenBeam Pro and the Netgear Push2TV (PTV3000). These and other Miracast receivers work great in bringing Windows 8.1 to the big screen. Additionally, ActionTec simplified firmware updating and configuration for their receiver by creating a Screenbeam Windows Store app using our new Wi-Fi Direct APIs (Windows.Devices.WiFiDirect). Whichever Miracast receiver you choose, be sure to update to the latest firmware for best results.
Note: ActionTec is providing readers of the Windows blog a 15% discount on the ActionTec Screenbeam Pro through their online store now through the end of this year (12/31). Please use the Screenbeam Pro links in this blog post to receive the discount.
To get started with wireless display, first ensure that your Windows 8.1 device is ready by checking Windows Update and your PC manufacturer for any driver updates, including drivers presented as optional. After your machine is ready, you need to add your wireless display receiver for the first time. To add it, open the Devices charm by swiping in from the right and then tapping Devices (or if you're using a mouse, point to the lower-right corner of the screen, move the mouse pointer up, and then click Devices.). Select Project and then Add a wireless device to have Windows scan for available Miracast receivers.
Note: Wireless display is available on most new Windows 8.1 PCs, but some PC manufacturers might choose not to include it on some new and upgraded PCs. Specifically, your PC needs WDDM 1.3 display and NDIS 6.4 Wi-Fi drivers, enabled by the IHV and OEM for Miracast. If you don’t see “Add a wireless display” when you tap the Devices charm and tap Project, try going to Windows Update and downloading all available updates (including optional drivers). If you still don’t see it, check for additional updates on your PC manufacturer’s support site, or contact them to ask how you can get this feature on your PC.
Selecting your receiver begins the secure pairing of your Windows 8.1 device to the Miracast receiver. After pairing is finished, you’ll be able to project your full Windows 8.1 experience wirelessly onto your big screen. To extend projection, open Devices and tap Project again (or press Windows key + P), and then tap Extend.
To end projection, open Devices and tap Project again (or press Windows key + P), and then tap or click Disconnect.
The next time you use your wireless display it will be even simpler, as Windows remembers the displays you’ve used, and automatically shows them whenever they’re available. Simply open Devices, tap or click Project, and then tap or click the display you want.
The Project to a wireless display with Miracast article provides info about source and receiver setup, how to project to the receiver, and troubleshooting problems.
What do app developers need to do?
App developers do not need to change their apps to take advantage of wireless display. By default, all apps will just work with wireless display. We do however provide the ProjectionManager APIs, for developers who want to provide an enhanced experience with wireless display.
ProjectionManager APIs allow an app to detect a secondary monitor, and when the monitor is present, control what the app displays on the primary and secondary monitors. An example is a video or photo app, where the local screen shows the box shots, thumbnails, or playlist, while the wireless display shows the full-screen video or slide show. A game developer could provide controls for the game on the local device (e.g., cards in hand, steering wheel and cockpit controls) while the wireless display shows the action of the game on the big screen.
The ProjectionManager APIs are not specific to wireless display and work equally well for wired monitors. In either case, wireless or wired, what gets displayed on either screen is up to the app developer.
How it works
For those interested in the nitty gritty of how wireless display works, here’s a quick rundown. It begins with the discovery of available Miracast receivers, and then proceeds to establishing a point-to-point connection between the source and receiver over Wi-Fi Direct. Security is negotiated using Wi-Fi Protected Setup (WPS), with communication secured using WPA2-AES directly between the Windows device and Miracast receiver. Once communication is established (2.4GHz by default or 5GHz if pre-connected to 5GHz AP), the source and receiver negotiate capabilities – e.g., the resolution and refresh rate (e.g., 30Hz), content protection scheme, audio channels, etc. Once capabilities are agreed, Windows begins projecting its display and audio onto the remote device by encoding the local display and sound, and sending to the receiver, where the receiver decodes and displays. Anything your Windows PC has access to, you can wirelessly display on your big screen. This is, of course, just a high-level explanation of the steps involved, with the Wi-Fi Alliance Miracast site having more details including the full specification.
There are other wireless display (“screen casting”) alternatives, each having their own advantages and drawbacks when compared to Miracast. Not all alternatives support full HD (1080p) and instead top-out at lower resolutions below what your TV/projector may natively support. Some of the alternatives work well in home environments, but have difficulty in corporate and hotspot environments where the receiver has to authenticate onto the network using enterprise-grade security such as WPA2-Enterprise or hotspot style authentication using a captive portal. Miracast is different, in that it is peer-to-peer, going directly between Windows and the receiver, and not over the Wi-Fi infrastructure network. This means that you can allow a guest (corporate or home) to project in your conference or living room without you having to grant them network access (which could potentially give them access to other devices and content beyond what you might have intended). With wireless display, you’re only granting them access to the display… not to your network.
Since the content comes from (or via) the Windows device, only the Windows device needs Internet access, which can come via its Wi-Fi, mobile broadband, or wired connection. Additionally, since we enabled wireless display in the OS and not tied to any particular application, any content in any app can take full advantage of the processing power of the PC, which enables a good wireless display experience across the range of Windows 8.1 devices and form-factors.
We are excited to have worked with our partners and the industry in bringing you a great, no compromise, and standards-based, approach to wireless display. We look forward to hearing about your experiences as you project your full Windows experience onto the big screen! Please let us know your thoughts by leaving us a comment.
Billy AndersGroup Program Manager, Wireless & Mobility
I have a Miracast Dongle bought from China, which has claimed DNLA/Miracast/AirPlay All-In-One. I've tested HTC One and LG G2, Both work perfectly with the Miracast function. And I've tested DNLA, it works as well as Xbox One in terms of a DNLA receiver. Also, it works with iPad/iPhone but only with the sound output if you don't jailbreak iOS. All in all, this Miracast Dongle can be called "PERFECT" with all other devices except those with Windows installed.
Unfortunately, I tried all my Windows 8.1 devices and all failed without exception.
I suppose Microsoft wants to be fair with all OEM vendors, not only for promoting a few firms as mentioned here as ActionTec and Push2TV, right? I think if microsoft can make all the Miracast Dongles work by talking with them first and then deciding to use which Miracast version or protocol, then Windows 8.1 Wireless Display will be spread everywhere since tens of millions of such Miracast Dongles like mine have been installed in place around the world, and why Microsoft wants to dump them all and solicit them to buy ActionTec or Netgear instead? It sounds pretty silly for Microsoft, right?
I tried to use HP i3, ASUS VivoTab Smart "Clover Trail" and the newest ASUS Transformer Book T100TA "Bay Trail" with Wireless Display function listed. When adding devices, I can see the dongle from Devices Search Window but all failed to build connection. Just wonder, why can I use Android devices like LG G2 and HTC One to project to Big TV Screen anytime for hours without losing any connection but Windows 8.1 provides so lousy an experience?
I also tried to use these three above-mentioned devices to connect my Mercedes-Benz car via Bluetooth, and all failed. What a pity? Is Mercedes-Benz famous enough for Microsoft to support it?
How can Microsoft compete with Google down the road if all Microsoft products are so lousy?
If Microsoft wants to keep this user experience down the road, I guess Google and Apple will eat Microsoft Raw.
Hope Microsoft can wake up and fight back.
And I've bought Xbox One and also without Miracast Function, how come?
If Microsoft wants to take over each and every living room around the world, Xbox One should be designed to be as open as possible so that people don't have to buy a third-party Miracast Dongle again since it can't be integrated into Xbox One's voice command system. I heard Xbox has Wi-Fi Direct build-in, why not open it so that everyone can cast their stuff via any Google Android or Windows Devices to the Big TV Screen anytime as they want?
If Microsoft wants to survive, Microsoft needs to change their mindset in the first place.
Shaking out Ben Palmer is a good sign for change...
What's the IP range that Win 8.1 Miracast uses? I think i need to configure my firewall for it to work properly...
I also have quite a few questions and would appreciate if you could collect the answers (possibly separate post)...
1) Are the streams re-encoded or transmitted as is, assuming it's a h264 video stream (was asked before)?
2) Which audio codecs are supported (mp3, aac, dolby digital, dts, dts-master, wma, wma lossless, etc.)?
3) If using wifi, does the "normal" Wifi Internet connection to my hotspot stay on?
I have windows phone, surface pro. Started to transcode e.g. flac to wma lossless (as it seems to be reasonable that microsoft products will support their own codec be default), this works fine on my windows phone.
My goal would be to transmit my lossless audio formats untouched and digitally to my hifi receiver.
Hi Oren Kaufman and Mobiletonster,
There is a ScreenBeam software to support Windows 7/8 laptops. ScreenBeam Kit comes with a CD software and USB dongle which attaches to Win 7/8 laptops. Here is the ScreenBeam software information: www.actiontec.com/screenbeamkit
I recently purchased Netgear PTV 3000 device (with latest firmware and drivers) and really impressed with the Wireless technology which Microsoft is collaboratively working on it. Here are my findings:
1. Dell Latitude E6320 using Intel WiDi app - Works as expected
2. Dell Latitude E6430s using inbuilt Windows 8.1 Miracast driver - Screen resolution cuts off and out of the display
3. Dell Latitude E6330 using inbuilt Windows 8.1 Miracast driver - Screen resolution cuts off and out of the display
4. Surface Pro 2 devices using inbuilt Windows 8.1 Miracast driver - Screen resolution cuts off and out of the display
To summarize, screen resolution cuts off from the display on all the devices using Windows 8.1 Miracast driver. I am using Casio XJ-A240 projector. I tried with my other TVs as well.
Additionally, Miracast projection is limited to 30Hz refresh rate (video is terrible in this frame rate and is expected to work at 60Hz).
Any alternatives to fix screen cut off and refresh rate issue?
do you know what changes the moment you join 8.1 to a domain? As of joining the work domain the surface does not give me the option to choose what I want to project to, I only get the 4 options of how to display. this happens if I am connect to a display via cable or not connected to anything!
The firewall is off, so I cant see what it is.
Any help at all?
@Capt_Ron - The issue with the Venue 8 Pro seems to be centered on the screen resolution. My TV doesn't have a screen resolution of 1280 x 800 so it can't drop to that resolution to provide a mirroring solution for it. This seems like it could be solved with a driver update that would "capture" the 1280 x 800 screen view and upscale or downscale the stream to 1366 x 768 or 1920 x 1080, or a more standard resolution.
@Oren Kaufman - (1) You don't lose your connection to WiFi when you connect to a Miracast Receiver. The only issue I have seen is with our particular Enterprise WiFi network. It won't let me connect to a Miracast Receiver if I'm connected to the Enterprise WPA-2 (with some extra security) network. I have to disconnect from that particular WiFi first before I can successfully connect to the Miracast receiver. This is more of an exception case than a normal situation. It should work fine on most networks. part (2) - I have looked for Miracast Receiver emulators (software) and I haven't found anything yet. I have to believe it exists, but no luck so far.
@Stephen Pate - YES, the Surface 2 and Surface Pro 2 support Miracast, as well as the Surface Pro 1, but not Surface RT (original).
@cleverclogs - Video streaming with Miracast ( in my experience ) is best described as pretty decent. I have some Miracast Dongles that I've been working with a Chinese Supplier that support multiple protocols. It has a Miracast mode and it has a mode where it supports DLNA, MirrorOp (an older protocol that provides mirroring on older laptops and devices using simple WiFi and software screen casting) and "Air Play"....but not really "Air Play"... in other words, it requires you to Jail Break your iOS device and install special software...so, not really "Air Play". Anyway, if you are just streaming video/audio/photos, DLNA seems to be smoother with the Surface Pro. It kind of makes sense why. Miracasting Video makes your PC work pretty hard, whereas DLNA just feeds the stream that would normally render on your local machine to the remote device.
@JakobK - Its pretty fast. It depends on your setup. Your PC needs to be able to handle Miracasting and the demands and your receiver needs to be decent as well. The better the devices on each end, the lower the latency and smoother the experience. My Miracast seem very responsive. I have tried to measure the latency and have seen it as little as 50-70 ms, which is pretty acceptable.
Miracast will be a bit rough for the first little while as OEMs work on their Graphics Drivers and WiDi drivers. As those things get smoothed out, I think it will be a great experience.
MiDi is Intel's version of Miracast. You need Intel WiFi adapter. Miracast is platform (android/Windows) agnostic.
I'm having trouble with my Venue 8 Pro. It connects bot only as a second screen (extended) I can't get it to display as Duplicated. It's very frustrating.
Question: If viewing an h264 (or x264) video on a tablet/device - does Windows still need to encode it in order to send to Miracast, or is it able to send it 'directly' without a de-compress/re-compress step. Seems inefficient if it has to decode/recode first, and of course would lose quality. Though I guess these things aren't really designed for epic quality blu-ray streaming, ah ha.
1. Since this is a brand new peer-peer WiFi connection, do you lose your current connection to your wireless AP? I always thought a WiFi card could only connect to 1 WiFi network / device.
2. Are there any software Miracast receivers? I have a Windows 7 PC connected to my TV already so if there was a Miracast receiver program I could install on it, I would save an HDMI slot and a bit of cash.
Will Xbox One work as a MIracast receiver?
Hi! I've been waiting for a standard for long if the wireless display and now it's here!
But how fast is it? Can you skip the cable and just use the miracast and play multiplayer internet games, working with engineering cad programs without any lag?
Or is it just for presentations and videos?
Please write your experience of what it is usable for.
Thanks for the article. I started seeing this just weeks ago with the release of the Dell Venue 8 Pro.
I assume none of the Nokia Lumia products support WiDi simply because they don't mention it
Does the Surface 2 support WiDi?
Why does the sending device need more than Wi-Fi and the Wi-Di drivers? Thanks again.
It is a great idea but seems like spotty implementation. The Actiontec receiver is very competitive and should get widespread adoption if it works well for consumers. Interestingly, the protocol is found on some Android phones.