Not detecting Thunderbolt Display

Hello,
I just purchased the Thunderbolt Display and there's a problem when I try using it with Windows 8 on my Macbook Pro.
The funny thing is that the first time I connected it (2 days ago), it WORKED. Then yesterday it didn't work at the beginning, but after a couple reboots (switching back and forth from Windows and OS X - where it obviously works every time), it somehow showed up in Windows again.
But today, I rebooted the system like 30 times already, no success. The display obviously continues to work in OS X, but it never gets even detected in Windows 8. Note that other Thunderbolt Display things work (ethernet, USB ports etc.).
How to solve it?
I already tried doing PRAM & SMC resets, no improvement. And yes, I always connect the display BEFORE I turn on the MBP. I also don't have anything else connected to the display via it's ports.
Thanks in advance,
Damien

Disconnect the Thunderbolt cable and then Reconnect it. Sorry to tell you but Apple still, in 2013, has not figured out how to do multiple displays on their notebook computers. Kind of odd for what is claimed to be "The Most Advanced Operating System in the World".
That is one reason I bought a Dell Latitude E6420 notebook for work and leave the Mac at home and use it as just a notebook. The Dell has no problems using an external screen as its main screen, as a second screen (Extended Dsktop) and its own screen when no other monitor is connected then back to using the external monitor when it is connected. All that with the internal screen shutting off when the external is setup as the main screen, even with the lid open.
Good Luck & Best Wishes.

Similar Messages

Macbook not detecting Thunderbolt display

I have a strange behavior with my brand new TB display. I unpacked it the other day, hooked my 15" MB to it and everything ran smooth. Then before going to sleep I shut down the system. At that time I had been running the TB as my main screen (manubar was on the TB display and not on the MB). When I then wanted to restart the computer it would not detect the monitor and no matter what I do it will not turn the display on. I have tried so many things also ran disk utility and reset p-ram but nothing helps. I noticed one strange thing, I connected my iphone to my TB displays usb port and it would not charge until I disconnected the TB plug from my MB, then it would give the ping sound and start charging. The MB charging plug works and lights up when connected so there is power on the display.
My system is running latest version
Anyone whit a solution?

Disconnect the Thunderbolt cable and then Reconnect it. Sorry to tell you but Apple still, in 2013, has not figured out how to do multiple displays on their notebook computers. Kind of odd for what is claimed to be "The Most Advanced Operating System in the World".
That is one reason I bought a Dell Latitude E6420 notebook for work and leave the Mac at home and use it as just a notebook. The Dell has no problems using an external screen as its main screen, as a second screen (Extended Dsktop) and its own screen when no other monitor is connected then back to using the external monitor when it is connected. All that with the internal screen shutting off when the external is setup as the main screen, even with the lid open.
Good Luck & Best Wishes.

Mac Mini does not detect DVI display on startup

Okay, I have a Pre 2009 Mac Mini 2Ghz Core 2 Duo. My monitor is a Westinghouse Digital LCM-22w3. The display is hooked up through DVI. When I start or restart the mac, it seems that it does not detect the display is plugged in. I have to wait for OS X to finish booting to either put the mac to sleep and bring it out of sleep or unplug the DVI cable and plug it back in to get the display on. If I hook the display via VGA using the VGA to DVI converter there is no problem. I have tried resetting the NVRAM but that does not fix the problem. I would like to get this fixed so I don't have to switch cables to be able to boot my boot camp windows install. Any help is appreciated. Thanks!

Following some investigations the problem appears to be with the power saving features of the monitor.
The MAC mini knows that the monitor is connected but the monitor puts itself to sleep.
The problem appears only when you use a single link DVI-D cable.
These are the ones with two blocks of nine pins with one large blade.
If you use a Dual link DVI-D cable (twenty four pins and one blade) the problem resolves itself and the display is active from power on.
It looks like the mini or the monitor is using one of the pins from the middle block of six for some reason.
Anyway, good look with this, I had a couple of spare DVI cables from when I was trying to get my original G4 mini working with my TV.
Regards
Gavin

Thinkpad Edge S430 - Windows does not detect external display connected via HDMI

