Windows 10 Hotfix Repository

Is this needed even if we are supposed to run the command without ResetBase?

 

No, i just copied the previous code

 

Does anyone know what the source is for the 18362.175 ISOs? It's not listed on MVLSC site.

 

The source is MVS, these checksums are extracted from the MVS website: https://forums.mydigitallife.net/th...x-pc-19h1_release.79259/page-184#post-1531434

 

Thanks. That's weird why I can't see it.

 

Do you have a subscription to MVS?

 

No, but I would think that anything that is on MVS would also show up in the MVLSC if it's a product I've purchased. Whenever a product I've purchased gets updated it gets added to MVLSC. New ISOs get added for every Windows 10 feature update. I just figured that if MS felt that a whole new ISO was warranted for this update that they would put it on the MVLSC as well.

 

W10 1809 LTSC (.107),
I am skipping resetbase with the registry switch enabled(incase it is breaking a captured/deployed image) so i just used the 2 below,

Dism /Online /Cleanup-Image /CheckHealth (no component store damage)
Dism /Online /Cleanup-Image /StartComponentCleanup

Do i need to use "Dism.exe /online /Cleanup-Image /SPSuperseded" aswell, if yes, then what order should i do them in?

Do i need to run "Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore" ?

 

This is the only one that is needed for the intended purposes of cleaning up superseded components.

Is this even still applicable to win >7?

 

You need to login to view this posts content.

 

Enabling the full reset reg tweak and using /resetbase may be breaking redployment of a captured image giving the oobekeyboard error. Just installed the captured image(without an answer file) and it installs perfectly. Im not bothering to check if its the reg tweak, resetbase, or a combination of the 2 that is the problem.

 

You need to login to view this posts content.

 

So it's just a CU?
Alright seen the other topic.

 

Yep, SSU/CU: https://forums.mydigitallife.net/th...000-pc-slow-rs_prerelease.79895/#post-1533892

 

Interesting. From the blog:

"will be delivered to customers running the May 2019 Update using servicing technology (like the monthly Cumulative Update process)."

That's... new. And old. Service Pack nostalgia.

 

They already hinted about this when 19H1 was released, backporting new features and fixes from 20H1 into 19H2.

 

Now we have the answer for changing 1903 CU format to service pack alike

 

Since installing the 19H2 service pack, activex controls (flash, shockwave, silverlight) stopped loading in IE.
Thanks Enthousiast. After resetting IE settings, issue seems fixed.

 

You need to login to view this posts content.

 

..