Disable Windows Error Recovery - Windows Server 2008 / Windows 7 / Etc.

We have Citrix XenApp servers that boot from an HP Lefthand P4500 SAN volume and for some reason during scheduled reboots on the weekend they would hang on the stupid "Windows Error Recovery" about 50% of the time.  Selecting "boot windows normally" would boot the server just fine - but it was always a manual operation.  So this would leave these production servers in a downed state until someone manually intervened.

To fix this problem I used the following command (from a command prompt):

bcdedit /set {current} bootstatuspolicy ignoreallfailures

To check to see if it is set you can simply use BCDEDIT by itself to display the settings.  For example:

C:\Users\administrator>bcdedit

Windows Boot Manager

--------------------

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume1

description             Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {current}

resumeobject            {E54e3a5f-48ad-11df-ae93-ced11e86b19d}

displayorder            {current}

toolsdisplayorder       {memdiag}

timeout                 30

Windows Boot Loader

-------------------

identifier              {current}

device                  partition=C:

path                    \Windows\system32\winload.exe

description             Windows Server 2008 R2

locale                  en-US

inherit                 {bootloadersettings}

recoverysequence        {E54e3a63-48ad-11df-ae93-ced11e86b19d}

recoveryenabled         Yes

osdevice                partition=C:

systemroot              \Windows

resumeobject            {E54e3a63-48ad-11df-ae93-ced11e86b19d}

nx                      OptOut

bootstatuspolicy        IgnoreAllFailures

If the setting has not been applied you will not see "bootstatuspolicy" in the list.   

Now upon reboot it does not stop and wait.  I know this has been helpful as we had to repair the boot info on a one of the servers and it started doing it again afterwards (after 8 months of smooth reboots.)   This setting got wiped-out when we did the repair so I had to set it again.