error message when trying to use add/remove windows components
setup was unable to open information file hiden. Contact your system
administrator, the specfic error code is 0x2 at line 2088999411
I have no idea what happened.......
John
Can't get into Add/Delete Windows Components
Mr. Ramesh, I am a computer novice and I am having the same problem with not being able to open my Add/Delete Windows Components. Unfortunately, my pc came with XP already loaded so I don't have a cd. Is there any way I can fix this? I think I screwed up my system by removing some MSM software and taking stuff off that I should have left on! My error message says 0x2 at line 2088999411, then a pop up box says msnmsn.info missing. I would appreciate any advice! Thanks.
Problems with Add/Remove Windows Components
Thank you very much for your response, but I have actually been able to resolve the problem now. I had messed up my computer by trying to remove AOL software (which is like trying to remove bubble gum from your hair) and couldn't do a system restore to get back to where I was before I started to tinker. I learned that my Norton Symantic Antivirus 2006 version was causing the problem so I disabled the Product Protection function and was able to restore my system back to where it was before I tinkered with it. BTW, the message I was getting was "0x2 at line ..... 208899592." My mistake when I quoted the 208.....411 error code. I was writing from a different computer. Anyway, everything seems to be ok now. I won't tinker again, but I would love to be able to get AOL off my machine! The AOL uninstaller refuses to be uninstalled! Should be a law against that company!
Re: error message when trying to use add/remove windows components
I have also recently been getting an error message when I try to use the Add/Remove Windows components.
THis is the exact error I get:
Setup Library StartOC.DLL could not be loaded, or function StarterOCSetupProc could not be found.
Contact your system administrator. The specific error code is 0x7e
I have searched the net for an answer to this, but the only solution I have found was for Windows 2000 Server, and that's not what I am running.
Windows XP SP3.
Will the solution in this thread also work for the error I am getting?