Welcome everybody!
On this video,
I will show you how to fix blue screen error of Startup Repair Tool with this error message:
“Automatic Repair couldn’t repair your PC” “Startup Repair couldn’t repair your PC"
Log file C:\windows\system32\logfiles\Srt\SrtTrail.txt
This error message is generated when the Startup Repair tool fails to fix errors that prevent your computer from booting normally,
and may associated with others blue screen errors, such as,
MACHINE_CHECK_EXCEPTION BSOD, or another error message.
There are many sources that can lead to this problem,
hence It’s too hard to show you only one solution for all of them,
so I will show you how to determine the exact error source
in order to select the most applicable solution from the suggested methods on this video.
The video contents is divided into three main parts:
Part number 1: will show you how to identify the exact error source either from the last changes you have made or by opening the SrtTrail log file.
Part number 2: will show you how to identify boot partition.
Part number 3: contains 12 methods to fix this issue, according to the identified error in addition to general methods.
The first part: How to identify the error source:
Before doing anything,
memorize the first letter in the log file path in your computer,
which is the letter of windows partition,
because you have to use it inplace of the D, which is my windows partition if you have another letter.
To open SrtTRail.txt file, do the followings:
From startup repair blue screen, click on advanced options then select troubleshoot option
Open command prompt
Type this command and press Enter from Keyboard to execute the command: NOTEPAD D:\WINDOWS\SYSTEM32\LOGFILES\SRT\SRTTRAIL.TXT
These 0x0 codes indicate that there is no error found in the test performed
Scroll down until you see the Root cause found.
As you can see, the error cause in my PC says that “NO OS FILE FOUND ON DISK”,
with error code =0x20,
and the startup repair tool suggested a PARTITION TABLE REPAIR as a REPAIR ACTION.
On my second operating system, the root cause and associated error code are different as well as the repair action.
Also, your computer may have another root cause.
If you can remember the last changes that happen in computer before appearance of this problem, you will be able to reach the appropriate solution easily.
For example, if the problem is related to the latest Windows update, delete that update to fix your problem.
If the problem occurs after installing a driver or app, delete that installation by booting the computer in safe mode or using Driver Manager View tool.
If the problem occurs after deleting a file, replace that file from a bootable USB of Windows installation or from backup files.
You will see all the methods to solve this problem in the third part of this video, but you will have to choose the appropriate method yourself according to identified error source.
If the computer restarted to this error code while using it, you can use BlueScreenView tool to open memory dumb file to show the affected file that cause the system failure.
Download the BlueScreenView.exe tool using your mobile then copy it into a USB pen drive.
The link is available in the video description.
Connect the USB drive to your computer.
Type notepad and hit Enter
Press Ctrl + O keys from keyboard to open files explorer.
Click on This PC icon then Open the USB drive.
Change file of types option to All
Right-click on the BlueScreenView file and select, Run as Administrator option
Click on Options tab and open Advanced options
Replace the X with the letter of your windows partition then click OK.
As you can see, the MiniDumb is available in my PC with this error code: 0xc00002e3, and its related to corruption of boot configuration data.
Second part: how to identify boot and recovery partitions:
1. Open command prompt.
2. Type DISKPART and hit Enter.
3. Type LIST DISK and hit Enter.
If you see this asterisk (*) under GPT column, then your disk is GPT (UEFI).
If there is no asterisk, then your disk is MBR.
4. Type SEL DISK 0 to select disk that contains windows if you have more than one disk.
5. Type LIST VOL and hit Enter to show available volumes.
As you can see, I have 2 volumes with size less than 5 megabytes with no assigned letter for both,
and boot and recovery partitions may have size of 500 MBs or less and may or may not have an assigned letter.
Also in rare cases, your PC may came with assigned letter for one or both partitions.
Now to identify which one is the boot and which one is the Recovery partition,
you have to assign a letter for one or both of small partitions in order to see their contents.
6. Select the partition that not have assigned letter using this command: SEL VOL X
(Replace the X with the volume number of partition without letter)
7. Type the following command to assign the letter to selected partition: ASSIGN LETTER=V:
8. If you have another partition without assigned letter, select it using SEL VOL X command,...
then assign any letter using ASSIGN LETTER=M: command.
9. Type list vol again to see if the letters assigned successfully to the partitions or not.
10. Type EXIT to close Diskpart.
11. Execute the following command to show files and folders inside V partition: DIR /A /B /S V:
As you can see, the V is the recovery partition in my laptop, because it contains the winre.wim file which stand for Windows Recovery Environment.
Now, lets confirm that the M partition is the boot.
14. Execute the following command: DIR /A /B /S M:
As you can see, the M is the boot partition in my laptop because it contain the BCD files.
The path to BCD file is not the same in both GPT and MBR systems.
In GPT system, the path is: Z:\EFI\Microsoft\Boot\
In MBR system, the path is: Z:\Boot\
In MBR system, the path is: Z:\Boot\ And the Z is the letter of the boot partition.
Third part: The Solutions:
Now, let’s see all methods used to fix this issue.
1. REBUILD BCD:
If the root cause or the associated blue screen indicate that the Boot Configuration Data file is corrupted,
rebuild the BCD file using one of the following methods:
1.a. Rebuild the BCD file using BCDBOOT tool:
1.a.1. Execute this command to rebuild BCD: BCDBOOT D:\WINDOWS
1.a.2. Replace the D with the letter of your windows partition.
1.a.3. Restart Your computer to see if the error fixed or not.
If the previous method failed,
rebuild BCD manually as followings:
1.b.1.a. Type Bootrec /rebuildbcd and hit Enter
Extra step
1.b.1.b. Remove editing protection from BCD file using this command: Attrib C:\boot\bcd -h -s -r
Replace the C with the letter of your boot partition and not Windows partition.
1.b.1.c. Rename the BCD file using this command: ren c:\boot\bcd bcd.old
1.b.1.d. Type Bootrec /rebuildbcd and hit Enter
1.b.1.e. Type Yes or Y and hit Enter to add the windows installation configuration to boot list.
In GPT systems, the steps are the same, but the path into the BCD is different,
so to rebuild BCD using this method do the followings:
1.b.2.a. Execute the following command: Dir /a /b /s V:
If the V is the boot partition, you will see the BCD file in this path: V:\EFI\Microsoft\Boot\BCD
1.b.2.b. Press Shift + F12 keys to open another CMD window.
1.b.2.c.Type Bootrec /rebuildbcd and hit Enter
Extra step
1.b.2.d. Remove editing protection from the old BCD file using this command: Attrib V:\EFI\Microsoft\Boot\BCD -h -s –r
Copy the path of BCD from first CMD window
1.b.2.e. Delete the old BCD file using This command: del V:\EFI\Microsoft\Boot\BCD
1.b.2.f. Press the upper arrow key from keyboard to explore previously executed commands then execute BOOTREC /REBUILDBCD again.
1.b.2.g. Type Y and hit Enter to add the windows installation configuration to boot list.
1.b.2.h. Close the command prompt then click on Continue button to restart your computer into Windows operating system.
2. REPAIRING BAD DISK SECTORS:
If the error source is related to bad disk sector, use check disk tool to fix that as followings:
2.a. Type this Command and press Enter: CHKDSK /R
2.b. If the previous command failed, type this Command and press Enter: CHKDSK C: /F /R /X
2.c. Restart your computer to see if the issue has been fixed or not.
3- RESTORING SYSTEM HEALTH USING DISM TOOL:
3.1.a. Type Notepad and press Enter.
3.1.b. Click on File then select Open option.
3.1.c. Navigate to Computer Folder and note the assigned letters.
In my laptop, the “D” is assigned for Windows partition and the “H” for the bootable USB drive of windows.
3.2. Checking if there is a corruption in the system:
3.2.a. Execute the following 2 commands to check if the system is healthy, repairable, or non-repairable. Dism /Image:C:\ /Cleanup-Image /ScanHealth Dism /Image:C:\ /Cleanup-Image /CheckHealth
Replace the C with the letter of your windows partition.
The result in my case state that “No component store corruption detected” because my system is healthy right now.
If you get a result that told you the system is non-repairable, you should remove the installed system and start a new windows installation.
If the result told you that the system is repairable, you have to use RestoreHealth command to repair that as on the next steps.
3.3.a. If you are booting into Advanced Recovery without windows installation media, execute this Command to restore system health: Dism /Image:C:\ /Cleanup-Image /RestoreHealth
3.3.b. Restart your computer to see if the issue has been fixed or not.
3.4. Restore Health From Installation Media
3.4. Use the same commands we used previously for checking and restoring system health when the Windows installation media is not available.
However, when using the RestoreHealth, you can add the Installation Media as the source for the repair files as in the following commands: MD D:\Scrach DISM /Image:D:\ /Cleanup-Image /RestoreHealth /Source:WIM:H:\Sources\install.wim:1 /LimitAccess /ScratchDir:D:\Scrach
Replace the D with your windows partition and the H with the DVD or USB drive letter.
4th method: REPAIRING SYSTEM FILES USING SYSTEM FILES CHECKER (SFC) TOOL:
Important note: If you are trying to fix Windows 10 or Windows 8,
first run the DISM tool before running SFC tool using Installation media as the repair source as on step number 3.4.
If you are running Windows 7 or Windows Vista, run the SFC directly.
4.1. Type BCDEDIT and press Enter to identify the boot and windows partitions.
4.2. In my PC, the C is the boot partition, and the D is the windows partition.
4.3. Execute this command to check and repair system files: SFC /SCANNOW /OFFBOOTDIR=C: /OFFWINDIR=D:\WINDOWS
The process will take longer time, so be patient and don’t close the CMD window or power off your PC.
If there is no any missing or corrupted system file, you will receive this message: "Windows Resource Protection did not find any integrity violations".
If there is a corrupted file in your system, the tool will replace that file from the system files backup in the Winsxs folder and you will receive this message: "Windows Resource Protection found corrupt files and successfully repaired them.".
But if the winSxs folder or its files are missing or corrupted, you will receive the following message: “Windows Resource Protection could not perform the requested operation"
In this case, you have to replace corrupted files manually as on the next method.
5. How to replace or remove the corrupted file manually:
5.1. Open SFC log file to determine the corrupted file using this command: NOTEPAD D:\WINDOWS\Logs\CBS\CBS.log
5.2. Determine the corrupted file that detected by the tool from the last check according to checking date and time.
5.3. Also you can open Srttrail log file to determine the corrupted or missed file using this command: NOTEPAD D:\WINDOWS\SYSTEM32\LOGFILES\SRT\SRTTRAIL.TXT
In my case, the corrupted file is Hal.dll
5.4. Search for the corrupted file inside windows folder using this command: DIR /S /A D:\WINDOWS\HAL.DLL
In my case, there is a backup file inside WinSxS folder which is approximately close in size to the corrupted file.
5.5. Take administrative ownership and full access of the corrupted file using these commands: TAKEOWN /F D:\WINDOWS\SYSTEM32\HAL.DLL ICACLS D:\WINDOWS\SYSTEM32\HAL.DLL /GRANT ADMINISTRATORS:F
If the file is missing, the previous 2 commands are not required.
5.6. Now, I will replace the corrupted file using these commands: Ren D:\WINDOWS\SYSTEM32\HAL.DLL HAL.DLL.old XCOPY /H D:\WINDOWS\WINSXS\ D:\WINDOWS\SYSTEM32
5.7. If there are many files available, copy the one with similar or close size to the corrupted file.
5.8. If you are trying to replace a missing file, add its name and path so we will help you to chose the suitable replacement file.
5.9. If a backup file not found in your computer, use a windows installation media like USB drive to replace it as followings:
5.10. Connect a bootable USB to your computer.
5.11. See how to create a bootable USB from the video in description.
5.12. Take administrative ownership and full access of the corrupted system file using these commands: TAKEOWN /F D:\WINDOWS\SYSTEM32\HAL.DLL ICACLS D:\WINDOWS\SYSTEM32\HAL.DLL /GRANT ADMINISTRATORS:F
5.13. Execute these commands to show the letters of all volumes: DISKPART LIST VOL
In my case the H is the letter of the USB drive.
5.14. Type EXIT and press Enter to close Diskpart.
5.15. Create new folder using this command: MD D:\MOUNT
5.16. Mount the first index of the windows installation using this command: DISM /MOUNT-IMAGE /IMAGEFILE:H:\SOURCES\INSTALL.WIM /INDEX:1 /MOUNTDIR:D:\MOUNT /READONLY
Replace the H with the letter of the USB or DVD drive in your computer.
5.17. Rename the corrupted file using this command: Ren D:\WINDOWS\SYSTEM32\HAL.DLL HAL.DLL.old
5.18. Copy the required file from mounted folder using this command: XCOPY /H D:\MOUNT\WINDOWS\SYSTEM32\HAL.DLL D:\WINDOWS\SYSTEM32
6- Changing startup behaviors or booting into Safe Mode:
6- Changing startup behaviors:
6.0. To change start-up behavior or to boot into safe mode, do the followings:
6.1. Click on Troubleshoot then click on Advanced options
6.2. Select Startup settings option, then click on Restart
6.3. Try the last three options one by one, by pressing the corresponding F key from keyboard.
Or you can try only one option if you think the issue is related to that option.
For example, if you think the issue is related to antimalware app, so you can Disable Early Launch Anti-malware protection by pressing the F8 key from keyboard.
6.4. If all three options not help, try to boot into Safe Mode with Networking by pressing the F6 key.
6.5. Once the Safe mode opened, you can try many options to fix your issue according to changes you have made in your system before appearance of your problem.
6.6. For example, if you think the issue is related to the latest windows update or software installation,
open programs and features panel then uninstall that update or installation.
Because some new updates may lead to such issue, especially in older computers when using newer operating system.
6.7. If you think the issue is related to driver installation,
open Device manager and remove that installation or disable that driver.
6.8. Also if you have an internet connection,
you can try to update the Graphic or another driver if you think that driver is the source of issue.
6.9. If you think the error source is related to a virus or malware,
scan your PC using Windows Security or another antivirus app.
7- Uninistalling latest Updates
7.1. Click on Uninstall Updates option.
7.2. Select Uninstall the latest quality update.
7.3. If the previous option didn't work, try to Uninstall the latest feature update.
8- uninstalling latest driver or disabling corrupted device:
8.1. Download Device manager view tool in your mobile from provided links.
8.2. Extract the tool into your mobile, then copy it to the USB drive.
8.3. Connect the USB drive to your computer
8.4. Type NOTEPAD and press Enter
8.5. Click on File tab then select Open option
8.6. Click on This PC icon then open the USB drive
8.7. Open the tool folder
8.8. Change File of type option to all files
8.9. Right-click the DevManView.exe and select, Run as administrator.
8.10. Click on Options tab and select, Advanced Options
8.11. Check External Windows Directory option.
8.12. Select the Windows path or type it manually into the text box then click OK.
8.13. Now, select the problematic device and disable it then restart your PC.
Important notes: A. Use this tool very carefully, because disabling or uninstalling the wrong device may cause severe system problems.
B. Some users reported that the blue screen appear after disabling a specific device, especially the Graphic or Display device.
If this is the source of your error, enable that device and restart your computer.
C. Sometimes the connected external device may lead to start up failure, especially if that device is corrupted.
So try to disconnect any external device, such as mouse or keyboard and restart the computer.
9- Restore system to previous restore point:
The System Restore option is required a manual activation in windows 10,
but in older windows versions such as windows 8, windows vista or windows 7, this option is came enabled by default.
The success rate of this method is very high if you have this option enabled in your laptop.
9.1. Click on the System Restore option then choose the required Windows to be restored if you have more than one OS.
9.2. Select a restore point to a date before the problem occurred. After that, press the Next button.
9.3. If there is no any restore point because the automatic system restore feature has been turned off,
due to removal of restore points by viruses or for any reason, then you have to proceed to the next method.
10- Reset the system to default:
10.1. Click on Troubleshoot option.
10.2. Click on Reset this PC option.
10.3. Select Keep my files option.
10.4. Select the profile which has administrator access if you have more than one profile.
10.5. Type the profile password if you have a password, otherwise, click Continue button.
10.6. Select Local reinstall option.
10.7. Select Reset option.
11- Restore System registry:
11.1. Execute the following command to see the contents of the REGBACK folder: DIR D:\WINDOWS\SYSTEM32\CONFIG\REGBACK
Replace the D with the letter of your windows partition.
11.2. If you get 5 files inside the REGBACK folder with a size for each file >0, then you have a copy of your registry backup.
11.3. If all hive files have a size of zero
or if there is no any file inside REGBACK folder,
then you didn’t have a copy of registry backup and you can’t repair your boot by restoring registry backup.
11.4. Rename registry files in the CONFIG folder using this command: Ren D:\Windows\System32\config\s?* s?*.old
This command will rename any registry file starting with S only.
11.5. Now, execute the following command to copy registry files starting with S, from REGBAK folder to Config folder: xcopy D:\Windows\System32\config\RegBack\ s?* C:\Windows\System32\config\
12- Reinstall Windows:
if all previous methods fail to repair start up problem due to a severe system corruption,
you still have a chance to recover your computer by reinstalling windows.
But before doing that,
you have to copy your important files from Windows partition to another partition or to external Disk or pen drive.
because all data on the windows partition will be lost after formatting.
Click on Use a device option if you see that.
Select the USB drive to boot back into windows preinstallation environment.
Press any key to continue.
If the previous options didn’t show in your PC,
power off the PC and watch the video from description to see how to boot into windows preinstallation environment.
4.g. Click on Format or delete options to format the Windows partition.
This step will delete all data on the Windows partition permanently,
but the data on other partitions will not be lost.
If you clicked on Delete option,
you have to create the partition again by clicking on New option,
then click on Apply icon.
Now select the Windows partition and click on Next icon to start installation processes of windows.
Connect the ethernet source if you have active internet connection, otherwise, click on I don’t have internet.
You can follow instructions from your installation screen,
or watch the video from description to see how to customize your windows while installing,
how to divide your disk if not divided and many more info.
Thanks for watching.
If you liked the video, leave a comment and subscribe.