Security Group Policy Is Applied During Every Startup Process

This article was previously published under Q329178
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
The Security Group Policy is applied during every startup process if the following group policies are set:
  • The "Apply Group Policy for computers asynchronously during startup" policy is turned on.
  • The "Do not apply during periodic background processing" policy is turned on for "Security policy processing."
RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version        Size       File name   --------------------------------------------------------------   25-Nov-2002  17:00  5.0.2195.5265     42,256  Basesrv.dll         25-Nov-2002  17:00  5.0.2195.5907    222,992  Gdi32.dll   25-Nov-2002  17:00  5.0.2195.6137    709,392  Kernel32.dll        25-Nov-2002  17:00  5.0.2195.6090    332,560  Msgina.dll          25-Nov-2002  17:00  5.0.2195.6097    379,664  User32.dll   25-Nov-2002  17:00  5.0.2195.6140    370,960  Userenv.dll   23-Nov-2002  01:53  5.0.2195.6139  1,643,344  Win32k.sys   29-Oct-2002  18:59  5.0.2195.6108    179,472  Winlogon.exe   25-Nov-2002  17:00  5.0.2195.6097    243,472  Winsrv.dll       

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
MORE INFORMATION
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
Właściwości

Identyfikator artykułu: 329178 — ostatni przegląd: 02/27/2014 21:15:10 — zmiana: 3.6

Microsoft Windows 2000 Professional SP1, Microsoft Windows 2000 Professional SP2, Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Server SP1, Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Service Pack 3, Microsoft Windows 2000 Advanced Server SP1, Microsoft Windows 2000 Advanced Server SP2, Microsoft Windows 2000 Advanced Server SP3

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbqfe kbbug kbfix kbwin2000presp4fix KB329178
Opinia
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)