This seems to be a very persistent issue.
Does anyone know if SU has reported it to Microsoft or do we have to just take pot-luck on when Microsoft will become aware of it and correct it (hopefully for good).
This seems to be a very persistent issue.
Does anyone know if SU has reported it to Microsoft or do we have to just take pot-luck on when Microsoft will become aware of it and correct it (hopefully for good).