What annoys you?

Those of us who have worked intensely in this area here for years have evolved to use Startup Repair because it is less threatening to the average User than line commands which must often be tailored for each specific case, and it also screens for other problems at the same time since corruption is always a real possibility in these cases.

I did not say this is the only way, Michael, but simply am putting it forward as a Best Practice. I have not seen you working through these boot cases day after day, but always count on your oppo if I lift my head up out of the trenches for air or to share notes.

So feel free to put your line commands out there. I am always open minded and learning.

When two respected and knowledgeable members argue about the same thing. Any Windows issue nearly always can be fixed in at least 2-3 ways, both work and are right.

noobvious said:

seavixen32 said:

Emperor Panais of Antarctica?

Panais the Penguin is more like it!

Flies,when i am ready to eat something very nice and a fly appears from nowhere.

I have to say I prefer having the OPs run Startup Repair because it is more foolproof, and, as Greg said, often addresses problems Bootrec commands alone won't solve.

mjf said:

2) Fact: Startup Repair can fail

True, but in my experience, when that is the case, the bootrec commands don't work either. After all, one of the first things the Startup Repair does is automatically run the Bootrec commands. Usually, when Startup Repair fails to write the boot files in the proper location, it's because the wrong drive is set to Active (which can be corrected with Diskpart).

Yet:

Britton30 said:

Any Windows issue nearly always can be fixed in at least 2-3 ways, both work and are right.

+1

Keep it civil guys.

Without bothering to find links to the technical details of Startup Repair, I'll just say that this is the Chillout Room, where anyone with an internet connection can access.

Mr King