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 →Repair Windows errors before they cause bigger problemsFix Now →owssupp.dll is a Microsoft Office file named Microsoft SharePoint Client Support. If owssupp.dll is missing, not found, or cannot be loaded, repair the Office installation that provided SharePoint integration instead of copying a replacement into a Windows system folder.
What owssupp.dll is
owssupp.dll belongs to Microsoft Office and supports client-side SharePoint integration. It is associated with the controls Office used to open, edit, and launch documents from SharePoint libraries.
Microsoft documentation places the file in an Office installation directory, such as:
C:Program FilesMicrosoft OfficeOffice14
Older Office 2003 installations commonly used:
C:Program FilesMicrosoft OfficeOffice11
It is not a normal Windows component stored in System32 or SysWOW64. It is also not a Visual C++ runtime, DirectX file, .NET component, or hardware driver.
#1 Best Overall
Microsoft identifies the file as part of Office and SharePoint client functionality in its documentation for the SpreadsheetLauncher control.
Version and architecture guide
| Item | What it means |
|---|---|
| File name | owssupp.dll or OWSSUPP.DLL |
| Description | Microsoft SharePoint Client Support |
| Publisher | Microsoft Corporation |
| Main role | Office and SharePoint document integration |
| Older Office location | Office11, commonly associated with Office 2003 |
| Office 2010 location | Office14 |
| Older reported copy | 32-bit, version 12.0.4518.1014 |
| Later reported copy | 32-bit, version 14.0.4761.1000 |
| Architecture rule | The DLL must match the Office process, not simply the Windows installation |
The listed version and size information comes from file indexes rather than a verified Microsoft package manifest. Do not use a reported version number as a reason to download a replacement.
Errors associated with owssupp.dll
A Windows program may display a generic loader message such as:
- “The program can’t start because OWSSUPP.dll is missing from your computer.”
- “This application failed to start because OWSSUPP.dll was not found.”
- “Error loading OWSSUPP.dll.”
- “The specified module could not be found.”
These are general Windows loader messages. They do not prove that the DLL itself is the only missing component.
Recommended Free Tools
The most specific documented failure is SharePoint’s Edit Document error:
“Edit Document” requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 5.0 or greater.
On older Office and SharePoint systems, this message can appear when the SharePoint support feature is absent, incorrectly registered, disabled, or damaged. Office 2007-era workflows had a corresponding Internet Explorer 6.0 requirement.
Before changing anything
Think about what happened immediately before the error appeared. The likely triggers are:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Office repair, update, or upgrade
- A partial Office uninstall
- Removal of SharePoint Designer or another Office version
- Installation of multiple Office generations
- Antivirus quarantine
- An incomplete optional-feature installation
- A damaged Office installation
- A disabled SharePoint ActiveX control on a legacy Internet Explorer system
If the error appears only when selecting Edit Document in a SharePoint library, start with Office feature repair. If every Office program is failing, repair Office before attempting registration.
Fix 1: Install or repair Windows SharePoint Services Support
This is the most likely fix for a genuine SharePoint integration failure.
Office 2003
- Close Word, Excel, Outlook, Internet Explorer, and other Office programs.
- Open Control Panel.
- Select Add or Remove Programs.
- Select Microsoft Office 2003.
- Click Change.
- Choose Repair or Reinstall/Repair Office.
- If Office Setup shows feature selection, expand Office Tools.
- Set Windows SharePoint Services Support to be installed.
- Continue through setup.
- Restart Windows.
For Office XP, the similarly named feature is Microsoft SharePoint Support.
MSI-based Office versions
For older Office releases installed through Windows Installer:
- Open Control Panel.
- Select Programs and Features.
- Select the Microsoft Office entry.
- Click Change.
- Choose Repair.
- Follow the prompts and restart Windows.
Current Click-to-Run Office
For a current Click-to-Run installation:
- Open Settings.
- Select Apps.
- Select Installed apps or Apps & features.
- Find Microsoft 365 or Microsoft Office.
- Select the three-dot menu.
- Choose Modify.
- Select Online Repair.
- Confirm the repair and allow it to finish.
- Restart Windows.
Microsoft’s current Office application repair instructions explain the differences between Quick Repair, Online Repair, and older Control Panel repair options.
How to check whether this worked
Open the SharePoint library and test Edit Document again. Also open the affected Office application normally.
If the file returns but the SharePoint command still fails, the remaining problem may be registration, a disabled legacy control, or incompatible Office versions. Continue with the next sections rather than downloading another DLL.
Fix 2: Repair Office from its original source
If the SharePoint feature does not appear in Office maintenance, or repair finishes without restoring the file, the installation may be incomplete.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use the original licensed Office media, an organization-managed Office installation source, or the Microsoft account and deployment method used to install the product. Do not combine files from Office 2003, Office 2007, Office 2010, SharePoint Designer, and Microsoft 365 manually.
- Close all Office programs.
- Open Control Panel → Programs and Features.
- Select the Office product that should provide SharePoint integration.
- Click Change.
- Choose Repair if available.
- If repair is unavailable or fails, uninstall the damaged Office installation.
- Restart Windows.
- Reinstall Office from its original trusted source.
- Include the SharePoint support feature when Office Setup offers feature selection.
- Restart Windows again.
- Test the SharePoint Edit Document action.
If several Office versions are installed, decide which one is supposed to handle SharePoint links. Repair that version first. A newer or older owssupp.dll can remain registered after another Office product is removed, causing a version conflict.
Office 2003 reached the end of Microsoft support on April 9, 2014. Its SharePoint integration may also be incompatible with modern SharePoint authentication, browser, TLS, or server requirements. Repairing the DLL cannot make unsupported legacy software compatible with a newer service. Microsoft lists the lifecycle details for Office 2003.
Fix 3: Register the correct Office copy
Registration is relevant for owssupp.dll because this DLL exposes Office and SharePoint ActiveX or COM functionality. It is not a generic step for every missing DLL.
First locate the copy belonging to the Office installation you repaired. Common folders include:
C:Program FilesMicrosoft OfficeOffice11
C:Program FilesMicrosoft OfficeOffice12
C:Program FilesMicrosoft OfficeOffice14
C:Program Files (x86)Microsoft OfficeOffice11
C:Program Files (x86)Microsoft OfficeOffice14
The folder names vary by Office generation and installation type.
Register from the DLL directory
- Open the Office directory containing the correct
owssupp.dll. - Click the address bar in File Explorer.
- Type
cmd. - Press Enter.
- In the Command Prompt window, run:
regsvr32 -u owssupp.dll
regsvr32 owssupp.dll
If Windows reports that administrator permission is required:
- Open the Start menu.
- Type
cmd. - Right-click Command Prompt.
- Select Run as administrator.
- Change to the Office directory, for example:
cd /d "C:Program Files (x86)Microsoft OfficeOffice11"
- Run:
regsvr32 -u owssupp.dll
regsvr32 owssupp.dll
A successful registration normally produces a message stating that the operation succeeded. Restart Windows and test SharePoint.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUse the matching regsvr32 architecture
On 64-bit Windows with 32-bit Office, use the 32-bit registration tool. For example:
%windir%SysWOW64regsvr32.exe "C:Program Files (x86)Microsoft OfficeOffice11owssupp.dll"
The name SysWOW64 is confusing: on 64-bit Windows, it contains the 32-bit system tools. A 32-bit Office process needs the 32-bit regsvr32.exe and the 32-bit owssupp.dll.
For 64-bit Office, use the 64-bit registration tool with the matching 64-bit Office DLL:
%windir%System32regsvr32.exe "C:Program FilesMicrosoft OfficeOffice14owssupp.dll"
Do not select the tool based only on whether Windows is 32-bit or 64-bit. Match the tool and DLL to Office.
If registration fails
A message such as LoadLibrary failed, The specified module could not be found, or error 0x80070716 usually means one of these things:
- The path points to the wrong Office generation.
- The registration tool has the wrong architecture.
- A dependency is missing.
- The DLL is damaged.
- An older Office copy is still registered.
- The Office feature was never installed.
Registration is not the root repair in those cases. Return to Office repair and remove version conflicts instead of repeatedly running regsvr32.
Fix 4: Check for a disabled SharePoint ActiveX control
This applies only to legacy SharePoint workflows that use Internet Explorer and ActiveX. It does not restore modern browser integration.
On an older system that still uses Internet Explorer for the SharePoint site:
Windows 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 reinstallCrashes, 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 minute- Open Internet Explorer.
- Select Tools.
- Choose Manage add-ons.
- Look for SharePoint OpenDocuments Class.
- If it is disabled, select it.
- Click Enable.
- Close and reopen Internet Explorer.
- Test Edit Document in the SharePoint library.
The control may not be present if Office SharePoint support was not installed. In that situation, return to Office maintenance and install Windows SharePoint Services Support.
Do not weaken all browser security settings to make one old SharePoint workflow operate. If the organization has moved to a modern SharePoint service, the correct solution may be a supported Office client rather than an ActiveX change.
Fix 5: Check antivirus quarantine
Security software may quarantine an Office DLL, although quarantine is only one possible cause and is not established as the cause in every owssupp.dll case.
In Windows Security:
- Open the Start menu.
- Type Windows Security.
- Open it.
- Select Virus & threat protection.
- Choose Protection history.
- Review recent actions.
- If
owssupp.dllappears, verify that its original path belongs to the trusted Office installation. - Check the file’s digital signature and the health of the Office installation.
- Restore or allow it only when you are certain it is the genuine Office copy.
- Run an Office repair afterward.
Microsoft explains quarantine and restore decisions in its Protection History documentation.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →If the file was found in a temporary folder, an unfamiliar application directory, or a DLL download archive, do not restore it. Remove the questionable file and repair Office from a trusted source.
Fix 6: Repair Windows components
owssupp.dll is normally an Office-installed file, so Windows component repair usually will not recreate it. Use DISM and SFC when Windows itself shows broader corruption, update failures, or damaged protected components.
- Open the Start menu.
- Type
cmd. - Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Then run:
sfc /scannow
- Restart Windows.
- Run Office repair again.
- Test the SharePoint action.
Microsoft documents these commands in its DISM repair guidance and System File Checker documentation.
If SFC reports that it repaired files, restart and test. If it reports that it could not repair some files, do not assume that it restored owssupp.dll; repair the Office installation separately.
Repeating SFC and DISM without knowing what changed can make troubleshooting difficult. Outbyte PC Repair can scan for issues and show what it identifies before its full-version repair is used, but repairing or reinstalling the affected Office product remains the definitive fix for an Office-owned DLL.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 7: Update related software only when the symptoms justify it
owssupp.dll is not a device-driver file, so Device Manager is not a normal repair path. Do not install a graphics, printer, chipset, or storage driver merely because the filename ends in .dll.
Use Device Manager only if the computer also has a separate hardware problem:
- Right-click the Start button.
- Select Device Manager.
- Expand the category for the affected hardware.
- Right-click the device.
- Select Update driver.
- Choose Search automatically for drivers, or install a driver supplied by the hardware manufacturer.
- Restart Windows.
- Test Office again.
A driver update will not recreate an absent Office SharePoint component. Outbyte Driver Updater can scan for outdated drivers and identify what needs attention before its full-version installation, but it is not a substitute for repairing Office when owssupp.dll is the actual problem.
Fix 8: Use System Restore only as a recovery option
System Restore can help when the failure began immediately after an Office uninstall, update, or system change and normal Office repair cannot restore the integration.
- Open the Start menu.
- Type Create a restore point.
- Open the result.
- Select System Restore.
- Choose a restore point from before the failure.
- Review the affected programs.
- Start the restore.
- Restart Windows and test Office.
System Restore is not a primary owssupp.dll repair. It may reverse other software changes, so use it only after confirming that Office repair and reinstall options are unavailable or unsuccessful.
Best Value
What not to do
Do not download owssupp.dll from a DLL website
Random DLL download sites can provide:
- The wrong Office generation
- The wrong architecture
- An unsigned or modified file
- A file with missing dependencies
- A copy that creates a stale registration conflict
- Malware disguised as a system component
Copying the file into C:WindowsSystem32, C:WindowsSysWOW64, or an unrelated application directory is incorrect. It can hide the damaged Office installation while leaving SharePoint registration broken.
The safe sources are Office repair, the original licensed Office installation media, an organization-managed Office deployment, or Microsoft’s current Office installation and repair workflow.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDo not install unrelated runtimes
Installing Visual C++ Redistributables, DirectX, .NET, registry cleaners, or game DLL packages will not normally restore an Office-installed SharePoint DLL. owssupp.dll is not a gaming runtime.
Do not use SFC as the first fix
SFC protects Windows system files. It generally does not restore an Office DLL unless that file is part of a protected Windows component set. Start with Office maintenance.
Frequently asked questions
Is owssupp.dll part of Windows?
No. It is associated with Microsoft Office and SharePoint client integration. It should not normally be placed in System32 or SysWOW64.
Which Office products can contain it?
It is associated with Office XP and Office 2003-era SharePoint support, the 2007 Office system, and later Office releases that include SharePoint-related components. Microsoft documentation explicitly shows it in an Office 2010 Office14 directory.
Is owssupp.dll 32-bit or 64-bit?
Older Office 2003-era copies are generally 32-bit. Later Office releases had architecture-specific copies. The DLL must match the Office process that loads it. A 32-bit Office installation on 64-bit Windows still requires the 32-bit DLL and 32-bit registration tool.
Should I run regsvr32?
Yes, but only after repairing Office and only against the correct Office copy. Use the matching registration tool and directory. A registration failure usually indicates a path, architecture, dependency, or Office-version problem.
Why does SharePoint say Edit Document requires a compatible application?
The Office SharePoint support feature may be missing, damaged, incorrectly registered, or disabled. On legacy systems, the SharePoint OpenDocuments control may also be disabled in Internet Explorer.
Can Windows Update fix this file?
Windows Update may update Windows components, but it is not the normal source for an Office-installed owssupp.dll. Repair or reinstall the relevant Office product.
Free tools Windows power users keep installed
One-click scans. No signup required.
Is Office 2003 still supported?
No. Microsoft Office 2003 support ended on April 9, 2014. Even after repairing its files, the client may not work correctly with modern SharePoint services or current browser and authentication requirements.
What if Office repair does not restore the file?
Check that the Office edition includes SharePoint support, remove conflicting Office versions if appropriate, and reinstall from the original trusted source. If the problem began after an uninstall or update, System Restore is a secondary recovery option.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
