I know. Branding from Server != Branding for client (and on old windows 10 even LTSB was a separate one) So just use the branding from a client version, 25393 is the closest, but any client build should do the job (not just the mui, all the files that belongs to the branding folder)
Personally I never cared about that, but I understand your point. My idea is... you can rename the Branding folder as BrandingS, then copy the folder from a client machine, and use your OS normally. If you need to sfc /scanos or Dism /restorehealt or whatever... rename the branding folder as brandingC, rename the brandingS folder as branding, do what you need to do, then rename back the folders. Simple, reversible and fast.
10.0.25398 needs full unstaging edition staging is not enuf to fix problems with powershell and such edit powershell is opened and ready for command but it get stucked after exec the command edit2 sysprep helped :O
Recovery is useless wasted space, *at least* two OSes in multiboot are everything a decent users need to get out of troubles. And if you are a technician going to serve a random user, surely you have (one or more) bootable media that includes a recovery environment, a linux distro, a full OS on a native vhd, or a swiss knife media like Strelec. If you are none of the above, very likely you have no idea of what to do once you have the recovery booted. But aside that, who said that a 25398 OS needs a 25398 Recovery? A random one does its (poor) job exactly like one of the same build.
xinso, you are able to repeat the above procedure for Starter for builds up to 10586 only? Or same applies to modern builds?
10586 Starter is compatible with 10240 only. But 10240 Starter is not blocked. So, 10240 Starter does not need patch.
Got it. If I understand correctly, 19041.1 doesn't exist at all? Or it is only a question of activation? Were you able to reconstruct 19041 or 22000/22621/26100 (without activation)? So, it is a matter of license only, or more packages are missing to do reconstruction?