Windows 7 Startup Repair Disjoining System From Domain

restorestartupwindows 7

We have recently run into the following issue :

Startup Repair : The Startup Repair tool can solve many common startup problems automatically. Startup Repair performs an exhaustive analysis to diagnose your startup problems, including analyzing boot sectors, the Boot Manager, disk configuration, disk integrity, BCD registry file integrity, system file integrity, registry integrity, boot logs, and event logs. It will then attempt to solve the problem, which may involve repairing configuration files, solving simple disk problems, replacing missing system files, or running System Restore to return the computer to an earlier state. Because Startup Repair performs these tasks automatically, you can solve startup problems much faster than performing the analysis and repair manually.

In our case, this behavior is disjoining our systems from the domain because it is restoring the system back to it's original image. It blows away most if not all of the installed software. I'm not convinced Startup Repair is making the right choice.

How can this be disabled if we choose to do so and can it be disabled globally (bcdedit ?) ? If it is disabled would the systems then just "Blue Screen" when a similar event occurs ?

Let me know if any of you have had to deal with this issue, or what really is the best practice here. I would hate for a large power failure etc to cause 100 systems to invoke startup repair and disjoin themselves.

Thanks

Best Answer

This should do the trick:

bcdedit /set {default} bootstatuspolicy ignoreallfailures

or

bcdedit /set {default} recoveryenabled No

Also, you can clear the registry key here: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager \ BootExecute

(Haven't tried this yet, but it looks promising)

Windows self-repair... never quite what I was hoping for.

As for automating, it looks like bcdedit has /save and /import flags - so if that export is transferrable to another system, you should be able to roll that into a login script easily.

(pre-edit idealistic thinking) Sorry if I'm oversimplifying, but if you take a system snapshot after the system is completely setup (or update your image to include that snapshot), I'd think that would cause the automatic rollback to revert to the state you're hoping for.

Related Topic