|
|
|
|
|
by fname
4166 days ago
|
|
From the comments in the article Microsoft informed us that a fix was planned for the January patches but has to be pulled due to compatibility issues. Therefore the fix is now expected in the February patches. So, they met the deadline and fixed the vulnerability, but due to compatibility issues had to pull it before being released through Windows Update. |
|