Stuck In The Loop Mac OS

1. Stuck In The Loop Mac Os X
2. Stuck In The Loop Mac Os 11
3. Stuck In The Loop Mac Os Catalina

The second one is another fault with Mac OS where the computer does not connect to the network while booting. Yet the computer (while booting up to about half way) tries to authenticate with our network. Over and over and over again. This is why it hangs at 50%. Annoying but there's no permanent solution until Mac OS steps up its game.

• If your device runs out of power, connect it to a power source and turn on the device to let the update or restore complete. If you think the update is stuck, press one of the buttons. If you see an updating message, the update is still in progress. In some cases, you may see the progress bar complete, then start again.
• If you're having trouble logging into your Mac or MacBook after installing macOS Big Sur, or you're stuck in a loop where you log in, then get logged out again, the following steps might help.

this usually has to do with a corrupt character that the finder cannot display in the desktop. for some reason it does not effect the finder when it is in a folder other than desktop. alot of times there will be a .textClipping file that is causing the constant crash loop, do you have one of those?
the other root of the problem is many times Fonts as well. have you removed some fonts from the /System/Library/Fonts folder? Some of the asian fonts are actually needed to prevent finder crashing when it encounters this bad character as well...

Note also i have had the same problem with corrupt dstore files, if anyone wants a copy of a corrupt dstore file? send us an email

You know, this exact thing happened to me a few days back. I had installed the newest version of DesInstaller (an uninstall program) and mistakenly removed the AsianCharacters.pkg (called something like that). I got the finder loop as soon as the uninstall was done. Restarting had no effect. Finally I booted from the system DVD and did an Archive and Install. Not sure if it was the package I removed or DesInstaller itself that caused the problem. Wish I had thought of the Path Finder thing. Ah well!

Hmmm. Wish I had read the other comment before posting. Lesson learned.

This bug can also happen if you have a corrupt application bundle, e.g. one with a damaged .plist file or icon. Apple could put some more work into making the Finder more robust in dealing with these sorts of things.

I see this problem a lot. As other posts have mentioned it's usually the fault of an evil .textclipping file sitting on the desktop. The problem is reproducible in Mail.app by dragging a word document attachment from an email to the desktop. Only seems to happen if the user has previously changed their default program for opening word files from MS office to TextEdit.
I always do a custom install of Mac OS X without the asian language support files to save HD space and these might be needed to display the text clipping on the desktop else the Finder crashes infinitely. It's a pain that the finder in 10.4.5 isn't more robust in this manner. If the user is a non admin user they are helpless to fix this.

To weird. Wish I had found this thread earlier. I just spent hours trying to find a cure for this ailment. I first thought it had to do with the new security update. Did all the usual.
Finally logging in as another user I just happenedd to look at my other desktop and saw this attachment I had dragged there earlier. Bingo... file name and I too have removed asian fonts.

Doing the mv command robg recommends will not preserve all resource forks and metadata on the desktop, probably some users will not want to do that!
Instead using ditto and then removing the files with rm will be a better way to do it, if any metadata is to preserved.
~ Jørgen

Actually with OS X 10.4 Apple sadly modified common Unix tools such as cp, mv, tar, rsync to supprt resourse forks so it will retain the fork unless you set a flag to not do so unless you are on an older version of OS X of course then you will need ditto or cpmac.

Does anyone know if Apple are aware of this Finder problem? I don't have developer status or access to the radar system and have been waiting for a bugfix since 10.4.0. I'd rather avoid installing the Asian Fonts package to fix this as it will add 1Gb to my Apple System Restore build image. I also use Monolingual to remove unused languages to save space.
Cheers for any info.

Another reason for Finder crahsing constantly is a another damaged .plist. Had this problem on several Macs before. If this hint doesn't work, try to remove
~/Library/Preferences/com.apple.sidebarlists.plist
To the fonts problem: I had so many problems with fonts removed by Users. It not only affects OS X itself, but also other programs if their fonts are removed. Filemaker 8, Office 2004 etc. tend to crash with debug entries (from crash-log) like
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x9073fba4 CFRetain + 60
1 com.apple.CoreText 0x90235b08 TFontCascade::InitParams() + 324
2 com.apple.CoreText 0x90235bac TFontCascade::CreateFallback(__CTFont const*, __CFString const*, CFRange) const + 52
If you see simular entries, check if all standard fonts are installed.

Awesome -- this just saved me hours of rebuilding that wouldn't have worked anyway if the user account was re-imported. The culprit was a file on the desktop named ???.textClipping . I suspect this appeared due to a failed/incomplete download, as it wasn't user-created. Since deleting it fixed the finder loop, it may be possible to re-create the problem (if one were so inclined) by creating such a file and rebooting or logging out.

