|colebantam||Windows Internal Database erroneously declared EOL|
|24th Apr, 2017 12:00|
User Since: 23rd Apr, 2010
System Score: N/A
PSI detects the Windows Internal Database as beeing EOL. Even though I haven't found any ressoure directly from MS, I have hints that the Window Internal Database (WID) is treated as a Windows Component (remember the Microsoft .NET Discussion we had lately? ;)) and not as a standalone product.
At least I found a statement from an MS partner on this Thread:
Can anybody deliver a "official" source to support my opinion, so that we again can make Secunia to not show that as EOL?