Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Wireless Keyboard and Mouse drivers. Win 7, iMac 5K

I have gotten Windows 7 Ultimate running on 2014 iMac 5K with 3 TB Fusion drive.


The problem is that some drivers are not working as well as an older installation we have on a 2010 iMac with Windows 7.


Specifically:

  • keyboard screen brightness and sound volume controls do not work
  • magic mouse scrolling is jerky and useless
  • wireless trackpad tap stuff isn’t quite right
  • bluetooth input devices take a few seconds to get recognized first time.


I used BCA to create a USB 2.0 Win 7 install disk with BCA-selected boot camp drivers, and BCA ran the Boot Camp installation normally right after Windows installation. (screen brightness and volume controls on keyboard did not work).


Then I did many rounds of Windows Update and eventually wound up with an updated SP1 installation. I went into the BootCamp folder on the USB 2 installation drive and ran Setup again. Screen brightness and volume controls on keyboard still do not work.


The version of Boot Camp is 5769, according to the XML.


In Device Manager there are no warning icons. But I don’t think some of the drivers look right. The keyboard driver, for example, shows up as HID Keyboard Device from Microsoft, dated 2006. The mouse and trackpad both show up as Microsoft 2006 era HID-compliant mice.


Can this be corrected easily, for example by using a slightly different version of the Boot Camp, or first changing some Microsoft settings before re-installing Boot Camp drivers? Or by installing specific drivers for the keyboard, mouse and trackpad? I am installing from an administrator account, but is there some additional setting for permissions?


Thanks!

iMac with Retina 5K display, OS X Yosemite (10.10.4), 3 TB Fusion

Posted on Jul 19, 2015 9:18 AM

Reply
58 replies

Jul 19, 2015 11:04 PM in response to Loner T

Okaaaayyy. That's very weird. As I thought, W7 had English (US) as the language, but for good measure, I clicked the adjacent Location tab. Said US. Good. Then clicked the Language tab again and I thought it briefly said English (UK). Clicked back and forth between tabs and it toggled sometimes. So I put aside the magic mouse, thinking it was scrolling due to bugginess, used the already attached USB mouse, made sure to select US English and click OK. Cliicked something in the Task Bar and got a BSOD. Went by too fast to catch what it said then rebooted to black screen saying something might be saved if I do a Safe Boot without Network, so I did that. Failed with BSOD again. Quickly moved to a reboot into another black screen with slightly different threat. Chose the most conservative response and it went into a Startup Repair screen with a sort of Win 3.1 look to it, thought a bit and is now offering a System Restore to some earlier point before some programs were installed.


Ugh.


I expected nothing odd to happen, and I would make a Monty Python reference to checking my shoe size. But not so much.

Jul 19, 2015 11:10 PM in response to Suzanne S

If you want to be brave like Captains Picard and Kirk, use BCA to remove the current Windows installation. Re-install Windows (I expect a bit of angst and bit of text-gnashing), but try to re-install Windows with US English and after the entire installation is complete and BC drivers are in place, switch to English (UK).

Jul 20, 2015 2:08 PM in response to Loner T

OK, I have really blown it now. I am ashamed to admit that I thought, heck, this Boot Camp installation is truly borked (Windows could not recover itself). So I will try to use Winclone to restore a sys-prepped clone of an older installation. Not too stupid according to Winclone. The stupid part was that I thought, "What if there is a hard drive problem? If I use Disk Utility to just erase the content of the BootCamp partition, this will force a surface check." STUPID. The Erase of course failed with an error, destroyed the BootCamp partition, and Boot Camp Assistant cannot remove the partition and put me back to a 3 TB OS X HPFS+ partition as it could have if I had not done this idiotic thing.


The OS X part of my drive still works perfectly, and I have a SuperDuper bootable clone and a Time Machine backup.


Should I:


1) Boot into Recovery, repartition the entire drive, reinstall OS X from the internet, then restore my SuperDuper clone.

2) Try to do some heroic and probably misguided Terminal magic to fix what I screwed up.


I think the answer is 1).


What do you say? Other than "I told you so"! ;-)

Jul 20, 2015 2:31 PM in response to Suzanne S

Option 1 is the officially supported answer. Option 2 avoids Internet Recovery, but the erase of a 3TB Fusion drives is not the Recovery Console's forte. Please try Option 1 first. If it does not work, state in Recovery console.


Please post the text output of diskutil cs list, in case I need to provide some Terminal magic and Pixie dust on sprinkled on top.


Erase the inner Macintosh HD (LV) in DU and then the outer Macintosh HD (LVG).

Jul 20, 2015 2:49 PM in response to Loner T

Current status, for reference.


diskutil cs list


CoreStorage logical volume groups (2 found)

|

+-- Logical Volume Group 10815421-827B-46CE-8DAE-C51C0253866B

| =========================================================

| Name: Macintosh HD

| Status: Online

| Size: 2814587740160 B (2.8 TB)

| Free Space: 159744 B (159.7 KB)

| |

| +-< Physical Volume 7792825B-4118-4062-BF46-0796BDC5D813

| | ----------------------------------------------------

| | Index: 0

| | Disk: disk0s2

| | Status: Online

| | Size: 120988852224 B (121.0 GB)

| |

| +-< Physical Volume 85F07FD5-3B8C-47EC-BC52-3349009E038F

| | ----------------------------------------------------

| | Index: 1

| | Disk: disk1s2

| | Status: Online

