The errors you may see
Outlook may display one of these messages:
- “outlvbs.dll was not found.”
- “outlvbs.dll is missing from your computer.”
- “The code execution cannot proceed because outlvbs.dll was not found.”
- “Failed to register a VB Script DLL. Reinstall or run Regsvr32.exe Vbscript.dll to self register.”
- “Microsoft Outlook cannot provide form scripting support.”
- “Microsoft Outlook cannot provide form scripting support. This feature is not currently installed.”
- “The form cache file FRMCACHE.DAT is not valid.”
The 60-second answer
Free tools Windows power users keep installed
One-click scans. No signup required.
outlvbs.dll is Microsoft Outlook’s Outlook VB Script Library, not a normal Windows System32 file. It normally belongs inside the installed Office or Outlook folder.
The safest first repair is:
- Close Outlook and other Office programs.
- Open Settings → Apps → Installed apps.
- Find Microsoft 365 or Microsoft Office.
- Select the three dots beside it and choose Modify.
- Run Quick Repair first.
- If the error remains, return to the same screen and run Online Repair.
- Restart Windows and test Outlook.
Do not download outlvbs.dll from a random DLL website. A loose replacement can contain malware, belong to the wrong Office generation, use the wrong architecture, or leave the damaged Office installation unfixed.
As an Amazon Associate I earn from qualifying purchases.
Microsoft’s official Office repair instructions are the correct starting point.
Recommended Free Tools
What outlvbs.dll is and where it belongs
The filename describes a genuine Microsoft component called Outlook VB Script Library. Microsoft Outlook uses it for VBScript and custom Outlook forms. Microsoft explains the relationship between Outlook forms and scripting in its guide to using Visual Basic with Outlook.
This is an Office component, not a standard Windows component. You should not expect to find it in:
C:WindowsSystem32
or:
C:WindowsSysWOW64
Depending on the Office installation, it may be under a path similar to:
C:Program FilesMicrosoft OfficerootOffice16
A 32-bit Office installation on 64-bit Windows commonly uses a path under:
C:Program Files (x86)Microsoft Office
Older MSI-based Office installations may use folders named Office12, Office14, Office15, or Office16. The correct folder depends on the installed Office generation and installation technology.
Do not treat files from different Office generations as interchangeable. A file from one Outlook installation is not automatically suitable for another.
Identify whether Outlook is 32-bit or 64-bit
Before investigating paths, check Office’s architecture:
- Open Outlook if it starts.
- Select File.
- Select Office Account.
- Select About Outlook.
- Read the text in the dialog. It identifies whether Outlook is 32-bit or 64-bit.
If Outlook will not start:
- Open Settings.
- Select Apps → Installed apps.
- Find Microsoft 365 or Microsoft Office.
- Open its details or repair options.
- If your organization manages Office, ask the administrator which architecture was deployed.
On 64-bit Windows, Program Files (x86) usually indicates a 32-bit application. That is normal. It does not mean Windows itself is broken.
A 32-bit Office installation needs the 32-bit Office component. Do not replace it with a 64-bit DLL copied from another computer.
Fix 1: Repair Office
Office repair is the most likely solution because outlvbs.dll normally arrives as part of Outlook or Office.
Quick Repair
Quick Repair uses files already available on the computer.
- Close Outlook, Word, Excel, Teams, and other Office applications.
- Press Windows + I.
- Select Apps.
- Select Installed apps.
- Find Microsoft 365 or Microsoft Office.
- Select the three dots beside the entry.
- Select Modify.
- Approve the administrator prompt.
- Choose Quick Repair.
- Select Repair.
When it finishes, restart Windows. Open Outlook and check whether the missing-file or form-scripting message returns.
If Quick Repair reports success but Outlook still cannot load the component, run Online Repair.
Online Repair
Online Repair downloads and replaces the complete Office installation. It takes longer and may require Office to be configured again.
- Close every Office program.
- Open Settings → Apps → Installed apps.
- Find Microsoft 365 or Microsoft Office.
- Select the three dots and choose Modify.
- Select Online Repair.
- Select Repair.
- Follow the prompts until the process completes.
- Restart Windows.
- Open Outlook and test the form or mailbox that produced the error.
Online Repair is more appropriate when a component is missing, an update was incomplete, or Quick Repair did not restore Outlook form support.
For an MSI-based Office installation:
- Open Control Panel.
- Select Programs → Programs and Features.
- Select Microsoft Office.
- Select Change.
- Choose Repair.
- Complete the wizard and restart Windows.
If repair does not restore Outlook, uninstall and reinstall Office using the Microsoft account, Microsoft 365 administrator deployment, or approved organizational installer that originally supplied it. There is no general Microsoft outlvbs.dll redistributable intended for copying into Windows.
Fix 2: Understand the two different scripting DLLs
The message mentioning a “VB Script DLL” is easy to misread.
outlvbs.dll is the Outlook component. Windows also has a separate scripting file named:
vbscript.dll
The exact error:
Failed to register a VB Script DLL. Reinstall or run Regsvr32.exe Vbscript.dll to self register.
explicitly names Windows’ vbscript.dll. It does not tell you to register outlvbs.dll.
That means the message can indicate an unavailable or unregistered Windows scripting engine, while a different message may indicate missing Outlook form support.
Register Windows vbscript.dll only when the message calls for it
If the exact message names Vbscript.dll, use an elevated Command Prompt:
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Enter:
regsvr32.exe vbscript.dll
- Press Enter.
- Read the result dialog.
- Restart Windows and test Outlook.
A successful registration only addresses the Windows scripting engine. It does not replace a missing Office file, repair Outlook, rebuild a damaged form cache, or override an Outlook policy that disables custom-form scripts.
Do not make this the default response to every outlvbs.dll error.
Should you run regsvr32 outlvbs.dll?
Usually, no.
The common Outlook error names vbscript.dll, not outlvbs.dll. Registering every DLL mentioned in an internet search is a poor repair method and can produce architecture or registration errors.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If outlvbs.dll is absent, the proper fix is to repair or reinstall the matching Office installation. If it exists but Outlook cannot use it, investigate Office configuration, form cache problems, user profiles, security policy, and Windows vbscript.dll.
Fix 3: Repair Windows components when broader corruption is suspected
SFC and DISM repair protected Windows components. They do not reliably reinstall Office files, so use them after Office repair or when Windows itself has other symptoms.
Run DISM first:
- Open Start.
- Type
Command Prompt. - Right-click it.
- Select Run as administrator.
- Enter:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Press Enter.
- Wait for the operation to finish.
Then run System File Checker:
sfc /scannow
Wait until verification reaches 100 percent. Restart Windows afterward and test Outlook.
If SFC reports that it repaired files, check whether Outlook now starts. If it reports that it could not repair everything, repeat the process after DISM has completed successfully, or investigate Windows servicing problems separately.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →The manual part of DISM and SFC gives you little visibility into which repair changed the system. If you are repeatedly hunting component problems and want a scan that identifies repair issues before applying a fix, Outbyte PC Repair can show what it finds; its repair functions require the full version. It is optional, and Office Online Repair remains the direct fix for a missing Outlook component.
Fix 4: Check antivirus quarantine
Security software may remove or quarantine an Office file after a detection.
Use Microsoft Defender’s history:
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Select Protection history.
- Open the relevant detection.
- Inspect the full file path and detection details.
Do not restore the file merely because its name is familiar. Confirm that it was inside the genuine Office installation folder and that the Office installation itself is trusted.
The safer sequence is usually:
- Note the path shown in Protection history.
- Run Office Online Repair.
- Restart Windows.
- Check Protection history again.
- If Defender repeatedly removes the repaired file, contact your administrator or Microsoft support before adding exclusions.
Microsoft explains the risks of restoring or allowing quarantined items in its guide to Protection History.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesNever replace a quarantined Office file with a download from a DLL website.
Fix 5: Rebuild the Outlook form cache
If the error mentions FRMCACHE.DAT, or if it appears only when opening a custom form, the form cache may be damaged.
- Close Outlook completely.
- Open Task Manager with Ctrl + Shift + Esc.
- Check that
OUTLOOK.EXEis not still running. - In File Explorer, search for:
FRMCACHE.DAT
- Rename the file to something such as:
FRMCACHE.DAT.old
- Do not delete it immediately.
- Start Outlook again.
Outlook may create a new cache when it needs one. Test the form that produced the error.
If renaming the cache changes nothing, do not keep deleting copies. Move on to Office repair, profile testing, and policy checks.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Fix 6: Test whether only one profile is affected
If other Windows users can open Outlook normally on the same computer, the installation may be intact and the problem may be limited to one profile.
First test a new Outlook profile:
- Close Outlook.
- Open Control Panel.
- Set View by to Small icons or Large icons.
- Select Mail.
- Select Show Profiles.
- Select Add.
- Create a test profile.
- Add the mailbox.
- Select Prompt for a profile to be used, or make the new profile the default.
- Start Outlook.
If the new profile works, the original profile or its form configuration needs attention. Do not delete the original profile until you have confirmed that mail, autocomplete data, archives, and account settings are available.
A Windows profile test can also help:
- Open Settings.
- Select Accounts.
- Select Other users.
- Add a temporary local user.
- Sign in to that account.
- Test Outlook if the installation supports the account.
If the error follows every profile, focus on Office deployment, Windows scripting, security software, and policy.
Fix 7: Terminal Server, Remote Desktop Services, and Citrix
Shared computers require a separate investigation. Historical Microsoft documentation describes Outlook VBScript support missing from some Terminal Server installations and emphasizes that the component must match the installed Outlook version. See Microsoft’s guidance for Outlook forms with VBScript on Terminal Services.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFor an RDS, Citrix, or shared Office deployment:
- Confirm whether the issue affects every user.
- Confirm the Office installation method: Click-to-Run or MSI.
- Confirm whether Office was installed for all users.
- Check the Office installation directory for the expected Outlook component.
- Run Office repair through the supported administrator workflow.
- Verify that the deployed Office architecture matches the organization’s image.
- Reapply the approved Office package if repair cannot restore the feature.
Manual copying is not the normal fix. If an administrator uses a legacy deployment workaround, the file must come from the same Outlook version, architecture, and approved installation source. A later Office update may require the component to be deployed again.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 8: Check whether custom-form scripting is disabled
A present and correctly signed Office file does not guarantee that Outlook will run custom-form scripts. Microsoft has disabled custom form script by default in supported Outlook versions and is progressively deprecating VBScript. Review Microsoft’s current information about custom form script being disabled by default.
This creates an important distinction:
- Missing
outlvbs.dll: repair Office. - Missing or unregistered
vbscript.dll: address the Windows scripting engine when the exact error calls for it. - Custom scripts disabled by policy or security changes: work with the administrator or form owner on a supported replacement or approved policy decision.
Do not blindly enable registry settings to restore old scripts. Such changes can weaken security, may be blocked by policy, and may stop working as Microsoft retires VBScript support.
Fix 9: Do not chase drivers or Windows Features for this file
outlvbs.dll is not a graphics, audio, chipset, or device driver file. Device Manager is therefore not a normal repair path.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →If you have separate device problems:
- Right-click Start.
- Select Device Manager.
- Expand the relevant device category.
- Right-click the device.
- Select Update driver.
- Choose Search automatically for drivers.
Do not expect this to restore Outlook. If you are manually checking many devices and need help identifying stale driver versions, Outbyte Driver Updater can scan for driver issues; driver installation through the full version is optional and unrelated to the normal Office repair for outlvbs.dll.
Likewise, opening Turn Windows features on or off is not a substitute for repairing Office. Do not enable unrelated Windows features to compensate for a missing Outlook component.
When System Restore is appropriate
Use System Restore only when the problem began after a recent system change and Office repair, profile testing, and security checks did not help.
Best Value
- Open Start.
- Type
Create a restore point. - Open the result.
- Select System Restore.
- Choose a restore point created before the problem.
- Review the affected programs.
- Confirm the restore.
System Restore is not a replacement for Office repair and may not restore an Office component correctly. Avoid it if you cannot identify a suitable restore point or if the computer is managed by an organization without administrator guidance.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What not to do
- Do not download
outlvbs.dllfrom a random DLL site. - Do not place it in
System32orSysWOW64. - Do not copy it from another computer without matching Office version and architecture.
- Do not assume Visual C++, DirectX, or .NET will restore it.
- Do not run
regsvr32 outlvbs.dllautomatically. - Do not assume SFC repairs Office files.
- Do not disable antivirus protection just to force a DLL into place.
- Do not enable legacy VBScript policy settings without understanding the security and support consequences.
Frequently asked questions
Is outlvbs.dll a Windows file?
No. It is an Outlook component supplied with Microsoft Office. It normally belongs in the Office installation directory, not in the standard Windows system folders.
Which Outlook versions use it?
Microsoft Outlook versions that support the relevant VBScript and custom-form features may include it. The exact file version and location depend on the Office generation, update channel, installation type, language, and 32-bit or 64-bit architecture.
Can I download a replacement outlvbs.dll?
Do not use an unofficial DLL download. Repair or reinstall Office from Microsoft or your organization’s approved Office installer.
Should I run regsvr32 outlvbs.dll?
Not as a default fix. The common registration message refers to Windows vbscript.dll. Repair Office when the Outlook component is missing, and register vbscript.dll only when the exact message calls for it.
Why does Outlook say it cannot provide form scripting support?
Outlook may be missing its form-scripting component, Windows scripting may be unavailable, the form cache may be corrupt, the Office deployment may be incomplete, or current security policy may have disabled custom-form scripting.
Will SFC restore outlvbs.dll?
Usually not. SFC and DISM repair protected Windows components. Use Office Quick Repair or Online Repair for an Outlook file.
What if Online Repair does not help?
Check antivirus Protection History, test a new Outlook profile, rebuild FRMCACHE.DAT if applicable, verify Office architecture, and ask an administrator to review custom-form policy or a shared-computer deployment.
What if only one user sees the error?
Test a new Outlook profile or Windows user profile. A user-specific form cache or profile configuration may be damaged even when Office itself is intact.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What is the correct final fix?
For most missing or unloadable outlvbs.dll errors, the correct path is to repair the installed Office suite, not to copy a DLL into Windows. If custom-form scripts are deliberately disabled, the solution may instead require an administrator-approved policy decision or replacing the legacy form workflow.
