Cumulative Update KB4090913 Windows 10 v1709 Build 16299.251 - Mar. 5

fdegrove · 17 Mar 2018

Hi,

This morning WU finally tells error code 0x800f0922 for (KB4088776) (3) update failure.

That's the same error as before: problems downloading (could be corrupted files as well) and/or System Reserved partition too small for WU to work with.
So, the same advise about running sfc/scannow and the DISM command lines to check general system health still apply.
You also want to a thorough virus and malware check.

Cheers,

mora67 · 17 Mar 2018

fdegrove said:

Hi,

That's the same error as before: problems downloading (could be corrupted files as well) and/or System Reserved partition too small for WU to work with.
So, the same advise about running sfc/scannow and othe DISM command lines to check general system health still apply.
You also want to a torough virus and malware check.

Cheers,

Got sfc/scannow done earlier, that found no violations. Virus scans I did several times as well, I have F-Secure Safe. Now doing more radical cleanup: Create Windows 10 installation media.

IronZorg89 · 17 Mar 2018

fdegrove said:

Hi,

That's the same error as before: problems downloading (could be corrupted files as well) and/or System Reserved partition too small for WU to work with.
So, the same advise about running sfc/scannow and the DISM command lines to check general system health still apply.
You also want to a thorough virus and malware check.

Cheers,

When the system reserved partition doesn't have enough free disk space, one would have a message specific to that effect in the genre:
"Windows couldn't be installed. We couldn't update the system reserved partition".
That would happen mostly when upgrading from a lower to a higher version of Windows. And, in the case of @mora67, I don't think that is the case. I am leaning more toward the corruption of the Windows Update data base.

mora67 · 17 Mar 2018

IronZorg89 said:

And, in the case of @mora67, I don't think that is the case. I am leaning more toward the corruption of the Windows Update data base.

My case was solved with Create Windows 10 installation media. Took about 90 minutes totally, and now I got 16299.309 running.

But: I just found out that my second singing local account is again having issues I got few weeks ago. Black screen after sign in, and it tries to find specific settings it has. Seems like the whole mess I had perhaps is based on that account. I did this new Windows mounting from fresh Admin account. I wrote about this account issue earlier here in Tenforum.

[EDIT] Also I wonder when signed in with Admin account, in WU I got red message that my updates has organisation control. What could that be?

Bree · 17 Mar 2018

mora67 said:

I wonder when signed in with Admin account, in WU I got red message that my updates has organisation control. What could that be?

Is there a View configured update policies link below that? If so, click on it and it will tell you what policies are in place. See the tutorial...

View Configured Update Policies in Windows 10

IronZorg89 · 17 Mar 2018

.

mora67 said:

[EDIT] Also I wonder when signed in with Admin account, in WU I got red message that my updates has organisation control. What could that be?

That means you have probably set some restrictions in gpedit.msc with regard to "Updates".

Bree · 17 Mar 2018

mora67 said:

I just found out that my second singing local account is again having issues I got few weeks ago.

As you had these issues before it may be that the user profile for that particular account is corrupt. Try creating another local account and see if that works without issue.

mora67 · 17 Mar 2018

Bree said:

Is there a View configured update policies link below that? If so, click on it and it will tell you what policies are in place. See the tutorial...

View Configured Update Policies in Windows 10

That red organisation control message in WU was after I did new Windows install from Create Windows 10 installation media. But after that I did this latest cumulative update .309 installed together with 1709 and now red message is gone.

Bree · 17 Mar 2018

mora67 said:

That red organisation control message in WU was after I did new Windows install from Create Windows 10 installation media. But after that I did this latest cumulative update .309 installed together with 1709 and now red message is gone.

Ah yes, you must have Pro then. There was a bug in the initial 16299.15 that incorrectly showed that 'organisation...' message on the windows update page, but was corrected in a subsequent cumulative update.

Bree said:

I'm running Windows 10 Home Edition, and for some reason, it won't allow me to check the box "Enabling this policy will automatically download updates, even over metered data connections (charges may apply)" and I'm not sure why?

When 1709 was first released (16299.15) you could tick that box in both Home and Pro. As I described, earlier there was a bug in Pro that left the red 'some settings are managed by your organisation' message even after you unticked that box. That has been fixed now, I'm not sure which build fixed it but it is fixed in 16299.248. ...it appears that this bug was still being reported as present in 16299.214.

https://www.tenforums.com/tutorials/...ml#post1302102 (post #8)

mora67 · 17 Mar 2018

Bree said:

As you had these issues before it may be that the user profile for that particular account is corrupt. Try creating another local account and see if that works without issue.

That old black screen issue concerns only one account, same when all WU issues together with that black screen thing started after Fabruary 14 when cumulative .248 update was installed in my previous Windows 10. Tested already another family member account after new WIndows and works fine. Also I created for a test a new account and no problems.