Solved Windows Boot Manager

[Jamesd0015]

Hi,

I am currently applying a .wim (Windows 7) to a machine and am planning to do this to another 50.

I have applied my image (.wim) and ran 'bcdboot c:\Windows /s c:' to include the boot entry otherwise it will error upon booting.

Now this is where I have a problem, if I re run the above, when it boots it displays windows boot manager asks which OS to load, due to the additional boot entry.

Is there a way clear all entry's in the boot manager via a command?

BCDEDIT.exe is very well to clear a single entry after specifying the identifier but not feasible do to the automation.

 

[gregrocker]

Go into msconfig>Boot and delete the extra entry.

If not there, install EasyBCD to delete the extra entry on Edit Boot Menu tab, the modern way.

 

[Jamesd0015]

Go into msconfig>Boot and delete the extra entry.

If not there, install EasyBCD to delete the extra entry on Edit Boot Menu tab, the modern way.

Thats very well doing that once the image has been applied, but i dont want to do this on all 50 machines.

I would like to correct the boot sequence upon applying the image.

Cheers

 

[gregrocker]

I would find out why there is an additional boot entry - what is it for?

 

[Jamesd0015]

I would find out why there is an additional boot entry - what is it for?

It's for the previous image I applied to the machine. In our organisation this is a common occurrence of reimaging machines, so this issue will occur.

 

[gregrocker]

THen I would find out how to overwrite the old image so it doesn't create a Dual Boot menu which is only supposed to occur when an OS is installed to another partition on the same machine.

I don't know why your new image isn't overwriting the old image anyway.

Diskpart Clean command will also wipe the old installation sufficiently so nothing will survive.

 

[Jamesd0015]

THen I would find out how to overwrite the old image so it doesn't create a Dual Boot menu which is only supposed to occur when an OS is installed to another partition on the same machine.

I don't know why your new image isn't overwriting the old image anyway.

Diskpart Clean command will also wipe the old installation sufficiently so nothing will survive.

I am deleting, cleaning, re-creating the partitions and formatting the drive before applying the image, so that is not the issue.

 

[gregrocker]

Then the Dual Boot could not be from the previous image as you stated, but must be something in the image.

A cleaned HD has its boot sector wiped of code, so has nothing existing to add.

 

[Jamesd0015]

Then the Dual Boot could not be from the previous image as you stated, but must be something in the image.

A cleaned HD has its boot sector wiped of code, so has nothing existing to add.

No it's not that. It's due to the image not being sysprep'd, if i apply a sysprep'd image, the boot configuration does not require alteration.


FYI - How to Capture and Deploy Image (.wim) Without Sysprep - Brian Jackson's IT Blog

Cheers