Has anyone else experienced Segoe UI font corruption when creating a Windows image using NTLite?
Here is an example of the banner text from NTLite running on a Windows 10 x64 1803 build that was created using NTLite:
Here is an example of the banner text from NTLite running on a Windows 10 x64 1803 build installed directly from the untouched Microsoft ISO (downloaded from VLSC).
Here are the 2 images next to each other to show the differences:
If I take the Segoe UI files from the default Windows 10 build and replace the Segoe UI files from the NTLite build, the font fixes itself, but the question is, why is the font getting "corrupted" in the first place?
Here is an example of the banner text from NTLite running on a Windows 10 x64 1803 build that was created using NTLite:
Here is an example of the banner text from NTLite running on a Windows 10 x64 1803 build installed directly from the untouched Microsoft ISO (downloaded from VLSC).
Here are the 2 images next to each other to show the differences:
If I take the Segoe UI files from the default Windows 10 build and replace the Segoe UI files from the NTLite build, the font fixes itself, but the question is, why is the font getting "corrupted" in the first place?
