Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, February 11, 2019 7:40 PM
What is the log file name that is generated when there is a failure of system restore?
startup repair fail may produce: C:\Windows\System32\Logfiles\Srt\SrtTrail.txt
reset save files fail may produce: $SysReset C:\recovery\Logs
If a reset save files was never performed on a computer should the folder exist and be empty, or not exist?
If file explorer is opened and show hidden files is checked the C:\recovery\logs displayed: No items matched your search
In notepad was opened as an administrator > file open > C:\recovery\logs displayed: No items matched you search
Please post a Microsoft link for each:
system restore failure log
reset save files failure log
All replies (6)
Wednesday, February 13, 2019 9:41 AM ✅Answered | 1 vote
Hi,
Thanks for your reply.
1. I have done a successfully system restore, like I previously posted, this log (C:\Windows\Logs\SystemRestore) will be produced. If had a failure system restore, you could check if this path exists.
Besides, if we failed, error message will be displayed on the screen. We could troubleshoot based on this error message.
2.For a failed reset save files the log file is: C:\SysReset\Logs\setupact ? Yes
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, February 12, 2019 6:34 AM
Hi，
Thanks for posting your query here.
Sorry I have not found the related Microsoft article, but i have done the tests.
1. It (C:\recovery\Logs) exists and it is not empty even if we do not reset save files. I have checked the logs and it seems that it cannot provide more information for troubleshooting the failure of resetting save files.
Before reset save files VS After reset save files:
2. It ($SysReset) does not exist if we do not reset save files. We can use this log ( C:\SysReset\Logs\Setupact.log ) to do the troubleshooting.
Before reset save files VS After reset save files:
For your reference:
https://foxdeploy.com/2017/03/13/solved-windows-10-reset-there-was-a-problem-resetting-your-pc/
3. For the system restore log, we could check this log (C:\Windows\Logs\SystemRestore). This log does not exist if we do not perform a system restore. Besides, we could also check event viewer for error message.
Best regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, February 13, 2019 4:40 AM
Please confirm or correct:
a) There is no log file for a failed system restore?
b) For a failed reset save files the log file is: C:\SysReset\Logs\setupact ?
If there is a log file for failed system restore please indicate the path.
If you create a brand new restore point then wait several days and attempt a system restore that fails are there no logs to troubleshoot that are specific to system restore?
For a failed system restore there is no specific information?
An end user must perform non-specific troubleshooting?
Monday, February 18, 2019 5:46 AM
Thank you
Tuesday, April 16, 2019 5:48 AM
C:\Windows\Logs\SystemRestore
is an ETL file.
How do you open and read it?
Isn't there a text file?
Thursday, April 18, 2019 8:28 AM
Hi,
The event tracer logs events in special binary files with an .etl extension. These binary files aren't human-readable, but you can use the tools Tracerpt to convert them into text, HTML, or comma-separated value (CSV) files.
Reference：https://www.techwalla.com/articles/how-to-read-an-etl-file
We could also open the ETL file with the tool Xperf (windows performance analyzer).
Reference:/en-us/windows-hardware/test/wpt/
Best regards,
Cora
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].