Q: New Retina Macbook pro 13 Haswell system hang/unresponsive

Just had my new   late2013 13 inch rmbp 8gb ram 256 ssd arrive, had it power on for 2 days in a row and the issue happened twice. Any updates from apple? Thanks

Hope you're right that it's a simple software fix.  I'm having the same problem after saving for a year to buy a late 2013 MBP.  First Apple computer in 20 years that I've had trouble with right out of the box... 

Just got confirmation from apple support thats is software related issue, although the guy that i chat with was not aware of the issue at first i explained it, so he was able to do a little reseach and thats what he posted it " 110% " that is was a software issue related to the firmware that runs the keyboard

Just got mine yesterday. Haven't used it that much. Hope it does not have the bug. In any case, I am really hoping that Apple releases a fix. This is my first time buying a mac and am not happy with the experience. When one pays top dollar, stuff should work out of the box. Another reason why Apple should actually SPEND its $135 Billion cash reserves!

I'm experiencing the same problem. 256gb / 8gb  13 inch

With respect, this is clearly a software/firmware issue. I have over 10 years experience as a technician and this problem is without doubt firmware/software.

I'd be more concerned about the image retension issue if I were you guys. Clearly it's not being fixed and that's hardware

I have the same issue of unresponsiveness. It happens several times a day. I´ve been using my new Macbook Pro only for few days.

My specs:

Macbook Pro

Retina, 13-inch, Late 2013

2,6 GHz Intel Core i5

8 GB 1600 MHz DDR3

512 gb

Annoying!

I experienced the same problem for Model A1502 Family Z0QA, MacBook Pro Retina Late 2013 2.4GHz CPU 16GB Memory 128GB SSD

The system freeze 3 times during my first day usage. Roughly every 5 hours, keyboard/trackpad not reponsive, need hard power off to resume to normal.

My work load is very small, just writing emails and surfing the web, and the machine is cool, not related to hardware overload.

Just bught my 2013 13" 8GB, i5 Haswell, 256GB SSD Retina, the $1499 config, and have had it 3 days, it froze when I was browsing, with Safari.  Keyboard/track pad unresponsive.  Power button fortunately was!  Long press to hard reset, not a good thing to do at all!  I sure hope we are not seeing a general QA issue with Apple products.  I now have (4) Macs, varying flavors and vintages, back to the early 2007 MBP, still works, I put a 128SSD in it years ago, if the left fan hadn't died I'd still be using as a daily usage device.  I'm shocked this was not caught in four corner testing by Apple QA!  Very disappointed.  I was quite happy that my home is now completely MSFT free.  Having doubts again, damnit, can anyone do this right anymore!  I'm a computer engineer of 32 years, clearly a driver and/or f/w issue, and given that it's happening right out of the box, it should have been caught!  What would Steve say!?

Just spent some time in the console logs, and there is nothing obvious.  I do see alot of these going on:

11/3/13 12:21:20.000 AM kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)

These are being produced about every 15-20 seconds, filling up the log nicely.... 

May be related...

What would Steve say!?

You are fired! Let's find a new responsible team now.

@loktibrada

Precisely.

Since the same questions are coming up and since there are a few new ppl watching this thread: Here is a summery of what we know so far and better yet, how to prevent those freezes while waiting on a patch. https://discussions.apple.com/thread/5509561

Hi Every One,

I've tried to install Mountain Lion and Mavericks (Build 13A603 from App Store) in order to make sure it's a software related issue.

Unfortunately, both are not allowed to be installed on the latest 13 inch MacBook Pro.

I think we all have to wait for the system patches or just return it.

I choose to wait until the due date.

Ok. No freezes as of yet but do see a lot of the erros mentioned by other users in the console log...