Q: 'no signed device drivers' can be found on windows bootcamp installation
-
Nov 19, 2015 5:41 PMby vulgarwizard,okay so here's the output now:
sudo gdisk /dev/rdisk0
Password:
GPT fdisk (gdisk) version 1.0.1
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/rdisk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8004E14C-384E-459E-85C0-A6DF34841402
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 2429 sectors (1.2 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 340908743 162.4 GiB AF05 Customer
3 340908744 342178279 619.9 MiB AB00 Recovery HD
4 342179840 490233855 70.6 GiB 0700 BOOTCAMP
Command (? for help): r
Recovery/transformation command (? for help): o
Disk size is 490234752 sectors (233.8 GiB)
MBR disk identifier: 0x17C45D2E
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 409639 primary 0xEE
2 409640 340908743 primary 0xAF
3 340908744 342178279 primary 0xAB
4 342179840 490233855 primary 0x07
Recovery/transformation command (? for help): h
WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
just hit the Enter key at the below prompt and your MBR partition table will
be untouched.
Type from one to three GPT partition numbers, separated by spaces, to be
added to the hybrid MBR, in sequence: 2 3 4
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF):
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default AB):
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #4 (MBR partition #4)
Enter an MBR hex code (default 07):
Set the bootable flag? (Y/N): n
Recovery/transformation command (? for help): o
Disk size is 490234752 sectors (233.8 GiB)
MBR disk identifier: 0x17C45D2E
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 409639 primary 0xEE
2 409640 340908743 primary 0xAF
3 340908744 342178279 primary 0xAB
4 342179840 490233855 primary 0x07
Recovery/transformation command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/rdisk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
Attempting to install Windows 8.1 as usual, still unable to find those drivers.
P.S. I went to the Genius Bar and the Microsoft store today. Stumped both of them. -
Nov 19, 2015 6:34 PMby Loner T,6.0.6133 does not support W8.1. From Install Windows 7 and earlier on your Mac using Boot Camp - Apple Support (and this also works on W8.1), you need Boot Camp Support Software 5.1.5640 . We can test replacing the $WinPEDriver$, AutoUnattend.xml and Bootcamp folder on the USB with what comes from 5.1.5640.
-
Nov 19, 2015 7:34 PMby vulgarwizard,okay so taking that into account I tried with the Windows 10 disc that I created earlier. The only reason I was attempting 8.1 was that I thought it would cause less problems because it would be more widely supported (and that bringing it to 10 would be easy). So while I still get the "no signed drivers..." message when both scanning for drivers and when I direct the file browser to $WinPEDriver$ during the installation, if I direct the browser to an individual folder, lets say AppleSSD64, the individual drivers in that folder come up. Now if I click Next, I'll get a status bar for a bit, but then it says it is unable to install AppleSSD.sys. So the problem here must lie in the drivers that are currently within the $WinPEDriver$ folder? is there a better place to get drivers in that folder? the folder was created by BC 6.0.6133 so if these are not the ideal drivers, then what are? where can I find them?
-
Nov 19, 2015 7:52 PMby Loner T,There are two sets of drivers. $WinPEDriver$ is the directory used to load drivers which may be needed during the install for hardware which are not natively available with Windows Installer. WinPE == Windows PreBoot Environment.
WinPE drivers are not installed when BC drivers are installed after Windows finishes installation. The post-installation drivers are in the Bootcamp -> Drivers folder. Some of them may have the same drivers. For example Broadcom BT and Intel GPU drivers.
You picked the worst driver possible for your test - AppleSSD.sys. It has a lot of issues and is unsigned in some versions of BC packages and cause a lot of grief.
In AutoUnattend.xml...
Notice the value of pass variable and the directory - $WinPEDriver$.
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserData>
<ProductKey>
<WillShowUI>Always</WillShowUI>
</ProductKey>
</UserData>
<UpgradeData>
<Upgrade>true</Upgrade>
<WillShowUI>Always</WillShowUI>
</UpgradeData>
</component>
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>$WinPEDriver$</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
There is a "specialize" section. Notice the For loop which loops across all valid Windows driver letters looking for available files/drivers. (In theory if you added A and B drives, you can use a floppy drive, but it is no there right now).
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>cmd /c "FOR %i IN (Z Y X W V U T S R Q P O M N L K J I H G F E D C) DO (FOR /F "tokens=6" %t in ('vol %i:') do (IF /I %t NEQ "" (IF EXIST %i:\BootCamp\BootCamp.xml SETX AppsRoot %i:\ -m)))"</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
The oobeSystem (Out-of-Box Experience - https://technet.microsoft.com/en-us/library/cc766165(v=ws.10).aspx) pass has the BC driver installation, and disables all User Input...
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Description>BootCamp setup</Description>
<CommandLine>cmd /c %AppsRoot%\BootCamp\setup.exe</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>
The commands are fairly intuitive and you can see what they can do in the CMD window help.
-
Nov 19, 2015 9:32 PMby vulgarwizard,so I'm not sure what happened, and what changed, but I'm typing this from Windows! Basically what happened was that I was prompted for the drivers to load again, and I opened up a random folder, and selected everything in it to load on. Windows gave me two errors about being unable to install these drivers, but then let me go past that and installed windows. So all I need to do now is find what I'm missing, if anything. Mouse works, and so do the speakers/volume/etc., and no alerts in the device manager. But something probably isn't here.
That said, RESPECT, FRIEND! you stuck this out till the end, and of all the people I talked to on the internet and with support systems, you're the only one who had something meaningful to say about all of this. I can't thank you enough! You are my hero!
