• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

XP SP3 Errors

ObscureTerror

Limp Gawd
Joined
Aug 29, 2007
Messages
145
I just installed SP3 on my wife's laptop, and have gotten a few strange errors. Though nothing since (only bee a few hours) I don't know if there's something wrong or not.

First error: a pop-up box (like a CMD) box, two of them, listed the error: "Error in parameter", then they both closed.

Second error: upon opening Diskeeper to defrag, keep getting the error: "Detected error in the MMC snap-in" (Microsoft Management Console; had to look up what it even was), though the program will run.

Third error: upon opening Firefox, ESET Security detected a change in the "svchost.exe", and I allowed it, since I figured it was a change that SP3 had made to my system. I don't know for sure, however. Haven't gotten since I allowed.

Upon checking the Even Viewer, I found the following "issues" listed, but again, have no idea what (if any) problems these represent:

The description for Event ID ( 1000 ) in Source ( Microsoft Management Console ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: dfrgsnap.dll, 10.0.593.0, dfrgsnap.dll, 10.0.593.0, 00007270.

A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.

A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

I have Computer Browser disabled in Services, and there was an "error" about that starting in Events, but I don't know if that's causing a problem or not.

Any info/help appreciated.
 
So they're all errors that displayed temporarily and then went away? If the event viewer log consistently showing this "issue"?

Edit: Upon reading this link about whats new in sp3, I came across "For example, the service pack includes functionality previously released as updates, such as the Microsoft® Management Console (MMC) 3.0..." Page 6 of that doc talks more about MMC too.
 
Second error: upon opening Diskeeper to defrag, keep getting the error: "Detected error in the MMC snap-in" (Microsoft Management Console; had to look up what it even was), though the program will run.

MMC is Microsoft Management Console. It's a foundation for applications to run in. Diskkeeper has been running in an MMC window for years. Programs that are controlled by the MMC are access by their snap-ins.

I'd say try reinstalling Diskkeeper. Or go to start, run and type mmc.exe and hit enter. It should pull up a blank window. Go to the file menu and choose Add Snapin. Once this window opens, hit the Add button and find diskkeeper. If you don't see it, it's not registered properly. If you do see it, click on it and hit the add button. Close, then OK, and you should see it. Does the error message still pop up? If not, save it and use that shortcut to open diskeeper.

Check this thread for a batch file that might fix your WMI problem. It sounds like your WMI repository needs to be rebuilt.
 
Back
Top