Forum Thread: Windows Internal Database erroneously declared EOL

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI

This thread has been marked as locked.
colebantam Windows Internal Database erroneously declared EOL
Member 24th Apr, 2017 12:00
Ranking: 23
Posts: 21
User Since: 23rd Apr, 2010
System Score: N/A
Location: AT
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:
https://social.technet.microsoft.com/Forums/window...

Can anybody deliver a "official" source to support my opinion, so that we again can make Secunia to not show that as EOL?

No one has replied to this thread yet - be the first
This thread has been marked as locked.