Keyboard/trackpad Unresponsive during Windows 7 Install

I have spent days scouring online forums troubleshooting issues that have arisen at virtually every step of the process. There seems to be a whole slew of issues people are having in addition to my own.
I had to try many workarounds to resolve the issue where Boot Camp 5 gets confused over whether you are installing the 32 or 64 bit version. Really dumb stuff... that should never have released in such a disjointed state.
You shouldn't have to hack such massively mainstream products just to get them to work. I have a job! But installing Microsoft apps is a full-time job itself. Are they out to lunch? Did Apple completely shut down? From what I'm reading they appear completely disengaged from their products. Tons of threads over tasks that should be simple. The slightest variation derails the installation process. It various from mac machine models, right side usb ports vs left side ports. This is a very expensive and time consuming joke being played on us consumers.
I am now CURRENTLY stuck.....
I have a new MacBook Pro 15" retina. I finally ran Boot Camp successfully and I downloaded the Apple Support Software although its location is a mystery. I get stuck at the very first installation window (Windows 7 Premium) asking to select the language. My keyboard and trackpad are unresponsive. I am NOT talking about wireless devices which is an issue flooding other threads.
I have to hold down the power button to get out of it. And after a couple of attempts the entire 5-hour long Boot Camp installation get undone and my Windows designated partition returns to being empty. Is there no pride in their work? Why burden their customers with their problems? Is their only demographic mac geniuses?
I have Windows 7 on dvd which I put on a thumb drive after learning how to convert it to an ISO image, a step MS is apparently too lazy to do.  It took only an hour to do but a full day do discover what the problem was.
None of this would even be an issue if I didn't need Windows. Apple used to be able to run anything on its own. What happened?

Hi Craig,
Apple advice is to use USB-connected keyboard and mouse during installation of Windows.
+"The drivers for your wireless mouse and keyboard are not installed yet, so you cannot use them. The use of a wired mouse and keyboard is required to install Windows. Once your installation is complete, you can install the Apple Windows drivers off your Mac OS X DVD. Then, pair the wireless mouse and keyboard to your system using the Bluetooth Control Panel."+
http://support.apple.com/kb/HT3777
Any PC- or Apple- USB keyboard/mouse should work.
If you don't have such try to borrow from a friend or colleague.
Regards
Stefan

