I tried editing the mum files but there is not Permanent marker there to change to removable. This update (Flash April 2019) is superseded by May update. Any pointers to remove this update?
tried using wusa.exe /uninstall /kb:4493478 from an Administrative command prompt? or a similar command using dism.exe /online /remove-package /packagename
Since i only work with dism, i don't have issue with uninstalling superseded LCU or Flash the thing with 1903 is that LCU is direct update to system packages, so running Update Cleanup normally will remove old base packages resetbase is not required BTW, flash update KB4503308 for 1903 is now normal package, not PSFX
I was just testing this: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-411#post-1530283
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-387#post-1514996 https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-408#post-1527117 https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-411#post-1530283
Thanks for replying and provide clarification about the LCU and the Flash package. I work mostly with WSUS, while checking with Windows Update later to see if there was anything missed. Sometimes I check with Windows Update upfront, but rarely install directly from WU, mostly when trying to resolve corruption and when this is not possible with WSUS alone. I encountered recently such an issue with Office Updates and with 1903 test which had partially installed from Windows Update in the process of installing the OS. This may be because I tend to decline the superseded packages and for a clean install, some of the old patches may still be needed. I expected WSUS to install full package and not "difference" package, but starting with 1903 it does not seem to be the case any longer. I don't use DISM for regular updates as I try to simulate what normal and business administrators would do. But I use DISM for cleanup and for troubleshooting when there is no other way.
I expected this to be discussed elsewhere, but as we know, the Win10 Hotfix thread is already over 400 pages in size and sometimes things get missed.