Resolving WinCC Component Object Manager Missing Error

Problem Overview

When opening an integrated SIMATIC Manager project that contains a WinCC (SCADA) sub-project, users encounter the diagnostic message "Missing software package: WinCC (Component Object Manager)" when WinCC Explorer or the integrated tag/message transfer functions are invoked. The dialog typically blocks the launch of WinCC Explorer from the SIMATIC Manager tree, and prevents AS-OS Engineering (the tag and message transfer mechanism) from running.

The most common cause is that the WinCC installation did not include the "Component Object Manager" option — one of the optional sub-packages in the WinCC setup tree. This option is not installed by default during a typical install, and is also not part of WinCC flexible 2007 / WinCC flexible 2008 (the predecessor HMI configuration suite) or TIA Portal's WinCC products.

Reference: Siemens Support Entry 109815085 — "Why does the message 'Missing software package > WinCC (Component Object Manager)' appear when opening a WinCC V7 project?"

WinCC vs. WinCC flexible — Product Boundary

A frequent source of confusion is the assumption that WinCC and WinCC flexible are interchangeable. They are distinct product lines with different project structures, different component object models, and different SIMATIC Manager integration paths.

Because the Component Object Manager is part of the WinCC V7 product line and is not bundled with WinCC flexible, the error typically appears when:

1. A vendor's S7 project contains a WinCC V7 sub-project and is opened on a PC that only has WinCC flexible installed.
2. WinCC V7 was installed but the "Component Object Manager" sub-component was deselected during setup.
3. WinCC was installed, but the installation was performed after SIMATIC Manager and the COM registration step was skipped or failed.

Root Cause Analysis

The Component Object Manager is a Windows COM (Component Object Model) server that registers WinCC project objects (graphics, tags, archives, alarms) so that external applications — primarily the SIMATIC Manager — can launch WinCC Explorer and read/write the integrated project tree. The diagnostic message is generated when SIMATIC Manager attempts to instantiate the WinCC COM class and the registry entry is absent or unregistered.

Three underlying root causes cover virtually every case observed in the field:

Required WinCC Components for SIMATIC Manager Integration

To open, edit, and synchronize an integrated WinCC V7 project from SIMATIC Manager, three optional WinCC setup components must be installed and registered:

All three options are sub-branches of the main WinCC setup tree and can be enabled or disabled independently. The default installation typically leaves them unchecked.

Solution Path 1 — Add Missing Components to an Existing WinCC Installation

This is the corrective path for the most common case: WinCC is installed but the Component Object Manager option was skipped.

Prerequisites

• Local administrator rights on the engineering station.
• Original WinCC V7 installation media (DVD or mounted ISO) matching the installed version (e.g. WinCC V7.4 SP1, V7.5, V7.5 SP1, V7.5 SP2). Mixed SP levels are not supported.
• STEP 7 V5.5 / V5.6 (for the SIMATIC Manager integration pathway; TIA Portal uses a different integration mechanism).

Step-by-Step

1. Close SIMATIC Manager, WinCC Explorer, and any instance of the WinCC Configuration Studio.
2. Open Windows Control Panel → Programs and Features (or Settings → Apps → Installed apps on Windows 10/11).
3. Locate SIMATIC WinCC (or SIMATIC WinCC V7.x) in the program list and select Change → Modify.
4. In the WinCC setup dialog, expand the component tree to WinCC → Options.
5. Check the following boxes:
   • Component Object Manager — mandatory.
   • AS-OS Engineering — required for tag and message transfer.
   • S7 Symbol Server — required for S7 tag browsing.
6. Click Next → Install. Setup copies the COM DLLs (e.g. WCCOleDb.dll, WCCRT.dll, CCTOM.dll) and registers them via regsvr32 automatically.
7. Reboot the engineering station to clear locked COM registrations and refresh the SIMATIC Manager cache.
8. Re-open the S7 project in SIMATIC Manager. The "Missing software package" message should no longer appear, and the WinCC sub-project should launch WinCC Explorer when double-clicked.

Solution Path 2 — Install WinCC V7 (Not WinCC flexible)

Applies when the engineering station only has WinCC flexible 2007 / 2008 installed. WinCC flexible cannot satisfy the Component Object Manager requirement for WinCC V7 projects.

Licensing

WinCC V7 is licensed separately from WinCC flexible. The relevant license keys are:

Step-by-Step

1. Verify the WinCC V7 license is available on the license server or USB dongle.
2. Insert the WinCC V7 installation DVD (or mount the ISO).
3. Run Setup.exe from the DVD root with administrator rights.
4. Accept the license agreement and enter the product key when prompted.
5. In the Installation Type dialog, select "Custom Installation" (or "User-defined") to expose all optional components.
6. Check the boxes for: WinCC V7 Explorer, Component Object Manager, AS-OS Engineering, S7 Symbol Server, and any language packs required (e.g. English, German).
7. Complete the setup and reboot.
8. From the Windows Start menu, run SIMATIC WinCC → Component Object Manager Registration (if listed) or open a command prompt and run:
   cd C:\Program Files\Siemens\Automation\WinCC\bin
