Home » Uncategories » How to Fix Mac Computer Stuck on Boot/login Screen Updated FREE

How to Fix Mac Computer Stuck on Boot/login Screen Updated FREE

How to Fix Mac Computer Stuck on Boot/login Screen

Skip to principal content

Advanced troubleshooting for Windows kick problems

Article
03/16/2022
11 minutes to read

Note

This article is intended for use by support agents and Information technology professionals. If y'all're looking for more than general information almost recovery options, see Recovery options in Windows 10.

Summary

There are several reasons why a Windows-based calculator may have issues during startup. To troubleshoot boot issues, first decide in which of the post-obit phases the computer gets stuck:

Phase	Boot Process	BIOS	UEFI
1	PreBoot	MBR/PBR (Bootstrap Code)	UEFI Firmware
2	Windows Kick Manager	%SystemDrive%\bootmgr	\EFI\Microsoft\Kick\bootmgfw.efi
3	Windows OS Loader	%SystemRoot%\system32\winload.exe	%SystemRoot%\system32\winload.efi
4	Windows NT Bone Kernel	%SystemRoot%\system32\ntoskrnl.exe

1. PreBoot

The PC's firmware initiates a Power-On Self Exam (Mail service) and loads firmware settings. This pre-boot process ends when a valid system disk is detected. Firmware reads the master boot record (MBR), and then starts Windows Boot Manager.

2. Windows Boot Manager

Windows Boot Manager finds and starts the Windows loader (Winload.exe) on the Windows boot partition.

3. Windows operating organization loader

Essential drivers required to start the Windows kernel are loaded and the kernel starts to run.

iv. Windows NT Bone Kernel

The kernel loads into retention the system registry hive and additional drivers that are marked as BOOT_START.

The kernel passes control to the session managing director process (Smss.exe) which initializes the organisation session, and loads and starts the devices and drivers that are non marked BOOT_START.

Hither is a summary of the kicking sequence, what volition be seen on the display, and typical boot problems at that betoken in the sequence. Before starting troubleshooting, you lot have to understand the outline of the kick process and brandish condition to ensure that the issue is properly identified at the beginning of the engagement.

Click to enlarge

Each stage has a different approach to troubleshooting. This commodity provides troubleshooting techniques for problems that occur during the first 3 phases.

Note

If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the bike:

Bcdedit /fix {default} recoveryenabled no

If the F8 options don't work, run the post-obit control:

Bcdedit /fix {default} bootmenupolicy legacy

BIOS phase

To determine whether the organization has passed the BIOS phase, follow these steps:

If there are any external peripherals connected to the reckoner, disconnect them.
Check whether the hard disk light on the physical computer is working. If it is not working, this indicates that the startup process is stuck at the BIOS stage.
Press the NumLock central to see whether the indicator lite toggles on and off. If it does not, this indicates that the startup process is stuck at BIOS.

If the system is stuck at the BIOS phase, there may be a hardware problem.

Boot loader phase

If the screen is completely black except for a blinking cursor, or if you lot receive one of the following error codes, this indicates that the boot process is stuck in the Kicking Loader phase:

Kicking Configuration Data (BCD) missing or corrupted
Kick file or MBR corrupted
Operating organization Missing
Boot sector missing or corrupted
Bootmgr missing or corrupted
Unable to boot due to system hive missing or corrupted

To troubleshoot this problem, use Windows installation media to get-go the computer, press Shift+F10 for a control prompt, and so utilise any of the following methods.

Method 1: Startup Repair tool

The Startup Repair tool automatically fixes many common bug. The tool also lets you quickly diagnose and repair more circuitous startup problems. When the figurer detects a startup problem, the calculator starts the Startup Repair tool. When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the trouble. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically.

To practise this, follow these steps.

Showtime the system to the installation media for the installed version of Windows. For more information, see Create installation media for Windows.
On the Install Windows screen, select Adjacent > Repair your figurer.
On the Choose an pick screen, select Troubleshoot.
On the Avant-garde options screen, select Startup Repair.
Afterward Startup Repair, select Shutdown, then turn on your PC to run across if Windows tin can boot properly.

The Startup Repair tool generates a log file to help you sympathize the startup problems and the repairs that were made. You can find the log file in the following location:

