Obsolescence review for components

Question

Obsolescence review for components

Aditya Shah 20

Dear Team,

We are compiling the Software Bill of Materials (SBOM) for some instruments and conducting a security and obsolescence review of components currently deployed in production. To complete our compliance documentation and plan upgrades, please provide the details below for each component:

Components:

DAO350.DLL 3.50.3602.0

DAO3032.DLL 3.000.2008

Microsoft Visual Studio10(ATL100.DLL) 10.00.30319.01

3D Windows Controls 2,31,0,0

MFC40D.DLL 4.0.000

MFCO42D.DLL 6.0.400

MSJINT32.DLL 3.000.2008

msrdo32.dll 1.0.2417

MSREPL35.DLL 3.51.0623.0

msvcrt.dll 7.0.2600.2180

MSVCRT20.DLL 2.10.000

MSVCRT40.DLL 4.00.5270

Microsoft Open Database Connectivity 3.51.1713.00

PSAPI 5.00.2134.1

SETUPKIT.DLL 4.00.2422

VBAJET32.DLL 6

VBAR332.DLL 3

VBDB32.DLL 4.00.2422

VB5DB.DLL 6.00.8169

MSVCI70.DLL 7.00.9466.0

MATLAB Win32 GUI Driver Library 6.5.0.180913a

vshost.exe 12.0.30723.0

cabarc.exe 5.1.2600.0

SETUP.EXE 5.00.3716

SETUP.EXE 6.00.8169

For each component, kindly share:

Lifecycle & Support • Official End of Support (EOS) / End of Life (EOL) dates • Link to the vendor’s lifecycle or support policy page
Current Supported Versions
Upgrade Guidance • Recommended upgrade path (target version and intermediate steps if required)

Thank you, Aditya Shah

Michael Le (WICLOUD CORPORATION) 11,080 Reputation points Microsoft External Staff Moderator

2026-03-03T09:40:42.63+00:00

Hello @Aditya Shah ,

It's been a while since we last heard from you. Hope things are going well.

If you're still interested or have any questions, feel free to reach out whenever it works best for you.

1 answer

Your answer

Michael Le (WICLOUD CORPORATION) 11,080 Reputation points Microsoft External Staff Moderator

2026-03-03T09:40:42.63+00:00

Hello @Aditya Shah ,

It's been a while since we last heard from you. Hope things are going well.

If you're still interested or have any questions, feel free to reach out whenever it works best for you.

Answer 1

Hi @Aditya Shah ,

Thanks for reaching out.

Microsoft doesn’t publish lifecycle, EOS, or EOL information at the individual DLL or file version level. Files like DAO350.DLL, MSVCRT40.DLL, MFC40D.DLL, and VB*.DLL are internal runtime components, not standalone products, so there isn’t an official source that provides support dates or upgrade paths for each DLL by itself.

Microsoft defines support at the product or platform level, for example:

Windows operating system versions
Visual Studio / Visual C++ toolsets and Redistributables
Visual Basic (VB5/VB6)
Microsoft Data Access Components (MDAC / Jet / ODBC)
Third-party products such as MATLAB

For compliance documentation, I recommend checking out these:

Product Lifecycle Search: https://learn.microsoft.com/en-us/lifecycle/products/
Visual C++ Lifecycle FAQ: https://learn.microsoft.com/en-us/lifecycle/faq/visual-c-faq
Data Access History (DAO, ODBC deprecation): https://learn.microsoft.com/en-us/sql/connect/connect-history
Visual Basic 6.0 Support Policy: https://learn.microsoft.com/en-us/lifecycle/announcements/visual-basic-6-support-announcement
Latest Supported VC++ Downloads: https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist/

Any upgrade or remediation planning is typically done at the product level (for example, moving to a supported Windows version or modern development toolchain), rather than updating individual DLLs.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Share via

Obsolescence review for components

1 answer

Your answer