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

'no signed device drivers' can be found on windows bootcamp installation

I'm pretty good with problem solving this sort of thing, but this one's got me stumped. I just bought a new MBP, and I'm installing Bootcamp on it, and no matter what, I'm stopped at the point of installing drivers on the Bootcamp drive during Windows installation with the message "no device drivers were found. make sure the installation media contains the correct drivers." I've tried multiple flash drives, multiple Windows iso images (8.1 and 10), directly downloaded from Microsoft, and from Apple's linked pages. I've tried formatting the virtual Bootcamp drive to MSDOS, I've tried resetting PRAM, I've tried using alternative methods to creating the USB install disk, I've downloaded fresh drivers from an Apple support page, I've even tried again in a different USB port. I've done everything anyone on any forum has ever said about this, and I've still got nothing. I must have attempted this installation around 15 times now, and I've run out of options here. I'm running El Capitan on a Mid-2014 15" MBP, and it says Bootcamp 6.0 should be able to install this without a USB disk, but I'm not given that option. If there's ANYthing besides new a iso, new flash drive, new Bootcamp, new partition format, or new USB creation method, I would love to hear your suggestion, no I need to hear your suggestion because I needed to use this Windows program four days ago.

MacBook Pro (Retina, 15-inch, Mid 2014), OS X El Capitan (10.11.1)

Posted on Nov 17, 2015 6:47 PM

Reply
37 replies

Nov 19, 2015 7:34 PM in response to Loner T

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 PM in response to vulgarwizard

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 PM in response to Loner T

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!

'no signed device drivers' can be found on windows bootcamp installation

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