Did what to post suggested but nothin doing, finder still crashes. Path Finder worked. The Finder only crashes when I move files over a gb. Any ideas? Thanks!

Fix: Boot into Safe Mode

1. 1. Insert the disc and reboot the system.
2. 2. Press any key to boot from the DVD.
3. 3. Choose your keyboard layout.
4. 4. Click Repair your computer at the Install now screen.
5. 5. Click Troubleshoot.
6. 6. Click Advanced options.
7. 7. Click Startup Settings.
8. 8. Click Restart...

7 Fixes to Stuck in Windows 7 Startup Repair Loop

'My computer keeps running Startup Repair during every startup and I can't boot it normally. I tried running Startup Repair multiple times but I'm still getting the same problem. Startup Repair won't seriously automate repair at all. I got stuck in an infinite loop.'

Follow the fixes to troubleshoot your Windows Startup Repair loop.

1 - Windows 7 Startup Repair Infinite Loop Error Details

Windows Error Recovery

Windows failed to start. A recent hardware or software change might be the cause.

If Windows files have been damaged or configured incorrectly, Startup Repair can help diagnose and fix the problem. If power was interrupted during startup, choose Start Windows Normally.
(Use the arrow keys to highlight your choice.)

Launch Startup Repair (recommended)
Start Windows Normally

Description: Fix problems that are preventing Windows from starting

Startup Repair will fail to load, launch but fail to repair, or run and claim repairs have been executed. Your PC will continue to attempt to endlessly start Startup Repair each boot. In Windows 8, Windows 8.1 and Windows 10 this is called Automatic Repair:

Stuck In The Loop Mac Os X

2 - Startup Repair Error Symptoms

Unexpected PC shutdown, virus, malware, driver issues, damaged BDC settings, corrupted boot partition, blue screen of death as well as a black screen of death on reboot, all those factors account for Windows startup problems.

As the 'Windows error recovery' suggests, Start Repair should automatically fix the abnormal Windows startup. However, when you choose the recommended option, you'll only confront 2 facts:

1. Startup Repair takes a fairly long time to load or launch.

2. Startup Repair immediately runs but the repairing process never finishes.

In both situations, on each reboot, your PC will continuously attempt to call Startup Repair for the fix, meanwhile, getting stuck in a Startup Repair loop that never ends

3 - Troubleshoot Windows Automatic Startup Repair Infinite Loop Error with 7 Fixes

A clean Windows installation is a guaranteed fix for Windows Startup Repair taking forever, but it costs a complete data loss. So, is there another option to recover from an infinitely looping Startup Repair without reinstalling Windows?

We gave the possible fixes from easy to complex, from safe to risky. You'd better try them sequentially.

Fix 1. Disable Automatic Startup Repair to Fix Startup Repair Loop

You should try to disable automatic restart, although it could not solve the boot error, it can stop the endless restart.

Step 1. Restart your computer.

Step 2. Wait for your BIOS to complete POST (the screen with your manufacturer logo and/or system information).

Step 3. Quickly begin tapping F8 repeatedly, until you see the list of boot options.

Step 4. Choose 'Disable automatic restart on system failure'.

Step 5. Press 'Enter' and wait for your PC to boot.

Fix 2. Run CHKDSK Command to Check and Repair Drive Errors

This helps check or even repair the drives to tackle file system corruption.

Step 1. Boot Windows from the bootable device. (If you cannot boot, use Window 7 installation CD.)

Step 2. Navigate to the 'Repair your computer' option and select 'Command Prompt'.

Step 3. In the Command Prompt window, type chkdsk /r c: and press 'Enter'. (c represents the drive where Windows is installed)

Step 4. Click 'Y' so that the next time the system restarts, the CHKDSK utility can check the disk errors and try to fix them. Restart the system and let CHKDSK check hard drive errors and repair.

If you don't have any technical know-how and want to minimize data risks, using third-party software could be a better choice. The Command line is suitable for computer professionals since wrong commands can cause severe problems. Therefore, we strongly recommend you try an automatic command line alternative.

EaseUS Tools M is a practical computer fixing tool that is safe and light-weighted. It's a perfect alternative to CHKDSK command. Use this one-click tool to solve your computer issues.

To fix file system error or disk error:

Step 1: DOWNLOAD EaseUS Tools M for Free and install it.

Step 2: Open the software and select the 'File showing' option.

Step 3: Choose the drive and wait for repairing. After the operation completes, click the 'View' button to check the drive.

Fix 3. Run Bootrec to Fix Damaged or Corrupted BCD Settings

If the bootloader installation or configuration comes with some errors, the startup repair loop could happen as well. You could solve this error by following the steps below.

Step 1. In the same way to open Command Prompt as the second fix did.

Step 2. In the Command Prompt window, type those following commands and press 'Enter'.

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Step 3. Restart the system and let bootrec repair MBR.

