Comment 26 for bug 1988119

Revision history for this message
Severity1 (johnreilly-pospos) wrote :

@sebastientardifverituity the Microsoft support fix you mentioned worked for me.