This is happening to me too, same update, I just get stuck in a boot cycle where it reverts and tries again and fails.
windows update
Please help: 2018-04 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4093112) - Error 0x800f081f
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.
91 answers
Sort by: Oldest
-
Anonymous
2018-04-17T01:58:46+00:00 -
Anonymous
2018-04-17T02:24:35+00:00 I have the same problem. The last time I had a similar update problem (this year) I wasted 2 days back and forward with support etc etc and in the end, those patient enough to wait for a couple of weeks until Microsoft fixed the problem, did not waste 2 days of their life. Admittedly that time I was unable to stop daily attempts/failures at updating so it was hard to ignore. This time I am ignoring the Red X for Device performance and hope Microsoft are going to get their act together eventually
It would not hurt Microsoft to acknowledge problems and keep us updated as to when we can expect a solution
-
Anonymous
2018-04-17T07:22:13+00:00 me2. happens on my HP Spectre. my other 2 Surface devices don't want to install this update even I force to check for. seem MS has withdrawn the April one?
so sit and wait for a fix...
-
Anonymous
2018-04-17T11:47:38+00:00 Gohran's solutions seems to work, except in order to prevent the computer from downloading the automatic update, I first downloaded the updates manually, then I disconnected from the internet by pulling the phone line from the router, and then ran the updates. It does seem I had to reboot the computer once before the manual updates would load because the auto update was still being called upon and the manual update indicated I already had the update (the one which kept repeatedly loading and failing.)
-
Anonymous
2018-04-17T11:55:45+00:00 That is so much trouble. The Windows Update Troubleshooter should be the tool for us to use; if you look at the output, it seems to be trying to do the same thing. I don't know whether it would run if I unplugged my PC from the Internet.
What a mess. I may just wait until next month and see if MS has this straightened out.