Windows Cumulative Updates failing with Linux/Windows dual boot
I'm going to answer myself although I'm open to more suggestions on a proper fix.
My laptop is dual-boot Linux and Windows - Linux being my OS of choice but since I got the laptop with a Win10 license I'm keeping it too. Each OS has its own dedicated partition, Linux detects the Windows one and setups GRUB with dual boot options (always boots last pick). The MBR is standard with the only change being after the Windows install I set the Linux partition back to Active so GRUB can present the choices.
For a long time I've had this issue that after the initial install, the next Cumulative Update would fail. I've tried reinstalling fresh, stuck to Windows Updates drivers only, etc. Eventually the next Cumulative Update would get shipped and laptop would fail to update again. I looked at all troubleshooting option, skimmed through the WU logs, tried all possible fixes out there (rebuilding WU catalog, etc.) but nothing worked.
The symptoms were WU reporting an error during the update phase following the first reboot and rebooting again to undo the update. The latest reported error codes in the updates history were 0x800f0922 and 0x80070643 (I could get alternatively either one for the same update - the last failed ones were 2018-11, 2019-01 and 2019-02).
As it turns out all I had to do was make Windows partition active again before reboot and the update went through. Besides pointing out how ridiculous this is, I'm wondering if there could be ways to avoid this, ex add hooks to set active partition before reboot following a WU install and back afterward, or verified Windows bootloader configuration that would provide similar behavior (allow selecting OS at boot and making last choice the default). I would also hope someone from MS sees this and either fix it or at least improve error reporting do ppl don't spend months/years figuring it out.
windows windows-10 multi-boot updates
add a comment |
I'm going to answer myself although I'm open to more suggestions on a proper fix.
My laptop is dual-boot Linux and Windows - Linux being my OS of choice but since I got the laptop with a Win10 license I'm keeping it too. Each OS has its own dedicated partition, Linux detects the Windows one and setups GRUB with dual boot options (always boots last pick). The MBR is standard with the only change being after the Windows install I set the Linux partition back to Active so GRUB can present the choices.
For a long time I've had this issue that after the initial install, the next Cumulative Update would fail. I've tried reinstalling fresh, stuck to Windows Updates drivers only, etc. Eventually the next Cumulative Update would get shipped and laptop would fail to update again. I looked at all troubleshooting option, skimmed through the WU logs, tried all possible fixes out there (rebuilding WU catalog, etc.) but nothing worked.
The symptoms were WU reporting an error during the update phase following the first reboot and rebooting again to undo the update. The latest reported error codes in the updates history were 0x800f0922 and 0x80070643 (I could get alternatively either one for the same update - the last failed ones were 2018-11, 2019-01 and 2019-02).
As it turns out all I had to do was make Windows partition active again before reboot and the update went through. Besides pointing out how ridiculous this is, I'm wondering if there could be ways to avoid this, ex add hooks to set active partition before reboot following a WU install and back afterward, or verified Windows bootloader configuration that would provide similar behavior (allow selecting OS at boot and making last choice the default). I would also hope someone from MS sees this and either fix it or at least improve error reporting do ppl don't spend months/years figuring it out.
windows windows-10 multi-boot updates
add a comment |
I'm going to answer myself although I'm open to more suggestions on a proper fix.
My laptop is dual-boot Linux and Windows - Linux being my OS of choice but since I got the laptop with a Win10 license I'm keeping it too. Each OS has its own dedicated partition, Linux detects the Windows one and setups GRUB with dual boot options (always boots last pick). The MBR is standard with the only change being after the Windows install I set the Linux partition back to Active so GRUB can present the choices.
For a long time I've had this issue that after the initial install, the next Cumulative Update would fail. I've tried reinstalling fresh, stuck to Windows Updates drivers only, etc. Eventually the next Cumulative Update would get shipped and laptop would fail to update again. I looked at all troubleshooting option, skimmed through the WU logs, tried all possible fixes out there (rebuilding WU catalog, etc.) but nothing worked.
The symptoms were WU reporting an error during the update phase following the first reboot and rebooting again to undo the update. The latest reported error codes in the updates history were 0x800f0922 and 0x80070643 (I could get alternatively either one for the same update - the last failed ones were 2018-11, 2019-01 and 2019-02).
As it turns out all I had to do was make Windows partition active again before reboot and the update went through. Besides pointing out how ridiculous this is, I'm wondering if there could be ways to avoid this, ex add hooks to set active partition before reboot following a WU install and back afterward, or verified Windows bootloader configuration that would provide similar behavior (allow selecting OS at boot and making last choice the default). I would also hope someone from MS sees this and either fix it or at least improve error reporting do ppl don't spend months/years figuring it out.
windows windows-10 multi-boot updates
I'm going to answer myself although I'm open to more suggestions on a proper fix.
My laptop is dual-boot Linux and Windows - Linux being my OS of choice but since I got the laptop with a Win10 license I'm keeping it too. Each OS has its own dedicated partition, Linux detects the Windows one and setups GRUB with dual boot options (always boots last pick). The MBR is standard with the only change being after the Windows install I set the Linux partition back to Active so GRUB can present the choices.
For a long time I've had this issue that after the initial install, the next Cumulative Update would fail. I've tried reinstalling fresh, stuck to Windows Updates drivers only, etc. Eventually the next Cumulative Update would get shipped and laptop would fail to update again. I looked at all troubleshooting option, skimmed through the WU logs, tried all possible fixes out there (rebuilding WU catalog, etc.) but nothing worked.
The symptoms were WU reporting an error during the update phase following the first reboot and rebooting again to undo the update. The latest reported error codes in the updates history were 0x800f0922 and 0x80070643 (I could get alternatively either one for the same update - the last failed ones were 2018-11, 2019-01 and 2019-02).
As it turns out all I had to do was make Windows partition active again before reboot and the update went through. Besides pointing out how ridiculous this is, I'm wondering if there could be ways to avoid this, ex add hooks to set active partition before reboot following a WU install and back afterward, or verified Windows bootloader configuration that would provide similar behavior (allow selecting OS at boot and making last choice the default). I would also hope someone from MS sees this and either fix it or at least improve error reporting do ppl don't spend months/years figuring it out.
windows windows-10 multi-boot updates
windows windows-10 multi-boot updates
edited Feb 21 at 18:51
Thomas Guyot-Sionnest
asked Feb 14 at 13:49
Thomas Guyot-SionnestThomas Guyot-Sionnest
27027
27027
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
So the fix where you have Linux/Windows dual boot using standard DOS MBR and GRUB on the Linux partition set active to perform OS selection is to set the Windows partition active before reboot after installing Windows Updates and set it back to Linux afterward.
My Windows partition is the 2nd and Linux is 3rd partition, so I created these two DISKPART scripts (The DRTAIL command is only to verify it's the right partition, can be removed):
diskpart_p2.txt:
SELECT DISK 0
SELECT PARTITION 2
DETAIL PARTITION
ACTIVE
diskpart_p3.txt:
SELECT DISK 0
SELECT PARTITION 3
DETAIL PARTITION
ACTIVE
I have a cmd file that runs this:
Toggle_Partition.cmd:
@ECHO OFF
DISKPART /S C:diskpart_p%1.txt
PAUSE
Finally with a pair of shortcuts I run the command with the right partition. The shortcut is configured to run as Administrator.
Make_Win_Active.cmd:
C:Toggle_Partition.cmd 2
Make_GRUB_Active.cmd:
C:Toggle_Partition.cmd 3
add a comment |
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%2f1405701%2fwindows-cumulative-updates-failing-with-linux-windows-dual-boot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So the fix where you have Linux/Windows dual boot using standard DOS MBR and GRUB on the Linux partition set active to perform OS selection is to set the Windows partition active before reboot after installing Windows Updates and set it back to Linux afterward.
My Windows partition is the 2nd and Linux is 3rd partition, so I created these two DISKPART scripts (The DRTAIL command is only to verify it's the right partition, can be removed):
diskpart_p2.txt:
SELECT DISK 0
SELECT PARTITION 2
DETAIL PARTITION
ACTIVE
diskpart_p3.txt:
SELECT DISK 0
SELECT PARTITION 3
DETAIL PARTITION
ACTIVE
I have a cmd file that runs this:
Toggle_Partition.cmd:
@ECHO OFF
DISKPART /S C:diskpart_p%1.txt
PAUSE
Finally with a pair of shortcuts I run the command with the right partition. The shortcut is configured to run as Administrator.
Make_Win_Active.cmd:
C:Toggle_Partition.cmd 2
Make_GRUB_Active.cmd:
C:Toggle_Partition.cmd 3
add a comment |
So the fix where you have Linux/Windows dual boot using standard DOS MBR and GRUB on the Linux partition set active to perform OS selection is to set the Windows partition active before reboot after installing Windows Updates and set it back to Linux afterward.
My Windows partition is the 2nd and Linux is 3rd partition, so I created these two DISKPART scripts (The DRTAIL command is only to verify it's the right partition, can be removed):
diskpart_p2.txt:
SELECT DISK 0
SELECT PARTITION 2
DETAIL PARTITION
ACTIVE
diskpart_p3.txt:
SELECT DISK 0
SELECT PARTITION 3
DETAIL PARTITION
ACTIVE
I have a cmd file that runs this:
Toggle_Partition.cmd:
@ECHO OFF
DISKPART /S C:diskpart_p%1.txt
PAUSE
Finally with a pair of shortcuts I run the command with the right partition. The shortcut is configured to run as Administrator.
Make_Win_Active.cmd:
C:Toggle_Partition.cmd 2
Make_GRUB_Active.cmd:
C:Toggle_Partition.cmd 3
add a comment |
So the fix where you have Linux/Windows dual boot using standard DOS MBR and GRUB on the Linux partition set active to perform OS selection is to set the Windows partition active before reboot after installing Windows Updates and set it back to Linux afterward.
My Windows partition is the 2nd and Linux is 3rd partition, so I created these two DISKPART scripts (The DRTAIL command is only to verify it's the right partition, can be removed):
diskpart_p2.txt:
SELECT DISK 0
SELECT PARTITION 2
DETAIL PARTITION
ACTIVE
diskpart_p3.txt:
SELECT DISK 0
SELECT PARTITION 3
DETAIL PARTITION
ACTIVE
I have a cmd file that runs this:
Toggle_Partition.cmd:
@ECHO OFF
DISKPART /S C:diskpart_p%1.txt
PAUSE
Finally with a pair of shortcuts I run the command with the right partition. The shortcut is configured to run as Administrator.
Make_Win_Active.cmd:
C:Toggle_Partition.cmd 2
Make_GRUB_Active.cmd:
C:Toggle_Partition.cmd 3
So the fix where you have Linux/Windows dual boot using standard DOS MBR and GRUB on the Linux partition set active to perform OS selection is to set the Windows partition active before reboot after installing Windows Updates and set it back to Linux afterward.
My Windows partition is the 2nd and Linux is 3rd partition, so I created these two DISKPART scripts (The DRTAIL command is only to verify it's the right partition, can be removed):
diskpart_p2.txt:
SELECT DISK 0
SELECT PARTITION 2
DETAIL PARTITION
ACTIVE
diskpart_p3.txt:
SELECT DISK 0
SELECT PARTITION 3
DETAIL PARTITION
ACTIVE
I have a cmd file that runs this:
Toggle_Partition.cmd:
@ECHO OFF
DISKPART /S C:diskpart_p%1.txt
PAUSE
Finally with a pair of shortcuts I run the command with the right partition. The shortcut is configured to run as Administrator.
Make_Win_Active.cmd:
C:Toggle_Partition.cmd 2
Make_GRUB_Active.cmd:
C:Toggle_Partition.cmd 3
edited Feb 21 at 18:52
answered Feb 14 at 13:49
Thomas Guyot-SionnestThomas Guyot-Sionnest
27027
27027
add a comment |
add a comment |
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%2f1405701%2fwindows-cumulative-updates-failing-with-linux-windows-dual-boot%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