How to Install McAfee With Error 1920

Written by jason artman
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Install McAfee With Error 1920
(Comstock Images/Comstock/Getty Images)

While installing McAfee VirusScan Enterprise 8.7i, you may encounter the error "Error 1920, service McShield failed to start." This issue occurs because of an error in the registry that refers Windows to the incorrect location for the McAfee background service. McAfee has corrected this issue with later versions of VirusScan Enterprise. Until you are able to update the software, you can resolve this error by modifying the Windows registry to display the correct location of the McAfee background service.

Skill level:
Moderately Easy


  1. 1

    Click the "Start" button then type "regedit" in the search box at the bottom of the "Start" menu if you are using Windows 7 or Windows Vista. Press "Enter." In Windows XP, click "Start" and "Run," then type "regedit" in the dialogue box.

  2. 2

    Navigate to the "HKEY_LOCAL_MACHINE," "SYSTEM," "CurrentControlSet," "Services" and "mfeapfk" folders on the left side of the window. Click the "mfeapfk" folder.

  3. 3

    Double-click "ImagePath" on the right side of the window.

  4. 4

    Change the information in the "Value Data" box from "system32\drivers\mfeapfk.sys" to "c:\windows\system32\drivers\mfeapfk.sys" and click "OK."

  5. 5

    Close the registry editor and restart the computer. McAfee VirusScan Enterprise should now function normally.

Tips and warnings

  • After successfully installing McAfee VirusScan Enterprise, allow the software to run through the update process completely. Alternatively, proceed to the McAfee software download page and enter the license number for your McAfee product to see all of the available downloads.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.