When I start my computer, it crashes and restarts with a blue screen that says "automatic repair couldnt repair your pc"
I've tried startup repair and I get the same screen saying that startup repair cant repair my pc either
I've tried resetting without losing my files but it simply says it does not work
I have no system restore points
The log file is D:\WINDOWS\System32\Logfiles\Srt\SrtTrail. Txt
Any help would be appreciated.
By the log file path you posted I will assume Windows 10 is installed on the D: drive?
Do you have a separate HDD of C: from a previous installation? or is C: and D: on the same HDD?
Can you login to the C: drive? If so, download HD Tune, not Pro. Take the drop down menu and choose the HDD that D: is on. Go to the Error Scan tab run a Full Error Scan, not Quick Scan on the D: drive. This may take some time. If all the blocks are Green, the drive is in good Health. If any of the blocks come up Red then this drive is beginning to fail and needs to be replaced.
Hi, Welcome to tenforums. I assume you don't have recent disk images e.g. Macrium , Aomei Backupper, Acronis... tenforums members repeatedly recommend the routine use of disk imaging to give you a relatively easy way to recover from situations like this.
Please create a bootable disk using this iso:
Toolkit Item: Kyhi’s Rescue Disk – Win10.Guru
Instructions on creating a bootable disk can be found here:
Create Bootable USB Flash Drive to Install Windows 10
- but use Kyhi's iso not a Win 10 one of course.
When you have booted your PC from that you wil have- as you can see there- a familiar win 10 environment with utilities like HD Tune as Spunk mentions above.
History- what led to this situation?
- Power outage
- Upgrade or update
- Sudden and unexpected
- Something you did
- Other....
Thankyou for your reply.
I had thought Windows was installed on my C: drive so I'm confused by the log file path. I recently tried to clear up my C: drive and im worried I did something stupid like move Windows files to the D: drive, can't remember though. Is there any way to check using only the recovery window?
How would I log into the C: drive from using the recovery window?
- - - Updated - - -
Thankyou Dalchina for replying.
I'll try that method you suggested tomorrow morning
To answer your question. I have a habit of turning off my pc at the switch rather than going through the proper windows shut down procedure. Maybe that has something to do with it. I also recently tried to clear my C: drive as I described to Spunk, above. However this was a few days ago and I did not see any immediate issues.
Startup Repair is a Windows recovery tool that can fix certain system problems that might prevent Windows from starting. If Windows 10 fails to start correctly two or three times, then the automated Startup Repair system will be invoked.
Startup Repair can only fix certain problems, such as missing or damaged system files. It can't fix hardware failures, such as a failing hard disk or incompatible memory, nor does it protect against virus attacks.
You can run Startup Repair manually from Windows 10 installation media by opening the Windows Recovery Environment menu (Click Repair your Computer at the Setup screen if starting from installation media) and then clicking Troubleshoot and Advanced Options.
If Startup Repair is able to fix the problem, it’ll do so and you’ll be asked to restart the PC. If it isn’t though, perhaps because it’s unable to identify the problem, then you’ll be prompted and given the details of the log file it created during the repair process.
You will be shown the location and name of the repair log file if Startup Repair cannot fix the problem.
Clicking Advanced Options at this point will return you to the Windows Recovery Environment menu, where other repair options are available to you. If you open the log file, you’ll be shown details of all the tests performed by Startup Repair, with any errors discovered detailed. You can use this information to help diagnose and get to the root cause of the problem.
To open log file from the Windows Recovery Environment, click and open the Command Prompt. When the Command Prompt is open, type Notepad and press Enter key to open the Notepad application. The Startup Repair log file is located at:
You will need to navigate to the drive on which you have Windows installed (usually the C: drive) to see the SrtTrail.txt log file.Code:C:\Windows\System32\Logfiles\Srt\SrtTrail.txt
I followed those instructions and in the log I found out that the root cause was a corrupted bootres.dll file
I have tried to verify files by using sfc \scannow but it did not fix the issue, i was told that windows resource protection could not perform the requested operation
Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.
Please type below command into Command Prompt and press Enter key.
The following command scans integrity of all protected Windows system files and repairs files with problems when possible.
Code:Sfc /Scannow /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows
Please replace partition letter D: with Windows installed partition letter. When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.
I entered that command but again "Windows Resource Protection could not perform the requested operation."
I did confirm that my windows partition is D: though
Have you restarted your computer and execute the SFC command?
Yes I've done those things. Was I meant to type the code you provided exactly as you formatted? That's how I did it.
Quote
