Thanks xCom, cannot replicate that, should not happen yet your dump file proves it can.
Do you get it each time or maybe a special sequence is required?
If it's each time, can you please attach the preset you load (and open no other pages or do anything manually) so that I can replicate it...
I mean do you load any preset, maybe automatically, and which ISO so that I can see the crash?
Maybe a gif recorded demonstrating the issue instead, you can send it to support at ntlite dot com.
as you have discovered that previous topic, the difference is if Servicing Stack or Windows Update is kept, NTLite will switch to package protection mode, which saves many more files in WinSxS.
Newer version should remove more unless the old one had a bug and removed what shouldn't...
Thanks gilius, appreciate the feedback.
Will review if that can be avoided or it's a hard dependency which should be linked to Bluetooth and description expanded.
Since Bluetooth is sort of a network, it's possible as that component is a broker/connection from apps to the functionality.
It seems the option "Use only latest CLR (.NET version)" is the one.
Make sure not to set it until the Windows setup is done.
I'll see about delaying it, because the issue is not 100% understood why would Windows do this.
For now skip it on images if you're in a hurry.
If I apply your preset, SQL setup doesn't even start, no error code for me.
Skipping/Resetting Settings and Services pages when making ISO made it work. I also used unattended autofil, was doubting on the "Administrator" computer name.
Now need to take a pause, will find which exact setting it...
first I tried the preset and it couldn't install SQL Express 2014 because it was missing .NET 3.5, but the error was different than yours on the screenshot.
So I have added the .NET in the Updates page (Add - Template). Also enabled .NET 3.5 WCF under Features.
Then it passed...