The exact pkmforms.dll errors
Windows may display one of these messages:
pkmforms.dll is missingpkmforms.dll was not foundCannot find pkmforms.dllError loading pkmforms.dllThe specified module could not be foundThis application failed to start because pkmforms.dll was not found. Re-installing the application may fix this problem.
The 60-second answer
pkmforms.dll is an old Microsoft application DLL associated with SharePoint Portal Server and Office-era Web Folders components. It is not a normal Windows 10 or Windows 11 system file, and it is not a Visual C++, DirectX, or .NET runtime component.
The safest fix is to identify which old Microsoft product originally installed it, then repair or reinstall that product. The likely parent is Visio 2002, an Office 2000/XP component, Publisher, or SharePoint Portal Server. Do not download a random copy and place it in C:WindowsSystem32 or C:WindowsSysWOW64.
If the error began after removing Office, Visio, SharePoint, or an old Web Folders feature, the remaining application or an installer repair entry is probably still looking for the file.
What pkmforms.dll is
The file is identified as Microsoft SharePoint Portal Server, with the internal product association SharePointPortalServer and Microsoft Corporation as its publisher.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Microsoft’s archived Visio 2002 Service Pack 2 documentation lists Pkmforms.dll among the files updated by that service pack. That connects the file directly with Visio 2002 and shared Office-era components. Historical file listings also place it beside related files such as pkmcore.dll, pkmcdo.dll, pkmres.dll, and pkmws.dll.
This is a legacy component, not a current Windows dependency. Modern SharePoint Server is a separate product with different binaries. SharePoint Online does not use this local DLL. SharePoint Portal Server 2003 reached the end of extended support on April 9, 2014, as recorded on Microsoft’s product lifecycle page.
Is it a Windows system file?
No. There is no good reason to treat pkmforms.dll as a protected Windows component.
Historical installations commonly placed it here:
C:Program FilesCommon FilesMicrosoft SharedWeb Folders
That path comes from old installation records rather than a current Microsoft installation guide, so treat it as a strong historical indication, not an absolute rule. A particular Office, Visio, or SharePoint installation may have used a different program or administrative installation path.
Free tools Windows power users keep installed
One-click scans. No signup required.
Historical metadata also describes the file as a Win32 component, but old versions and file sizes should not be treated as universal specifications. The repair installer is the authority for the copy that belongs to your product.
Which programs usually installed it?
Start with these possibilities:
- Microsoft Visio 2002, especially when the error appears while Visio starts or repairs itself.
- Microsoft Office 2000 or Office XP shared components.
- Microsoft Publisher or another Office application using the old Web Folders integration.
- SharePoint Portal Server, if the computer was used with that legacy server product.
- A leftover installer or startup entry from one of those products.
A program that merely reports the error is not always the program that originally installed the DLL. For example, a damaged Office installation can trigger Windows Installer while you are opening Publisher, Visio, or another Office application.
If a modern application or game reports this file, do not assume it genuinely requires a Windows-wide copy. First identify the old Microsoft component that came with the application or was installed alongside it.
Before repairing: identify the parent product
Check installed applications
- Press
Windowsand type Control Panel. - Open Control Panel.
- Select Programs → Programs and Features.
- Look for entries containing:
- Microsoft Office
- Microsoft Visio
- Microsoft Publisher
- SharePoint
- Web Folders
- Note which product is still installed.
- Check whether the error occurs when starting that product.
On older Windows installations, the same list may be under Control Panel → Add or Remove Programs.
Recommended Free Tools
Check the error timing
The timing usually narrows the cause:
- During Office or Visio startup: the installation is damaged, incomplete, or missing a shared component.
- During repair or setup: Windows Installer cannot write or locate the file.
- Immediately after uninstalling software: an orphaned shortcut, startup entry, or repair request remains.
- After antivirus detection: the file may have been quarantined or deleted.
- Only when opening an old document: the document or its associated application may be invoking the legacy component.
Do not begin by copying a DLL. Establish which product owns the dependency first.
Fix 1: repair Office, Visio, or SharePoint
This is the most likely and most reliable solution.
On Windows 10 or Windows 11
- Press
Windows + R. - Type:
text
appwiz.cpl
- Press
Enter. - Select the relevant Microsoft Office, Visio, Publisher, or SharePoint entry.
- Select Change, Modify, or Repair.
- Choose Repair or Reinstall, depending on the installer.
- Follow the prompts.
- Provide the original CD, network installation source, or administrative installation point if requested.
- Restart Windows.
- Open the application that produced the error.
For Office XP or Office 2000, the historical path was:
Add or Remove Programs → Microsoft Office → Change → Repair Office
Outdated 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 matchWindows 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 reinstallThe exact wording varies with the edition and Windows version.
How to tell whether repair worked
Repair succeeded if:
- The application starts without the missing-file message.
- Windows Installer no longer repeatedly requests the installation source.
- The historical Web Folders directory contains the expected Microsoft files.
- The error does not return after a restart.
If repair fails because the installer cannot find source files, do not substitute a downloaded DLL. Locate the original licensed installation media or the organization’s administrative installation source.
If the product is no longer needed
If Visio, Office, or SharePoint is obsolete and you do not use it:
- Open Programs and Features.
- Select the remaining related product.
- Choose Uninstall.
- Restart Windows.
- Check whether the error has disappeared.
This is preferable to restoring an obsolete DLL just to satisfy a leftover startup entry.
If the message continues after uninstalling, inspect Task Manager → Startup apps for an old Office, Visio, or SharePoint entry. Also check Task Scheduler for a task belonging to software that has already been removed. Disable or remove only entries you can positively identify.
Rank #2
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
Fix 2: check antivirus quarantine
Security software may have removed the file, especially if the installation was already damaged or the file was in an unexpected location.
- Open Windows Security.
- Select Virus & threat protection.
- Choose Protection history.
- Look for an event involving
pkmforms.dll. - Record the original path and detection details.
- Do not restore the file immediately.
- Repair the Office, Visio, or SharePoint installation first.
Restore a quarantined copy only when all of these are true:
- It came from the original Microsoft installation.
- Its path matches the expected parent product.
- The security event is understood.
- The file’s signature and properties are consistent with the installation.
If antivirus repeatedly removes the file after repair, update Windows Security, run a full scan, and contact the security vendor if the detection appears incorrect. A random replacement from a DLL download site is not an authenticated Microsoft file.
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 →Fix 3: verify an existing file
If pkmforms.dll is already present, the error may name a missing dependency rather than the DLL itself.
- Open File Explorer.
- Browse to the product’s installation directory.
- Check the historical location:
text
C:Program FilesCommon FilesMicrosoft SharedWeb Folders
- Right-click
pkmforms.dll. - Select Properties.
- Check the Digital Signatures tab if present.
- Check the Details tab for publisher and product information.
- Confirm that the file belongs to the Office, Visio, or SharePoint installation.
A “module could not be found” message can mean that Windows found pkmforms.dll but could not load another library that it needs. Reinstalling the parent product is still the correct first response because it restores the complete matching file set.
For advanced verification, an administrator can calculate a hash in PowerShell:
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 errorsGet-FileHash "C:Program FilesCommon FilesMicrosoft SharedWeb Folderspkmforms.dll"
A hash is useful only when compared with a trusted copy from the same original installation source. There is no universal hash that proves every historical release of this file is correct.
Fix 4: repair Windows components with DISM and SFC
SFC and DISM are useful when Windows itself has corrupted protected components. They may not restore pkmforms.dll, because this file appears to be an application or shared Office component rather than a Windows system file.
Run the commands in this order.
Run DISM
- Open Start.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Approve the prompt.
- Run:
cmd
DISM.exe /Online /Cleanup-image /Restorehealth
- Wait for the operation to finish.
Run System File Checker
In the same elevated window, run:
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Test the affected application again.
Microsoft documents this DISM-then-SFC sequence in its System File Checker repair instructions.
If SFC reports that it found no integrity violations, that does not prove that an old Office or Visio DLL is installed. It only means protected Windows files passed the check.
Running the commands repeatedly without identifying the parent product rarely helps. When Windows is healthy but the old application is incomplete, repair the application instead.
If you prefer assistance identifying corrupted Windows components rather than repeatedly comparing command output, Outbyte PC Repair can scan for issues and show what needs attention; its repair actions require the full version, and it is not a substitute for reinstalling the Office or Visio product that owns pkmforms.dll.
Fix 5: do not use regsvr32 unless registration genuinely applies
regsvr32 is for DLLs that expose registration entry points such as DllRegisterServer. Microsoft describes its behavior in the regsvr32 command documentation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →There is no verified evidence that pkmforms.dll is an ActiveX or COM library that needs manual registration. Therefore, this is normally the wrong command:
regsvr32 pkmforms.dll
It will not repair a missing file, restore its dependencies, or fix an incomplete Office installation. It can also produce a second error that sends troubleshooting in the wrong direction.
Use the original Office, Visio, or SharePoint installer instead.
Fix 6: do not copy it to System32 or SysWOW64
Do not place the file manually in:
C:WindowsSystem32
C:WindowsSysWOW64
Those directories are not interchangeable repair locations. Copying a 32-bit application DLL into a Windows directory can create version conflicts, allow the wrong program to load it, and leave the actual parent installation broken.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
A 32-bit application running on 64-bit Windows normally loads its 32-bit dependencies from its application or shared-component directory. The installer should put the file in the location expected by that product.
The same warning applies to copying the DLL into an unrelated application directory. If the application needs it, repair or reinstall the application that installed it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 7: check Windows Features only when the error points there
pkmforms.dll is not a normal optional Windows feature. Turning random features on and off will not normally restore it.
You can still check whether an old organization-managed component was enabled:
- Press
Windows + R. - Type:
text
optionalfeatures
- Press
Enter. - Review the Windows Features list.
- Do not enable an unrelated feature merely because its name contains “SharePoint,” “Web,” or “Framework.”
- Close the window without changes unless your administrator has identified a specific required feature.
Modern SharePoint Server installation and repair guidance does not apply to this old DLL. A current SharePoint Server download is not a replacement for the historical SharePoint Portal Server component.
Fix 8: driver troubleshooting is usually irrelevant
pkmforms.dll is not a graphics, audio, chipset, printer, or other hardware driver file. Device Manager cannot normally repair it.
Use Device Manager only if the application error is accompanied by a separate hardware problem:
- Right-click Start.
- Select Device Manager.
- Expand the relevant hardware category.
- Right-click the affected device.
- Select Update driver.
- Choose Search automatically for drivers, or install a driver from the hardware manufacturer.
- Restart Windows.
Do not install a driver to fix a missing Office or Visio DLL. If a separate driver problem is making version hunting difficult, Outbyte Driver Updater can scan and identify outdated drivers; its driver installation requires the full version, and it does not replace repairing the Microsoft application that originally supplied pkmforms.dll.
What to do when the installation media is unavailable
If repair asks for a CD or network source:
- Identify the exact Office, Visio, Publisher, or SharePoint edition.
- Look for the original licensed CD or organization-provided installation share.
- Check with the administrator who maintained the original installation.
- Confirm that the source matches the installed product and language.
- Run repair again.
- Restart after the repair completes.
Avoid unofficial repackaged installers. They may contain altered files, incompatible versions, or unwanted software. A third-party DLL copy also cannot recreate the registry entries, companion files, installer records, and dependencies that the original product may require.
If the product is unsupported and no licensed source exists, the practical choices are to remove the obsolete product or migrate to a supported application. Reconstructing its shared runtime one DLL at a time is unreliable.
Frequently asked questions
Is pkmforms.dll safe?
A genuine copy associated with a Microsoft Office-era installation can be legitimate. The filename alone does not prove that a file is safe. Check its path, publisher information, digital signature, and relationship to the original installation.
Is pkmforms.dll part of modern SharePoint?
No. It is associated with the historical SharePoint Portal Server and old Office/Web Folders technology. Modern SharePoint Server is a different product, and SharePoint Online does not require this local DLL.
Should I download pkmforms.dll?
No. Random DLL download sites can provide malware, a mismatched version, or the wrong architecture. They also leave the damaged Office or Visio installation unresolved. Use the original Microsoft product installer or licensed installation source.
Should I put it in System32?
No. Repair the parent product and allow its installer to place the file where the application expects it.
Does SFC fix this file?
Usually not. SFC repairs protected Windows components, while pkmforms.dll appears to be an old application/shared component. Run DISM and SFC for general Windows corruption, but repair Office, Visio, or SharePoint for this specific dependency.
Why does a 32-bit application matter?
Historical metadata identifies this as a Win32 component. A 32-bit Office or Visio application on 64-bit Windows needs the matching 32-bit dependency in its application or shared-component location. Copying files between System32 and SysWOW64 is not a valid architecture fix.
Free tools Windows power users keep installed
One-click scans. No signup required.
What if the error appears after uninstalling Office or Visio?
Remove the remaining obsolete product, startup entry, scheduled task, or installer reference. Restoring the DLL may only hide the orphaned configuration.
Final diagnosis
Treat pkmforms.dll as a clue to an old Microsoft installation, not as a standalone Windows repair file.
- Identify the application that originally installed it.
- Check whether antivirus quarantined it.
- Repair or reinstall that Office, Visio, Publisher, or SharePoint component.
- Use the original installation media when requested.
- Run DISM and SFC only as secondary Windows-integrity checks.
- Avoid
regsvr32, System32 copying, SysWOW64 copying, and unofficial DLL downloads.
Once the parent product is repaired, the missing-file error should disappear because the complete, matching component set has been restored.
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.
