I can use the UEFI boot menu to explicitly select the Windows Boot Manager (there are actually two identically-named 'Windows Boot Managers': one appears to be the regular OS, the other appears to the the Windows Recovery Environment), and I get this screen: Windows Boot Manager Windows failed to start.
Hey, thanks so much for the info, much appreciated. I managed to boot from USB after setting the motherboard options to just 'optimised defaults'. The resultant windows install though, doesn't appear to boot from UEFI, at least there's no UEFI option for it, just something called 'Windows boot manager'. If I allow it to go through to Clover rather than asking the MoBo to list boot options, Clover shows a couple of NTFS partitions such as 'Boot Windows from EFI' but they seem legacy. Not sure what I did wrong here, but will try to persevere a little longer. Hey, thanks so much for the info, much appreciated. I managed to boot from USB after setting the motherboard options to just 'optimised defaults'.
The resultant windows install though, doesn't appear to boot from UEFI, at least there's no UEFI option for it, just something called 'Windows boot manager'. If I allow it to go through to Clover rather than asking the MoBo to list boot options, Clover shows a couple of NTFS partitions such as 'Boot Windows from EFI' but they seem legacy. Not sure what I did wrong here, but will try to persevere a little longer.
Hi I have been running IoT on RPi just fine for a long time. Two days ago it updated and died with BCD cannot boot error. Since then I have reinstalled the image (and the insider images suggested in other similar threads) various times, each time same thing, starts an update cycle then dies at 50-70%, no response from keyboard or remote login. Reboot results in BCD failed to boot error. Have tested other SD cards too. (notable too that the dashboard can no longer images either, it gets stuck at 'unpacking installer'.
It ALSO updated recently. ) Anyone know how to force the updates OFF until someone in MS actually tests things before they release?
Apologies, ill be more verbose. The board has been reinstalled on two separate PC's, both running Win10 Anniversary Edition, both on LAN to RPi.
Two cards, a 16 and 32gb Sandisk Class 10 (the 32 is the one thats been running fine all along, tested putting NOOBS on both cards, both boot raspbian fine. (running raspbian right now, learning python so i can move my app over to a stable platform. With advantage of the hardware support. ) Cards formatted with SDFormatter, I even did the LOOOONG format to be sure.
No difference. Updates via Cable, machine1 on a 100mb connection, machine2 on a 32mb connection.
Both stable internet. RPi is the 1GB version 3b. Each time RPi boots after clean install, it is available in Dashboard for an hour or so, then the update kicks in, at some point about 20-30 minutes later the board become unresponsive, have left it for 6 hours on the longest run. Reboot results in black screen with Cannot Boot BCD error.
Tested standard Image and two of the insider images. Same result, stable until i get update which never completes. All i need to be able to carry on working is a way to force that update not to happen. Thanks for your response. Just to reiterate. The card isn't corrupt, it just doesn't boot. Raspberry pi 3.
Only power and Ethernet plugged in for headless operation. The intention was to use the raspberry pi 3 with an arduino uno, however I can't even get the pi to boot, so the uno is not plugged in. Windows 10 build 14986. I plugged it in yesterday and it attempted to update to 14993. Update stalled. After leaving it plugged in, and repeatedly seeing the bcd message it again attempted an update (after several hours!!), this time it succeeded.
Device boots only occasionally. Can't believe the power supply is the issue otherwise it would never boot. Power supply is 5v, 2.1a. The memory card is class 10, 16GB. Have wasted too much time on this. Intend now to give up and use Linux (just a reality I'm afraid, I can't spend forever debugging why windows 10 iot won't start). I have attempted to install IoT Core on a Raspberry Pi 3 via a few ways:.
Loading an SD card with the image. Loading an SD card with NOOBs and then installing IoT Core. Loading an SD card with a preview image I have even used multiple SD cards, so it's not an issue with the card. When I load IoT Core, it appears to work - for a while. I'll have it hooked up to a display, and after installation I'll get the dashboard screen, and I'll go ahead and connect to Wifi, the IoT dashboard even recognized it on the network on at least one occasion when i was paying attention.
However, when I reboot the device after this point, I then get an error indicating it can't find the Boot Configuration Data for my PC. (screenshot attached) I'm stumped by this and have no idea what to do. Anyone have any thoughts? Hi Chris, I am 99% sure you are 'rebooting' while the device is writing to the SD card. Please ensure you are doing a controlled shutdown rather than pulling power to reboot. There is really no reason for you to reboot the device. My recommendation is to let it keep running and never pull power unless you are certain the SD card is not being accessed.
You can try this on your PC as well. Put and SD card into your SD card slot and start copying a large file then pull the card while the file is still being written. At this point if you re-insert that card it will ask to be fixed and that is the equivalent issue you have when getting the BCD error. Sincerely, IoTGirl.
This is a very old thread, not sure how its cropped up again, but if you read the first post, leaving it for 6 hours didn't help either. Pretty sure that is enough time to finalise a write to an sd card. Anyhow, the point is mute in terms of my requirement, i dumped IoT and went made myself learn linux and python, finished my app there. Native support for the gpu camera was a bonus. Im sure ill revisit IoT at some later date, but once its a bit more mature on the RPi.
(saw today msdn article on library's in c# to support various peripherals were released). Sorry, I don't understand. What makes you 99% sure that a write is still occurring when the device is shutdown?How do we/you know a write is occurring? Are there any log files we can look at?
It sounds like Chris is trying to remotely configure his device. You say 'there is no reason to reboot the device' but the official documentation contradicts this (see here ) which states 'Restart the device for changes to take effect' (this is when setting the computer name, for example). The restart in the link is done by a command that I've used in Windows for years (shutdown /r /t 0). It also sounds unreasonable to say never pull the power. When I was looking at Windows 10 IoT in December I installed Windows IoT (build 14986) to a new, fresh out of the box Class 10 SD Card via a Windows machine (and safely disconnected the card before removing it from the Windows machine) then inserted the SD card into the Raspberry Pi 3. In my case the device booted occassionally, but more often than not I'd see the BCD screen.
If it was a power issue the device shouldn't boot at all. Booting sometimes and not others is extremely frustrating and its what led me to Linux/Python rather than Windows/C# for my app. Hi Monkey.Net, BCD means the Raspberry Pi is not recognizing the SD card as a bootable media. You are correct that there are multiple situations that can cause the SD not to be bootable but in my experience it is usually because someone either cut power or removed the SD card during a write cycle.
As to the reset, I only perform that as required. My devices reset themselves after an update and I have not had to ever pull power without a controlled shutdown for any reason. All of my devices are updating without issue at this point for me but I do not have any custom RPi hardware other than the RPI USB Wifi Dongle on my RPi2b. All the rest of my hardware is HDMI & USB based to ensure they are not custom.
From reading the forums regarding 'Booting occasionally':. SD card is not class 10 - Documented that slower cards will not meet boot speed response times.
SD card is seated incorrectly in RPi3 as it does not have the same click based receiver that the RPi2 does so it can seem seated even when it is not. This is a standard issue on the Pi forums as well. Power distribution - Power can be drawn down by added hardware as well as shorted by bread board errors and poorly wired custom cables. Also power supplies less than 2.2 amps can sometimes work and sometimes not depending on the power up sequence of the board itself. Your assumption 'If it was a power issue the device shouldn't boot at all' is not correct as power requirements change based on boot order and devices attached lighting up and drawing power through the board circuitry. For example, I had an ancient USB keyboard that pulled 5.5v instead of 5V and would kill almost any embedded device I attached it to. I am sure there are others, these are just off the top of my head but I am sure you can see the pattern emerging.
As an aside, IoT Core is not designed specifically for the Raspberry Pi but is expected to port to other hardware as well. Solutions such as Raspian are only expected to work on one set of hardware so can deal with the nuances of that device within the OS but that breaks its ability to be portable. Raspian also has the goal of being a desktop replacement with a shell which IoT Core does not.
If you are curious about the various flavors of Windows IoT, the section called “Windows IoT Portfolio” at highlights the difference focus between the Windows IoT options. Sincerely, IoTGirl.