I have never witnessed a time where MS actually removed the base files from a build, but it's possible. If they actually compiled a whole new build based on the updated source code they could do it, but all files would have like .15 at the end instead of some being .1 They were talking about this one time an insider build did that a few pages back. Every build they've released to consumers has had the full base image files with the addition of possible updated package files. AFAIK even resetbase doesn't actually remove the base system files. It just compresses them until you need them such as with the refresh tool.
OP I believe means Original Post. A lot of forum types use it as shorthand. It's basically the first post in the thread.
I've never heard of disabling this with the registry. I guess depending on how updates are applied, this could be a really bad idea. Also refresh feature as you noted. I'm unsure if they always ship the full files in compressed form or some delta variants. If they have delta variants of .1 to .xx, it would obviously fail without the source file.
OP= Original Post, i.e. the very first post on the 1st page of the topic/thread that contains all major links & information about the topic/thread. See the attached Screenshot for ref.
I have the same issue and I don't even have any dedicated soundcard - also removed all USB devices and uninstalled BattleEye/EAC but still the same. EDIT: It seems removing BattleEye/EAC AND restarting the setup (I also ran disk cleanup to remove update data from the failed attempt) fixed this and I can install the update now.
1903 is one surprise after another, didn't test. Like this: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-387#post-1514996
The finished .esd and .iso versions are a bit superior, in my opinion because of the updated setup files, but I think the downloaded uup package method they've been using has a lot of potential. If they are to somehow consolidate all their different versions and distribution methods in the future as more and more people download Windows versions, it would be advantageous to have the core components separate. They already kind-of do it, but they still have a lot of strings that are localized in the various system files. If they can separate it into proper language cabs and feature cabs, it will be more efficient. They wouldn't need to host quite as much data and what little they did host could always remain in memory.
the only diff that I've noticed in between UUP files made ISO & an MSDN/MVS ISO is that the different discoloured background in OOBX, can you specify what other superiority you noticed here in this new v1903 distribution?
It is not like people can make a localized ISO from it, I definitely can not. Who knows, I never read it, it is full of info that makes no sense at all, not for normal people anyway. People mostly just want a download link and that is it.
I found my problem. It thought the "Print to PDF" and "XPS Document Writer" drivers were incompatible. Even though they are built-in Windows drivers lol. All good now.