regsvr32 CCComObjManager.dll
9. Verify the registration succeeded ("DllRegisterServer in CCComObjManager.dll succeeded").

Solution Path 3 — Repair COM Registration Without Reinstall

For installations where the files are present but the COM registration has been corrupted (common after Windows updates, antivirus scans, or partial uninstalls):

1. Open Command Prompt (Run as Administrator).
2. Navigate to the WinCC binary directory:
   cd "C:\Program Files\Siemens\Automation\WinCC\bin"
3. Re-register the core COM libraries:
   regsvr32 /u CCComObjManager.dll (unregister first)
   regsvr32 CCComObjManager.dll (re-register)
4. Repeat for adjacent COM modules that SIMATIC Manager calls when launching WinCC Explorer:
   regsvr32 WCCOleDb.dll
regsvr32 WCCRT.dll
regsvr32 CCTOM.dll
5. Confirm that the following registry hive is populated (regedit → HKEY_CLASSES_ROOT\CLSID):
   {A5B020AF-0C46-11D1-AB02-00C04FB6CFA3} — WinCC Project Manager
   {3D2BB45C-6CBB-11D2-8B05-006008A0AF0E} — WinCC Graphics Designer
   (Actual CLSIDs vary by WinCC version; cross-check with a working engineering station.)
6. Reboot and re-open the S7 project in SIMATIC Manager.

Version-Specific Considerations

If the vendor's project was created on a different WinCC SP level, install a matching SP (or the highest SP that is downward-compatible) to avoid additional incompatibility messages such as "WinCC version does not match project version."

Verification

After applying any of the three solution paths, verify the fix with the following checklist:

1. SIMATIC Manager launch test: Open the integrated S7 project. The WinCC sub-project icon in the project tree should be active (not greyed out) and double-clicking it should launch WinCC Explorer without the "Missing software package" dialog.
2. COM registration check: Open regedit and confirm that HKEY_CLASSES_ROOT\CLSID contains entries for the WinCC COM classes (CLSIDs as listed above). On a 64-bit OS, check both HKEY_CLASSES_ROOT\Wow6432Node\CLSID and HKEY_CLASSES_ROOT\CLSID if the COM server is 32-bit.
3. AS-OS Engineering test: In HW Config, right-click the CPU and select "Compile OS". The transfer dialog should appear and the project should compile without COM errors.
4. S7 Symbol Server test: In WinCC Explorer, open Tag Management → Add → S7 tags → Browse. The S7 Symbol Server should return the CPU's symbol table.
5. Event log check: Open eventvwr.msc and review Application and System logs for COM-related errors (Event ID 10016, DCOM permission errors are common secondary symptoms).

Troubleshooting Matrix

Working with the SCADA Sub-Project Without the Component Object Manager

If the engineering station is used purely for PLC programming and the SCADA portion of the integrated project is owned by another team or vendor, the Component Object Manager is not strictly required to continue work. In that scenario:

• Open the .s7p file in SIMATIC Manager.
• Expand the project tree but do not double-click the WinCC sub-project.
• Edit S7 programs, hardware configuration, and netpro topologies as normal.
• If a vendor re-issues the project with WinCC changes, request a fresh .zip archive of the complete S7 project, including the WinCC_proj subfolder. Re-import the archive and open it on a PC that has the full WinCC V7 + Component Object Manager installation.

Best Practices

• Always perform a custom installation of WinCC V7 on engineering stations that will open vendor or third-party S7 projects, and enable Component Object Manager, AS-OS Engineering, and S7 Symbol Server at install time.
• Maintain a version matrix on every engineering PC: WinCC version, SP level, STEP 7 version, and license key fingerprint. This speeds diagnosis when a vendor's project triggers a compatibility error.
• Keep a baseline disk image of a known-good engineering station. If COM registration becomes corrupted, restore the image rather than chasing registry-level repairs.
• Configure Windows Defender / third-party AV to exclude the WinCC binary directory (C:\Program Files\Siemens\Automation\WinCC) and the STEP 7 directory to prevent heuristic quarantine of .dll and .ocx files.
• After any major Windows feature update, run the WinCC setup in Repair mode to re-verify COM registrations before resuming work.
• Document the CLSID list from a known-good station in a shared engineering KB. When a broken PC is encountered, the CLSID list provides a quick way to spot missing entries in regedit.

Related Siemens Documentation

• Siemens Support Entry 109815085 — "Missing software package: WinCC (Component Object Manager)"
• WinCC V7.5 Installation / Configuration Manual (on the product DVD under \Manuals and on the Siemens Support portal under entry 109769074 for the relevant SP level)
• STEP 7 V5.6 AS-OS Engineering Manual (on the STEP 7 V5.6 DVD and Siemens Support portal)
• SIMATIC WinCC V7.5 SP2 Release Notes / Readme (on the product DVD; check for known installation issues with the Component Object Manager on Windows 10/11 LTSC builds)
• Automation License Manager manual (for license key management when adding WinCC V7 to an existing WinCC flexible station)