@Rubert Mumps and @Holly1958
May I ask both of you why you are ignoring my repair suggestion?
Is it too complicated to describe?
Friendly greetings
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
@Rubert Mumps and @Holly1958
May I ask both of you why you are ignoring my repair suggestion?
Is it too complicated to describe?
Friendly greetings
I went to the live chat -- https://support.microsoft.com/en-us/contact/virtual-agent/ again today (I went yesterday) and did what the automated chat said but it didn't work again today so was told to do something else but was afraid to try so I was transferred to a real person via the computer and that person wanted to do a remote, but I didn't care to do a remote so asked the person if he could tell me something else I could do later, and he gave me the following directions which I copied and pasted from the site:
Restart Windows Update services
====================================== +Press Win key + R, type services.msc, and click Enter. + Locate Windows Update service. + If the status of Windows Update is not indicated (the column is blank), right-click on it, and select Start. + It might be that force start of Windows Update ends up with an error. + In this case, find the option Startup Type, and set it to Automatic. + Finally, restart the system and try to run the update.
I am not going to try this just yet but this weekend will ask a relative who knows all about computers to help me. If he solves the problem, I will let you know.
After getting the above information, I got an email with a case number and they are supposed to get back to me.
Been there and done that Holly. Actually, I shut down the Background Intelligent Transfers and Windows Update, rebooted and then started both over again. It did zero.
Also, I checked my Startup Type in Properties and it was set to Manual, so I set it to Automatic at the counsel of the lad you were chatting with.
I thought for a moment it was going to work for it was installing and went right up to 100% and then I got the same error again.
This is a total mess and no doubt to do with an update that Microsoft will no doubt fix in another update. If not, an Inhouse Repair at the advice of Tekker Boy! :-)
@Rubert Mumps and @Holly1958
May I ask both of you why you are ignoring my repair suggestion?
Is it too complicated to describe?
Friendly greetings
Friendly greetings to you O Tekkie boy! As to your query, it is a little complicated and embarrassing to say why up to this point (I) am not ready to do the Inhouse Repair.
I'm not so sure what this does yet (although I haven't looked into it either) but I don't want to do something that will be fixed in a few hours or minutes by Microsoft. We all know how quick to the draw they are on fixer uppers with Updates. One or more have even suggested doing the Service Stack updates and then someone said that could also cause great grief.
If it comes down to the wire where nothing will fix this, then I'll be begging for your furthered assistance. Hope this clarifies the mind numbing side stepping your advice, at least for the moment. :-)
I don't see a reply from you to me in the place where I posted my problem with installing Windows Update KB4566782. However, I have gone back and read your suggestion to Robert Mumps and noticed that the error code you posted is not the one Robert Mumps and I have. Our error code is 0x80073712.
With all that said I have tried very few of the many suggestions I have gotten as some I don't feel capable of trying without making a mistake, and I don't want to mess up my computer. As I informed Robert Mumps I am going to get some advice from a relative, who is very computer knowledgeable, this weekend.
I am 84 years old and don't feel as comfortable coping with these kind of problems as I once did.
Also if you read my most last post to Robert Mumps you will see what I most recently have done.
Holly
Only 84, hey? I'd say you're doing pretty well Holly! I'll look forward to your feedback after your relative takes a look at this. Till then, we'll see ya next summer on the ice! :-)