Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Error in installing Live One Care RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I get an error message when I try to install Live One care.  The message reads "The procedure entry point GetprocessID could not be located in the dynamic link library KERNEL32.dll"  My computer crashed and I had to reformat my hard drive and I installed Windows XP Professional.  The previous version had been Windows XP Home.  I saw in some help sections that is the problem.  I also have no sound because according to the help sections, that is due to the fact that the sound cards are with the old version which has been deleted. . . .so my problem is I need HELP and I need it badly. . .anyone have any solutions to these problems?

     

    Tuesday, September 23, 2008 3:34 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The OneCare installer has called kernel32.dll and passed a process handle to it, asking it to return the process ID. When kernel32.dll is unable to find the required GetProcessId ( ) function in its function library, it responds to the call by returning this error message. Since the GetProcessId ( ) function was not included in versions of kernel32.dll that shipped prior to Windows XP SP1, attempting to install OneCare on an older operating system would be the most common cause of this error message.

    If you are using Windows XP and receive this error, then you should first update to service pack 2 (or 3) and verify that all critical updates, and any optional updates for .Net Framework 1.1 and 2.0, are installed, since these updates have been reported to solve this issue.

    If the operating system on your computer is a supported version of Windows, and updating fails to resolve the issue, then replacing the kernel32.dll file with the identical version would be advisable, because this will eliminate the possibility that the error message is being caused by a corrupted kernel32.dll file. The System File Checker is supposed to fix problems like this if you enter “sfc /scannow” at the command prompt, but I’m not sure how effective it is. Any other potential sources of this error message on a supported operating system would probably be difficult to identify, and would require the assistance of OneCare Support: http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2

    GreginMich

     

    Tuesday, September 23, 2008 6:27 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Your Operating system does not meet the system requirements for OneCare. Most probably your Windows is not updated to Service Pack 2.

     

    For details of onecare requirements please visit this link.

    http://onecare.live.com/standard/en-us/purchase/sysreq.htm

     

    If you are interested in installing Service Pack 2 on your computer. Click on the link, Save it first before running.

     

    http://download.microsoft.com/download/1/6/5/165b076b-aaa9-443d-84f0-73cf11fdcdf8/WindowsXP-KB835935-SP2-ENU.exe

     

     

    In regards with the sound of your computer, you should contact your sound card manufacturer or your computer manufacturer for the device driver.

     

     

    Tuesday, September 23, 2008 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    hi i have the same problem

    except im running on Vista home premium

    version 6.0 (build 6001: service pack 1)

     

    i just recently bought the Windows Live One Care

    it says for Windows vista but i cannot find anything to help me.

     

     

    Tuesday, September 23, 2008 6:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The OneCare installer has called kernel32.dll and passed a process handle to it, asking it to return the process ID. When kernel32.dll is unable to find the required GetProcessId ( ) function in its function library, it responds to the call by returning this error message. Since the GetProcessId ( ) function was not included in versions of kernel32.dll that shipped prior to Windows XP SP1, attempting to install OneCare on an older operating system would be the most common cause of this error message.

    If you are using Windows XP and receive this error, then you should first update to service pack 2 (or 3) and verify that all critical updates, and any optional updates for .Net Framework 1.1 and 2.0, are installed, since these updates have been reported to solve this issue.

    If the operating system on your computer is a supported version of Windows, and updating fails to resolve the issue, then replacing the kernel32.dll file with the identical version would be advisable, because this will eliminate the possibility that the error message is being caused by a corrupted kernel32.dll file. The System File Checker is supposed to fix problems like this if you enter “sfc /scannow” at the command prompt, but I’m not sure how effective it is. Any other potential sources of this error message on a supported operating system would probably be difficult to identify, and would require the assistance of OneCare Support: http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=2421771&SiteID=2

    GreginMich

     

    Tuesday, September 23, 2008 6:27 PM