%windir%\System32\LogFiles\Srt\Srttrail.txt

For more data, see A Stop fault occurs, or the figurer stops responding when you try to start Windows Vista or Windows seven

Method 2: Repair Kicking Codes

To repair kicking codes, run the following control:

              BOOTREC /FIXMBR

To repair the kicking sector, run the following command:

              BOOTREC /FIXBOOT

Note

Running BOOTREC together with Fixmbr overwrites only the main boot code. If the corruption in the MBR affects the partition table, running Fixmbr may not fix the problem.

Method 3: Prepare BCD errors

If yous receive BCD-related errors, follow these steps:

Scan for all the systems that are installed. To practice this, run the post-obit command:

                  Bootrec /ScanOS

Restart the estimator to check whether the trouble is fixed.

If the problem is not fixed, run the following commands:

                  bcdedit /export c:\bcdbackup  attrib c:\boot\bcd -r -south -h  ren c:\kicking\bcd bcd.old  bootrec /rebuildbcd

Restart the system.

Method 4: Supersede Bootmgr

If methods i, 2 and 3 practice not fix the problem, supplant the Bootmgr file from drive C to the Arrangement Reserved sectionalization. To do this, follow these steps:

At a command prompt, change the directory to the System Reserved partitioning.

Run the attrib control to unhide the file:

                  attrib -r -s -h

Navigate to the system drive and run the same command:

                  attrib -r -s -h

Rename the Bootmgr file as Bootmgr.former:

                  ren c:\bootmgr bootmgr.sometime

Navigate to the system drive.
Copy the Bootmgr file, and and so paste information technology to the System Reserved partition.
Restart the figurer.

Method 5: Restore System Hive

If Windows cannot load the system registry hive into memory, you must restore the system hive. To practise this, employ the Windows Recovery Environment or apply Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack to C:\Windows\System32\config.

If the problem persists, you may want to restore the system country backup to an alternative location, and then retrieve the registry hives to exist replaced.

Note

Starting in Windows 10, version 1803, Windows no longer automatically backs upwards the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a organisation restore point. For more details, check this article

Kernel Phase

If the system gets stuck during the kernel phase, y'all experience multiple symptoms or receive multiple error messages. These include, but are not limited to, the following:

A Stop mistake appears after the splash screen (Windows Logo screen).
Specific error code is displayed.

For instance, "0x00000C2" , "0x0000007B" , "inaccessible boot device" and then on.
- Avant-garde troubleshooting for Stop error 7B or Inaccessible_Boot_Device
- Advanced troubleshooting for Event ID 41 "The system has rebooted without cleanly shutting downwardly showtime"
The screen is stuck at the "spinning bicycle" (rolling dots) "system decorated" icon.
A black screen appears later on the splash screen.

To troubleshoot these problems, endeavour the post-obit recovery kicking options 1 at a time.

Scenario 1: Try to get-go the computer in Safe mode or Final Known Practiced Configuration

On the Advanced Boot Options screen, try to start the reckoner in Safety Mode or Rubber Mode with Networking. If either of these options works, employ Consequence Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the issue logs, follow these steps:

Use one of the following methods to open Event Viewer:
- Click Get-go, signal to Administrative Tools, then click Event Viewer.
- Kickoff the Result Viewer snap-in in Microsoft Direction Console (MMC).
In the console tree, expand Issue Viewer, and so click the log that you want to view. For instance, click Organisation log or Application log.
In the details pane, double-click the event that you want to view.
On the Edit card, click Copy, open a new document in the plan in which you lot desire to paste the effect (for case, Microsoft Word), and then click Paste.
Utilize the Up Arrow or Downwardly Arrow central to view the clarification of the previous or next upshot.

Clean kick

To troubleshoot problems that affect services, do a clean boot by using System Configuration (msconfig). Select Selective startup to exam the services i at a fourth dimension to determine which one is causing the problem. If you lot cannot find the cause, try including arrangement services. However, in most cases, the problematic service is 3rd-party.

Disable any service that you observe to exist faulty, and effort to start the computer over again by selecting Normal startup.

For detailed instructions, see How to perform a make clean boot in Windows.