| | Size: 1892162347008 B (1.9 TB)

| |

| +-< Physical Volume 97F265B9-9021-4FDF-B6B1-D3C1FB1B252D

| | ----------------------------------------------------

| | Index: 2

| | Disk: disk1s6

| | Status: Online

| | Size: 801436540928 B (801.4 GB)

| |

| +-> Logical Volume Family 5DDEF125-8B96-4CC6-BA0B-452F2A4971B8

| ----------------------------------------------------------

| Encryption Status: Unlocked

| Encryption Type: None

| Conversion Status: NoConversion

| Conversion Direction: -none-

| Has Encrypted Extents: No

| Fully Secure: No

| Passphrase Required: No

| |

| +-> Logical Volume 3ACF34D7-A79E-4B1B-B5E2-07AA5289177C

| ---------------------------------------------------

| Disk: disk2

| Status: Online

| Size (Total): 2808446976000 B (2.8 TB)

| Conversion Progress: -none-

| Revertible: No

| LV Name: Macintosh HD

| Volume Name: Macintosh HD

| Content Hint: Apple_HFS

|

+-- Logical Volume Group 48B6F8A3-963C-482E-8E16-BECF81EB739A

=========================================================

Name: BOOTCAMP

Status: Online

Size: 305865420800 B (305.9 GB)

Free Space: 305513095168 B (305.5 GB)

|

+-< Physical Volume BF2B7A3A-0904-484C-879F-EF4E6647061E

----------------------------------------------------

Index: 0

Disk: disk1s4

Status: Online

Size: 305865420800 B (305.9 GB)

Jul 20, 2015 3:26 PM in response to Loner T

Retinia:~ suzanne$ sudo gpt -vv -r show /dev/disk0

Password:

gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176

gpt show: /dev/disk0: PMBR at sector 0

gpt show: /dev/disk0: Pri GPT at sector 1

gpt show: /dev/disk0: Sec GPT at sector 236978175

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 236306352 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

236715992 262144 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

236978136 7

236978143 32 Sec GPT table

236978175 1 Sec GPT header


_______________________________________


Retinia:~ suzanne$ sudo gpt -vv -r show /dev/disk1

gpt show: /dev/disk1: mediasize=3000592982016; sectorsize=512; blocks=5860533168

gpt show: /dev/disk1: PMBR at sector 0

gpt show: /dev/disk1: Pri GPT at sector 1

gpt show: /dev/disk1: Sec GPT at sector 5860533167

start size index contents

0 1 PMBR

1 1 Pri GPT header

2 32 Pri GPT table

34 6

40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

409640 3695629584 2 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

3696039224 1269760 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

3697308984 712

3697309696 597393400 4 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

4294703096 262144 5 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

4294965240 1565305744 6 GPT part - 53746F72-6167-11AA-AA11-00306543ECAC

5860270984 262144 7 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC

5860533128 7

5860533135 32 Sec GPT table

5860533167 1 Sec GPT header

Jul 20, 2015 10:07 PM in response to Loner T

I have come to realization that I do not know what to do once booted from Recovery, since things I used to think I knew about using Disk Utility to partition and format do not seem to apply to Core Storage. I'd really like to end up with an internal drive in the state in which I bought the computer: Single 3 TB Fusion HPFS+, plus a secret Recovery partition and whatever other secret giblets are supposed to be there. From there, I can use SuperDuper on my clone to restore my system back to normal. And from THERE, I can use BCA to try to get some version of Windows going.


Booted form Recovery, or from an external bootable OS X drive, or from Macintosh HD, Disk Utility now shows BootCamp as a separate drive, not a subset of Macintosh HD like before.

  • Before I screwed things up using DU on Bootcamp: Bootcamp under Macintosh HD.
  • After I tried to erase BootCamp with Disk Utility: BootCamp didn't show up?
  • After the commands you had me run this afternoon, BootCamp separate drive. See Screen cap.

User uploaded file

Hovering over each of those partitions gives a box that says: "The size of the selected partition will change, but the partition won't be erased."


Right now, Macintosh HD works normally and is the size it should considering the 300GB missing for BootCamp. But the 300 GB are missing, and I cannot have a BootCamp until this is reverted. I thought I'd see what to do when booted into Recovery, but I do not. Will Repair Disk on Macintosh HD fix the problem where the system now thinks BootCamp is completely separate? Or will I just make things worse doing this?

Jul 20, 2015 10:15 PM in response to Suzanne S

Notice this part...


+-- Logical Volume Group 48B6F8A3-963C-482E-8E16-BECF81EB739A

=========================================================

Name: BOOTCAMP

Status: Online

Size: 305865420800 B (305.9 GB)

Free Space: 305513095168 B (305.5 GB)

|

+-< Physical Volume BF2B7A3A-0904-484C-879F-EF4E6647061E

----------------------------------------------------

Index: 0

Disk: disk1s4

Status: Online

Size: 305865420800 B (305.9 GB)


Bootcamp should either be FAT or NTFS, but never a CS LVG/LV.


In Utilities -> Terminal,


1. Delete the BOOTCAMP LVG - diskutil cs delete 48B6F8A3-963C-482E-8E16-BECF81EB739A

2. Convert the resulting disk1s4 to a FAT partition - diskutil eraseVolume fat32 BOOTCAMP disk1s4


Please post the output of diskutil cs list and diskutil list disk1.

Wireless Keyboard and Mouse drivers. Win 7, iMac 5K

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.