Oh my, go easy on the language Mike. No need to go ballistic! Just think, there's another fantastic update being created while you're building up steam to explode and while I'm typing out another intelligent response. :-)
KB4566782 Update Loop
My laptop is running Windows 10 2004 OS build 19041.388 and windows update decides to automatically install cumulative update KB4566782 (build 19041.450). The installation will fail (0x800f081f) during updating Windows and Windows update automatically retry to install it until my laptop's battery dies.
How get out of this update loop?
update: We need a true solution, and please do not mark reinstalling windows 10 as an answer, dear moderators.
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
154 answers
Sort by: Oldest
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2020-08-28T01:48:31+00:00 -
Anonymous
2020-08-28T02:52:04+00:00 I have the same issue, but based on what I am reading we do not have a solution. I have tried most of what was recommended, including the manual install and still get the 0x800f081f error code.
It may be causing my disk to run most of the time at 100%.
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2020-08-28T03:29:29+00:00 I have an idea Mike, that your chances of getting money back from Microsoft is slim to none. But I'd be too happy to be proven wrong! Post back for sure if you manage to pull it off.
As to the Update, I'm beaddled & surprised that Microsoft didn't address this shortly after that was pushed down the tubes!