Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →pkmcdo.dll is a genuine legacy Microsoft DLL associated with SharePoint Portal Server and its Web Folders integration, not a normal Windows system file. The safest fix is to identify the program requesting it, then repair or reinstall that original SharePoint or Office-era component instead of downloading a replacement DLL.
What this file actually does
Historical file inventories identify pkmcdo.dll as part of the Microsoft SharePoint Portal Server Object Model. SharePoint Portal Server used Web Folders, an Explorer-style WebDAV interface for accessing portal workspaces, as described in Microsoft’s archived SharePoint documentation.
As an Amazon Associate I earn from qualifying purchases.
The file is most strongly associated with Microsoft Office SharePoint Portal Server 2003 and older related Office components. That product is obsolete and reached end of support on April 9, 2014, according to Microsoft’s lifecycle record.
A historical installation path is:
C:Program FilesCommon FilesMicrosoft SharedWeb Folderspkmcdo.dll
pkmcdo.dll is generally identified as a 32-bit library. Do not assume that a copy found in C:WindowsSystem32, C:WindowsSysWOW64, a temporary folder, or an unrelated application directory is legitimate.
Historical inventories report more than one build, so a version, file size, or hash found online should not be treated as universal. The correct file must come from the original licensed installation and match the application’s expected architecture.
Causes by symptom
| What you see | Most likely cause | Best response |
|---|---|---|
An old Office or SharePoint program reports that pkmcdo.dll is missing |
Incomplete installation, repair, or uninstall | Repair or reinstall the original product |
| The error appeared after antivirus activity | The DLL may have been quarantined or deleted | Verify the path and publisher, then repair the parent product |
| The file exists but the program still will not start | Wrong build, wrong architecture, or broken COM registration | Check the caller and repair the original installation |
| The message appears during Windows startup | An abandoned startup, protocol, or registry entry still calls old software | Identify and remove the obsolete reference |
| A BizTalk or legacy CDO application reports a loading or registration error | A CDO COM class may point to the wrong library | Inspect the documented COM registration before using regsvr32 |
| The error appears on a modern PC with no SharePoint software | Leftover software, migration debris, or filename impersonation | Investigate the caller before restoring any file |
| SFC reports no problems | Windows did not find protected system corruption | This is expected for a missing third-party SharePoint DLL |
Fix 1: Identify the program requesting pkmcdo.dll
Do this before copying files or changing the registry.
Check the error dialog
Read the title bar and the text around the missing-file message. The application name may identify the caller directly. Note whether the error appears:
- When launching a specific program
- At Windows sign-in
- When opening a document or Web Folder
- During a scheduled task
- When starting a server service
If the message appears only with one old program, that program is the repair target.
Check installed programs
- Press Windows + R.
- Type
appwiz.cpl. - Press Enter.
- Sort the list by name.
- Look for SharePoint Portal Server, older Microsoft Office components, Web Folders software, BizTalk-related software, or another legacy application installed around the time the problem began.
- Select a likely entry and check whether Change, Repair, or Modify is available.
On Windows 11, you can also open Settings > Apps > Installed apps. Search for SharePoint, Office, or the application named in the error.
Check Event Viewer
- Right-click Start and select Event Viewer.
- Expand Windows Logs.
- Select Application.
- Choose Filter Current Log in the right pane.
- Select Error under event level.
- Search the filtered entries for
pkmcdo.dll. - Open a matching event and record the Faulting application name, application path, and timestamp.
Do not delete registry entries based only on an Event Viewer filename. Use the application path to identify the software first.
Check startup references
If the error appears immediately after sign-in:
- Press Ctrl + Shift + Esc to open Task Manager.
- Select Startup apps.
- Disable only an entry clearly associated with the abandoned application.
- Restart Windows.
- If the error disappears, uninstall the associated software or follow its documented removal procedure.
For a deeper investigation, administrators can use Microsoft Sysinternals Autoruns to locate startup, scheduled-task, service, and protocol references. Disable an entry before deleting anything, and export or record the original configuration.
Rank #2
Fix 2: Repair the original SharePoint or Office component
Repair is the most likely solution when the caller is still needed.
Try the Windows installer repair option
- Press Windows + R.
- Type
appwiz.cpl. - Press Enter.
- Select the SharePoint, Office, or related legacy application.
- Click Change.
- Choose Repair, if offered.
- Provide the original installation media or network installation source if requested.
- Restart Windows.
- Launch the program that produced the error.
If the repair completes and the error is gone, confirm that the restored file is located under the product’s expected installation directory rather than a Windows system directory.
Reinstall from licensed media
If repair is unavailable or fails:
- Back up application data and configuration.
- Record the installed product and service-pack level.
- Uninstall the damaged product from Control Panel > Programs and Features.
- Restart the computer.
- Install the same product from its original licensed media or approved company deployment source.
- Apply the applicable updates for that product.
- Restart again.
- Test the original application.
For SharePoint Portal Server 2003, Microsoft’s lifecycle record lists SP3 as the final listed service pack. This is unsupported legacy software, so use an approved internal installation source and plan a migration or removal rather than placing an exposed old server back into service indefinitely.
Do not mix a DLL from one Office, SharePoint, or Windows installation with another. Different historical builds can have different dependencies, and a 32-bit program needs the original 32-bit package.
Fix 3: Check antivirus quarantine safely
A security product may have removed a genuine old file, or it may have detected a malicious file using the same name.
- Open Windows Security.
- Select Virus & threat protection.
- Click Protection history.
- Look for an event involving
pkmcdo.dll. - Expand the event and record the detected path, action, and threat name.
- Compare the path with the expected SharePoint installation directory and the application that requested it.
- Check the file’s publisher and signature before restoring it.
- If the file is clearly from the original installation, restore it only through the security product’s quarantine controls.
- Run a full scan.
- Repair the parent SharePoint or Office product afterward.
Do not restore a file simply because its name matches. A copy in a temporary directory or system folder requires investigation, not automatic approval.
Fix 4: Verify the file’s path, publisher, signature, and hash
If a copy is already present, verify it before using it.
- Right-click the file and select Properties.
- Check the General tab for its full location.
- Open Digital Signatures, if present.
- Select the signature and click Details.
- Confirm that Windows reports a valid signature and that the signer belongs to Microsoft.
- Check Details for the file description and product information.
- Compare the path with the original product’s installation structure.
For an administrator Command Prompt, calculate a hash with:
Free tools Windows power users keep installed
One-click scans. No signup required.
certutil -hashfile "C:Program FilesCommon FilesMicrosoft SharedWeb Folderspkmcdo.dll" SHA256
The hash is useful when comparing the file with a known-good copy from the same licensed installation source. It is not useful as a universal answer because historical builds differ.
Fix 5: Treat COM registration as a specialized case
A missing-file error and a COM-registration error are different problems.
Microsoft’s archived KB 825886 describes a legacy BizTalk scenario in which Pkmcdo.dll or Cdoex.dll was registered for the CDOMessage class when Cdosys.dll should have been registered. The affected registry location is:
HKEY_CLASSES_ROOTCLSID{CD000001-8B95-11D1-82DB-00C04FB1625D}InprocServer32
Only investigate this path when the affected application is a known BizTalk or legacy CDO installation and the evidence points to an incorrect COM class registration.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBefore changing it:
- Create a system restore point.
- Export the relevant registry key from Registry Editor.
- Record the current
InprocServer32value. - Follow the application vendor’s or Microsoft’s product-specific repair procedure.
- Confirm that the replacement library belongs to the correct application and architecture.
- Restart the affected service or computer.
- Test the application.
regsvr32 is not a general missing-DLL repair command. It may be relevant when a known COM registration is damaged, but registering pkmcdo.dll at random can produce an entry-point error, an architecture error, or a worse COM conflict.
Fix 6: Use DISM and SFC only for broader Windows corruption
Because pkmcdo.dll is not normally a Windows-protected system component, these commands usually will not recreate it. They are appropriate when other Windows files and features are also failing.
Rank #4
- Right-click Start.
- Select Terminal (Admin) or Command Prompt (Admin).
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for the operation to finish.
- Then run:
sfc /scannow
- Restart Windows.
- Test the application again.
Microsoft documents the DISM repair process and System File Checker. If SFC reports no integrity violations, that does not disprove a missing SharePoint file. It generally means Windows found no protected system-file corruption.
Repeating SFC and DISM without identifying the calling program rarely helps. Outbyte PC Repair can show what its free scan finds, while repair is performed by the full version; reinstalling the original SharePoint or Office component remains the definitive fix for this application-specific DLL.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Fix 7: Do not chase drivers or Windows Features
A display, audio, network, or chipset driver does not normally install pkmcdo.dll. Device Manager is therefore not a primary repair route.
If the error began alongside wider hardware or driver failures:
- Right-click Start and open Device Manager.
- Expand the relevant device category.
- Right-click the affected device and select Properties.
- Check the Driver tab for the provider and status.
- Install drivers only from the computer manufacturer or hardware vendor.
- Restart and retest the application.
Do not enable random entries under Windows Features expecting them to recreate this legacy SharePoint DLL. Windows Features can install operating-system components, but they do not normally restore an abandoned third-party SharePoint file.
When many devices show stale or mismatched drivers, Outbyte Driver Updater can scan for what needs attention, while driver installation is performed by the full version; it is not a substitute for reinstalling the program that owns pkmcdo.dll.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchFix 8: Remove the obsolete reference if the program is no longer needed
If no one uses the old SharePoint or Office component, restoring the DLL may preserve a security and maintenance problem.
- Identify the application path from Event Viewer, Task Manager, or the startup entry.
- Back up required documents and configuration.
- Uninstall the obsolete application from Programs and Features.
- Restart the computer.
- Check Startup apps, Task Scheduler, and the related service for leftover entries.
- Remove only entries confirmed to belong to the uninstalled product.
- Recheck Event Viewer after another restart.
Do not delete pkmcdo.dll first. Remove the software or its documented registration so Windows no longer calls a missing component.
Why downloading pkmcdo.dll is unsafe
Random DLL download sites sites can provide malware, the wrong historical build, or a file with the wrong architecture. Copying a 32-bit library into System32 or SysWOW64 can also create new loading and registration problems, and it does not repair the application’s installer, dependencies, or COM configuration.
Use the original licensed SharePoint or Office installation media, an approved organizational deployment source, or the vendor’s official repair process. Windows Update cannot normally obtain an obsolete SharePoint DLL, although it should still be installed when Windows itself needs updates.
Recommended Free Tools
FAQ
Is pkmcdo.dll part of Windows 10 or Windows 11?
No. It is associated with legacy Microsoft SharePoint Portal Server software, not a normal Windows component or modern SharePoint installation.
Is `pkmcdo.dll malware?
The filename is associated with a genuine historical Microsoft component, but the name alone proves nothing. Verify the path, digital signature, parent application, and hash before trusting a copy.
Should I copy it to System32?
No. Use the original product installer and its expected installation directory. The file is generally treated as a 32-bit application DLL.
Will reinstalling Office fix it?
Only if the installed Office-era package originally supplied or integrated with the file. Identify the caller first, then repair that specific product.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why does regsvr32 say the entry point is missing?
The command may be inappropriate, or the DLL may not be a self-registering COM library for that use. Stop and restore the original registration procedure rather than trying different regsvr32 locations.
What if the error appears on a new PC with no SharePoint software?
Look for an abandoned startup task, migrated registry entry, old application, or suspicious file. Identify the caller and remove the obsolete reference instead of downloading the DLL.
Can System Restore fix this?
It may help if the error began immediately after a known recent change and a suitable restore point exists. It is not a replacement for reinstalling unsupported SharePoint software.
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.
