Certain versions of windows prevent turning on test signing (this way) with Secure Boot / UEFI, which has to be turned off first.
A faster way is to disable driver signature enforcement for one boot cycle. On Saturday, January 28, 2017 at 6:23:00 PM UTC-7, woody stanford wrote: > > I had a problem with my core drivers for the host not installing (so you > can teather the BBB to a desktop via USB to miniUSB on the BBB). It just > came up with red X's every time. > > There are a lot of "fixes" out there that are pretty flakey so I thought > I'd post the most linear path I found. > > Windows now comes in 32-bit and true 64-bit versions. I'll save you the > time and aggravation on this that find out first if your OS is 32 or 64 > bit. Download the appropriate flavor of the BBB drivers from here (official > site): http://beagleboard.org/static/beaglebone/latest/README.htm > > The problem if its not installing at all is that Windows REQUIRES driver > signing by default. > > Hit <win> X and select "Command Prompt (admin)" > > and type the following: > > bcdedit /set testsigning on > > Now its critical to understand what this does; it PERMANENTLY sets the > default on your box to prompt you if its OK to use an unsigned driver. > Since it prompts every time, I believe it secure. A lot of other procedures > take a lot of time and frankly don't work on my Win 64 machine (burned up > hours on it :( The Beagleboard core drivers are unsigned so make sure you > get them from a trustable web site. > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8d842e1f-f426-486c-920d-dacf9ac2f80e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
