x86 VM upgraded without any problems from 16199 > 16215. x64 VM upgraded without any problems from 16199 > 16215.
I also saw the runtime error, rest of the install runs fine. Weird error, could it be a VMWare incompatibillity error with this build? You can see my results in this thread, the install runs fine after that vc++ runtime error on my VM's (will do a test on my testsystem asap).
But I tried installing on my laptop, not in VM. I guess I should wait for some more time and see if OOBE proceeds further.
You probably don't use an ei.cfg, use this one (to be put in "USB/ISO:\Sources\"): Code: [Channel] _Default [VL] 0 I don't get the error anymore now.
hmmm fresh install no errors kinda shocking for it to be this stable for a early stage also seeing some great Fluent UI effects
@LostED, is it possible for you to get the nl-NL (Dutch) files for me? PS, retaildemo package(s) can be left out, according to abbodi1406.
For those experiencing 0x80070057, my fix was uninstalling Kaspersky AV 2017... It seems Kaspersky applications are having a hard time with almost every new build of Win10... Also this update used A LOT of disk space compared to earlier builds, so make sure you have PLENTY of free space available (Updated from 16193 to 16215 over WU)
Yep. I already have them for a couple of weeks. Edit: not sure about the sport car. I doubt that I have seen it before.