Summary of Solutions to failed McAfee initialization of common updater Subsystem

Comments: I found this error when I configured mcafee on the U.S. server today. I have configured dozens of machines. The first time I saw this problem, I sorted it out.An error occurred while Updating McAfee. A message indicating "failed to initialize Common Updater subsystem" is displayed.
As a loyal wheat flour, I have been using McAfee antivirus software for many years. However, in the last week, McAfee failed to update. Both automatic and manual updates failed. The pop-up error message is "failed to initialize the Common Updater subsystem. make sure that the McAfee Framework service is running. the error ffffffdf @ 3 "is returned for the McAfee Framework service ".
I first searched on Google for the solution keyword "McAfee failed to initialize the Common Updater subsystem" and found a lot of results, but mostly for how to reinstall McAfee, the rest are also invalid answers, especially the Q & A pages that Baidu knows, and their content is simply incredible. The query keyword is changed to "mcafee common updater ffffffdf". Only English results are displayed. The first query result is the official McAfee knowledge base, where the solution to the problem is found at one time, and the Chinese people have to lament that they have answered scientific questions carelessly.

The solution is as follows:
Re-Register the OLE32.DLL to Re-Populate the Registry
To re-register the OLE32.DLL:
Click Start, Run, type CMD and press ENTER.
From the command prompt, type: Regsvr32.exe % Windir % \ System32 \ Ole32.dll and press ENTER.
The following RegSvr32 popup message is displayed:
DllRegisterServer in C: \ WINNT \ System32 \ ole32.dll succeeded
Click OK.
You only need to register ole32.dll again. I tried it again in steps and it immediately took effect.

Method 2:
Run regedit to enter the registry and delete the following:

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ McAfee Framework

HKEY_LOCAL_MACHINE \ SOFTWARE \ Network Associates \ TVD

HKEY_LOCAL_MACHINE \ SOFTWARE \ Network Associates \ ePolicy orchestrator

The preceding three directories must be deleted, restarted, and deleted.

C: \ Program Files \ Network Associates \ Common Framework

C: \ Documents ents and Settings \ All Users \ Application Data \ Network Associates

If you do not have the all Users directory or the all users directory does not have the Network Associates directory, you can use the search function to delete the Network Associates directory!

Uninstall and solve the problem after reinstallation.

-------------------------------------------------------------------------------

Other methods:

Some users may encounter an update failure when using McAfee in the Windows XP SP2 test version. To solve this problem, you need to make the following settings:

1. "Run"> mongodcomcnfg.exe"

2. Double-click "component service> Computer> my computer"

3. Expand "DCOM configuration" and open the properties of the "FrameworkService" item.

4. Select the "Security" tab in "FrameworkService properties ".

5. Select "Custom" under "launch and activation permissions" and click "edit.

6. In the pop-up "launch permission" dialog box, "add" your windows Logon account and SYSTEM user accounts, and grant "Local activation" permissions respectively.

7. OK. The problem is fixed. Now McAfee can be updated normally ~

--------------------------------------------------------------------------------

Another method

1. Run: dcomcnfg.exe (enter dcomconfig in start-Run and execute)

2. Component Services-Computers-My COmputer-DCOM config

3. Find FrameworkService, select the Security tab in Properties, and set Launch and Activation Permissions to "User Default ".

If you do not install the macloud firewall, there should be a total of seven processes:

Updaterui.exe+shstat.exe%tbmon.exe %vstskmgr.exe %mcshield.exe %frameworkservice.exe %naprdmgr.exe

UpdaterUI.exe: automatic upgrade (once a week for coffee .)

Shstat.exe: The same icon as the shield in your system bar. The startup item is in the Registry. (after the system is restarted, the icon appears in the system taskbar. However, even if there is no icon, VirusScan Enterprise is still running and your computer is still protected .)

You can check the following registry keys for confirmation:

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Run ShStatEXE = "C: \ Program Files \ Network Associates \ VirusScan \ SHSTAT. EXE"/STANDALONE

Tbmon.exe: Error Reporting Program

Vstskmgr.exe (Network Associates Task Manager): this is a system service.

Mcshield.exe: the Core of coffee, system service!

Frameworkservice.exe (McAfee Framework Service, the shared component Framework of McAfee products): the background Framework process of coffee, which is a service. In other words, the test will not affect normal use, but the upgrade will be affected. This process is different from vstskmgr.exe and cannot start the service automatically. If you change it to manual, you have to start the service by yourself to run the Upgrade Program.

NaPrdMgr.exe: This process is based on the previous steps. The progress is a combination of frameworkservice.exe. if frameworkservice.exe is stopped, it will never appear in the task manager.

Open your coffee below (right-click the system tray coffee icon and select virusscan console)

After the McAfeeFramework fails to be started

If McAfee fails to update the virus database and an error is reported during installation:

Error 1920/1923: "service McAfeeFramework startup failed. Make sure you have sufficient permissions to start the system service. "and" initialization of the general update program subsystem failed. Make sure that the McAfee Framework Service is running. McAfee Common Framework returns an error such as fffff95b @ 2/fffFFBC @ 3.

A thorough solution can be adopted (basically solving various faults in MCAFEE)

The details are as follows:

Step 1: uninstall the McAfee product. You can directly Delete the product from the Add/delete program, or run the following command to uninstall the product:

McAfee8.0 uninstall:

