My Computer
At a glance
Windows 7 pro x64
- Computer type
- PC/Desktop
- OS
- Windows 7 pro x64
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.
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.
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.
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.