Whenever I start system update on my M55e (WinXP Pro (SP3)), and endless loop of annoucements that "A problem occurred while loading the System Update configuration settings. Please wait while System Update restarts" begin.
Since I found no way to uninstall System Update, I checked my services list. I reached the lenovo system update service and found that its dependencies information is flawed, starting the following error message:
WMI Invalid namespace
The 'root\cmv2' namespace is not defined in the WMI Repository

Well, I looked for the Windows Management Instrumentation item in my services, and to my surprise, found two identical lines, one which started automatically and the other, configured to be started manually. I checked both definitions, and the dependencies window on the manually activated option brought up exactly the same error message

WMI Invalid namespace
The 'root\cmv2' namespace is not defined in the WMI Repository

Looks like the problem stems from a problem in my WMI service configuration.

One way or another, what can be about the "System Update" issue?

System Update should be listed in control panel, add/remove progams. I can't understand why it would not be there, it would be listed as 'Thinkvantage System Update'. If it isn't, you could simply install the latest version over it;

http://www-307.ibm.com/pc/support/site. ... PDATE.html

Hi HarryC,
I've installed System Update, but the problem previaled with the new installation.
Since the new installation added the SU to add/remove listing, I could do a standard uninstall, clean the my system from the SU subdirectory, clean the registry, and reinstall it.
Unfortunately, even this clean install sets the same problematic response, "The 'root\cmv2' namespace is not defined in the WMI Repasitory".

So, back to square one. How do I solve this namespace problem? Or else, how do I solve the SU problem?

Seen these posts...?

http://www.pcreview.co.uk/forums/thread-198403.php
http://www.pcreview.co.uk/forums/thread-531758.php

loyukfai,
Thanks for offering such a wide solutions. Unfortunately, none solved my problem.
Still, the bug seems to be much wider, not just a System Update deficiency. Each and every service misses a way to check dependencies. Whenever I look for dependencies information, no matter what service I choose, the same "The 'root\cmv2' namespace is not defined in the WMI repasitory" jumps.

So, is there a solution to this problem?

So you already tried rebuilding the WMI repository...?

http://windowsxp.mvps.org/repairwmi.htm

And tried using the WMI diagnosis utility...?

http://www.microsoft.com/technet/script ... idiag.mspx

At worst, a re-installation could be the only solution...

Your're right, loyukfai, I was not aware of the existence of the WMIDiag tool. Still' after running it, its technical report is much mich above my capabilities.
Her it is. Can you help me in implementing its suggestion?

