I have seen the same issue, but just with all builds *after* 16215. It exists in the latest build as well. It is hard to tell if it's a Windows bug (unlikely?) or a bug in light.exe. I haven't seen this with any other tools so far.