Oh trust me, I did refer to that and many other places... many times over. I was just hoping someone can tell me at least approximately when and at this point IF there will ever be a fix for this.
At least someone should have suggested work arounds for this for those of us that rely on this feature daily... It is very frustrating being a customer and not getting any support. I've been stuck using an ancient laptop or using Hyper-V just for VLAN tagging every time I need to do anything than DHCP.
Oh, and apparently Intel has a feedback form which I filled out in detail about this issue and checked the option for someone to follow up if needed - never heard a thing from anyone.
By the way for anyone that hasn't already done this or figured out their own workaround, there is a way to do VLAN tagging by using Hyper-V to create a virtual external switch and do the VLAN tagging on it. It's a hassle compared to natively supported VLAN tagging but at least it works. Your hardware has to be capable of running Hyper-V to do this.