Disable Windows Startup Repair as Default Option

Here is a script to disable it completely

Script Disable Startup Repair

Hi. Does this also disable the disk check that happens sometimes after an unclean shutdown? It hasn't run since I made these changes.

busterh said:

Hi..

Not sure what you're really asking me, but I do have an even cleaner solution:

In testing, we found that the command did not work properly with Windows 7 RTM....

But, through some pretty extensive testing today, we did figure out that it is still a bcdedit issue.

Here's how to do it, PROPERLY:

bcdedit /set {default} bootstatuspolicy ignoreallfailures

You can crash as often as you like and you will not be prompted for the Startup Repair.

To restore things to normal, simply issue the following command:

bcdedit /set {default} bootstatuspolicy displayallfailures

Again, either UAC must be turned off or you must run CMD as an Admin....

Boy, this was a tough one to crack! I'm getting too old for this!

Oh, and a bonus....this should work on all versions of Vista and Windows 7....Our tests were on Windows 7 32bit RTM.

does this block autochk from running on startup?

edit: no, it does not. something else did, probably AVG Free.

edit2: many people said it's AVG free, uninstalling this hasn't helped. restoring to displayallfailures hasn't helped.

Please start a new thread explaining in full the problem you're having. This old thread appears to encourage a bad practice, since Startup Repair should never be a default option unless you have serious problems needing repair.

gregrocker said:

Please start a new thread explaining in full the problem you're having. This old thread appears to encourage a bad practice, since Startup Repair should never be a default option unless you have serious problems needing repair.

this is terrible false. there are many very legitimate reasons why Startup Repair will trigger when there's nothing at all wrong with the installation.

gregrocker said:

Are you referring to the choice between "Start Windows Normally" and "Run Startup Repair" if there is a hard shutdown. This is not a default Startup Repair option, does not trigger Startup Repair - nor should it be or do either.

If you know "many very legitimate reasons why Startup Repair will trigger when there's nothing at all wrong with the installation" then please enlighten us with some of those reasons.

mine has been jumping straight to 'Run Startup Repair' and I have to hammer ESC on keyboard before it restores to an earlier point.

Reason #1: I'm overclocking the CPU and pushed it too far without enough voltage. This hasn't happened in a while.
Reason #2: I have 2 bad sticks of PNY 1600-99927 RAM that are giving me no end of trouble
Reason #3: I have RMA'd replacement sticks of RAM and my motherboard has trouble with 4 sticks of RAM and I need to increase drive strength or increase voltage supplied to the RAM to reach stability
Reason #4: Previous ASUS mobo that I returned has BIOS software defect in voltage supplied to CPU that consistently cmanifests after a WOL packet is sent, I run some stress testing software to check voltage droop on load, and the LLC voltage dips to 1.28v before sending the CPU to 1.6v after unloading.
Reason #5: I know what the hell I'm doing while troubleshooting my PC and don't need Windows freaking out on me and running system restore to a 'bootable restore point' by default every time reason numbers 1-4 happen.



more like Microsoft LVP imo.

rancur3p1c said:

gregrocker said:

Please start a new thread explaining in full the problem you're having. This old thread appears to encourage a bad practice, since Startup Repair should never be a default option unless you have serious problems needing repair.

this is terrible false. there are many very legitimate reasons why Startup Repair will trigger when there's nothing at all wrong with the installation.

Yeah, mine triggers every time I try to restart with a somewhat older RAID card. No fun when I am remote and it's stuck on the repair screen. It's because the BIOS doesn't always read the raid card as a boot option every time, so it reboots, and then reboots once more, causing a BSOD. I will try this to see if it lets me back into windows, thanks!

I have tried the solutions of the command prompt with the bcdedit.... but it doesn't work!! Mostly pc has been ok to startup normally, but today it went into the repair loop and couldn't be cancelled. Freshly reformated last month, and i have some precious games i don't want to erase
So i powered off manually and find nothing is wrong with it. I don't really want to mess up the internal pc stuff.

Hope someone can answer me! thanks