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

[/quote] That one (un)reclaimable package appears to be a remnant of KB4058258 (16299.214) and was first spotted when the next cumulative update came out...

Cumulative Update KB4058258 Windows 10 v1709 Build 16299.214 - Jan. 31 (post #111)

If you had KB4058258 at the end of January then I think that's your issue, not this update. DISM works without error for me, but then I have purged all trace of KB4058258 from my system.

Code: C:\WINDOWS\system32>dism /Online /Cleanup-Image /AnalyzeComponentStore Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.251 [==========================100.0%==========================] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 6.82 GB Actual Size of Component Store : 6.73 GB Shared with Windows : 5.91 GB Backups and Disabled Features : 662.24 MB Cache and Temporary Data : 163.92 MB Date of Last Cleanup : 2018-03-06 00:13:06 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : No The operation completed successfully. C:\WINDOWS\system32>[/quote]

 

Brink thanks for that information !

 

hi guys, could you check Windows Defender exploit guard form and its settings?

Mine infact is useless since all items are mixed and i no longer have the right perception on the specific mitigation on which i'm operating...

Pics: Hardware Upgrade Forum - View Single Post - [Thread ufficiale] Windows 10 (no preview builds)

 

What is this? Page not available? (Next to Open Network) and yes, firewall still works but this looks kinda weird...?

 

A faster one, less than 5 minutes, but Disk Cleanup has taken too long for a few weeks. About 30 minutes to get rid of Windows. old (2.65GB).

The good news is that for the first time, updates history in Settings was not removed and shows kb4090913 = intact. Thanks for the correction! One more to go there (under construction), drivers link is not shown.

Code: Microsoft Windows [Version 10.0.16299.251 (c) 2017 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism /online /get-packages ... Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.251.1.4 State : Installed Release Type : Update Install Time : 3/6/2018 12:50 PM The operation completed successfully.[/quote] All the best,

 

installed and so far no problems

 

Checked a lot of times over the past 24 hours for this and kept getting the message that my PC was up to date.
I ended up downloading the file manually (thanks for the link Shawn) and installing. Everything is running fine up to now *Smile

 

Hi,

Had the same issue on a Haswell powered pc. Installed manually and all is fine now.

Cheers, *Wink

 

[/quote] I don't have KB4058258 listed at all ...

 

Hmmm, could be MS updates are getting picky over CPUs then . I'm still on a Sandy Bridge *Smile

Thinking I may test that out by switching to the Fast Ring and see what happens.

 

You said you had 16299.214 on Feb. 4th. and it was KB4058258 that raised the build number to .214.

Cumulative Update KB4058258 Windows 10 v1709 Build 16299.214 - Jan. 31

...so it appears that you did have it at one time. Unless you have done a clean install or (as I did) an in-place upgrade repair since then, you will still have the some remnants of KB4058258 on the system. It is this that seems to be responsible for DISM being unable to reclaim that package. It appear to be a package that was part of KB4058258.

 

Yes, remnants may be present and I will now wait until next Tue to see if this mess resolves before spending hours to bring 7 machines back to norm ...

 

As I said in the post I linked to earlier, it wasn't just DISM that was affected, there was also a 49MB of update backups that Disk Clean-up couldn't remove. I was investigating this, and the only fix I could find was the in-place upgrade repair.

Apart from wasting some disk space, the rogue package didn't seem to cause any problems. You might just as well wait for 1803, as that upgrade will also remove the problem.

 

I had the same problem on one system. I use Norton Security and this key was missing on that system. My other 2 systems had the key and WU worked fine. With out that key WU will not offer this KB. I did a manually update on this system and it works fine.

Jim *Cool

 

Strange thing for me on my lappy, could not sign in with my pin. Kept telling me it was invalid. It has always defaulted to the pin input, but this time it changed to password input. Duh!