Similar Messages

  • Black screen during Windows install

    Hello,
    I have a late 2012 27-inch iMac with the GeForce 680MX 2GB graphics card. I'm trying to install Windows 7 or Windows 8 using Boot Camp, but neither works.
    In either case, I can use the Boot Camp Assistant to create a bootable USB install disk, download the latest Windows support software from Apple, and partition the drive to allocate space for the Windows installation.
    As soon as I partition the drive, the iMac restarts and tries to boot into Windows. But the only thing I ever see is a black screen (no blinking cursor), no matter how long I wait.
    This seems like the exact same issue that plagued the late-2009/mid-2010 iMacs,
    http://support.apple.com/kb/TS3173
    In other words, it looks like the drivers included with the default Windows install disk don't work on the late 2012 iMac, at least not when configured with the 680MX. 
    Since this looks like the old problem but Apple doesn't appear to have provided drivers for the new iMac yet (the older iMacs above used ATI graphics, not NVIDIA), I tried to add the latest NVIDIA notebook graphics card drivers to the Windows install disk using the directions here,
    http://superuser.com/questions/501812/corrupt-graphics-during-windows-8-installa tion
    In particular, I used these drivers,
    http://www.geforce.com/drivers/results/55125
    They're not explicitly supporting the 680MX (I couldn't find any drivers for it in NVIDIA's website) but they do support the 680M and a whole slew of other cards. Thought it was worth a try.
    Anyway, that didn't do the trick. Still the black screen for me.
    Any ideas? Have others had this issue with the new iMacs?
    Thanks

    OK, I figured it out.
    You know how the Boot Camp Assistant gives you three options? Create Windows Boot Disk, Download Latest Drivers, Install. You basically need to do all three at once, from scratch.
    I'm not sure exactly when in the last couple of months, but Apple updated their drivers. A few days ago I gave this another shot. Initially I tried using the USB stick I had previously created, but using some of the links at the first post above, I tried to inject the new NVidia drivers provided by Apple. That didn't help. I got the black screen and all that all over again.
    But then I just tried to start from scratch, remaking the USB stick while simultaneously downloading the drivers. It then also asked me if I wanted to install a new helper tool. I never got that prompt before. Either that tool solved it, or when it was creating the boot disk now it was injecting the new drivers itself in some different way.
    Whatever it was, try starting from scratch and going through all the steps and you might be successful in classic "it just works" Apple fashion. Took them a couple of months, but they got there.

  • PowerBook G4 15 Keyboard not working during Leopard install

    I need help!
    I have a powerbook G4 I wanted to sell. I was looking on amazon at a few reviews, and I found a MacBook Pro review that said how to do a reset of the entire computer. I was excited, because I wanted to sell, and I did it. Here is what it told me to do:
    "Instructions for resetting a Mac computer to factory specs.
    First, you need to reboot the machine in single-user mode.This will start the computer up in a text-only terminal.To start up in single-user mode,turn the computer on while holding down the Command and "S" keys until the screen begins to show text.
    Eventually,the text will stop loading,and you'll be left at a prompt with the word "root". Once you're there,you type in a few commands.Make sure you type it exactly as I have written it, and hit the Return key at the end of each line:
    Type:
    mount -uw /
    What we did here was tell the computer to make your hard drive readable and writable. Next you type the command that will erase all of the users' data.I assume you want to erase all personal data,since you want the computer to start up as though it's brand new.
    Type:
    rm -rf /Users/*
    The above command says to remove absolutely everything in the Users folder (make sure you type shift-8 to make the asterisk symbol).
    Now, type this:
    cd /var/db/
    rm .AppleSetupDone
    rm .TimeMachine.Cookie
    rm .TimeMachine.Results.plist
    rm .com.apple.iokit.graphics
    rm -rf dhcpclient
    rm -rf samba
    Basically, these are settings and preference files for some programs on a Mac, and we want those to be reset when the computer turns back on.The most important file to remove is the .AppleSetupDone file (and yes, it does start with a period). The computer thinks you're turning it on for the first time.
    We're done, so you've got two choices: if you want to shut the computer down, type:
    shutdown -h now
    This will shut down the computer and make it ready for the purchaser to set up the computer and register it.
    If you want to reboot the computer (to check out your handy work), type:
    reboot
    Press the return key."
    Now, when the language slideshow appears (the leopard install video), after that, I cannot use my keyboard to press enter, or type. It makes the sound that is made when you cannot type, so it is not a hardware issue. I cannot get past the registration, so that is not it either. Help!
    Powerbook G4 15"-2005 model
    Backlit Keyboard
    1gb RAM

    Tough without the Install disc, but some things to try...
    Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
    /sbin/fsck -fy
    Repeat until it shows no errors fixed.
    (Space between fsck AND -fy important).

  • Blue Screen during Windows install on SATA Raid1

    Hi Folks!
    I have a BIG problem with my brand new Eclipse SLI.
    I can't install Windows (tried Vista and XP x64). It crashes already in the beginning!!! 
    I'm not an OC,yet so all my settings are like default or AUTO. Only my memory I set to 1600 through automatic settings.
    Flashed in a brand new 1.6 BIOS.
    Now, anytime I start the Windows setup if crashes with a blue screen when it comes to the point it tries to access the hard discs.
    I was already able to set up a new partition and then Visat was extracting files. But after a few minutes (1% finished) it crash.
    The blue screen indicates that it had problems to write a file.
    Thing is ... it's always at different times, but still at the beginning of the setup. Sometime it don't get the setup even running.
    I tried the Drive Booster RAID and the JMicron. Always created a new RAID1!
    Sometimes the board freezed even by entering the BIOS.
    I already figured it my be to hot.
    Here my temperatures.  CPU: 28- 35C, IOH: 50-68C, System: 35C
    But I already read that IOH temperatur seems normal.
    So what's the problem?
    PLEEEEEAAAASSEEEEE HEEEEEEEEEELP !!!! 

    Thanks!
    Found myself a solution. Deactivated all additional features in the BIOS. Now it'S working even with 1600 RAM frequency.
    Trying now to still do some OC without getting into the same trouble.
    Jan.

  • During Windows install, says the Bootcamp Windows partition is incorrect file system and won't install

    I had another Macbook Pro retina which I installed Windows 8 on with no problems via bootcamp.  I just updated to the late 2013 model of the Macbook Pro, and attempted to do the same thing but have had problems.  I create the partition for Windows with Bootcamp, restart the computer, and after I enter my security key in the Windows installation screen it comes to the screen where you have to select the appropriate installation drive.  When I select the drive I created for Windows, it says that it can't install due to the file system.  I have no idea why I'm having this problem because I had done this once before....I can't for the life of me figure out what's wrong and I'm at a loss.
    If anyone can point me in the right direction I will greatly appreciate it...also let me know if there are differences from the early 2013 model and late 2013 model that would've created this problem.  Thanks!!
    Robert

    Well, here is what happened...
    Somehow in making a Windows partition then removing the partition so many times I created an error where it only showed 1/2 of my hard drive...like it was starting to create the second half for the windows side and ran into an error.
    So this turned out to be a blessing in disguise, because what I had to do was go to "Command + R" when I was starting up and format the entire drive, all 500 gb.  This formatted the whole drive and must've erased whatever was causing the trouble.
    Of course, then I had to reinstall OS X, and reinstall my Time Machine backup, but then I opened bootcamp and created the Windows partition again.  This time, when I ran the EFI installer you were referring to on the far right (which I had tried before), it allowed me to click next and continue once I selected the Windows partition.  Thank God!  It must've fixed whatever file system error was hanging it up there every time....because it's installing now.
    What I would suggest if all else fails, just format the whole dang thing.  Then try from square one and see if you can install

  • Mac stuck during Windows installing

    I failed to install Windows on ny Mac book Pro, using boot Camp and Windows 8 cd. Now the screen is black and showing this message: " no bootable device -- insert boot disk and Press any key". How do i det back to normal Mac ox? It keeps ejecting the cd..

    try the solution posted by kunu here and report back
    https://discussions.apple.com/thread/5105056?tstart=0

  • X79A-GD65 8D - Won't detect drives during Windows Install

    As the title suggests, Windows installer refuses to detect the SSD/HDDs in my system. I'm guessing I need to preload a driver but Im completely in the dark about what driver.
    Anyone have any insight?

    RAID Mode on the Intel Controller, correct?
    http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2101&DwnldID=20625&ProductFamily=Chips%C3%A4tze&ProductLine=Chipsatz-Software&ProductProduct=Intel%C2%AE+Rapid-Storage-Technik&lang=deu

  • Can't use mouse/keyboard/trackpad when waking iMac from sleep mode

    Basically as the title says. When I wake my iMac from sleep mode I am unable to use my keyboard/trackpad/mouse during the login window. Once the screen goes black by itself, after a minute or so I can then log in properly.
    Yes the keyboard/mouse/trackpad are all connected when it wakes from sleep as I can use any of them to wake it from sleep, I just can't move them or type with them in the login window.
    Processor  3.4 GHz Intel Core i7
    Memory  24 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 680MX 2048 MB
    Software  OS X 10.8.5 (12F37)

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, or by corruption of certain system caches. 
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and  Wi-Fi on certain models. The next normal boot may also be somewhat slow.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • TS5296 MacBook Pro (Retina, 15-inch, Late 2013): Keyboard and Multi-Touch trackpad unresponsive

    Brand new Macbook PRO Retina 15inch. (1 day old) Running 10.9
    EFI 1.2 installed.
    Keyboard/trackpad hangs when using the left USB.
    The EFI update 1.3 apparently fixes this issue for the 13inch macbook pro.
    I have a 15inch macbook pro. The EFI update 1.2 does not resolve this issue for me.
    Whenever I plug something into the left USB, after the 2nd or 3rd time, the keyboard and trackpad become unresponsive. To get the keyboard/trackpad back again, I must restart the machine.
    This is what the consol says:
    Nov 12 11:29:56 leaf kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2
    Nov 12 11:29:56 leaf kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    Nov 12 11:29:56 leaf kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    I cannot install the EFI update 1.3 as I get an alert "This software is not supported on your system." I assume because it was made only for the 13inch.
    Is this a hardware or firmware issue? If it's only firmware, why does this issue only affect some users? If it's hardware, should I just return this macbook?

    I can reproduce the behavior at will. I just have to plug in the tablet on the left USB board, reboot the tablet, disconnect the cable and reconnect. At that moment the trackpad and keyboard will both freeze.
    This is the complete sequence of console logs I have
    20/11/13 22:58:38,000 kernel[0]: considerRebuildOfPrelinkedKernel prebuild rebuild has expired
    20/11/13 22:58:38,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=544[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 22:58:38,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=550[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 22:58:38,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 22:58:38,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=551[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 22:58:38,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    20/11/13 22:58:38,915 hidd[71]: MultitouchHID: device bootloaded
    20/11/13 22:58:40,401 WindowServer[105]: disable_update_timeout: UI updates were forcibly disabled by application "Trasferimento file Android" for over 1.00 seconds. Server has re-enabled them.
    20/11/13 22:58:40,957 WindowServer[105]: common_reenable_update: UI updates were finally reenabled by application "Trasferimento file Android" after 1.56 seconds (server forcibly re-enabled them after 1.00 seconds)
    20/11/13 22:58:52,000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xb400 ****
    20/11/13 22:58:58,187 sandboxd[556]: ([177]) mds_stores(177) deny file-read-data /private/var/root/Library/Preferences/.GlobalPreferences.plist
    20/11/13 22:58:58,393 com.apple.IconServicesAgent[303]: main Failed to composit image for binding VariantBinding [0x1e3] flags: 0x8 binding: FileInfoBinding [0x2ed] - extension: jpg, UTI: public.jpeg, fileType: ????.
    20/11/13 22:58:58,394 quicklookd[558]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x203] flags: 0x8 binding: FileInfoBinding [0x103] - extension: jpg, UTI: public.jpeg, fileType: ???? request size:128 scale: 1
    20/11/13 22:58:58,454 com.apple.IconServicesAgent[303]: main Failed to composit image for binding VariantBinding [0x1e5] flags: 0x8 binding: FileInfoBinding [0x345] - extension: pdf, UTI: com.adobe.pdf, fileType: PDF .
    20/11/13 22:58:58,455 quicklookd[558]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x403] flags: 0x8 binding: FileInfoBinding [0x303] - extension: pdf, UTI: com.adobe.pdf, fileType: PDF  request size:128 scale: 1
    20/11/13 22:58:58,457 com.apple.IconServicesAgent[303]: main Failed to composit image for binding VariantBinding [0x1e7] flags: 0x8 binding: FileInfoBinding [0x2ef] - extension: txt, UTI: public.plain-text, fileType: ????.
    20/11/13 22:58:58,457 quicklookd[558]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x603] flags: 0x8 binding: FileInfoBinding [0x503] - extension: txt, UTI: public.plain-text, fileType: ???? request size:128 scale: 1
    20/11/13 22:58:58,518 com.apple.IconServicesAgent[303]: main Failed to composit image for binding VariantBinding [0x1e9] flags: 0x8 binding: FileInfoBinding [0x347] - extension: pdf, UTI: com.adobe.pdf, fileType: ????.
    20/11/13 22:58:58,519 quicklookd[558]: Warning: Cache image returned by the server has size range covering all valid image sizes. Binding: VariantBinding [0x803] flags: 0x8 binding: FileInfoBinding [0x703] - extension: pdf, UTI: com.adobe.pdf, fileType: ???? request size:128 scale: 1
    20/11/13 22:59:06,399 Console[561]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
    20/11/13 22:59:53,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 22:59:54,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    20/11/13 22:59:54,099 hidd[71]: MultitouchHID: device bootloaded
    20/11/13 23:00:06,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:00:06,000 kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    20/11/13 23:00:06,659 hidd[71]: MultitouchHID: device bootloaded
    20/11/13 23:00:32,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:00:45,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=575[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:00:46,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=581[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:00:46,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=582[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:00:46,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:00:46,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:00:46,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:01:33,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=588[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:01:33,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=594[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:01:33,000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=595[ksadmin] final status 0x0, allow (remove VALID)ing page
    20/11/13 23:01:33,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:01:34,000 kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    20/11/13 23:01:38,604 WindowServer[105]: disable_update_timeout: UI updates were forcibly disabled by application "Trasferimento file Android" for over 1.00 seconds. Server has re-enabled them.
    20/11/13 23:01:39,393 WindowServer[105]: common_reenable_update: UI updates were finally reenabled by application "Trasferimento file Android" after 1.79 seconds (server forcibly re-enabled them after 1.00 seconds)
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe0004051 - retrying
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retrying
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest returned error 0xe000404f (interface 1, reportID 0xac, payload 2
    20/11/13 23:01:48,000 kernel[0]: AppleUSBMultitouchDebug: _deviceSetReport returned an error in configureDataMode
    Disconnecting the tablet doesn't resolve the issue. A reboot does. I still have to try if the workaround posted by Apple for the MBP-13 Late 2013 (close the lid and reopen after a few minutes) would work here too.

  • Keyboard and Trackpad Unresponsive

    I recently had to replace a failing harddrive in my early 2008 MBP and afterwards everything worked fine. I then installed VMWare with Ubuntu everything worked fine, then I tried to install Windows 7 and afterwards my trackpad and keyboard are unresponsive. I first opened it back up to make sure everything was connected and it was, everything still unresponsive. I then uninstalled VMWare thinking it was a software problem, still didn't work. I finally decided to do a clean install of Lion and that aso didn't work, lastly I opened it back up to make sure everything was still connected which it was. What's odd is that the power button works just fine and it seems to be connected to the same thing. Is there some sort of connection inside that I missed? What can I do to try to fix it? Thanks!

    Also external mouse and keyboards work fine. When I log in without usb keyboard pluged in it asks me to setup a bluetooth keyboard.

  • HELP! In middle of upgrade to windows 8 and keyboard/trackpad stopped working!

    Hey all, new mac user here. Just bought a new macbook air 13" 2014 model. I succedded in installing windows 7 via bootcamp via a usb drive and was in the middle of installing a downloadable windows 8 upgrade (at a preferences page when they ask you to select your favorite color) when my macbook's keyboard/trackpad stopped functioning. I plugged in a usb mouse and that would not work either. I have absolutely no clue as to what to do next. If I had to install some driver or thing please tell me how to cancel the windows 8 install and return to windows 7. Thanks for all your help strangers

    I was not able to find any drivers specifically for the web cam. I did find software to use the camera, but that was all I could find.
    However, I do have a question about the Windows 8 upgrade process that was used.
    Did you do an in-place upgrade or a clean install of Windows 8?
    Go back to device manager. Is there anything here at all in an other category indicating it is having some type of an issue?
    There are certain events that will need to happen.
    Go to the start screen and search for uninstall a program. Select this option in the settings category.
    This should take you to the Desktop app and show the familiar uninstall a program feature from Windows 7.
    Select add/remove Windows Components on the left.
    Is Framework 3.5 checked here? If not, enable this and install it.
    Then, install the HP framework which is needed for some HP programs. This is a Windows 7 installation, but it should go through.
    http://goo.gl/jDI7X
    Once that is finished, reboot the system.
    Let me know what happens.
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • Late 2013 Keyboard / Trackpad still unresponsive AFTER EFI 1.3 update

    I thought I would start a new thread / discussion since the previous thread here seems to be riddled with "install the update" suggestions and off topic assistance such as battery life questions. I have also logged detailed information regarding this issue on my professional blog here.
    Anyway, here is a short, condensed version of my story. I have had two brand new late 2013 Retina MacBook Pro's with the 2.4/16GB/256 configuration. Since the config I chose is a CTO, this problem has been going on since the day the first model arrived (December 10th, 2013). The EFI update was preinstalled on both systems and I can verify that because the boot ROM version is MBP111.0138.B03 (the boot rom prior to the update ended in B00 or B01). I am also an AASP and an ACMT meaning that I am certified and employed with a company that allows me to fix all Apple hardware under warranty. I am well-versed in technology and Apple hardware and I have never seen anything quite like this.
    Here is the quick summary of things I have attempted and I have been able to re-recreate the issue:
    The system will not mount the root device when I boot via a known good external hard drive running 10.9.1. Verbose mode and Single user mode reports a still waiting for root device error.
    The system (rMBP) will not boot from another system (late 2011 MacBook Pro 13") when said system (late 2011 MacBook Pro) pushed into target disk mode via thunderbolt.
    My system, rMBP, will boot up with the internal SSD but will not allow the keyboard and track pad to function. The caps lock key will not illuminate. The keyboard and track pad will work OUTSIDE of 10.9.1, however. I have installed a clean internet recovery version of Mavericks over 4 times.
    If I put my system, rMBP, into target disk mode and connect to any other computer via thunderbolt and boot it on the other Apple systems, the operating system running on the internal SSD of the rMBP will work just fine -- keyboard and mouse included (again, as a target disk mode thunderbolt connection to another host).
    If I use a remote agent to connect to my rMBP such as LogMeIn or vnc, the keyboard and mouse will work just fine from the remote system which leaves me to beleive that this is not a software issue nor is it fully a hardware issue since the keyboard and mouse work outside of mavericks.
    I believe we are still dealing with a firmware issue here. It took several tries to create a bootable device for the late 2013 rMBP since NONE of my other up-to-date and verified working external drives will boot but I finally created a bootable USB stick. When I run the system from the USB stick, the keyboard and trackpad will work but if I touch the keyboard and / or trackpad in 5 second intervals, I will receive the following error:
    1/4/14 4:44:41.000 PM
    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)
    1/4/14 4:45:00.000 PM
    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)
    1/4/14 4:45:43.000 PM
    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)
    1/4/14 4:49:03.000 PM
    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)
    1/4/14 4:50:20.000 PM
    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)
    1/4/14 4:51:24.000 PM
    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)
    1/4/14 4:52:49.000 PM
    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)
    1/4/14 4:53:00.000 PM
    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)
    1/4/14 4:53:10.000 PM
    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)
    1/4/14 4:55:25.000 PM
    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)
    1/4/14 4:56:07.000 PM
    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)
    1/4/14 4:57:06.000 PM
    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)
    1/4/14 4:58:40.000 PM
    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)
    1/4/14 4:59:45.000 PM
    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)
    I had actually created a system log query to search for the above. The search string includes "the USB " and any entry after 1/1/2014. The above error should only present itself when waking an Apple system from sleep and instead it happens on every touch after, at least, a 5 second period of non-use.
    When I remote into the system using LogMeIn, VNC or even use an application called ShareMouse which shares the keyboard and mouse of my Windows system with any other computer on the network presuming they have ShareMouse also installed, I can use the system as I would expect, without continuous error in the console log. When I check the system information, Bluetooth is completely disabled and the USB hub does not report address information. Since the keyboard, track pad, Bluetooth peripheral and USB ports all sit on the same USB stack / hub this leads me to think there is a firmware / driver failure occurring after Mavericks loads. The only two errors I see when I am using a remote keyboard and mouse via a remote service is as follows:
    1/5/14 6:58:16.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0xfa000000) may have caused a wake by issuing a remote wakeup (2)
    1/5/14 6:58:16.000 PM kernel[0]: The USB device Apple Internal Keyboard / Track pad (Port 2 of Hub at 0xfa100000) may have caused a wake by issuing a remote wakeup (3)
    Bottom line: Even for those of you who have installed the EFI 1.3 update and have verified that your freezing issues have ceased, for the most part, could you check your console log for the above error. My guess is, you will still see the error repeated there in 5 second intervals if you touch the keyboard, put your hands up for 5 seconds, touch the keyboard and / or track pad again. My concerns is that this is a product line issue since it has occurred on two brand new systems and the log errors appeared on another model on display in an Apple store. (The display model was logged into an Admin account so I took the liberty of checking the console log.)

    I'm tired of this message. Bought a Mac 13" retina from bestbuy that was shipped to me on December 24th. The finder took a long time to load 'All My Files' with three to five second delay. My older macbook unibody (late 2009)was instantaneous. My wife's macbook aluminum (2011) also loaded the files instantaneously. Sorry I digressed but while I was trying to research that issue, I was caught up in the console and multiple of these,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)' kept showing up whenever I touched the trackpad in intervals of 6-7 seconds.
    Called up apple, used screen sharing and after spending an hour was transferred to the second tier tech. The second tier rep troubleshooted and told me it WAS an issue and asked me to go to apple store to run diagnostics and that most likely I'll receive another notebook in exchange since it fell within 14 day period. I told him the internet was filled with this discussion and asked if it was prevalent. He said it was the first time he has come across this issue and most forums on the internet may not be addressing my specific issue. I wasn't convinced and simply returned it at best buy.
    The unfortunate thing is I sold my macbook unibody and having owned 2 macbooks for last eight years I caved and ordered another 13". After a week and a half I received it today and guess what, I see the same message filling up my console.
    I noted the following,
    * Use guest account and you'll never see the message,'The USB device Apple Internal Keyboard / Trackpad (Port 5 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2)'. All admin accounts created will throw that error.
    Though off topic I'd like to state what happened with the Finder's 'All my files' issue:
    1. Once I upgraded my older macbook unibody to mavericks, the 'All my files' took longer to load as the new macbook pro.
    2. I was able to replicate the same slow load times with macbook aluminium(2011) when I upgraded it to mavericks.
    Oh, I also showed the slowness to the representatives and all they tried doing was reindex spotlight which did no good.
    So much for 1799$ notebook and the "free" OS. Very disappointed.

  • Unresponsive keyboard/trackpad and intermittent Bluetooth on MacBook...possible internal USB problem?

    I have a mid-2010 polycarbonate/white MacBook (model A1342) running OS X 10.6.8. My machine has been having issues with the internal Bluetooth and keyboard/trackpad randomly ceasing to function.
    Bluetooth issue
    As of recently (the past month or two), the Bluetooth adapter will completely disappear and eventually reappear on a random basis. It won't appear at all in System Profiler, and the BT menu says "not available". Also, I have had a few kernel panics recently, all of which were apparently thrown by a Bluetooth process/daemon/driver (unfortunately I forgot which one, and also lost the logs from the panics.)
    My system has a Broadcom Bluetooth chip that's part of the AirPort card, but is basically just an internal USB device. The adapter has some sort of integrated USB hub ("BRCM2070 Hub"), which the "Bluetooth Module" device itself is connected to.
    Nonetheless, this seems to be some sort of problem on the USB bus. Whenever there is a failure, I will almost always see output in Console showing USB errors (ie errors about "enumerating a USB device", "clearing port power", "setting port power", "getting port status", etc). It will either be on any of the ports of the hub at 0x6600000 (the "BRCM2070 Hub" that "Bluetooth Module" is connected to), or port 6 of the hub at 0x6000000 (BRCM2070's port on the internal bus, which the keyboard/trackpad is also connected to on port 3).
    I can post more/longer ones, but here's a somewhat short example of the error messages I might receive:
    11/18/12 3:18:36 PM kernel USBF: 7351.492 [0xcf9b300] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 6 of Hub at 0x6000000)
    11/18/12 3:18:38 PM kernel USBF: 7353.987 AppleUSBHubPort[0xcf9b300]::FatalError - Port 6 of Hub at 0x6000000 reported error 0xe00002c7 while doing clearing port power feature
    11/18/12 3:18:38 PM kernel USBF: 7353.987 [0xcf9b300] The IOUSBFamily was not able to enumerate a device.
    11/18/12 3:20:20 PM blued[448] Apple Bluetooth daemon started
    11/18/12 3:20:20 PM kernel USBF: 7456.186 [0x11fb1300] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 2 of Hub at 0x6600000)
    11/18/12 3:20:20 PM kernel USBF: 7456.188 [0x11fb1300] The IOUSBFamily was not able to enumerate a device.
    Keyboard/trackpad issue
    There's also an issue where the internal keyboard/trackpad will randomly cease functioning (until I restart), often a couple of times a day as of recently. I've had this issue on rare occasion for a while now, but it's gotten more frequent. And more recently, the caps lock light on the keyboard occasionally turns itself on when I'm away.
    Both the internal keyboard/trackpad as well as the Bluetooth "hub"/device are connected to the same USB bus/hub. When the keyboard/trackpad die, I've noticed that there will be very similar messages in Console to those above and usually a Bluetooth failure at the same time. (In some cases, it seems to notice that the keyboard/trackpad isn't responding, then attempts to reset/reinitialize it...ie log below.) What could the root cause be...could it be the USB "root" hub/bus causing one or both of these to fail, or possibly a problematic device causing the other to lose connection? I haven't had issues with USB devices on other buses failing, though (ie no problems with external devices.)
    Maybe more out of curiosity than anything else, but I've been poking around for info on what might be going on with the USB (aside from the 0x66 hub repeatedly dropping/reconnecting and etc), but can't find much. There seems to be no documentation about the error codes (ie 0xe00002c7) that the hardware/OS are relaying. I even poked through the source for some of the relevant kexts and some reading on OS X driver/kernel programming too...might as well learn more about the inner workings of OS X
    Here's an example of some of the messages that I get about the Keyboard/Trackpad:
    11/21/12 2:57:22 AM kernel USBF: 1439.228 IOUSBHIDDriver(AppleUSBMultitouchDriver)[0xd1ff000]: Detected an kIONotResponding error but still connected. Resetting port
    11/21/12 2:57:22 AM kernel USBF: 1439.234 AppleUSBHubPort[0xd040600]::Resetting device Apple Internal Keyboard / Trackpad: port 3 of Hub at 0x6000000
    11/21/12 2:57:22 AM kernel USBF: 1439.319 [0x14452600] USB HID Interface #0 of device CompositeDevice @ 5 (0x6610000)
    11/21/12 2:57:22 AM kernel AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
    11/21/12 2:57:23 AM blued[248] Apple Bluetooth daemon started
    11/21/12 2:57:23 AM kernel AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
    Attempted fixes
    Unfortunately, my Macbook isn't under warranty so I'm mostly on my own. First I zapped PRAM, reset SMC, ensured OS updates are installed (still on 10.6.8), and threw out a few drivers/software that were possible troublemakers. Next, I tried running another OS/install to rule out software issues. Accordingly, I found that the BT adapter sometimes disappears on Windows 7 as well (just did a clean install). And finally, I bought a new AirPort/BT card and installed it the other day. That seemed better at first, but I still have the problem of intermittent Bluetooth and keyboard/trackpad.
    Problems/solutions?
    What might the issue be, or is there anything that may be worth trying? As I mentioned, I've reset PRAM and SMC, made sure it's not an OS/driver issue (it happens on Win7 too), and replaced the Airport card. The machine does have aftermarket RAM (from OWC, ~2 years old) and SSD (Crucial M4, installed September)...but it seems unlikely that either of these would cause the problem. There haven't been any accidents that would have caused physical or (to my knowledge) electrical damage to it.
    I also searched for any occurrences of similar problems, but could not find any that were applicable to the Macbook revision in question. There was a similar keyboard/trackpad issue on older Macbook Pros that was caused by stress on a ribbon cable...but that seems unlikely given the concurrent issues with Bluetooth as well as the different design.
    The only thing I can think of next is to possibly replace the cable connecting the Airport card to the logic board, and possibly look at replacing the keyboard/trackpad (topcase). Anyway, I'm worried that it might be a hardware issue with the internal USB controller/hub, which would probably mean that it's unfixable unless I replace the logic board.
    Any advice as to which of these might be a potential solution or cause of the problem? Or might I just as well sell it off in its current condition and replace it?
    Thanks all!

    Has anyone find a fix for this?  I've been using my Dragon Dictate headset on my MacBook Pro for about a year, and then today, when I plugged it in, I got this:
    4/16/14 10:01:04.000 AM kernel[0]: USBF:    47.766    The IOUSBFamily is having trouble enumerating a USB device that has been plugged in.  It will keep retrying.  (Port 1 of Hub at 0x4000000)
    4/16/14 10:01:07.000 AM kernel[0]: USBF:    50.269    AppleUSBHubPort::FatalError - Port 1 of Hub at 0x4000000 reported error 0xe00002c7 while doing clearing port power feature
    4/16/14 10:01:07.000 AM kernel[0]: USBF:    50.269    The IOUSBFamily was not able to enumerate a device.
    Here is what I have tried so far:
    Reset the PRAM
    Reset SMC
    Verify disk (there were no problems)
    Repair permissions
    Boot with an external USB hard drive (which works fine on the "problem" computer) that contained an old SuperDuper clone of my hard drive from several months ago. I received the same "The IOUSBFamily was not able to enumerate a device" error when I plug in the headset.
    Tried to headset on another computer, and it worked fine.
    Plug in an external USB keyboard into the problem computer, and it works fine.
    All of this would lead me to conclude that it is a hardware problem. But it seems that if it were a hardware problem, the external USB keyboard and external USB hard drive would not work (which they do). If the problem were with the headset, it wouldn't work on another computer, but it does.  So I'm wondering if it's some sort of firmware issue…???????  URG!!!!!!

  • My USB Apple Aluminum Keyboard is not responding during Bootcamp Install!

    I am going crazy, I have had the worst experience with this Bootcamp install which is supposed to be so easy, resulting in Apple replacing my MAC pro, and I still can't get it to work on the new machine.
    My first problem was using a Windows XP Pro disk, which resulted in my continually getting a black screen saying "no bootable device, press any key to restart." I ran into this problem because I overlooked the instructions to use a USB keyboard and mouse, I was using the wireless. This process resulted in Apple replaceing my MAC Pro because some how my start-up files dissappered and the MAC geniuses couldn't even reformat my drive.
    After recieving the new MAC Pro, I tried to run the Boot Camp install, using the same Windows XP Pro Disk, but now with a wired USB Apple Aluminum Keyboard and USB might mouse. I was still running into the same problem, after windows finished the Install and restarted a black screen would appear "no bootable device..." After searching many forums I found that for some reason Windows XP Professional disk skip the step where you would format the drive you partioned for Windows. I found in a forum a way to address this problem by going in DOS and entering commands to tell Windows to format the drive. I was not comfortable doing this, so I thought I would take an easyier route and get a Windows XP Home edition.
    All windows versions I used were OEM, but they were all full installs (fancy hologram CD) w/Service Pack to and certificates of authenticity**
    I thought great now everything should go smoothly, I have Windows XP Home Edition w/SP2, I have a USB wired apple aluminum keyboard, and I have a USB wired might mouse. This has not been the case.
    After I complete the Bootcamp process on my Leopard operating system and Windows XP completes loading all the file prior to begin the Install, the Windows XP Installation asks to press "Enter" to begin Install. This is the point now I can't get past, because I get no response from my keyboard. I tried every USB port on my CPU and still no response when I reach this step in the Windows Installation. I am becoming very disgruntle with Apple because the AppleCare, which I pay for, and the MAC genius will not help me with this problem because it is during the Windows Install. Please help before I flip out.

    That worked after using a generic DELL PC keyboard no extra keys. Apple hustled me into buying a wired keyboard, because I had only ordered the wireless keyboard.
    Thanks

  • Keyboard/trackpad freeze on launch from 10.5.1 install dvd - please test

    I, like legions of others on this forum and others, have had nothing but problems with the MacBook Pro keyboard/trackpad. All of these problems have disappeared since reinstalling 10.4.5 from the original dvds that came with my MacBook Pro.
    A while ago, hopeful that 10.5 would solve the problems that 10.4.9 introduced, I bought the 10.5.1 dvd. After ugrading/reinstalling a number of times but always having the keyboard and trackpad problem, I tried the following experiment.
    I wiped the hard disk clean (wrote "0" 's on the disk), then stuck the 10.5.1 dvd into the drive and booted. Then, before choosing the language, I waited one minute. The keyboard/trackpad completely froze. I was able to repeat this experiment a few times, and in each case, the same thing happened. I then re-installed 10.4.5, and all of my problems are gone.
    I would like to know if others can test this out - even if you do not wipe your drive clean first. Just boot from the install disk, then - don't do anything - just wait a couple of minutes to see if the keyboard and trackpad freeze. I don't understand why it would be purely a hardware issue when
    1. the hardware works perfectly with 10.4.5, and
    2. many people are having the same problem, and we don't all have identical hardware.
    the hardware I'd like to really see replaced are the apple care representatives. somehow, "apple care" has become an oxymoron, as far as I can see.
    thanks.

    MacBook Pro Apple Discussion:
    http://discussions.apple.com/category.jspa?categoryID=190
    Hopefully, someone there is more familiar with this very annoying and frustrating problem.

Maybe you are looking for