[unbodi]

Hi unbodi,

Please download the Microsoft Support Tool: WMI Diagnosis Utility. Once downloaded, execute and extract the files. You will then have a folder with a number of files; execute the VBScript file WMIDiag --> Depending on your System configuration, this file may run 'silently' in the background. It may take up to 15 minutes to complete (usually alot less), and upon completion it will give you a popup informing you that it is finished. Once you recieve this prompt, press 'OK'. Now, hold down the Windows key located on your Keyboard, and then press E. This will open up Windows Explorer -- in the Address Bar, type: %TEMP% and press Enter. In this directory, you should see a number of files; locate a text file which starts with WMIDIAG-V --> There should be two files in your Temp Folder that start with this; however only one should be a text file. Once you've located this file, please upload it to this website (it will have alot of text in it, so please don't copy/paste it, as it'll take up too much space ).

Thanks,
Dan.

Hi and thanks for the reply.
but i'm getting an error after i run the file, you can see it here:
http://img269.images...neterror9dg.jpg

is it good or bad?

Thanks!

Edited by unbodi, 26 April 2006 - 01:18 PM.

[Advertisements]

After the error ive the done the other stuff you told me to do and i got the text file you wanted me to upload.

Here it is(i've uploadad it to some other site because it was too big for geeks to go) :

http://s52.yousendit...3T0YZ2XL23NBZKJ

[unbodi]

After the error ive the done the other stuff you told me to do and i got the text file you wanted me to upload.

Here it is(i've uploadad it to some other site because it was too big for geeks to go) :

http://s52.yousendit...3T0YZ2XL23NBZKJ

[Dan]

is it good or bad?

Both It's good in the sense that we now (hopefully) know what's wrong, but bad in the sense that WMI Repository is corrupted.. Luckily it's relatively easy to repair.

If you're running Windows XP SP2 (and you really should be.. SP2 offers more protection along with added Support Tools), please goto Start --> Run --> type CMD and press OK --> then type: rundll32 wbemupgd, UpgradeRepository (this command is case sensitive, so ensure you type it AS IS). Once you have run this command, test to see if you can access the Advanced tab of your properties; does it work?

If you're not using XP SP2 (then I'd recommend you upgrade), you can repair it via the following means --
goto Start --> Run --> type CMD and press OK --> then type: net stop winmgmt --> Now, hold down the Windows Key and press E, and then in the Address Bar, type: %windir%\System32\Wbem --> In this new directory, click on the folder Repository once, so that it is highlighted, and then press the F2 key. Rename the folder to RepositoryBACKUP and press enter. Now, goto Start --> Run --> type CMD and press OK --> then type: net start winmgmt and press enter. Once this command completes, try to access the Advanced tab of your properties again; does it work?

- Dan

[unbodi]

Both It's good in the sense that we now (hopefully) know what's wrong, but bad in the sense that WMI Repository is corrupted.. Luckily it's relatively easy to repair.

If you're running Windows XP SP2 (and you really should be.. SP2 offers more protection along with added Support Tools), please goto Start --> Run --> type CMD and press OK --> then type: rundll32 wbemupgd, UpgradeRepository (this command is case sensitive, so ensure you type it AS IS). Once you have run this command, test to see if you can access the Advanced tab of your properties; does it work?


- Dan

No it didnt work.Same as befor...

Other ways to fix it?


Edit: Ive done a restart and its ok now...

So, problem Solved.


Thanks

Edited by unbodi, 27 April 2006 - 05:07 AM.

[Dan]

Glad to hear it, and happy to help Thanks for letting us know what worked -- will hopefully help future Google'rs

[unbodi]

Glad to hear it, and happy to help Thanks for letting us know what worked -- will hopefully help future Google'rs

Hi,

I just wanted you to know that the advance tab is still working, but i just ran the WMIDiag test again and i get the same error.so i think that there are more problems but i'm not sure.


What do you think?

thanks,
Unbodi

[Dan]

Hi,

If you wish, you can upload another log, and I'll have a look at it -- however if you aren't experiencing any issues, running any scripts etc, then there's nothing to panic about. That said, I'd be happy to look into it if you're worried that some components are not functioning correctly.

[unbodi]

Hi,

If you wish, you can upload another log, and I'll have a look at it -- however if you aren't experiencing any issues, running any scripts etc, then there's nothing to panic about. That said, I'd be happy to look into it if you're worried that some components are not functioning correctly.

I'm not experiencing any problems right now, but i'm worried that like i found that the advance tab is not working i'll find something els.

So here is a new log, and thanks for your help (:

[unbodi]

Hi,

If you wish, you can upload another log, and I'll have a look at it -- however if you aren't experiencing any issues, running any scripts etc, then there's nothing to panic about. That said, I'd be happy to look into it if you're worried that some components are not functioning correctly.

I'm not experiencing any problems right now, but i'm worried that like i found that the advance tab is not working i'll find something els.

So here is a new log, and thanks for your help (:

http://beta.yousendi...2A6AEF0345AFF10

[Dan]

I'm not experiencing any problems right now, but i'm worried that like i found that the advance tab is not working i'll find something els.

Fair enough Better to be safe than sorry.

The good news is that the repair was a success.. You shouldn't experience any issues in relation to your WMI. The "errors" you're recieving are due to some files not being registered properly, which is a common backlash when repairing the WMI, but which generally doesn't result in any problems. To re-register these files, please goto Start --> Run --> type CMD and press OK --> In the new Command Prompt window, please type the following commands, one after the other.. Once again, it's important that you type these commands exactly as listed.

• cd /d %windir%\system32\wbem <Press ENTER>
• for %i in (*.dll) do RegSvr32 -s %i <Press ENTER> Wait for this command to finish, then continue..
• for %i in (*.exe) do %i /RegServer <Press ENTER>

Once done, reboot your computer and then see if you're still recieving errors. If you are, please upload a new log.

Thanks,
Dan.

[unbodi]

Yeah i'm still getting that error.

Here is a fresh log:

http://download.yous...A36895F38175712

[Dan]

The only errors remaining are in relation to programs that are no longer on your computer, but which failed to remove all of their components when uninstalled / deleted. The WMI service is unable to re-register these files to their host, subsequently producing an error. There is no need to worry about this; your WMI service will function normally.. If you ever re-install these programs, then they'll simply replace the files, and the link will be re-established automatically.

[unbodi]

Ok,

So like i said befor, Thanks for all of the help and the time you have givin to me



Thanks,
unbodi