Windows 10 unable to boot, failure to repair loop-refer to srttrail.txt inside
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
UDPATE2: This has been SOLVED by following this video: https://www.youtube.com/watch?v=2f-GorXWkoc
It shows how to copy the registry hives from the Regback folder to the config folder. The Regback folder contains backups of the Registry Hives in the config folder which may have been corrupted during the update.
UPDATE: I have an AMD processor. dism.txt output pasted here: https://pastebin.com/XLuLQpc0
ISSUE: We have a relatively new (couple months) Windows 10 HP Computer that was suddenly unable to boot into the OS. Unable to enter Safe Mode. Automatic Repair failed. System Restore failed.
After trying a bunch of solutions, Self-Repair system referred an srttrail.txt file to me, which I copied to a drive and have posted below. I'm not sure what to glean from it. Can anyone else:
Session details
System Disk = DeviceHarddisk0
Windows directory = C:WINDOWS
AutoChk Run = 0
Number of root causes = 0
Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1656 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 187 ms
Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 469 ms
Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms
Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms
Test Performed:
Name: Check for pending package install
Result: Completed successfully. Error code = 0x4
Time taken = 2422 ms
---------------------------
windows-10
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
|
show 4 more comments
UDPATE2: This has been SOLVED by following this video: https://www.youtube.com/watch?v=2f-GorXWkoc
It shows how to copy the registry hives from the Regback folder to the config folder. The Regback folder contains backups of the Registry Hives in the config folder which may have been corrupted during the update.
UPDATE: I have an AMD processor. dism.txt output pasted here: https://pastebin.com/XLuLQpc0
ISSUE: We have a relatively new (couple months) Windows 10 HP Computer that was suddenly unable to boot into the OS. Unable to enter Safe Mode. Automatic Repair failed. System Restore failed.
After trying a bunch of solutions, Self-Repair system referred an srttrail.txt file to me, which I copied to a drive and have posted below. I'm not sure what to glean from it. Can anyone else:
Session details
System Disk = DeviceHarddisk0
Windows directory = C:WINDOWS
AutoChk Run = 0
Number of root causes = 0
Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1656 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 187 ms
Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 469 ms
Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms
Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms
Test Performed:
Name: Check for pending package install
Result: Completed successfully. Error code = 0x4
Time taken = 2422 ms
---------------------------
windows-10
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
So all tests passed except the test which tests if an update is pending. You can usedism.exe /image:C: /cleanup-image /revertpendingactionsto remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.
– Ramhound
Jan 17 '18 at 0:57
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.DISM /image:C: /cleanup-image /revertpendingactionsshould revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.
– Ramhound
Jan 17 '18 at 2:25
|
show 4 more comments
UDPATE2: This has been SOLVED by following this video: https://www.youtube.com/watch?v=2f-GorXWkoc
It shows how to copy the registry hives from the Regback folder to the config folder. The Regback folder contains backups of the Registry Hives in the config folder which may have been corrupted during the update.
UPDATE: I have an AMD processor. dism.txt output pasted here: https://pastebin.com/XLuLQpc0
ISSUE: We have a relatively new (couple months) Windows 10 HP Computer that was suddenly unable to boot into the OS. Unable to enter Safe Mode. Automatic Repair failed. System Restore failed.
After trying a bunch of solutions, Self-Repair system referred an srttrail.txt file to me, which I copied to a drive and have posted below. I'm not sure what to glean from it. Can anyone else:
Session details
System Disk = DeviceHarddisk0
Windows directory = C:WINDOWS
AutoChk Run = 0
Number of root causes = 0
Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1656 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 187 ms
Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 469 ms
Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms
Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms
Test Performed:
Name: Check for pending package install
Result: Completed successfully. Error code = 0x4
Time taken = 2422 ms
---------------------------
windows-10
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
UDPATE2: This has been SOLVED by following this video: https://www.youtube.com/watch?v=2f-GorXWkoc
It shows how to copy the registry hives from the Regback folder to the config folder. The Regback folder contains backups of the Registry Hives in the config folder which may have been corrupted during the update.
UPDATE: I have an AMD processor. dism.txt output pasted here: https://pastebin.com/XLuLQpc0
ISSUE: We have a relatively new (couple months) Windows 10 HP Computer that was suddenly unable to boot into the OS. Unable to enter Safe Mode. Automatic Repair failed. System Restore failed.
After trying a bunch of solutions, Self-Repair system referred an srttrail.txt file to me, which I copied to a drive and have posted below. I'm not sure what to glean from it. Can anyone else:
Session details
System Disk = DeviceHarddisk0
Windows directory = C:WINDOWS
AutoChk Run = 0
Number of root causes = 0
Test Performed:
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 1656 ms
Test Performed:
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms
Test Performed:
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 187 ms
Test Performed:
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 469 ms
Test Performed:
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms
Test Performed:
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms
Test Performed:
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms
Test Performed:
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms
Test Performed:
Name: Check for pending package install
Result: Completed successfully. Error code = 0x4
Time taken = 2422 ms
---------------------------
windows-10
windows-10
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
edited Jan 17 '18 at 22:23
SuicuneSol San
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
asked Jan 17 '18 at 0:29
SuicuneSol SanSuicuneSol San
3113
3113
So all tests passed except the test which tests if an update is pending. You can usedism.exe /image:C: /cleanup-image /revertpendingactionsto remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.
– Ramhound
Jan 17 '18 at 0:57
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.DISM /image:C: /cleanup-image /revertpendingactionsshould revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.
– Ramhound
Jan 17 '18 at 2:25
|
show 4 more comments
So all tests passed except the test which tests if an update is pending. You can usedism.exe /image:C: /cleanup-image /revertpendingactionsto remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.
– Ramhound
Jan 17 '18 at 0:57
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.DISM /image:C: /cleanup-image /revertpendingactionsshould revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.
– Ramhound
Jan 17 '18 at 2:25
So all tests passed except the test which tests if an update is pending. You can use
dism.exe /image:C: /cleanup-image /revertpendingactions to remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.– Ramhound
Jan 17 '18 at 0:57
So all tests passed except the test which tests if an update is pending. You can use
dism.exe /image:C: /cleanup-image /revertpendingactions to remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.– Ramhound
Jan 17 '18 at 0:57
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.
DISM /image:C: /cleanup-image /revertpendingactions should revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.– Ramhound
Jan 17 '18 at 2:25
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.
DISM /image:C: /cleanup-image /revertpendingactions should revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.– Ramhound
Jan 17 '18 at 2:25
|
show 4 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1286232%2fwindows-10-unable-to-boot-failure-to-repair-loop-refer-to-srttrail-txt-inside%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1286232%2fwindows-10-unable-to-boot-failure-to-repair-loop-refer-to-srttrail-txt-inside%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
So all tests passed except the test which tests if an update is pending. You can use
dism.exe /image:C: /cleanup-image /revertpendingactionsto remove the pending updates. Source. Do you have an Intel or AMD processor, update your question, don't leave a comment.– Ramhound
Jan 17 '18 at 0:57
Question updated. It's an AMD. I did the dism.exe command and received an Error code #2, Unable to Access Image. The dism.txt output is pasted in the original post.
– SuicuneSol San
Jan 17 '18 at 1:40
Did you by chance install the January update?
– Ramhound
Jan 17 '18 at 1:50
Probably? The updates were automatic. It's not my machine, but my sister's. I attempted a System Restore to January 3rd, but the restore apparently didn't work.
– SuicuneSol San
Jan 17 '18 at 1:58
You need to use the correct drive letter. It might or might not be C. Depends on what other drives you have connected.
DISM /image:C: /cleanup-image /revertpendingactionsshould revert the pending update, but it would really be helpful, if you could determine if the incompatible patch was being installed or not.– Ramhound
Jan 17 '18 at 2:25