Windows 7: Dual Boot Ubuntu cant remove loader

I recently installed ubuntu 10.04 LTS on my system, and now, even when the windows partition is active, it boots into the ubuntu loader, then the windows bootloader. How can I remove the ubuntu bootloader?

Boot into Win 7 , D/l this bootsect.zip .

Copy bootsect.exe file into win 7 c:\windows\system32.

Open an elevated command prompt and type ( assuming Windows 7 partition sees itself as C )

bootsect /nt60 C: /mbr

press enter.

That's it

Attachment 73878

That was the result. And iv been getting that I/O message ever since i had the message

boot0:
boot0:
boot0: success

at startup. Any ideas?

So it would be helpful if you explained what your trying to do. Do you want the MS bootloader to load Lucid when you want it? Or have you removed Lucid and just want to run MS. I am surprised you were given a command to remove grub without any questions. As a open source user my self mainly, and also using XP and Windows 7 I would never rely on the MS bootloader it is problematic in reading other operating systems and will only read a MS system automatically. If you had a dualboot working with Windows 7 and Lucid, then you probably should have just left it alone, there is a program called startup manager in Ubuntu that will adjust the countdown boot time and what you want to be the default boot.

If you just want to reload the MS boot loader do this.

thank you that fixed both my problems. +1

When going to install ubuntu onto a flash drive I ended up trashing the 7 mbr on one occasion where I simply booted from the 7 dvd itself to use the startup repair tool in the repair tools. Once that was done and the restart was seen the dual boot at the time showed "Windows 7 Ultimate(recovered)".

Your lucky the auto-repair worked, but if you had just checked the advanced button in the last gui of the install you would have seen that grub was defaulting to the hard drive rather then the thumbs mbr.

The only thing I would like to add here is that I like a auto-system fix and a shiny gui, I'm not a code writer or a big command line user, but sometimes that is what you have to do if you have mixed MS with open source. I think this is basically MS's fault since to them open source is a very small part of the desktop market. But open source is used on over 50% of the severs on the web, and in Governments, and the fastest super computers run a Linux variant, with about 70% running a Linux setup. Unix and Linux are usually behind the MS desktop in many situations it is more stable and safer.

Really if you are just cruising the web and not gaming a open source or even apple is a better setup out of the box, and most open source is free. Don't be brainwashed into running just MS, it is now quite better with Windows 7, but any on line banking or using a credit card should never be run on a MS setup. The operating system was never designed for safety and has to be seriously locked down and cleaned regularly. And because it has the market share of the desktop market, it has a huge bulls-eye on it for the crackers. Don't get me wrong here it is a inter mixture of problems that make using a MS system only that makes it problematic.

Personally though I don't like the key set up for verification, I have a upgrade from XP to Windows 7 that had to be a fresh install to run. And every-time I reinstall it I either have to do the Paul T method or call MS as I don't get the activate it by phone line unless I reset it before trying. This is ridiculous, it is easy for me but I have a bit of a clue as to what to due, I shudder when I see the problems of those that don't.

The repair also worked well for seeing a second install of 7(stand alone) on another drive added into the BCD store on the host drive. It doesn't take much for Grub to trash the 7 mbr while it doesn't that much to restore it either fortunately!

I would agree with the easy fix but grub will not trash anything unless directed to do so. That is the problem we see at the Ubuntu Forums is that people see the install gui that asks where should grub go, and if your not sure put it everywhere. That is a bug of a gui, for the in-experienced user, not knowing that the bootloader goes to the mbr most of the time only.

Another thing is that the chkdsk /r options in the command set is a very good tool for checking the file system and fixing any anomalies, every user should run that at least once from a install or recovery disc so that they know how to do it, it will fix a lot of stuff. Here is another link to what is used often for messed up grub installs when grub has been loaded into the windows partition.

SourceForge.net: Boot Problems:Boot Sector - bootinfoscript

I guess since grub never messes up my installs unless I mess up, I am biased to it being user error, but hey anything is possible in the end.