Wireless Display Adapter Disconnects

So I've just bought the Wireless Display Adapter and have the same problems with disconnects every few minutes actually, even with the device next to the TV. I'm disappointed that this forum has not thrown up any solutions or even helpful suggestions as to the problem. Has anyone actually contacted Microsoft Support regarding this issue?

Does Microsoft monitor what your putting here because these answers look like generic responses and have nothing to do with the issue. You are actually ignoring what the customer is actually telling you at points. This is an issue that most purchasers of this product are having. The wireless network has nothing to do with this product. There are also major lag issues with the product as well for the video quality. You can tell the video is being streamed to its connected devices. You can also see noise in the picture and there are audio glitches. The computer has the most up to date drivers and the display adapter has the most up to date firmware. What channel does this device work on? What kind of frequency does it work with? Is there a way to get a diagnostics log?

Microsoft is really starting to confuse me with their product line up. Now apparently there is another Miracast device sold in the Microsoft store called the Microsoft HD-10 Miracast Adapter. You can still buy both with no explanation as to why there is a need for two separate devices that do the exact same thing. There is the added NFC paring plate on the new one, but why do you need that when screen mirroring from most devices is just a couple clicks or swipes away. That could justify the increase in price if the unit wasn't larger and less mobile than the old one.

Could we get some form of roadmap on products before we spend our money? Are early adopters just beta testers for products that will be replaced? This isn't a kickstarter project. I fully expect the devices we purchase to work the way they are advertised.

We have 25 identical Surface Pro 3 units.  SOME of them exhibit this behavior, some don't.  We're thinking that since Microsoft used multiple sub-vendors, (including different regions, countries, facilities, etc..), there are very many 'versions' of the MS Surface Pro 3 and therefore a totally inconsistent hardware/'firwmware' (I know, it's really UEFI...).  If follows then, that some units will behave a certain way while others won't.

It would be wise at some point for Microsoft, (especially being such painfully inexperienced 'newbies' at hardware production), would do well to take a lesson from Dell.  When they produced and released hardware platforms such as the Dell Optiplex (desktop) series computers, they were absolutely consistent from the very first unit to roll off the line to the very last.  And even after the particular model was discontinued, Dell ensured continued customer support by stockpiling chips, PCB's, drive assemblies, and power supplies.  I experienced this phenomenon personally for about 10 years, (I have 30+ years industry experience, yet Microsoft is not just reluctant to listen to people like me, but downright, and reultcantly obstinent when it comes to re-examining your basic product roll-out and support initiatives and accepted behaviors!)

The Surface Pro 3 is most clearly, and most-obviously a product that didn't come close to passing muster for an anticpated roll-out, but was dropped on the public without care regarding compatibility, functionality, or even market sector feasibility, (Consider that it is simply the single-most fragile computer hardware in existence, yet Microsoft chose to market this to the 5th grade-to-12th grade education sector.  Our students purchased 274 units, of which nearly 60 had to be returned for a damage warranty replacement!  Why?  Because Microsoft had ZERO products available to protect the Surface Pro 3!!)

I think that every person who communicates on this and every other Microsoft-subjected forum would agree to at least three things:

1. Microsoft should NEVER have gotten into the hardware market place.
2. Microsoft needs to slow WAY DOWN in releasing products and updates and take a look at providing products and suites of products and operating systems that will actually work as advertised and documented when they are delivered!
3. Stop the marketing hype!  Who are you competing against?  MAC?!?!?  Seriously, MAC will never, EVER do the things that Microsoft does in a network/business environment.  

Sorry but I have to completely disagree with you on that point.  First Microsoft is in the hardware business for many many years for periphericals (mouse, keyboards, etc) delivering high quality products.

My Surface Pro 2 is simply the best device and most solid one I have purchased in 20 years of computing.

As for the Wireless Display Adapter, it seems better now.  I can't remember last time it disconnected. Maybe one of the firmware update of the Surface fixed that.  Lets hope its permanently fixed.

Dan

I'm with you...

The support tech on this forum has little clue as to what the users have been saying.  Apparently te thread title is not enough for him to understand that:

A:  This is NOT a wireless networking issue, it is a Wireless DISPLAY issue!

B:  Updating drivers, getting rid of viruses, downloading drivers from the 'manufacturers' site is a statement beyond idoicy when the manufacturere is Microsoft!

I have a continuing, and escalating relationship with Microsoft.  I will be shooting for the upper-eschelon Veeps to finally try to talk them back down to Earth, where people buy technology to be productive, not to become technical engineers who spend over 25% of their days trying to figure out why updates, drivers, and hardware from Microsoft has caused significant partitions of otherwise productivity systems to be rendered inoperable.

Maybe we can start a new web blog site :Love to Hate/Hate to Love-> Microsoft, where installing their products in your company will give you limitless job security!