On a Thinkpad S430 with HD4000 integrated graphics, an external display connected via a HDMI cable is not detected at all when using Windows. The system is fully updated as of the time of posting this message, both via the Lenovo Update tool as well as Windows update.
The Intel driver version is 8.15.10.2696. It appears that this is the latest version, since it does not offer an update when I try to auto-update it via Device Manager.
NB: I am running Ubuntu 12.04 with kernel 3.4.0 on the same machine, and the external display works perfectly fine with this software configuration.
Hence I think that it's very likely that this is a Windows-specific driver issue.
Would Lenovo happen to have a driver update in the works? Alternatively, I will be thankful for any suggestions about possible resolution of this problem.

skn2011 wrote:
My Macbook Pro notbook 13.3" does not detect external display throught it's mini display port to HDMI connector when connected to Sony Bravia 32" LCD TV.Can anyone help me get the answer as i tried reading everywhere on internet and none does not seems to work.Please help me out guys.
Are you using the Apple adaptor or a 3rd party

Hi, my computer is not detecting any display, i'd been having this problem since i connected my computer to a tv, the tv burned up, and after that my port doesn't detect anything at all?? Was that the problem can I fix it.I have the lion 10.7.5.

Hi, my computer is not detecting any display, i'd been having this problem since i connected my computer to a tv, the tv burned up, and after that my port doesn't detect anything at all?? Was that the problem can I fix it.I have the lion 10.7.5. Dont know if I changed settings or something.

Hello,
It isn't the fw in Network you want o use or look at, that's for something completely different.
My first suspect is the Power Adapter on the LaCie has gone.
At the Apple Icon at top left>About this Mac, then click on More Info, then click on Hardware>Firewire, what is listed there?
Reset the Firewire bus
If your Firewire or USB isn't recognizing any device. A solution which has worked for some whose hard drive became invisible in 10.4 was simply to follow these four steps to reset the Firewire/USB bus:
1. Shut the machine down.
2. UNPLUG the power lead to the computer and any firewire/USB drive or devices.
3. leave it for 10 minutes.
4. Connect back up and reboot.
http://www.macmaps.com/firewirebug2.html

Photo Downloader does not detect Thunderbolt connection. Help!

I am using Bridge CS5.1 on MacBook OSX 10.8.3. I bought a Seagate Thunderbolt Adapter which works with 2.5" eSATA hard drives (Seagate Backup Plus). Instead of connecting a 2.5" eSATA to this Thunderbolt Adapter to my Mac, I am doubling this thunderbolt connection as a CF card reader by swapping the eSATA portable drive with a CF to eSATA Adapter instead. Photo Downloader does not detect anything connected through thunderbolt!?
When the CF card or portable drive is connected via the TB adapter, it appears in Bridge and Finder. The Canon's Image Browser (Memory Card Utility) detects only the CF card (not the portable drive) as a Camera and downloads the images from the CF card via the thunderbolt adapter with no issues. I would prefer Bridge to download the images due how the folder names are created by Bridge. (I have been using Bridge for few years now and dont want to change the naming convention. Can't seem to find a way for Canon to name it exactly the same as Bridge. It does YYYY_MM_DD amd I cant get rid of the underscores in Canon's software)
How can I get Photo Downloader (File: Get Photos from Camera...) on Bridge CS5.1 to detect the Thunderbolt connection as a Camera?
Excuse my messy desk, here's a pic of the set up with the CF card plugged into the CF to eSATA adapter : and onto the Seagate TB Adapter. and the TB cable goes into the Mac

