Jump to content

Add/remove Software Error


Recommended Posts


Posted

tried using the normal XP view?

its usually direct CD that messes add remove up isnt it? iforget.

try use a different view and if it still wont open its the repair console for you my man :)

Posted

It's your theme. To be precise, it's your shellstyle. Try a different theme, or delete the shell folder in the theme folder. I'm 100% sure about this. :)

Posted

Yup you are are right, i tryed acessing the add/remove funtion from the classic theme and all worked fine.....its really too bad, this theme kicks serious tail...

:)

=Drew

Posted

It's because SP1 changed something and the shellstyles of a lot of old themes don't work. Either find an updated version of the theme, or delete the shell folder in c:\windows\resources\themes\yourtheme\

Posted

It's great to finally find out why i was getting that bloody error. I've had it for months and sought help many times but no one seemed to know, even had to install an add & remove prog so i could uninstall stuff. Thx for enlightening me.

  • 1 year later...
Posted

Although this topic is a year old, I have some new info regarding this error.

It seems this is caused when certain regtweaks are applied relating to the theme/visual style. I haven't pinpointed the exact tweak yet.

On my system, changing the theme did not fix the problem. The only themes available were Classic and Luna. I also manually removed all the registry entries that I had initally modified with my regtweaks.reg. It still did not fix the 'parser message'

I found this solution on MS website. There is a file, "shellstyle.dll" located in C:\Windows\System32. The parser message is a result of a corrupt or missing shellstyle.dll file. I checked the location on my PC and sure enough, the file was missing. I replaced it from another machine, and instantly, the problem was fixed, no reboot necessary. For some reason, during my unattended upgrade (i'm pretty sure it's the regtweaks causing it) that file disappears. My next test will be to insert that file in the $OEM$ area on my unattended CD and hopefully the problem will be solved permanently.

Just thought I should add that here, since none of the previously mentioned fixes seemed to work on my system.

First post here BTW, I like it here, very helpful. Thanks.

Posted

I've always blamed this error on SP2!

Thanks for the answer to my 'unasked' question.

I would never have figured this one out on my own.

Shark007

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...