Previous 1 6 7 8 9 10 Next 207 Replies Latest reply: Jan 10, 2015 3:39 PM by kavanagh.adam Go to original post
  • Juhaz Level 1 Level 1


    this helps a lot wiht Retina MBP. But sadly Aplle haven´t done anything to help older MBP. I have still same problem with HDMI and my MBP (17-inch, mid 2010).

  • greenone83 Level 1 Level 1



    I also have a strange hdmi-problem:


    - macbook air 11" (C02G2HS1DJYD)

    - osx 10.8.2 (12C60)

    - belkin screencast av 4 wireless hdmi


    when i connect any wireless hdmi system to my macbook air it seems like the output from the thunderbolt-hdmi-adapter collapses. its really strange.


    its the second wireless hdmi solution i tried and the result is exactly the same. it doesnt matter what i connect to the wireless receiver, a tv, a beamer... doesnt matter.


    since i tried two different wireless hdmi solutions and two different devices, i assume its the macbooks /osx's fault.


    setup that works:

    imac(10.7) -> dvi -> hdmi -> wireless hdmi transmitter -> wireless hdmi receiver -> beamer or tv


    setup that does not work:

    macbook air(10.8.2) -> thunderbolt -> hdmi -> wireless hdmi transmitter -> wireless hdmi receiver -> beamer or tv

    (signal gets lost over and over again)


    is there any way to debug hdmi somehow? to check what the macbook is putting out?

    has anyone ever had similar problems?

  • Drdul Level 1 Level 1

    Thanks for the helpful info. The PRAM reset worked for me. My external monitor is connected via MiniDisplayPort-to-DisplayPort, and initally all I got was two black screens (MBP and external monitor) with the cursor. I left everything connected and turned on, reset the PRAM and I'm good to go.

  • KenV54 Level 1 Level 1

    Guess what folks--


    With the new Apple software update dated October 30th for the newer MacBook Pro and Retina Pro, you're going to have to once again trash the from the main Library preferences directory, and the from the ByHost directory of the [youruser]/Library/Preferences, along with any onther windoserver plist files you find. It does work, once again, and will create new plist files which you don't have to remove. Remember to reboot after doing this.


    Doing a PRAM reset alone without removing the plist files did not work for me, even with the HDMI plugged in.


    This is supposed to be a Mac software (not firmware) graphics upgrade--I don't know what they improved, but it did reintroduce the HDMI problem.

  • JevGenius Level 1 Level 1

    Hi to every one.
    Sorry for my poor english.


    I use Apple almost 2y and MS over 18y.


    After KenV54 solution i wasn't get success by deleting *windowserver* files. BUT, i was find file

 *.plist and deleted it. after that my MBP 13" 2010 start work nice with HDMI.


    houpe it will help to you.



  • skeeter2u Level 1 Level 1

    Hi Ken,

    I have a MacBook Pro Retina 15in. running OSX 10.8.2.  I'm trying to use HDMI output to a Philips 50PFL3807/F7

    HD tv. 


    I've removed all the prescribed windowserver.xxxxx.plist files, but still no input detected by the TV.



    Any other folks had this problem?




  • KenV54 Level 1 Level 1



    At this point, I don't really know. And maybe the Phillips has something to do with it.


    See my post of Novermber 10. The latest software update--not a complete OS update--for the MBP Retina seems to add the windowserver plist files back in again, and they have to be re-deleted. Make sure you have deleted anything that looks like a Windowserver plist both in the root Library Preferences and in any User Library Preference directories and Preferences ByHost directories.


    Also see JevGenius's post above about deleting a different file, as well.


    One other thing to try--after you have done all these deletions, reboot with the HDMI cable plugged in, and on reboot do the PRAM reset, option-command-R-P, still with the HDMI cable plugged in. That has worked for some people.


    Hope it helps. Let us know here.



  • skeeter2u Level 1 Level 1

    Well, I tried everything you said, KenV54: deleted anything in the root and user library preferences folders that even hinted of windowserver and ended with .plist.  I also did what JevGenius said was needed, then I did the reboot for the PRAM reset with the HDMI connected.  Finally, I even switched to another tv, a Samsung LN46, but the result was the same.  I get an error message on the Samsung that says input mode not supported.  I even see my laptop desktop for a few moments before the tv goes blank except I get the mode not supported error.  This is friggin ridiculous!  Doesn't apple ever test these things?  I have a colleague with an HP windows machine and, you guessed it, he plugged my tv into his hdmi display port and it worked instantly.. arrrghhh and embarrassing. 

  • KenV54 Level 1 Level 1



    It is frustrating, indeed.


    If you still have AppleCare support on your Retina MBP I'd suggest you use it, even pay the $49 if you have to for a single support issue. They can run some diagnostics and maybe come up with a different answer, but it will take a few days. Are you near an Apple Store? Sometimes the "Geniuses" can help.


    Otherwise, you can try reinstalling the OS, but I doubt that will work unless you do a "clean install" which means reinstalling all the thrid party stuff, unless you have everything backed up on Time Machine.


    I don't understand Apple either. Maybe they're losing it. Look at their stock these days.



  • nunorasheed Level 1 Level 1

    apparently not even doing a clean install of mac OS mountain lion 10.8.2. makes my external HMDI monitor (HP w2207h) work.

    i have the most recent 11' macbook air with the same problem as you guys.

    tried everything... and yesterday i've made a hard format on my hd and installed a clean copy of mac os 10.8.2.

    external monitor still doesn't work at its full potential, just works @ 720p.


    i just hope apple can sort this out... i'm regreating buing the MBA 11', since before i had an MBP 13' mid 2010 where everything worked just great!

  • skeeter2u Level 1 Level 1

    I'll give the AppleCare folks a hollar and see if they can help.  Thanks for all your ideas and patience.


    QC on Apple products does seem to be compromised under Tim Cook's regime.  QC was the primary reason I moved to Apple a few years ago, so I hate to see them lose this competitive edge. 



  • Bowie Salvatore Level 1 Level 1

    I installed apple's latest update and it worked for me, I can now connect my MacBook Pro via HDMI perfectly, as per before the 10.8.2 update. I'm not sure if it'll work for everyone of you, but it definitely solved my problem. My plist files are still intact. Thanks

  • alfredandrew Level 1 Level 1

    Oh dear... and now this is really irritating and frustating.. after I had clean install on my 13 mid-2012 MBP with 10.8.2 now I'm facing HDMI issue again after keychain issue udpating from 10.8.1 to 10.8.2 and now with HDMI????... was excited to test my newly bought mini display port HDMI but it doesnt work on my external display this is really really annoying

  • KenV54 Level 1 Level 1

    See earlier posts regarding 10.8.2 and the recent additional "software update" for the Retina MBPs which has no number associated with it.


    In some cases, apparently, installing 10.8.2 cleanly can cause the HDMI problem, and in others it can cure it. The same thing applies to the addtional "software update"--I don't know exactly what that update does.


    In any case, all I know to do is to find and delete all Windowserver plist files (however much extra stuff may be in the file name) in the root Library Preferences, and in your user Library Preferences and User Library Preferences/ByHost directories. Some people have two such files, some several files. Once they are put in the trash, reboot the computer, and try doing a PRAM reset on that reboot.


    If that doesn't work, then the problem is related to something else, and I don't have a solution to it. You will have to call AppleCare, maybe spend $50 for the incident if not still covered, let them gather information from your computer, send it to their engineers, and get back to you with an answer. It's a painful process, but the one thing I have learned from AppleCare is that they don't consider the incident closed until the problem is solved.


    I appreciate that some here have given me "ownership" of this thread, and I am humbled by it. The sad truth is that I really have no technical expertise beyond what AppleCare has told me, and in this case am the proverbial "one trick pony" who only knows the Windowserver Plist file solution. :-)

  • Bowie Salvatore Level 1 Level 1

    Hey guys, to all those facing this problem, I think I may have just found a solution, and that does not involve deleting anything for those uncomfortable with deleting original files from their Macs. I'm using the highest end Macbook Pro with Retina Display and this method worked for me, it should work for all of you guys too, who knows, give it a shot!


    Here's what I did, I went to Apple support page and downloaded the 10.8.2 Combo update and the Supplemental Update for 10.8.2. Installed them, and restarted. I hooked it up to my HDTV and it worked. If it doesn't work for you then I wouldn't think it's a software problem because for some of us out there, 10.8.2 seems to be working just fine. I think it's pretty obvious if it's not a software problem it might very likely be a hardware problem, which Apple Care should cover. I haven't tried the .plist method yet, don't get me wrong, I'm sure it works, but just for information, this issue is not evident in all Macbook Pro with Retina Display users. Cheers and good luck!

Previous 1 6 7 8 9 10 Next