• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1565
  • Last Modified:

Gpedit.msc pop up errors after Service Pack 2...

I receive the following starting sentence when in gpedit.msc."The following entry in the (strings) section was too long and has been truncated." I get 25 in row for differnet processes. settings etc. I can not access gpedit.msc. This occured after uninstalling SP 2..

I need to change my settings. How can I set them back to default..or anyo other ideas?
  • 5
  • 3
1 Solution
Asta CuCommented:
XP Pro, I assume?
Asta CuCommented:
Are you logging in as Administrator?  Click Start, click Run, type gpedit.msc doesn't work at all?

"The following entry in the [strings] section is too long and has been truncated" error message when you try to modify or to view GPOs in Windows Server 2003, Windows XP Professional, or Windows 2000
chick7t7Author Commented:
Yes XP Pro.

Yes gpedit.msc works, until I click on any setting then it proceeds to give me 25 of the popup error messages. I have never seen these error messages  before.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

chick7t7Author Commented:

both of the links describe my problem exactly. But the first link has a fix for 2000 SP or later...can I use that?

The other link says this occurs on SERVER 2003, XP PRO, connected to network. I beleive it said something about downloading stuff for a Server.

I am standaolne PC...just little ol me minding my own business.

Is there  a way to "reset" gpedit to default?
In the first link given by Asta, Did you try to download this the package for xp from here


If not , then install it , restart the machine to see if it helps solve the issue.

Asta CuCommented:
I hope the above helps you make progress here.  I'll research further, if you need more; but thought his is quite informative and may help you in the process.  I'm unclear if uninstalling the snap-in and reinstalling it would work for you since logic tells me that the new installation would be the default settings, but very honestly, don't know the implications of this process.  Others better versed in using this snap in may have more insights than I.

How To Use the Group Policy Editor to Manage Local Computer Policy in Windows XP

For additional information about using computer management in Microsoft Windows XP, click the article number below to view the article in the Microsoft Knowledge Base:
308423 How To Use Computer Management

For more information about the use of Group Policies, visit the following Microsoft Web sites:





Group Policy Object Editor snap-in  - How to add a Windows 2000 ADM template to a Group Policy snap-in in Office XP (includes troubleshooting info)

You cannot access the folders in the SMS Administrator console from a computer that is running Windows XP Professional Service Pack 2
Note By default, this Group Policy setting is disabled.


Asta CuCommented:
Re. the Pop ups and errors using GPedit in XP SP2, these may also help
New Administrative Templates
Additional security settings are available in Unicode-based files called Administrative Templates. These files contain registry settings that affect Windows XP and its components. New Administrative Templates are included in Windows XP SP2. These new templates require you to use a computer running Windows XP SP2 when managing GPOs.

Older versions of the Group Policy Object Editor (Gpedit.exe) do not support the new Administrative Templates. Modifications to new or existing GPOs must be performed using a computer running Windows XP SP2. For information on using other operating systems to manage GPOs, see Microsoft Knowledge Base Article 842933 at http://support.microsoft.com/?kbid=842933.

The settings in the new Administrative Templates only affect computers running Windows XP SP2; Windows XP SP1 and previous operating system versions will ignore the new settings. This approach allows you to implement GPOs using the same OU structure described in Chapter 2 of the Windows XP Security Guide to enhance the security of all computers running Windows XP in your environment.

Managing Windows XP Service Pack 2 Features Using Group Policy

chick7t7Author Commented:
Hi...and Thank You!!!! The information you gave helped me, but I chose to reinstall. Sometimes reinsalling seems safeer, rather than dealing with left over problems.

I am not sure what casued the problem, or what WOULD have fixed it. I do know your s suggestions, and links hot the nail right on the head on all accounts...thanks

I think I had a problem with  SP and Symantec. Then when I unistalled SP2, it only partially unistalled. So I had an updated Group Policy, with older settings causing the error. I didn't think about it, but I had a ton of registry hacks, GPO settings, etc, that SP is supposed to fix. I think aleady being set, then using SP2...confused my system. Well, I think anyway....:):):):)

Thanks...I hope to find you again if..  well when my next problem occurs.
Asta CuCommented:
I'm very pleased to have added value to your troubleshooting process and will definitely continue to work on your behalf if I can help further.  Thank you for taking the time to update this with your implementation/solution and thank you for the fine grade.

Norton also has a number of links that relate to the XP SP2 upgrade.  Here's just one example:

Best wishes,
":0) Asta

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now