Wrong OS version when capturing Windows 10 LTSB 1607 (with current patch)
We detected a little bug in the capture process:
When capturing a Windows 10 LTSB 1607 system and creating an OS image with the captured WIM in the ConfigMgr console, a wrong OS Version is reported. The installed OS shows e.g. 14393.2430 (August) or 14393.2485 (September) as OS version, but the captured WIM in both cases 14393.2214. I assume the capture process calculates a "wrong" OS version, producing at least a misleading result. We recognized this with the OS version mentioned above, but this might be a general problem.
It would be interesting to know if this is indeed a bug or probablly by design (?). We weren't able to figure out so far where the 2214 comes from (?) in our scenario.