Windows 7 December 2018 Security Rollup fails with error 8000FFFF












1














Has anyone successfully installed the Windows 7 December 2018 Security Rollup? On three different computers it fails for me with the exact same error: 8000FFFF. I've tried renaming the SoftwareDistribution folder to no avail. I also ran an SFC scan which came back clean. At first I thought it might have something to do with the computers being dual-booted with Linux (and thus the Windows bootloader was replaced with GRUB) but it just now failed on another computer that is not dual-booted...



All three machines have been clean-installed within about 1.5 years, and I don't do anything screwy to them that would mess anything up so I'm totally stumped on this one.



Anyone have some ideas on how to resolve this?










share|improve this question






















  • @Ramhound I fixed it, see my answer
    – Android Dev
    Jan 1 at 22:59
















1














Has anyone successfully installed the Windows 7 December 2018 Security Rollup? On three different computers it fails for me with the exact same error: 8000FFFF. I've tried renaming the SoftwareDistribution folder to no avail. I also ran an SFC scan which came back clean. At first I thought it might have something to do with the computers being dual-booted with Linux (and thus the Windows bootloader was replaced with GRUB) but it just now failed on another computer that is not dual-booted...



All three machines have been clean-installed within about 1.5 years, and I don't do anything screwy to them that would mess anything up so I'm totally stumped on this one.



Anyone have some ideas on how to resolve this?










share|improve this question






















  • @Ramhound I fixed it, see my answer
    – Android Dev
    Jan 1 at 22:59














1












1








1







Has anyone successfully installed the Windows 7 December 2018 Security Rollup? On three different computers it fails for me with the exact same error: 8000FFFF. I've tried renaming the SoftwareDistribution folder to no avail. I also ran an SFC scan which came back clean. At first I thought it might have something to do with the computers being dual-booted with Linux (and thus the Windows bootloader was replaced with GRUB) but it just now failed on another computer that is not dual-booted...



All three machines have been clean-installed within about 1.5 years, and I don't do anything screwy to them that would mess anything up so I'm totally stumped on this one.



Anyone have some ideas on how to resolve this?










share|improve this question













Has anyone successfully installed the Windows 7 December 2018 Security Rollup? On three different computers it fails for me with the exact same error: 8000FFFF. I've tried renaming the SoftwareDistribution folder to no avail. I also ran an SFC scan which came back clean. At first I thought it might have something to do with the computers being dual-booted with Linux (and thus the Windows bootloader was replaced with GRUB) but it just now failed on another computer that is not dual-booted...



All three machines have been clean-installed within about 1.5 years, and I don't do anything screwy to them that would mess anything up so I'm totally stumped on this one.



Anyone have some ideas on how to resolve this?







windows-7 windows-update






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 23 '18 at 22:13









Android DevAndroid Dev

544316




544316












  • @Ramhound I fixed it, see my answer
    – Android Dev
    Jan 1 at 22:59


















  • @Ramhound I fixed it, see my answer
    – Android Dev
    Jan 1 at 22:59
















@Ramhound I fixed it, see my answer
– Android Dev
Jan 1 at 22:59




@Ramhound I fixed it, see my answer
– Android Dev
Jan 1 at 22:59










1 Answer
1






active

oldest

votes


















0














Turns out MS screwed up something and KB3177467




enter image description here




never showed up in Windows Update. After manually downloading it from the online Update Catalog and installing it, the December 2018 Security Rollup installed successfully.






share|improve this answer





















  • I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
    – Ramhound
    Jan 2 at 0:13












  • @Ramhound well but the point is the SSU never showed up in the Windows Update client.
    – Android Dev
    Jan 2 at 3:45











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1387228%2fwindows-7-december-2018-security-rollup-fails-with-error-8000ffff%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









0














Turns out MS screwed up something and KB3177467




enter image description here




never showed up in Windows Update. After manually downloading it from the online Update Catalog and installing it, the December 2018 Security Rollup installed successfully.






share|improve this answer





















  • I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
    – Ramhound
    Jan 2 at 0:13












  • @Ramhound well but the point is the SSU never showed up in the Windows Update client.
    – Android Dev
    Jan 2 at 3:45
















0














Turns out MS screwed up something and KB3177467




enter image description here




never showed up in Windows Update. After manually downloading it from the online Update Catalog and installing it, the December 2018 Security Rollup installed successfully.






share|improve this answer





















  • I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
    – Ramhound
    Jan 2 at 0:13












  • @Ramhound well but the point is the SSU never showed up in the Windows Update client.
    – Android Dev
    Jan 2 at 3:45














0












0








0






Turns out MS screwed up something and KB3177467




enter image description here




never showed up in Windows Update. After manually downloading it from the online Update Catalog and installing it, the December 2018 Security Rollup installed successfully.






share|improve this answer












Turns out MS screwed up something and KB3177467




enter image description here




never showed up in Windows Update. After manually downloading it from the online Update Catalog and installing it, the December 2018 Security Rollup installed successfully.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 1 at 22:59









Android DevAndroid Dev

544316




544316












  • I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
    – Ramhound
    Jan 2 at 0:13












  • @Ramhound well but the point is the SSU never showed up in the Windows Update client.
    – Android Dev
    Jan 2 at 3:45


















  • I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
    – Ramhound
    Jan 2 at 0:13












  • @Ramhound well but the point is the SSU never showed up in the Windows Update client.
    – Android Dev
    Jan 2 at 3:45
















I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
– Ramhound
Jan 2 at 0:13






I wouldn't say that "Microsoft screwed up" if the patch summary clearly. indicates the monthly security update should be installed after the SSU It is important to note, the monthly update the summary is referring to is actually the October monthly security update, not the December monthly security update. However, due to the October monthly security update being included in the December update, it still applies (which is the reason keeping track of SSUs is important).
– Ramhound
Jan 2 at 0:13














@Ramhound well but the point is the SSU never showed up in the Windows Update client.
– Android Dev
Jan 2 at 3:45




@Ramhound well but the point is the SSU never showed up in the Windows Update client.
– Android Dev
Jan 2 at 3:45


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1387228%2fwindows-7-december-2018-security-rollup-fails-with-error-8000ffff%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