So we have all seen and heard the many solutions to this issue, most which refer to the direct editing of the BCD and MBR..
However, no one has pointed out exactly why this issue
happens, which should be the first step in identifying a fix. The
corruption of BCD occurs, In the most part, when the vista setup
finishes and the sysprep command is run, generalising BCD, and in most
cases i have found, users running either a dual boot, or seperate HD's,
the generalisation of BCD fails. It can also occur after installing the
update KB936330, also known as Vista service pack 1.
I am unsure why the issue can occur after installing the
service pack, but I am certain that a generalised BCD was included in
the package (Generalised being an OOBE prepared BCD.exe) and this may
pertain to why some systems have this issue after, as additional HD's
may not be installed until after the initial setup. We can be certain
that no system with one HD is suffering from this issue, and that the
problem extends from the shutdown sequence.
There are two fixes, One pertaining to a single boot
system, and one pertaining to a multi-boot system. Usually the system
will be afflicted with either, but in some cases, can be afflicted by
both.
THE PROCESS
Once running a repair from the Vista disc, windows
should boot fine once, but upon a shutdown the same error will be
presented. However upon a "Restart" the issue is not present and windows
will boot fine. It appears that upon the shutdown sequence, the BCD is
corrupted and the information is erased.
Most people would follow the onscreen prompts and insert
the vista disc and proceed with a repair, when in 99% of cases, simply
turning the pc off and back on again will be sufice and the system will
then boot into windows fine. Try it, I can almost guareentee that it is
the case.
If this is not the case, you may need to insert the
installation disc and proceed to the repair OS screen, and select
command prompt. Once in the command prompt;
Run bootrec
You will see a number of options;
/repairmbr
/repairbcd
/osscan
Repair BCD is the most essential command, as it locates
missing OS's from BCD and links them, without modifying the other
contents of BCD. Repair MBR is a dangerous command, and should only be
used after running repairbcd as it will wipe the MBR and recreate it
using the information from BCD. If the MBR is corrupted with false
information from BCD, windows will be unable to repair this itself and a
reinstall will be needed to correct it. Os Scan is a simple tool, used
by repairbcd to scan for OS's not linked to either the MBR or the BCD.
Run bootrec /repairbcd
Answer Y once repairbcd has found the desired installation. You should recieve the message, "All tasks completed successfully"
Run bootrec /osscan
If osscan returns an OS that is not linked, that is a vista OS, you will need to;
Run bootrec /repairmbr
Repairmbr is fully automated. There is no need to explain it here.
Once these steps have been completed, your "generalised"
BCD will no longer be "generalised" and the system should be able to
start without problem. If you are presented with the same error, simply
turn the system off and back on again, The system should boot fine. I
have notified microsoft of the fact that this only occurs upon issuing
of the shutdown command and hopefully they should release a fix.
WHEN ALL ELSE FAILS
If the problem persists even after performing all of
these steps and restarting does not fix the issue, the problem directly
extends from the installation and the system should be reinstalled with a
fresh install, and with the primary drive only. After this, the service
pack should be applied. Once this has been completed, additional drives
should then be installed and configured.
USE OF BCDEDIT
In 90% of cases, this does not fix the issue. Only when
pertaining to dual boot systems, will this correctely identify and fix
the issue, because the "Generalised" BCD is not the problem, it is the
actual "Unknown" entries in the BCD. If those are not present, then your
issue is the "Generalisation" of BCD and not the actual entries in BCD,
and this WILL NOT WORK.
Divine Logix wrote: | |
|
Hopefully this has helped many people, and I am sorry
that I could not provide a complete fix for this issue, but I have been
able to point out why and hopefuly someone with a greater knowledge in
those areas can provide a fix.
Source:
www.technet.microsoft.com
Published by
S.G.Godwin Dinesh.MCA
Sr.System Administrator
Sr.System Administrator
No comments:
Post a Comment