We're having some trouble downloading updates. Restarting your device

I don't understand why but I'm getting this error after a few weeks not using the OS. "after it was updated" (since I mostly use windows 7 under a dual boot setup.) This is pretty much almost a clean install btw.

anyways you can see from this picture I attached...

My windows is not updating and asks me to reboot I've rebooted several times now with the same effect.

Also I thought hey I can try to use the Windows update mini tool instead just to update. it give me this error
Downloading updates: Failed (0x80240022)

As you can see I get no errors back from DISM/SFC

I also want to point out I have tried to reset windows update using this thread below:
Reset Windows Update in Windows 10

-
Windows 10 Enterprise 2016 LTSB
Version 1607 (OS Build 14393.2941)

How had you been able to use windows 1607 without having a failure to upgrade?

Actually the build version I have of said "1607" is Enterprise 1607 as its the LTSB edition from 2016,
But I do have windows 7, LTSB, and 20H1 Branch installed so yes I technically do have 3 OS installed.

Also I benchmark and do testing on each and every OS build that comes out with windows 10... to why and yes it shows 1803 under my specs was from when I signed up on here a while back I tried to change during this post today but it would not let me for some reason not that it matters much to me.

The reason I have these... what seems you describe very old versions of windows, but I'll describe them as actually more stable and better in performance when it comes to benchmarks and gaming in general IMHO final release candidates of a stable OS builds, rather than some ongoing update of a beta build as windows 10 is the last version of windows and just will keep getting update after update and its never stable and keeps getting worse and worse following testing of my results, but I digress

Anyways...

This post was made was under the system OS as shown in my OP again I'll copy and paste the exact specs below:

Windows 10 Enterprise 2016 LTSB Version 1607 (OS Build 14393.2941)

^ that is the OS I'm currently having this windows update issue with.

oddly enough I didn't wanna mess up my install so I did a fresh install on another partition and sadly again, several hours later so now I have a 4th OS installed under my grub loader, and its the same build as this OP. Giving me the same issue, I'm assuming its a common issue as if i type the subject of this post in to google it comes up with many many results, but as I skim threw an waste my time reading mostly crap off of Microsoft actual forum site that never offers any actual help I figured I'd post here that has people with more expedience in my honest opinion but thats another subject, going back to the subject at hand based on what I just mentioned about the same issue with the 4th partition I don't think a in place upgrade will resolve my problem, also to be quite honest I really would like to avoid any sort of "hey reinstall the whole operating system to fix your problem" when maybe its just something as simple as a network driver or idk since its easy for someone to suggest to fix the issue but more hard for the person with the issue to resolve, see to me that is very extreme and I'm sure there is someone out there might know a thing or two to get this windows update error to go away with out doing so. thanks!

- - - Updated - - -

zbook said:

How had you been able to use windows 1607 without having a failure to upgrade?

This is LTSB 2016 yes the build is 1607 but its not a pro/home standadard edition of 1607 that would upgrade as you are asking...

ok sorry but for people that don't know what that means it's basically a acronym "LTSB" for "Long Term Servicing Branch"
you can think of it similar to how linux has LTS for long-term support, rather than incremental required mandatory in place updates shoved upon you over and over each week ... this version will not upgrade because its made to stay this build.

hence one of the reasons I favor and choose this build for the stability and performance results with out being raped of a update that just breaks everything each month. ( and yes it still gets updates just not build updates )

dalchina said:

Agreed, in principle you should be getting updates for that- for now.

Windows 10 Enterprise 2016 LTSB support lifecycle end date is marked for October 13, 2026

dalchina said:

Given what you've tried, I'd suggest the most straightforward option (bar the fact of your multiple boot) is an in-place upgrade repair install of that build.

Not sure what to try as noone has suggested anything really so far besides what you said with ole reinstall pitch that I'm really not looking for, but I already pointed out I'm trying to avoid that route as I described very specifically in much detail above already...

dalchina said:

You could, of course, try manually downloading the relevant update and see what happens.

Yes actually, The manual updates do work, but I still want to resolve the Windows Update ERROR. " with out a refresh/upgrade "

I know what In-place Upgrade does, also I'd like to point out that you had mentioned this same sledgehammer of a approach already THREE times now, to which I've replied again over and, I will still reply again that this resolution is not a solution to me...I'm not looking to try and fix this small wu error at hand that I currently face with having to throw the whole system image at it. That's ridiculous. Really. Listen imagine you run a computer lab and in your lab you have over thirty computers all running the same software and operating system. hence, all the machines will have the same issue. now how time consuming and, a burden do you think it would be to have to push each system image on each device and wait for such a long process for a simple issue, and please do not answer that question as it was rhetorical, long story short I'm looking for a solution again for third time that can fix the little windows update error with out me having to pull out a windows image. thanks for the easy suggestion, but what I'm looking for here is a shorter to process actual solution that will specifically fix only the wu error that can be quickly managed I digress.