Monday, January 28, 2013

How To: Fix IPSEC Service does not start under Windows Server 2003


  • Windows Server 2003
  • Cannot connect to network
  • Ping-ed gateway and destination is not reachable
  • IPSEC Service is not started
  • "The system cannot find the file specified" when trying to start IPSEC Service
  • Other symptoms are found in Microsoft Article KB912023


You may attempt to follow the resolution found in Microsoft Article KB912023, but do consider the following before performing them.
  1. Ensure that the server harddisk is in working condition. You may check this thru the storage controller (RAID controller) utility. The usual errors to look out for are faulty harddisk or controller batteries that needs to be replaced.

  2. Ensure that your file system is intact by running a chkdsk. This is ensure that your file system does not contain errors.

    chkdsk {system drive} /f /r

  3. Ensure that your operating system files are checked for consistency (Be prepared to insert Windows Server 2003 CD). This is important if item 1 and 2 above contains errors on the server.

    sfc /scannow

  4. Delete local policy registry subkey (if present)


  5. Rebuild local policy store by running the command

    regsvr32 polstore.dll

  6. Attempt to start service and test network connectivity.

 For exact details on step 4 and 5, please refer to Microsoft Article mentioned.


  1. It helped (point 5). Thank You.

  2. nice post, it's working..........

  3. Same here..Rebuilt local policy..regsvr32 polstore.dll

  4. Worked for me, too but interestingly I didn't have the regedit entries, before or after I registered the DLL. Server 2003

  5. guys just take this file and replace it!i did it and my ipsec service starded to work!

  6. Point 5 works, But we are having this issue on more than 50+ servers, what is the permanent fix and its keep happening for more servers, how to prevent it? your valuable suggestion is really appreciated.