Windows 10: Preparing Automatic repair continuing saga

I keep getting the "Preparing Automatic Repair" comment and the related "diagnosing your PC' Etc" , along with the dreadful slow restart. I've searched the forum for an answer and it appears the only real solution to this is to reset Windows 10 and then reload various programs. Is there no easier solution to this? I had a quick comment "Drive IRLQ.....? Didn't quite catch what it was saying. Is this related? There doesn't seem to be any device driver errors in my device list. Win 8.1 was also slow restarting but this has become painful.
Would falling back to Win 8.1 then re-downloading Win 10 work or is that even possible?
Thanks for listening!

:)

 

Stuck in Continuous "Preparing Automatic Repair" LOOP!

Hi,

We got your concern. We would like to know if you have tried uninstalling the update and reinstall everything? There are some that can be fixed by doing this. Have you tried running your computer in safe mode? Did you install a software before this issue happens?

We'll be waiting for your response.

 

Stuck in Continuous "Preparing Automatic Repair" LOOP!

Have an iMac and installed Windows 10 on Bootcamp (Unknown Date). I updated Windows 10 on 23 October 2016 with the latest update. I had to delete the version of McAfee due to not being compatible with the update. After installing the update I installed the
version of McAfee compatible with the update. Everything was working properly until 26 October 2016 when I booted up my computer and it started "Preparing Automatic Repair". I have been stuck in this loop ever since and have tried all the options available
with no results!!

I have spoke with a Microsoft technician 29 October 2016 and was told he could not do anything and was connected to the Microsoft Store to make an appointment to take my computer in to hopefully be analyzed and repaired!

I am VERY frustrated and confused that:

#1 My computer is messed up.

#2 That the Microsoft HELP line is unable to help.

#3 I have to take my computer to the local Microsoft Store.

Mahalo (Hawaiian for Thank You) in advance for any help!

 

Hi if you're trapped in the boot loop, the only way I've found out is pretty horrible. Power off, then power on and a couple of seconds later switch the power off/pull the plug out (DC, laptop)..

Press the PC power button, release, wait a few seconds, do a cold boot.

A number of times after a thermal shutdown (in 8 and 10) that's what I've had to do. Otherwise restart, power up works normally. I'd struggle to say I've ever seen automatic repair repair anything..

That's been the only way back to a normal boot sequence.

Beyond that, always be prepared for a non-bootable PC and use disk imaging regularly and create the boot disk for the program (e.g. Macrium Reflect, Aomei Backupper...). Good luck

 

Hello oldbiker Welcome to the Ten Forums!

Too many times you can't get into the F8 boot options to use the repair tools available which includes the Startup Repair option. If you saw the 10 Installation media created and not simply seen the instant online by way of updates upgrade through the 10 app you already have one live media means to run repair tools. If not able to get back into 10 you wouldn't be able to see the Recovery Drive option you need to see a flash drive made into a recovery stick either.

What dalchina was referring to was recycling power on the power supply itself where you simply discharge the main capacitor inside. When a supply won't work when the power button or switch is used that is a method to bring life back into the supply itself to see the system power up normally again. The live media however will not only you to run the recovery options available but to run the Disk Check tool from the command prompt to scan and repair disk errors.

 

Hi, I've reread this a couple of times... agree with Nighthawk it would be great to start with a disk check. (E.g. schedule chkdsk /r to run on restart).

It sounds like you can boot normally, if slowly- am I then correct in thinking you (sometimes) get a BSOD crash into an automatic repair loop?

Can you boot into Safe Mode successfully and reliably?

If so, try using msconfig in normal mode to disable everything bar MS services (hide them) and task man to disable startups. Reboot and if successful, progressively enable services then startups until you find anything that causes the boot to slow or fail.

Remember programs can install drivers that are not necessarily device related, so don't show in Dev Mgr, but can cause conflicts.

It can also be the case that despite disabling programs as above- or even using Safe Mode- that a few programs will load drivers anyway.

 

I ended up to a reset. I was able to get it to restart "ok" in safe mode but it was so painfully slow I decided to bite the bullet so to speak. Thanks for your advise. Nice to know a place to go that can actually help!!

 

Sorry to hear you were forced to take that route! But with the upgrades to 10 seen on three systems already two desktops and a laptop I ended up seeing serveral clean installs between all three. The first desktop saw one following the second upgrade install to repair the upgrade!

The second desktop saw two clean installs one following a nuke of the single drive after first seeing a dual boot split up of the drive to put 10 on the second primary until upgrading 7 to 10 and once activated I nuked the first and moved the fresh second back and grew that out but needed the second clean install to see 10 boot up since the first had the boot files and BCD Store! The clean install activated only following the upgrade over 7 as I confirmed for that. Later a second drive added in saw the system image made of 7 restored to that drive for the planned dual boot.

And ironically the third being the laptop ended up seeing three clean installs(seems to increase by number for each new pc! *Eek*chuckle) with the first 32bit clean install immediately following the activated upgrade over the 32bit 7 Home Premuim preinstall which later saw the 64bit 10 Home replace the first clean install but couldn't resize the OEM primary any! The drive had to be wiped clean! Subsequently a smaller primary about 200gb with the remainder converted to a storage backup partition took place.

So where were amd what were the problems? The first main build here didn't see the storage drives unplugged until reviewing the clean install guide where the warning about having any non OS drives or devices with rewriteable memory was provided. By then a good number of failed upgrade attempts were first thought to be with the clone of the then 7 host drive followed by the temp 7 with SP1 clean install still not seeing 10 go on!

Once the two storage drives were unplugged and 10 went on it was "Buggy" not allowing av or other softwares besides Steam and a few other older games to go on. The Upgrade to Repair saw good results but would not activate during that first week 10 was out. That was replaced the following weekend. As for the second case besides the need to replace the first clean install not one issue with the upgrade to find while that was still on. The laptop however saw the missing Start button and a blank Settings screen and no access to the AllApps!

One out of three can't be too bad can it? But with any new version of Windows being looked over in the past I always had to expect ending up seeing multiple clean installs anyways just for simply trying things out as well as what was seen when testing 7 in beta form back in 2009. Back then however you didn't need to see upgrade installs since even the upgrade media could still see a clean install from that. 10 is the change in another loop of things have worked all these years.

 

I think a good deal at times is how the upgrade takes place. For the first system the copy of 7 was brand new even with SP1 and a lengthy list of updates but was likely seeing something simply not go on fully due to the prior failed attempts leaving traces on the drive. Yet at the same time something may simply have not copied over fully from the flash drive during the setup file copy process..

The second desktop had a 4yr. old copy of 7 Pro there and had hardly been used in all the time since it first intended as a spare pc from parts gathered up from other builds and didn't need much of anything. Smooth sailing until dumping the first primary to move the second back in hopes of building a new BCD store which didn't come about. The laptop bought in May 2012 had seen some steady and then only light use and now simply used to play media files and dvd movies for someone. The upgrade came out Buggy as all Heck! You knew right away something was beyond repair!