Using wmic in cmd from booted USB in troubleshoot mode
I am having a Windows installation which fails to boot (BSOD). Safe mode is not working, too. So I created a Windows bootable USB stick and am now in the command prompt from the troubleshoot mode.
The USB stick is mounted on X:, the non-working Windows installation is on C:. I can browse all my personal files etc, so I am sure C: is the correct drive.
To debug further, I want to enable Minidumps. The internet says the following command is the way to go:
wmic recoveros set DebugInfoType = 3
Done and it says it was successful. Still, there are no Minidumps created. Turns out when I reboot into the recovery, the DebugInfoType is changed back to 7.
When I get all properties using
wmic recovers get
it also shows all paths with X: instead of C:.
My suspicion is that the wmic command operates on the currently booted recovery Windows but not for the actually intended installation on C:.
How can I force wmic to operate on behalf of the C:-installation?
windows-10 bsod wmic recovery
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
add a comment |
I am having a Windows installation which fails to boot (BSOD). Safe mode is not working, too. So I created a Windows bootable USB stick and am now in the command prompt from the troubleshoot mode.
The USB stick is mounted on X:, the non-working Windows installation is on C:. I can browse all my personal files etc, so I am sure C: is the correct drive.
To debug further, I want to enable Minidumps. The internet says the following command is the way to go:
wmic recoveros set DebugInfoType = 3
Done and it says it was successful. Still, there are no Minidumps created. Turns out when I reboot into the recovery, the DebugInfoType is changed back to 7.
When I get all properties using
wmic recovers get
it also shows all paths with X: instead of C:.
My suspicion is that the wmic command operates on the currently booted recovery Windows but not for the actually intended installation on C:.
How can I force wmic to operate on behalf of the C:-installation?
windows-10 bsod wmic recovery
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09
add a comment |
I am having a Windows installation which fails to boot (BSOD). Safe mode is not working, too. So I created a Windows bootable USB stick and am now in the command prompt from the troubleshoot mode.
The USB stick is mounted on X:, the non-working Windows installation is on C:. I can browse all my personal files etc, so I am sure C: is the correct drive.
To debug further, I want to enable Minidumps. The internet says the following command is the way to go:
wmic recoveros set DebugInfoType = 3
Done and it says it was successful. Still, there are no Minidumps created. Turns out when I reboot into the recovery, the DebugInfoType is changed back to 7.
When I get all properties using
wmic recovers get
it also shows all paths with X: instead of C:.
My suspicion is that the wmic command operates on the currently booted recovery Windows but not for the actually intended installation on C:.
How can I force wmic to operate on behalf of the C:-installation?
windows-10 bsod wmic recovery
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
I am having a Windows installation which fails to boot (BSOD). Safe mode is not working, too. So I created a Windows bootable USB stick and am now in the command prompt from the troubleshoot mode.
The USB stick is mounted on X:, the non-working Windows installation is on C:. I can browse all my personal files etc, so I am sure C: is the correct drive.
To debug further, I want to enable Minidumps. The internet says the following command is the way to go:
wmic recoveros set DebugInfoType = 3
Done and it says it was successful. Still, there are no Minidumps created. Turns out when I reboot into the recovery, the DebugInfoType is changed back to 7.
When I get all properties using
wmic recovers get
it also shows all paths with X: instead of C:.
My suspicion is that the wmic command operates on the currently booted recovery Windows but not for the actually intended installation on C:.
How can I force wmic to operate on behalf of the C:-installation?
windows-10 bsod wmic recovery
windows-10 bsod wmic recovery
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
asked Jan 26 at 9:24
The WavelengthThe Wavelength
2791417
2791417
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09
add a comment |
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09
add a comment |
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%2f1398671%2fusing-wmic-in-cmd-from-booted-usb-in-troubleshoot-mode%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%2f1398671%2fusing-wmic-in-cmd-from-booted-usb-in-troubleshoot-mode%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
Possible duplicate : superuser.com/questions/1398043/…
– lx07
Jan 26 at 12:41
Thanks! I was now able to change the setting. Nevertheless, I don't get minidumps.
– The Wavelength
Jan 26 at 15:04
Did you set the page file size to >=400MB? Details in same link. You also have to recreate the error - it will not recreate dumps from historical bugchecks.
– lx07
Jan 26 at 15:21
I set it to 1GB. I recreated the error (blue screen). Even on the blue screen page it says nothing about dumping memory. I know that from previous BSODs that a text is shown, even with a percentage counter.
– The Wavelength
Jan 26 at 16:16
@moderators: It indeed is a duplicate by the way.
– The Wavelength
Jan 27 at 16:09