Msiexec/x {7B256F27-273D-4358-8DBE-8C910EAF8857} REMOVE = all reboot = R/q

Step 2: uninstall the agent: (skip this step if mcafee epo is not used)

McAfee Common Management Agent uninstall:

"X:/Program Files/Network Associates/Common Framework/FrmInst.exe"/Remove = Agent

Step 3: Clear related registries

Delete the McAfee Common Management Agent service (delete the McAfeeFramework key value ):

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/McAfeeFramework

McAfee VirusScan Service (delete McShield and McTaskManager key values ):

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/McShield

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/McTaskManager

The following key values in the Registry are directly deleted:

HKEY_LOCAL_MACHINE/SOFTWARE/Network Associates

HKEY_CURRENT_USER/Software/Network Associates

RUN key value (delete ShStatEXE and McAfeeUpdaterUI key values ):

HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Run/ShStatEXE

HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Run/McAfeeUpdaterUI

Step 4: restart the computer;

Step 5: Delete the McAfee directory (delete the related Network Associates directory ):

X:/Documents and Settings/All Users/Application Data/Network Associates

X:/Program Files/Network Associates

Step 6: reinstall MCAFEE, install the latest Sdatxxxx, and update it online immediately.
Third statement:
Speaking of nonsense, the initialization of the Common updater subsystem fails during mcafee upgrade, and the reinstallation and repair problems still exist and cannot be solved. See the figure below:


There are two solutions: copy the FrameworkManifest. xml file to overwrite, and delete FrameworkManifest. xml and reinstall the Common Management Agent (CMA)

8.5.0. I FrameworkManifest. xml file download:
/201103/other/mcafee_fix.rar
Official bug description:

Revoke ate KnowledgeBase
ERROR: McAfee Common Framework returned error fffff95b @ 2 (issue: FrameworkManifest. xml writable upt)

Revoke ate KnowledgeBase ID: KB54520
Published: August 08,200 8

Environment
McAfee Common Management Agent 3.60
McAfee Common Management Agent 3.5x
McAfee VirusScan Enterprise 8.5i
McAfee VirusScan Enterprise 8.0i
Problem 1
The following errors occur after initiating an AutoUpdate:
McAfee Common Framework returned error fffff95b @ 2. (FrameworkManifest. xml extends upt)

Failed to initialize common updater subsystem

Make sure the McAfee Framework Services is running
Problem 2

Subsequent errors when trying to start the McAfee Framework Service:
Cocould not start the McAfee Framework Service on Local Computer

The system cannot find the file specified
Problem 3

Any of the following update methods will result in the AutoUpdate error:
Right-clicking the McShield icon in the system tray and selecting Update Now
Right-clicking the AutoUpdate in the VirusScan Console and clicking Start
Creating a new scheduled task
Editing the properties of the existing AutoUpdate task
Cause
FrameworkManifest. xml has become extends upted.
Solution 1
McAfee Agent 4.0

Changes in the design of the McAfee Agent 4.0 will prevent the specified uption of the FrameworkManifest. xml file.
To download the McAfee Agent from the www.mcafee.com website, see KB54808.

Solution 2

Common Management Agent

Solution 1-Obtain FrameworkManifest. xml from another computer:
Locate another VirusScan Enterprise (VSE) computer where the updates are working without error.
Copy the FrameworkManifest. xml from the following path:

For VSE 8.5i (running on Windows Vista)
X: \ Program Data \ McAfee \ Common Framework

For VSE 8.5i (running on Windows XP and earlier)
X: \ Documents ents and Settings \ All Users \ Application Data \ McAfee \ Common Framework

For VSE 8.0i (running on Windows XP and earlier)
X: \ Documents ents and Settings \ All Users \ Application Data \ Network Associates \ Common Framework


Paste the file to portable media or network share that can be accessed by both computers.
Click Start, Run, type services. msc, and click OK.
Right-click McAfee Framework Service and select Stop.
Copy FrameworkManifest. xml to the Common Framework directory.
Right-click McAfee Framework Service and select Start.
Update the product.

Solution 2-Delete FrameworkManifest. xml and reinstall the Common Management Agent (CMA)
It is necessary to delete FrameworkManifest. xml because it may not be removed or replaced when an uninstall/re-install is undertaken.

Step 1-Allow VSE files and settings to be modified (VirusScan Enterprise 8.5i and higher only)

Click Start, Programs, McAfee, VirusScan Console.
Right-click Access Protection, then select Properties.
Select Common Standard Protection.
Select Prevent modification of McAfee files and settings and disable this option.
Click OK.

Step 2-Delete FrameworkManifest. xml and reinstall CMA:
Delete FrameworkManifest. xml from the following path:

For VSE 8.5i (running on Windows Vista)
X: \ Program Data \ McAfee \ Common Framework

For VSE 8.5i (running on Windows XP and earlier)
X: \ Documents ents and Settings \ All Users \ Application Data \ McAfee \ Common Framework

For VSE 8.0i (running on Windows XP and earlier)
X: \ Documents ents and Settings \ All Users \ Application Data \ Network Associates \ Common Framework


Restart your computer.
Re-install the Common Management Agent (CMA)/ePO agent.


NOTE: CMA is available for download from the McAfee Downloads site. See KB54808.
Previous Document ID
5432392


Rate this Page
Please take a moment to complete this form to help us better serve you.


The official solution is as follows:
Https://kc.mcafee.com/corporate/index? Page = content & id = KB54520