".3999 23:56:56 (0) ** WMIDiag v2.0 started on ‏שבת ‏13 ‏דצמבר ‏2008 at 23:56.
.4000 23:56:56 (0) **
.4001 23:56:56 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.4002 23:56:56 (0) **
.4003 23:56:56 (0) ** This script is not supported under any Microsoft standard support program or service.
.4004 23:56:56 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.4005 23:56:56 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.4006 23:56:56 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.4007 23:56:56 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.4008 23:56:56 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.4009 23:56:56 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.4010 23:56:56 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.4011 23:56:56 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.4012 23:56:56 (0) ** of the possibility of such damages.
.4013 23:56:56 (0) **
.4014 23:56:56 (0) **
.4015 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4016 23:56:56 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.4017 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4018 23:56:56 (0) **
.4019 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4020 23:56:56 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'RAN-HOME\CHERMESH' on computer 'RAN-HOME'.
.4021 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4022 23:56:56 (0) ** Environment: ........................................................................................................ OK..
.4023 23:56:56 (1) !! ERROR: The following WMI system file(s) is/are missing: ............................................................. 2 ERROR(S)!
.4024 23:56:56 (0) ** - C:\WINDOWS\System32\WBEM\xml\cim20.dtd
.4025 23:56:56 (0) ** - C:\WINDOWS\System32\WBEM\xml\wmi20.dtd
.4026 23:56:56 (0) ** => Recopy from a working system the missing WMI system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
.4027 23:56:56 (0) **
.4028 23:56:56 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.4029 23:56:56 (0) ** WMI repository state: ............................................................................................... N/A.
.4030 23:56:56 (0) ** BEFORE running WMIDiag:
.4031 23:56:56 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.4032 23:56:56 (0) ** - Disk free space on 'C:': .......................................................................................... 8386 MB.
.4033 23:56:56 (0) ** - INDEX.BTR, 114688 bytes, 13/12/2008 00:11:13
.4034 23:56:56 (0) ** - INDEX.MAP, 80 bytes, 13/12/2008 00:11:13
.4035 23:56:56 (0) ** - OBJECTS.DATA, 253952 bytes, 13/12/2008 00:11:13
.4036 23:56:56 (0) ** - OBJECTS.MAP, 148 bytes, 13/12/2008 00:11:13
.4037 23:56:56 (0) ** AFTER running WMIDiag:
.4038 23:56:56 (0) ** The WMI repository has a size of: ................................................................................... 0 MB.
.4039 23:56:56 (0) ** - Disk free space on 'C:': .......................................................................................... 8386 MB.
.4040 23:56:56 (0) ** - INDEX.BTR, 114688 bytes, 13/12/2008 00:11:13
.4041 23:56:56 (0) ** - INDEX.MAP, 80 bytes, 13/12/2008 00:11:13
.4042 23:56:56 (0) ** - OBJECTS.DATA, 253952 bytes, 13/12/2008 00:11:13
.4043 23:56:56 (0) ** - OBJECTS.MAP, 148 bytes, 13/12/2008 00:11:13
.4044 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4045 23:56:56 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.4046 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4047 23:56:56 (0) ** DCOM Status: ........................................................................................................ OK.
.4048 23:56:56 (0) ** WMI registry setup: ................................................................................................. OK.
.4049 23:56:56 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.4050 23:56:56 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.4051 23:56:56 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.4052 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4053 23:56:56 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.4054 23:56:56 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
.4055 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
.4056 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
.4057 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
.4058 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
.4059 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
.4060 23:56:56 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
.4061 23:56:56 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.4062 23:56:56 (0) ** fail depending on the operation requested.
.4063 23:56:56 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.4064 23:56:56 (0) **
.4065 23:56:56 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.4066 23:56:56 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.4067 23:56:56 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.4068 23:56:56 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.4069 23:56:56 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.4070 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4071 23:56:56 (0) ** Overall DCOM security status: ....................................................................................... OK.
.4072 23:56:56 (0) ** Overall WMI security status: ........................................................................................ OK.
.4073 23:56:56 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.4074 23:56:56 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.4075 23:56:56 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.4076 23:56:56 (0) ** WMI ADAP status: .................................................................................................... OK.
.4077 23:56:56 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
.4078 23:56:56 (0) ** - ROOT/SERVICEMODEL.
.4079 23:56:56 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
.4080 23:56:56 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
.4081 23:56:56 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
.4082 23:56:56 (0) ** i.e. 'WMIC.EXE /NODE:"RAN-HOME" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
.4083 23:56:56 (0) **
.4084 23:56:56 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
.4085 23:56:56 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 2 ERROR(S)!
.4086 23:56:56 (0) ** - Root/CIMv2, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
.4087 23:56:56 (0) ** - Root/WMI, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
.4088 23:56:56 (0) **
.4089 23:56:56 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 4 ERROR(S)!
.4090 23:56:56 (0) ** - Root/Default, SystemRestore, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.4091 23:56:56 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
.4092 23:56:56 (0) ** - Root/Default, SystemRestoreConfig, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.4093 23:56:56 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
.4094 23:56:56 (0) ** - Root/Default, SystemRestore, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.4095 23:56:56 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
.4096 23:56:56 (0) ** - Root/Default, SystemRestoreConfig, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
.4097 23:56:56 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
.4098 23:56:56 (0) **
.4099 23:56:56 (0) ** WMI MOF representations: ............................................................................................ OK.
.4100 23:56:56 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.4101 23:56:56 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.4102 23:56:56 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.4103 23:56:56 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.4104 23:56:56 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.4105 23:56:56 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.4106 23:56:56 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.4107 23:56:56 (0) ** WMI static instances retrieved: ..................................................................................... 25.
.4108 23:56:56 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.4109 23:56:56 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.4110 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4111 23:56:56 (0) **
.4112 23:56:56 (0) ** 2 error(s) 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found
.4113 23:56:56 (0) **
.4114 23:56:56 (0) ** 4 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
.4115 23:56:56 (0) ** => This error is typically a WMI error. This WMI error is due to:
.4116 23:56:56 (0) ** - a missing WMI class definition or object.
.4117 23:56:56 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
.4118 23:56:56 (0) ** You can correct the missing class definitions by:
.4119 23:56:56 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
.4120 23:56:56 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
.4121 23:56:56 (0) ** (This list can be built on a similar and working WMI Windows installation)
.4122 23:56:56 (0) ** The following command line must be used:
.4123 23:56:56 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
.4124 23:56:56 (0) ** - a WMI repository corruption.
.4125 23:56:56 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.4126 23:56:56 (0) ** to validate the WMI repository operations.
.4127 23:56:56 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.4128 23:56:56 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.4129 23:56:56 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
.4130 23:56:56 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.4131 23:56:56 (0) ** the WMI repository must be reconstructed.
.4132 23:56:56 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.4133 23:56:56 (0) ** otherwise some applications may fail after the reconstruction.
.4134 23:56:56 (0) ** This can be achieved with the following command:
.4135 23:56:56 (0) ** i.e. 'WMIDiag ShowMOFErrors'
.4136 23:56:56 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.4137 23:56:56 (0) ** ALL fixes previously mentioned.
.4138 23:56:56 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.4139 23:56:56 (0) **
.4140 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4141 23:56:56 (0) ** WMI Registry key setup: ............................................................................................. OK.
.4142 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4143 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4144 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4145 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4146 23:56:56 (0) **
.4147 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4148 23:56:56 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.4149 23:56:56 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.4150 23:56:56 (0) **
.4151 23:56:56 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'E:\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_RAN-HOME_2008.12.13_23.56.01.LOG' for details.
.4152 23:56:56 (0) **
.4153 23:56:56 (0) ** WMIDiag v2.0 ended on ‏שבת ‏13 ‏דצמבר ‏2008 at 23:56 (W:28 E:26 S:1)."

