-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- start up diagnosis error: c:\windows\system32\logfiles\srt\...

Create an account on the HP Community to personalize your profile and ask a question
07-02-2018
10:51 AM
- last edited on
07-02-2018
10:53 AM
by
danny-r
I have done so many different system restores, I have even totally wiped my hard drive, I mean TOTALLY reformatted my hard drive, blank, no information on the drive at all and still have the same error on the start up diagnosis. I have tried everything on Microsofts website. I have gone into DOS on the recovery option and have tried:
1. Choose Troubleshoot > Advanced Options.
2. Select Command Prompt from list of options.
3. When Command Prompt appears, enter the following lines and press Enter after each line in order to run it:
bootrec.exe /rebuildbcd
bootrec.exe /fixmbr
bootrec.exe /fixboot
4. To perform these commands, you need to know drive letters for all your hard drive partitions. In Command Prompt you should enter the following (but remember to use the letters that match your hard drive partitions on your PC):
chkdsk /r c:
still have the same error :c:\windows\system32\logfiles\srt\srttrails.txt
[personal information removed]
Product Number
N5Y13UA#ABA
Windows 10 Home 64-bit
07-02-2018 02:01 PM
This error is most often seen when Windows Update crashes and leaves the PC in a corrupted state, with the error message buried in that log.
But, you said you completely blanked your drive, so there should be nothing there when you are attempting to do a clean reinstall of Win10.
IF your drive is indeed blank, then what are you using to boot in order to get into DOS?
I am a volunteer and I do not work for, nor represent, HP
07-02-2018 02:42 PM
So where do we go from here?
07-02-2018 05:01 PM
Based on what generally causes this, my guess is that after your reboot, Win10 starts immediately doing Windows Updates and that leads to the logfile problem.
If you can get to a command prompt, then enter "winver" to see what build of Win10 got installed. If it's prior to v 1803, it could be that MS is trying to force the April 2018 Update on you, and that is huge.
If you went into Win10 before a reboot and set it to "metered connections", that should at least prevent Windows Update from running immediately.
I am a volunteer and I do not work for, nor represent, HP