I used the Workaround that the guy on TechNet suggested. I added an additional step (Run Commandline) to run this command C:\Windows\CCM\ccmrepair.exe right after the "Setup Windows and ConfigMgr" step to fix the issue. I added it into my build and capture TS and once the new Image was captured i was able to use it without any issues.
If you don't know yet, a fix for this has been release last week.
https://support.microsoft.com/en-us/kb/3127032
Did anyone of you already test the new Windows 10 servicing feature?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.