Ran

I see that several are having problems with the latest System Update as I am.

I have installed it twice and still it won't go past the Admin login (I use UAC). When it put up the screen sign the Administrator on, it says it wants to open the registry editor.

I don't understand why it is opening the registry editor.

We need Lenovo help with this.

Umm... I'm sorry that I don't have any idea at this moment... Thought rebuilding the WMI repository would have solved the problem... Just want to make sure, did you run the WMI Diag tool with an Admin account...?

Sure, I did run it. I've even uploaded its report to this forum on Dec 14, 2008

I suspect this probably is due to SP3 breaking something in the WMI, though I can't find a definitive reference. I've seen lots of similarly related issues but no working solutions

Hi,
I'm glad to have found a solution to my, and hopefully others' System Update problem. The problem stems from a deficient WMI installation.
I raised my problem on another forum http://www.experts-exchange.com/ and following a long process of raising and rephrasing, got a solution.
A set of solutions is offered in http://windowsxp.mvps.org/repairwmi.htm. and for me' only the last option "Comprehensive rebuild method" did it. The impact was immediate. As any of us who experienced the System Update problem knows, you are thrown into an endless loop of system trials to start the update procedure. I ran some of the trial while such a message was popping on my desktop. And here, one of a sudden, the updating procedure started. Wou!! Such a good surprise!!

I referenced that webpage a few posts back then, did you not try it at that time...? Anyway, glad you solved the problem.

Cheers and nice weekend.

You're right, loyukfai. I did check this site following your advice. Still, I got stuck with the WMIDiag application. I posted the WMIDiag report, expecting a way out on the basis of this log. Since I got no assistance on this front, I looked elsewhere.
Well, here' another proof that the globe is round. Got back to your link, which I, unfortunately, didn't make an exhaustive use.
Thanks again.

Ran