Microsoft forms 2 0 object library missing

Microsoft Forms 2.0 Object Library missing usually means a broken VBA reference, not a missing control. Start by checking References in the VBE, then verify FM20.DLL and its registry registration before reinstalling anything. Ignoring it can stop UserForms, break compile, and block code that depends on MSForms controls. This guide shows how to tell a registry fault from a bad reference or wrong file path, then pick the safest fix.

What the missing Forms reference means

Microsoft Forms 2.0 Object Library is a legacy VBA component used for UserForms and controls such as TextBox and ComboBox. When it is registered, it appears in the VBA References dialog. If it is absent, the problem may be registration, not the file itself; if it is present but marked MISSING, the project already has a broken reference.

In Excel and Word, UserForms can pull the reference in automatically when you add a form in the VBE. In Access, the same library is often used for forms and code modules, so the error tends to appear there as well.

Likely causes

• Not in the References list: the library is not registered or not present in that Office environment.
• MISSING in the project: the project points to a file that moved, was removed, or no longer matches the installed version.
• Browse cannot find DLL: the path is wrong, or the file is not in the folder you checked.
• Excel or Access version limitation: a web-based or limited edition may not include VBA support.
• Wrong filename typed: MF20.DLL is a typo; the file name in the fix path is FM20.DLL.

Forms 2.0 diagnostic table

Use this table to separate the three problems that get labeled the same way. It tells you whether you need to register the library, clear a broken reference, or locate the file path.

Suppose Access opens a project with a compile error and the References dialog shows MISSING: Microsoft Forms 2.0 Object Library. That is a broken reference. A different case is Excel showing no Forms entry at all in References. That points first to registration or edition limits, not a damaged project file.

Why is Microsoft Forms 2.0 not in References?

If the library does not appear in Tools > References, the problem is usually registration or product scope, not a hidden control. In Access, a library that is not listed is not registered or not present. A limited Office install, a web-based edition, or a policy-restricted environment can also keep it out of the list (per Microsoft support).

1. Open the VBA editor with Alt + F11 (per Microsoft support).
2. Go to Tools > References.
3. Look for Microsoft Forms 2.0 Object Library.
4. If it is absent, check whether you are in the correct workbook, document, or Access database.
5. Confirm that you have a full desktop Office installation with Developer access enabled.

A common first-timer mistake is treating a hidden Developer tab as proof that VBA is unavailable. It is not. The tab can be hidden while the desktop Office install still supports VBA and the Forms library. In Excel or Word, reveal it with File > Options > Customize Ribbon > check Developer.

How do you fix a broken MISSING reference?

A broken reference appears as MISSING in the References dialog, and it can stop VBA code from compiling until you remove it or point it to the correct file. This is the fastest fix when the library used to work but the project now fails after a move, upgrade, or cleanup (per Microsoft support).

1. Open the VBA editor with Alt + F11.
2. Go to Tools > References.
3. Find the entry marked MISSING.
4. Clear the check box for the broken entry, or use Browse… if you know the correct file path.
5. Save the project, then run Debug > Compile VBAProject if that menu is available.

If the project contains one bad reference, other references can fail next. Fix the broken item first. Then reopen References and confirm that no entry is still marked MISSING. That order matters because a single broken library can block the rest of the compile chain.

Where is FM20.DLL located on my PC?

FM20.DLL is the legacy file associated with Microsoft Forms 2.0. It is often installed with Office components or placed in Windows system folders, so do not assume it is missing just because it is not in an Office folder. Common locations include C:\Windows\System32 and C:\Windows\SysWOW64; 32-bit and 64-bit Office may point to different paths.

1. Open the VBA editor with Alt + F11.
2. Go to Tools > References.
3. Select Browse….
4. Select FM20.DLL if it appears, then confirm the reference.

Browsed paths that point only to Office folders can mislead you. The file may already be in a Windows system folder. If Browse opens the wrong folder, move up one level and check both system paths before deciding the DLL is absent.

How do I add FM20.DLL to VBA references?

You can add the file manually through the VBA References dialog, which lists registered libraries and lets you browse for DLL, TLB, and EXE files. Microsoft’s step sequence is simple: open the VBE, open References, choose Browse, and enter FM20.DLL exactly. The file is a legacy component used primarily in VBA environments and is not a standalone modern download (per Microsoft support).

1. Open the VBA editor with Alt + F11.
2. Go to Tools > References.
3. Click Browse….
4. In the file name field, enter FM20.DLL.
5. Click Open, then return to the project and check the reference list.

Say your macro uses a UserForm with a ComboBox, but the project throws a compile error after a PC migration. The quickest check is References, not a fresh download. If FM20.DLL is already on the machine, Browse should find it; if not, the issue is usually the Office install or the project’s reference map.

How do I fix Microsoft Forms 2.0 object library missing?

Start with the least invasive fix: open the project in the VBA editor, inspect References, and decide whether you are dealing with a missing entry, a MISSING entry, or a file-path problem. If the library is not listed, try Office repair before searching for the file. If the project already shows MISSING, clear or redirect that reference first (per Microsoft support).

1. Confirm you are using a full desktop Office installation.
2. In Excel or Word, enable File > Options > Customize Ribbon > Developer if needed.
3. Open VBA with Alt + F11.
4. Use Tools > References to check for the library or a broken entry.
5. Use Browse… and enter FM20.DLL only if the file exists locally.

If the library still will not appear, run Office repair from Windows Settings > Apps > Microsoft 365 or Office > Modify > Quick Repair. If Quick Repair fails, run Online Repair from the same path. That is the safer escalation than downloading a DLL from an unofficial site, which Microsoft warns against.

Still not working?

At this point, separate setup problems from project problems. If the file exists in System32 or SysWOW64 and the project still shows MISSING, the workbook, database, or add-in may be carrying a stale reference that needs removal. If the library never appears in References on a limited Office edition, stop trying to add it and move the project to a desktop Office installation with VBA support (per Microsoft support).

1. Run Windows Settings > Apps > Microsoft 365 or Office > Modify > Online Repair if Quick Repair did not restore the library.
2. Check bitness: 32-bit Office often expects different file locations than 64-bit Office.
3. Verify the filename is FM20.DLL, not MF20.DLL.
4. If the project still depends on this library, decide whether to keep the VBA form or redesign the feature for a different approach.

Microsoft Forms or Power Apps are not drop-in replacements for VBA UserForms and MSForms controls. For new work, choose them only if the project can change architecture. For an existing macro that depends on UserForms, first repair the reference path, then decide whether the project should stay on Forms 2.0 at all.

Frequently asked questions

Why is microsoft Forms 2.0 object library not in references?

In Access, if the library is not listed, it is not registered or not present. In Excel or Word, it may also be blocked by a limited edition, a missing desktop Office installation, or policy restrictions. First confirm you opened the correct project, then check whether VBA and Developer features are available.

Is Microsoft Forms 2.0 dll available as a download?

No standalone Microsoft download is provided for FM20.DLL. Microsoft warns against unofficial sources, so do not pull the file from a third-party site. If the component is absent, the safer path is Office repair or fixing the project’s reference, not downloading a random copy.

Can I browse for MF20.dll instead of FM20.dll?

No. MF20.DLL is a typo. The filename used in the VBA fix path is FM20.DLL. If you type the wrong name, Browse will fail even when the correct file is already on the system. Recheck the spelling before assuming the library is gone.