Fix 4. Perform System Restore to Solve Windows Startup Repair Loop

The System Protection is enabled by default, you can use it to restore your computer to an earlier state to fix your problem.

Step 1. Boot Windows from the bootable device.

Step 2. Click 'Troubleshoot > System Restore'.

Step 3. Follow the wizard instructions to continue the process. Choose a restore point before the date when the Automatic Startup Repair loop error happened.

Fix 5. Delete the Problematic File to Resolve Startup Repair

Step 1. Access Command Prompt again and enter the following command:

cd C:WindowsSystem32LogFilesSrt
SrtTrail.txt

Step 2. Then, you could see 'Boot critical file c:windowssystem32driverstmel.sys is corrupt.' Type the following command:

cd c:windowssystem32drivers
delvsock.sys

Restart your PC. If these steps can not help, try the following troubleshooting steps.

Fix 6. Restore Windows 10 Registry to Fix Repair Loop

Step 1. In the Windows Boot Options menu, choose 'Troubleshoot >Advanced Options>Command Prompt'.

Step 2. In Command Prompt, type the following command in Command Prompt and then hit 'Enter'.

cd C:windowssystem32logfilessrt

Change your drive letter according to your needs.

Step 3. Type txt to open the file in notepad.

Step 4. Press 'Ctrl + O'. Select 'All files' from file type and navigate to C:windowssystem32.

Step 5. Right-click CMD and select 'Run as administrator'. Type the following command and press 'Enter'.

cd C:windowssystem32config

Step 6. Backup those files by renaming Default, Software, SAM, System and Security files to .bak. Type the following command one by one and hit 'Enter':

rename DEFAULT DEFAULT.bakrename SAM SAM.bak
rename SECURITY SECURITY.bak
rename SOFTWARE SOFTWARE.bak
rename SYSTEM SYSTEM.bak
copyc:windowssystem32configRegBack c:windowssystem32config

Step 7. Restart your PC to check if you have solved the error.

Fix 7. Check Device Partition and Osdevice Partition

Sometimes, if your device partition values aren’t correct, you will get stuck in the startup repair loop. Follow the steps below to check the device partition and os device partition and fix your error.

Step 1. In Command Prompt, type bcdedit and press 'enter'.

Step 2. Find device partition and os device partition values. Make sure their values are correct and set to the correct partition.

Windows is preinstalled on C partition only, and the correct value is C. Enter the following commands and press 'Enter' after each one if the value isn’t set to C.

bcdedit /set {default} device partition=c:
bcdedit /set {default} osdevice partition=c:

After that, reboot the PC and fix the Windows startup repair loop.

Additional Fix - Boot into Safe Mode in Windows 7/8/10

Often booting into Safe Mode and uninstall recently install device drivers or software may fix the Automatic Repair loop error. To boot into Safe Mode of a Windows 7, 8, 8.1, or 10 system, you need to have the original DVD or USB. If you do not have the installation disc, follow the guide from Microsoft to create a Windows Installation Media. Then enter Safe Mode:

Step 1. Insert the disc and reboot the system.

Step 2. Press any key to boot from the DVD.

Step 3. Choose your keyboard layout.

Step 4. Click Repair your computer at the Install now screen. Choose 'Troubleshoot > Advanced options >StartupSettings'.

Choose a Safe Mode option (Safe Mode, Safe Mode with Networking, and Safe Mode with Command Prompt) to enter.

How to Recover Data After Fixing Startup Repair Infinite Loop

Besides a clean install of the Windows operating system, the fixes for users to get rid of an endless startup repair loop including system restore and PC factory resetting will also result in part of computer data loss.

It's not the end of the day and a third-party data recovery tool perhaps can salvage your data. For example, EaseUS Data Recovery Wizard is able to recover data after formatting, deleting, PC resetting, system refreshing, and more. And You deserve a try for its data recovery software and see if the software really helps find your lost data.

Step 1. Select a location and start scanning.

Launch EaseUS Data Recovery Wizard, hover on the location(hard drive partition, external HDD, Card devices) where you lost data, then click 'Scan'.

Stuck In The Loop Mac Os 11

Step 2. Preview and select the files.

Wait until the scanning completes. If you need to double-click the item to preview the file, then select the data you attempt to recover.

Stuck In The Loop Mac Os Catalina

Step 3. Recover lost data.

Click 'Recover', choose a location to save the recovered data, then click 'OK'. You should store the data in another place instead of the original one.

You get 7 ways to get rid of the Startup Repair Windows 7 loop, no matter whether you have an installation disc or not. Don't worry if the windows 7/8/10 startup repair is taking forever and you cannot stop or cancel it. Also, you can get back lost data after you have fixed the error with EaseUS data recovery software.

Stuck In The Loop Mac OS