Readers like you help support MUO. When you make a purchase using links on our site, we may earn an affiliate commission. Read More.
I am trying to install Ubuntu alongside Windows 7. All goes well until the end, then it doesn't complete dual-boot, it says I'm missing a file but doesn't say which. Here is the error:
>>Command=C:\windows\sysnative\bcdedit.exe/create/d Ubuntu/application bootsector
>>retval=1
>>stderr=The boot configuration data store could not be opened.The system cannot find the file specified
>>stdout
2013-04-12 22:51:30
You can set up Ubuntu on an External Hard drive it that's an option for you. It's essentialy the same as when you would normally install it, except that you select the EHD instead of your internal hard drive.
2013-04-12 13:31:16
1) Windows Dual Boot Articlehttps://help.ubuntu.com/community/WindowsDualBoot2) How to install Windows 7 and Ubuntu side by side http://www.dedoimedo.com/computers/dual-boot-windows-7-ubuntu.html
2013-04-12 11:31:03
Wubi Installer Error http://ubuntuforums.org/showthread.php?t=1871823
2013-04-12 05:59:25
i would suggest you to install ubuntu on your other drives. so if windows is on c: then you can install ubuntu on d: or e: whichever you prefer. empty the drive and just install using a usb or use wubi. it will dual boot. i had done this without any problem.
2013-04-12 04:21:32
Have you tried Wubi? It automatically installs Ubuntu as a dual boot. Sets it up. And then, next time you boot your comp up, it offers which one you want to log into.The Wiki linky: http://en.wikipedia.org/wiki/Wubi_%28Ubuntu_installer%29Good luck!
2013-04-12 12:58:05
The only time you will get the error message OP is reporting is if you are doing a Wubi install. Installing from a live CD will replace the Windows boot sector and install GRUB2 which will automatically add an entry to boot Windows in the GRUB configuration file and therefore does not require any kind of modification of the BCD database.
2013-04-12 01:01:49
Have you tried the suggestions from the
Ubuntu forums
? They also link to a Microsoft KB article addressing the issue.