It works perfectly well. My issue is getting Adobe Bridge 5.1 to recognise the CF card via thunderbolt in photo downloader.
Despite having bought a MacPro just a few months ago I still have no Thunderbolt connection so i can't confirm this.
I do know Photodownloader has not changed a bit since it was presented long time ago and definitively needs a lot of improvement.
It is very possible that Photodownloader is not capable detecting thunderbolt connections and Canon software doing so does almost proof APDL does not do so.
You can try to dive in the user library (by default hidden, use menu Go and press option to reveal it) and in the folder preferences find and delete the Photodownloader plist file manual.
restart photodownloader and try again.
The other option is to use a USB 3.0 or Firewire (both also pretty fast).
The third option is to use Bridge itself for renaming the files you imported manual. Using the sort order creation date and batch rename use the option for shot date (yymmdd-number or other info) and either organize with stacks or create folders.
There is also a nice app (not free but cheap called 'big mean folder machine" from the same team that offers 'A better finder rename'.
Both offer plenty of options that makes life easier, such as producing folders with specific naming and order in no time

Not detecting external display after waking up MBP from sleep mode

I am a recent owner of a MBP and enjoying it. However, one problem that I can't seem to find a solution to is the external display problem after sleep mode.
When I first boot up the Mac and plug in my Dell external monitor via the mini adapter, there is no problem with detection or display. However, every time I put the MBP in sleep mode and then wake it up again, the external monitor does not "wake" up and my MBP only displays my normal screen on the Mac.
I tried to 'Detect Displays' to no avail and the only solution is unplugging the mini connection and plugging it back into the MBP for the MBP to re-detect the external monitor.
Although this is a quick fix in itself, I do not want to wear out the mini port by doing this every timeI come out of sleep mode. Any solutions so that the external monitor will detect the MBP waking up from sleep and display properly? Thanks!

And same problem here.
Using a MBP 2.66 i7 with a Dell 3008WFP that's connected to the MBP through DisplayPort. It works some of the time but once in a while (only been using the new MBP for a couple of days now) the monitor won't come out of sleep mode. Turning it off/on causes OS X to completely ignore the monitor. I was able to get this setup to work again by pressing 'Detect Displays' in the System Preferences pane but most of the times that doesn't help. The only sure way to get the monitor working again is by booting into Windows through Bootcamp, Windows is able to use the monitor, if I reboot after that OS X sees the monitor again.
Also saw a magenta line/stripe on the left side of my monitor and the monitor sometimes makes a buzzing sound when connected to the MBP through DisplayPort. That's what you get by using bleeding edge tech I guess :\ Only alternative is buying the mini-DP to dual-DVI connector but paying $99 just to be able to use an external monitor is rather insane. Besides that lots of users are having problems with this adapter.

Macbook will not detect external display

Was using a $7 aftermarket minidisplay port to HDMI cable with success for about 2 months with no problems detecting external display. Started having problems (it would randomly detect until it eventually would not at all) and tried all solutions I could find in discussion boards to no avail. I recently bought a $40 cable from the apple store and it worked fine for about a month and now it only recognizes my external display about 50% of the time (which is how the problem began the first time). Very frustrating! What is the deal here?

Did you have any luck resolving this? I have had exactly the same issue when updating the EFI Firmware to Version 2.8 (the latest for a Mid-2013 MacBook Air 6.2 model) - MBA61.0099.B12
I've tried flushing the NVRAM/PRAM and also resetting the SMC but no joy. I'm trying to drive an AOC Q2963 monitor using a display port connector. Annoyingly, I don't think there's a way to rollback to a previous firmware version.

MacBook Pro won't detect Thunderbolt display after sleep

I've noticed a rather anoying bug with Mavericks (or at least this issue only started after upgrading to the latest Mavericks) When the MacBook goes to sleep and I wake it up again, it no longer recognises the Thunderbolt display and USB devices attached to it. The only way yo resolve the problem simply is to remove the thunderbolt cable and re-insert it.
Has anyone else come across this or have any views on how to resolve more permanetly.
Many thanks
Stuart.

I have the same problem and I find it very annoying. There are many threads on the Internet (such as https://discussions.apple.com/thread/5602696) but so far no solution. :-(

Not Detecting External Display - 24" Gateway FPD2485W

Hi everyone,
I'd really appreciate any help I can get on getting my monitor to display at 1920x1200.
My setup:
Mac Book Pro 2.2Ghz
4Gb memory
128 M video memory - NVidia GeForce 8600M GT Memory Card
OSX - 10.5.2
Bios - MBP 31.0070.B05
External Display - 24" Gateway FPD2485W
What I've tried... all manner of plugging in the display, then booting up, then laptop then powering up display. I've applied the latest bios. I've run apple-opt-P-R at startup.
I haven't yet been able to get it to detect this display. Can anyone confirm that the 128M card can handle the local display plus a 1920x1200 display? From what I've read, I believe this is possible. Anybody got any other suggests for me to detect the monitor and set a display resolution higher than 1440x900?
Thanks,
Alan

Hi Mac Wise,
Thank you for your response.
I am using the DVI connection and it displays normally, but just can't detect the monitor. It gives me the default 15" MBP resolutions... do you get different behavior? I can't go higher than 1440x900.
Thanks,
Alan

Thunderbolt Does not detect my displays

I have a Late 2013 MBP 15inch... Thunderbolt port works with the ethernet adapter, BUT it will not with the Video adapter. The Displays will not even notice the connection...
Though when I disconnect the cable from the MBP, the screen goes to black for half a second as acknowledging that the disconnection has occurred, while the cable is connected, NOTHING appears int the Thunderbolt or Display info as connected...
What is funnier, is that trying the SAME video adapter and the SAME displays, on a 13inch late 2013 MBP worked PERFECTLY!!!
Any ideas? I have already tried reseting everything I could... I even reinstalled the system!!!
HELP!!!!

Please add a little more info such as how are you connecting and what happens so someone may be able to try to help.

Not detecting tv display when connected with Apple Mini-DVI to Video Adapte

I am connecting my macbook to my older tv using a Apple Mini-DVI to Video Adapter to an RCA (yellow video prong) and then into the tv. The red and white audio prongs hang loose, not hooked into anything on both ends. When I go into Displays there is no option for mirroring displays. I hit 'detect displays' but nothing happens. The Apple Mini-DVI to Video Adapter is brand new, just ordered it from apple. And I use the RCA cord all the time with other machines into my tv and it works fine.
Any help is really appreciated. Thanks!

Which generation MacBook do you have because at some point Apple dropped support for that adapter. Here is a link to a list of Apple adapters and compatible computer models:
http://support.apple.com/kb/HT3235

MBP not detecting external display

I encountered a strange problem today when I tried re-connecting my external monitor: it is not being detected by OS X.
I tried everything I could think of; I selected "detect displays" in preferences, I restarted the computer, I dis- and re-connected everything, I reset the PRAM, I tried connecting to a different monitor, and nothing seems to work. When I disconnect and reconnect the DVI cable, the laptop's screen flashes blue like it normally does, but nothing appears on the external monitor's screen. For the record I'm using the Dell 2209WA, and I haven't had any problems like this yet.
If anybody has any other suggestions as to what I should try doing, please let me know. Thanks!

Hey all, did a software update on my partner's mbp yesterday (10.5.8, security update 2009-006) and had the same thing happen where our external viewsonic display was no longer being detected. Plugging the cable in and out of the mini display port had the same effect already mentioned here where the mbp screen flashed blue like it was about to recognise the external display, but then nothing. Selecting detect displays from display preferences also had no effect. Tried resetting the PRAM and also the PMU, still nothing. So I shut down the mbp; disconnected the mini display cable; then turned off the viewsonic monitor at the power outlet and left it off for 10-20 seconds. Then I turned the viewsonic's power outlet back on, started up the mbp, turned the monitor on and plugged the mini display port cable in and the external display was back and working properly. Have shut down/restarted numerous times since then and it's all still working normally. Not quite sure how/why this busted in the first place, or why turning the viewsonic off at the power outlet seems to have fixed it, but it might be worth a shot for those experiencing similar problems... and it sure beats having to install/reinstall a different os version (which was going to be my next option)!

Macbook Pro not detecting external display

I can't seem to make this work. I'm using a MiniDP-DVI cable which is plugged into an DVI cable plugged into an external monitor. I know it works because I have tried it on other computers and it has worked on the Macbook (erratically).
I've reset the PRAM several times and it has not fixed the problem. I did it in this order:
1. Remove adapter from computer
2. Shutdown
3. Press Option Command P R until the second chime is heard.
4. Log on as usual
5. Reconnect adapter to MBP
This is what the system log states when I plug the adapter in:
Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x42732c0
Oct 27 20:47:01 SMBP.local WindowServer[80]: Created shield window 0x66 for display 0x042732c0
Oct 27 20:47:01 SMBP.local WindowServer[80]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003d
Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003e
Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003f
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 9 modes available
          Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9ccb, S/N 0, Unit 0, Rotation 0
          UUID 0x0000061000009ccb00000000042732c0, ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}
Oct 27 20:47:02 SMBP.local WindowServer[80]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00004333, unit 0, caps QEX|QGL|MIPMAP, vram 451 MB
          texture units 8, texture max 8192, viewport max {8192, 8192}, extensions FPRG|NPOT|GLSL|FLOAT
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003f: GL mask 0x8; bounds (2304, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003f
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003e: GL mask 0x4; bounds (2305, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003e
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003d: GL mask 0x2; bounds (2306, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003d
Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x68 for display 0x042732c0
Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x69 for display 0x003f003f
Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x6a for display 0x003f003e
Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x6b for display 0x003f003d
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0: Startup Mode 1280 x 800, CGSThirtytwoBitColor, Resolution 1, IOMode 0x80000000, IODepth 0x0, IOReturn 0x0
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display added
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display removed
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 9 modes available
          Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9ccb, S/N 0, Unit 0, Rotation 0
          UUID 0x0000061000009ccb00000000042732c0, ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}
Oct 27 20:47:02 SMBP.local WindowServer[80]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00004333, unit 0, caps QEX|QGL|MIPMAP, vram 451 MB
          texture units 8, texture max 8192, viewport max {8192, 8192}, extensions FPRG|NPOT|GLSL|FLOAT
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003f: GL mask 0x8; bounds (2304, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003f
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003e: GL mask 0x4; bounds (2305, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003e
Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003d: GL mask 0x2; bounds (2306, 0)[1 x 1], 1 modes available
          off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
          UUID 0xffffffffffffffffffffffff003f003d
Oct 27 20:47:03 SMBP.local WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Oct 27 20:47:03 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0; ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}; TransferTable (256, 3)
Oct 27 20:47:04 --- last message repeated 1 time ---
Oct 27 20:47:04 SMBP.local WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Oct 27 20:47:04 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0; ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}; TransferTable (256, 3)

I had the exact same behavior and log and I solved the issue by replacing the MiniDP-DVI adapter. I tried the "broken" adapter on another set of laptop+display and it was working there, so that made me think the adapter was ok, when apparently it was not.

I have a Mini DisplayPort to VGA adapter, then I purchased 3 VGA adapters: a VGA to HDMI, VGA to Component, and VGA to RCA. When I hook them up to my TV (I've tried multiple TVs) they do not detect a display, even when I click Detect Displays.

Does anyone have any suggestions on a solution for this? The only other Mini DP I found was a HDMI connection. I want to make sure I can connect to not only TV's via HDMI, Component or RCA, but also projectors (some of which may be older requiring a Component or RCA connection).
I'm using this Mini DisplayPort:
http://store.apple.com/us/product/MB572Z/A?fnode=MTY1NDA3Ng&mco=MTA4NDU0NjA
These are the VGA Adapters I'm using:
VGA to HDMI:
http://www.amazon.com/gp/product/B001OLCHJ6
VGA to Component:
http://www.amazon.com/gp/product/B000P3Q0YW
VGA to RCA:
http://www.amazon.com/gp/product/B000Y7T5UU
Any help would be greatly appreciated.

None of the three lower adapters pictured in your post will do you any good with your MBP.
1. The VGA-HDMI adapter does the reverse of what you want: it yields VGA output from HDMI input. The opposite is not possible; a VGA input does not contain all the information necessary to create an HDMI output. You'll have to get a direct mini-Displayport-to-HDMI adapter instead.
http://store.apple.com/us/product/H1824ZM/A/Moshi_Mini_DisplayPort_to_HDMI_Adapt er?mco=MTY3ODQ5OTY
2. VGA-Component: Lots of posters here when the MDP-equipped MBs and MBPs first came out tried adapters like this one with no success. What does work with the MDP (and a VGA adapter) is a converter box like this:
http://www.amazon.com/Startech-Component-YPbPr-Video-Converter/dp/B000G6Y0S6
3. VGA-Composite: This doesn't work with MBPs either. For Composite or S-Video output, you need a converter box like this:
http://www.amazon.com/PC-To-TV-Video-Converter/dp/B001CJOLBW/ref=pd_cp_e_2
or this:
http://www.startech.com/AV/Converters/Video/High-Resolution-PC-VGA-to-TV-Convert er-with-Remote-Control~VGA2NTSCPRO
These converter boxes will work fine in combination with your Apple MDP-VGA adapter.

Not detecting Thunderbolt Display

Similar Messages

Maybe you are looking for