KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836 Win Update

Steve C said:

Thanks for reminding me. I think I need a new brain. The issue this time is my desktop PC not my HP laptop.

Mine gets a bi-annual reboot courtesy of MS upgrades

Steve C said:

See the result of the DISM Component Store commands below after this update. It says one package is reclaimable but when I run the cleanup command it zips to 20% and then just drops out without doing anything.

I've seen this twice before, once in 1909 on just one machine then again in the RP 2004. The issue seems to be a corrupt manifest for a previous update. It's not a significant issue, the package has been superseded and is no longer in use. Dism's RestoreHealth seems unable to fix this.

In the case of my 1909 machine the corruption was caused by the local system and appeared after needing to use chkdsk /f. In 2004 RP is was an error on the part of MS which they fixed in the next CU.

For my 1909 problem I just had to wait it out until a subsequent update replaced the problem package and Dism (or Disk Clean up) could finally clear out the dross.

Steve C said:

when I run the cleanup command it zips to 20% and then just drops out without doing anything.

Same here. . .

KCR said:

Same here. . .

You've got more problems than just DISM if that's a current screenshot. Your image version 18363.693 is nearly three months out of date. It was release in February.

February 27, 2020 - KB4535996 (OS Builds 18362.693 and 18363.693)

Bree said:

You've got more problems than just DISM if that's a current screenshot. Your image version 18363.693 is nearly three months out of date. It was release in February

Yeah... I know. 😞






Windows 10 Upgrade 2020 - Windows 10 Forums

Hi folks

This is meant to be as near as possible the current release running on most people's computers

All these things like having to use DISM and REG fixes shouldn't be necessary at all on a version that is supposedly the nearest to the current running release.

I've no problems with all this type of tinkering on latest insider builds etc as these are test builds --but on essentially "Bog standard" Mom and Pop builds --- C'mon peeps --imagine the chaos if ordinary bog standard users had to twiddle around with these sorts of settings.

Updates on these types of builds should just work 100% or have clear warnings that if you have specific hardware you will probably be out of luck.

That said though I haven't encountered any problems with this particular build --it installed and worked fine on the following computers (3) :

ON stand alone Windows computer, on Linux NAS box as KVM/QEMU VM and on another Linux NAS box as VMWARE VM so 3 different scenarios all OK.

Cheers
jimbo

hi

About this post (Dism, sfc command sequence), Is auggested to use to fix windows system files and/or after installing a windows update?

thanks

CountMike said:

I always run them, SFC to check on system files and dism to clean up after updates. I also do that as part of check and cleanup before making backup, Can't hurt.

Hi there
It's fine for people on these Forums etc who I assume are generally far more computer literate compared with the average.

My point was that this stuff shouldn't be necessary on updating essentially standard builds where people haven't done anything special to their machines other than adding stable working software.

If You've already tinkered with a machine (nothing wrong for people capable of doing it) then IMO it's then not reasonable to be disappointed in an "update" doesn't work as advertised. My point was that updates for "Standard --Untouched by Human Hand" type of Windows installations should just work !!!

Cheers
jimbo