If the figurer starts in Disable Driver Signature mode, start the computer in Disable Driver Signature Enforcement mode, and so follow the steps that are documented in the following article to decide which drivers or files require driver signature enforcement: Troubleshooting boot trouble acquired by missing driver signature (x64)

Note

If the computer is a domain controller, endeavour Directory Services Restore mode (DSRM).

This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2"

Examples

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or past using another method. These problems might crave that you reinstall the operating arrangement. Microsoft cannot guarantee that these issues can exist solved. Modify the registry at your ain risk.

Mistake code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)

To troubleshoot this Stop error, follow these steps to filter the drivers:

Go to Windows Recovery Environment (WinRE) by putting an ISO disk of the system in the disk drive. The ISO should be of same version of Windows or a later version.
Open the registry.
Load the system hive, and name information technology every bit "test."
Under the following registry subkey, check for lower filter and upper filter items for Non-Microsoft Drivers:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class
For each 3rd-party driver that you lot locate, click the upper or lower filter, so delete the value data.
Search through the whole registry for similar items. Process as an advisable, and so unload the registry hive.
Restart the server in Normal fashion.

For additional troubleshooting steps, see the following articles:

Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device

To gear up problems that occur after you install Windows updates, check for awaiting updates by using these steps:

Open a Command Prompt window in WinRE.

Run the command:

                  DISM /image:C:\ /go-packages

If there are any pending updates, uninstall them by running the post-obit commands:

                  DISM /image:C:\ /remove-package /packagename: proper noun of the packet

                  DISM /Epitome:C:\ /Cleanup-Epitome /RevertPendingActions

Endeavour to start the computer.

If the reckoner does not offset, follow these steps:

Open up A Command Prompt window in WinRE, and showtime a text editor, such as Notepad.
Navigate to the system drive, and search for windows\winsxs\pending.xml.
If the Pending.xml file is found, rename the file equally Pending.xml.former.
Open the registry, and and then load the component hive in HKEY_LOCAL_MACHINE equally a examination.
Highlight the loaded exam hive, so search for the pendingxmlidentifier value.
If the pendingxmlidentifier value exists, delete the value.
Unload the examination hive.
Load the system hive, proper name it equally "exam".
Navigate to the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TrustedInstaller
Change the Start value from 1 to 4
Unload the hive.
Try to start the reckoner.

If the Stop error occurs late in the startup process, or if the Terminate error is withal being generated, you can capture a retentivity dump. A good memory dump can aid decide the root cause of the Stop fault. For details, meet the post-obit articles:

Generate a kernel or complete crash dump

For more information about page file bug in Windows 10 or Windows Server 2016, see the post-obit:

Introduction to folio files

For more information about Stop errors, see the following Knowledge Base article:

Advanced troubleshooting for Finish error or blue screen fault issue

If the dump file shows an error that is related to a commuter (for example, windows\system32\drivers\stcvsm.sys is missing or corrupted), follow these guidelines:

Check the functionality that is provided past the commuter. If the driver is a tertiary-party boot driver, make sure that you sympathise what information technology does.
If the driver is not of import and has no dependencies, load the organisation hive, and then disable the driver.
If the end fault indicates organisation file abuse, run the organization file checker in offline mode.
- To exercise this, open WinRE, open a command prompt, and then run the following command:
```
                      SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows                                          
```
  For more data, see Using Arrangement File Checker (SFC) To Fix Problems
- If there is deejay corruption, run the check disk command:
```
                      chkdsk /f /r                                          
```
- If the Terminate mistake indicates general registry corruption, or if you lot believe that new drivers or services were installed, follow these steps:
  1. Starting time WinRE, and open a Command Prompt window.
  2. Offset a text editor, such as Notepad.
  3. Navigate to C:\Windows\System32\Config.
  4. Rename the all five hives by appending ".erstwhile" to the name.
  5. Copy all the hives from the Regback folder, paste them in the Config folder, so try to start the calculator in Normal manner.

Note

Starting in Windows x, version 1803, Windows no longer automatically backs upward the system registry to the RegBack folder.This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a organisation with a corrupt registry hive, Microsoft recommends that you lot use a arrangement restore point. For more details, check this commodity.

Feedback

Submit and view feedback for