View Full Version : A problem occured while patching: 0x80041012
sdeck
10-28-2007, 04:40 AM
Problem: A problem occured while patching: 0x80041012
Specs: Windows XP sp2 etc, have been playing game fine all day after latest patch. I log out and come back on later to play again get this error.
I run the program as admin, I do not have anti-virus software installed and I do not have a firewall on.
Steps I took: Reinstalled, Rebooted, deleted acclient all kinds of stuff.. still getting the error.
AGAIN, I have zero firewall/anti-virus/routing/port problems.
scguy
10-29-2007, 04:50 PM
did a search for that number. and found this:
I’m getting an error regarding provider registration
Even after re-registering your WMI components (see I’m getting an 0x80041013 (“Provider not found”) or an 0x80041014 (“Component failed to initialize”) error) you might not be able to run your script; in particular, you might get one of the following errors:
Error Number
Description
0x80041011
Provider referenced in the schema has an incorrect or incomplete registration.
0x80041012
Provider referenced in the schema does not have a corresponding registration.
0x80041085
Provider was not registered.
If you receive one of these errors you will need to recompile one or more of your .MOF files. A .MOF (Managed Object Format) file is the mechanism by which information about WMI classes is entered into the WMI Repository. It is possible that the class definitions currently in the Repository have somehow become corrupted; in that case, recompiling your .MOF files will cause those class definitions to be overwritten and replaced with the same, uncorrupted class definitions used when the operating system was originally installed.
Before you begin recompiling .MOF files note two things. First, most .MOF files can be found in the folder %windir%\System32\Wbem. However, there can be exceptions. You might want to search your hard disk for all .MOF files before beginning.
Second, there are a few applications that automatically populate the Repository during installation; these applications do not use .MOF files. If one of these applications is responsible for the problem with the WMI service (an admittedly difficult problem to diagnose) the only way to correct the class definitions in the Repository is by reinstalling the application.
The easiest way to recompile your .MOF and .MFL files (a .MOF file will often have a corresponding .MFL file which contains localized descriptions of classes, properties, and methods) is to open a command window and use the cd command to switch to the %windir%\System32\Wbem folder. From there type the following:
for %i in (*.mof, *.mfl) do Mofcomp %i
If you use a script or batch file to recompile .MOF files or if you manually call Mofcomp.exe make sure that you compile a .MOF file before you compile the corresponding .MFL file. In other words, compile items in this order:
there's more. can read it here: http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx#EQFAC
now. i don't know if that will fix it or what. so do so at your own risk.
vBulletin® v3.7.1, Copyright ©2000-2010, Jelsoft Enterprises Ltd.