Re: WMI Failure
- From: "Scott McNairy \(MVP\)" <v-scomcn@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 13 May 2005 12:59:31 -0700
Sorry for late response. Can you try to troubleshoot via this link and see
if that corrects the problem that I unfortunately only vaguely remember.
http://www.microsoft.com/technet/scriptcenter/resources/wmifaq.mspx#EIAA
An alternative to doing a clean install is to just do these steps which will
re-install over the top of your existing settings for your windows
installation. You will find that the settings and programs currently
installed on your computer will remain after it is done but this has got
people out of this situation before.
open a "cmd.exe" process
type the drive letter of your Windows XP installation media. ie. "D:"
type "cd\"
cd i386
winnt32.exe /unattend
This will re-install your OS and hopefully fix the problems you were having
while preserving your current settings.
--
Scott McNairy
Microsoft MVP - Windows Server Management Infrastructure
"Dr. Steven Berk" <sberk@xxxxxxxxxxx> wrote in message
news:O4ffs%23lVFHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
> Scott--
>
> Posting as new message. Got error on reply to you.
> Thanks for the response. While I'm pretty literate with computers and XP,
> scripting code is a bit beyond me. When I check WMI status via control
> panel > admin>services. WMI, RPC, etc look like they are all running. I've
> even gone through the WBEM folder and deleted repository and reset
> registry
> values; however when I run WMI from help and support....I get a lott of
> null
> object responses. This suggests some files are mssing from WMI rather than
> corrupted. Problem is I have an OEM machine with XP and Apps restoration
> in
> a hard drive partition...no CD to extract WMI files collectively and
> locate
> within my boot dirve. Short of clean install (which always makes me want
> to
> scream), I suspect I should just live with this and use standalone
> programs
> like Sisoft Sandra, SIW (G. Topala) or System Properties (Simaika) to
> yield
> info. By the way, I've even uninstalled these programs wondering if they
> coopted the procedure calls from MSInfo32. No such luck.
>
>
>
> --
> Dr. Steven Berk
> 781-431-7792 (phone)
> 781-431-9622 (telefax)
> sberk@xxxxxxxxxxx (e-mail)
>
> The information contained in this message may be CONFIDENTIAL and is for
> the intended addressee only. Any unauthorized use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> intended addressee, please notify the sender immediately and delete this
> message.
>
>
>
>
.
- Follow-Ups:
- Re: WMI Failure
- From: Dr. Steven Berk
- Re: WMI Failure
- References:
- WMI Failure
- From: Dr. Steven Berk
- WMI Failure
- Prev by Date: Re: WMI Query for on board security chip
- Next by Date: Re: root\CIMV2\Win32_Processor
- Previous by thread: WMI Failure
- Next by thread: Re: WMI Failure
- Index(es):
Relevant Pages
|
