P
PHLee
Guest
My Windows 7 (SP1, 32-bit) machine has failed to install EVERY single Security Monthly Quality Rollup update since October 2017, beginning with KB4041681 (October 2017) through the current patch KB4457144 (September 2018).
A lot of users worldwide have reported the same issue with KB4457144 (September 2018):
Solution for the error 0x8000FFF in Windows 7 @ AskWoody
Reported error 0x8000FFFF with the Win7 Monthly Rollup KB 4457144 @ AskWoody
One common solution that works for many is by installing the missing Servicing Stack Update KB3177467 (September 2016), which seems to be a prerequisite for KB4457144 (September 2018). In another Microsoft Community thread, one user suggested installing the Malicious Software Removal Tool KB890830.
Unfortunately, my machine already installed KB3177467 back in October 2016 and KB890830 this month, so these solutions do NOT apply to me. I have already tried:
- running sfc/scannow in Command Prompt (which finds no corrupt files);
- installing the System Update Readiness tool;
- installing KB4041681 (October 2017) (which still fails);
but none of these works.
Has anyone in the same situation figured out a solution?
Continue reading...
A lot of users worldwide have reported the same issue with KB4457144 (September 2018):
Solution for the error 0x8000FFF in Windows 7 @ AskWoody
Reported error 0x8000FFFF with the Win7 Monthly Rollup KB 4457144 @ AskWoody
One common solution that works for many is by installing the missing Servicing Stack Update KB3177467 (September 2016), which seems to be a prerequisite for KB4457144 (September 2018). In another Microsoft Community thread, one user suggested installing the Malicious Software Removal Tool KB890830.
Unfortunately, my machine already installed KB3177467 back in October 2016 and KB890830 this month, so these solutions do NOT apply to me. I have already tried:
- running sfc/scannow in Command Prompt (which finds no corrupt files);
- installing the System Update Readiness tool;
- installing KB4041681 (October 2017) (which still fails);
but none of these works.
Has anyone in the same situation figured out a solution?
Continue reading...
