Determination of OS properties failed

[mrmkamath]

Hi,

I am getting error "Error: Determination of OS properties failed" in wsusofflineupdate.log and even in cmd windows.

SetSystemEnvVars.cmd is created in %temp% and I have attached for ref.

I have searched in net, checked and found WMI and Automatic Update server is in started mode.

Have tries to install scripten.exe with /overwriteoem but ends with error "...service pack installed is latest...need not install.."

Kindly provide some steps to resolve this issues.

Thanks

Kamath

[harry]

Welcome mrmkamath,

please post the content of wsusofflineupdate.log and SetSystemEnvVars.cmd with the code-Tag.

[mrmkamath]

Hi Harry,

In new XP OS installation and in new OS+all Applications installed system WSUS Offline update works fine. But when run on user system(2 systems tried) it is not working.

Please help, we are planning to implement this patch update solution for 1000+ systems.

wsusofflineupdate.log Contents

Code: Select all

Fri 04/13/2012 14:18:03.15 - Info: Starting WSUS Offline Update (v. 7.3) on BLR-2310DT0004 (user: wpsadmin)
Fri 04/13/2012 14:18:03.18 - Info: Option /updatecpp detected
Fri 04/13/2012 14:18:03.45 - Info: Option /updatedx detected
Fri 04/13/2012 14:18:03.72 - Info: Option /autoreboot detected
Fri 04/13/2012 14:18:04.09 - Info: Executed custom initialization hook (Errorlevel: 0)
Fri 04/13/2012 14:18:07.15 - Error: Determination of OS properties failed
Fri 04/13/2012 14:18:07.29 - Info: Executed custom finalization hook (Errorlevel: 0)
Fri 04/13/2012 14:18:08.07 - Info: Ending WSUS Offline Update


SetSystemEnvVars.cmd Contents

Code: Select all

set OS_CAPTION=Microsoft Windows XP Professional
set OS_VER_MAJOR=5
set OS_VER_MINOR=1
set OS_VER_REVIS=2600
set OS_VER_BUILD=0
set OS_SP_VER_MAJOR=3
set OS_SP_VER_MINOR=0
set OS_LANG_CODE=0x409
set OS_LANG=enu
set OS_LANG_SHORT=en
set SystemDirectory=C:\WINDOWS\system32
set OS_ARCH=x86
set OS_DOMAIN_ROLE=1
set FS_TYPE=FAT32
set PWR_POL_IDX=0
set WUA_VER_MAJOR=7
set WUA_VER_MINOR=4
set WUA_VER_REVIS=7600
set WUA_VER_BUILD=226
set MSI_VER_MAJOR=3
set MSI_VER_MINOR=1
set MSI_VER_REVIS=4001
set MSI_VER_BUILD=5512
set WSH_VER_MAJOR=5
set WSH_VER_MINOR=7
set WSH_VER_REVIS=0
set WSH_VER_BUILD=18066
set IE_VER_MAJOR=7
set IE_VER_MINOR=0
set IE_VER_REVIS=5730
set IE_VER_BUILD=13
set MDAC_VER_MAJOR=2
set MDAC_VER_MINOR=81
set MDAC_VER_REVIS=1132
set MDAC_VER_BUILD=0
set DX_CORE_VER_MAJOR=4
set DX_CORE_VER_MINOR=09
set DX_CORE_VER_REVIS=00
set DX_CORE_VER_BUILD=0904
set DX_NAME=9.0c
set DOTNET35_VER_MAJOR=0
set DOTNET35_VER_MINOR=0
set DOTNET35_VER_REVIS=0
set DOTNET35_VER_BUILD=0
set DOTNET4_VER_MAJOR=0
set DOTNET4_VER_MINOR=0
set DOTNET4_VER_REVIS=0
set DOTNET4_VER_BUILD=0
set PSH_VER_MAJOR=0
set PSH_VER_MINOR=0
set PSH_VER_REVIS=0
set PSH_VER_BUILD=0
set MSSE_INSTALLED=0
set MSSEDEFS_VER_MAJOR=0
set MSSEDEFS_VER_MINOR=0
set MSSEDEFS_VER_REVIS=0
set MSSEDEFS_VER_BUILD=0
set WD_INSTALLED=1
set WDDEFS_VER_MAJOR=0
set WDDEFS_VER_MINOR=0
set WDDEFS_VER_REVIS=0
set WDDEFS_VER_BUILD=0
set RCERTS_VER_MAJOR=0
set RCERTS_VER_MINOR=0
set RCERTS_VER_REVIS=0
set RCERTS_VER_BUILD=0
set TSC_VER_MAJOR=6
set TSC_VER_MINOR=0
set TSC_VER_REVIS=6001
set TSC_VER_BUILD=18589
set WMP_VER_MAJOR=10
set WMP_VER_MINOR=0
set WMP_VER_REVIS=0
set WMP_VER_BUILD=4074
set O2K3_VER_APP=Outlook
set O2K3_VER_MAJOR=11
set O2K3_VER_MINOR=0
set O2K3_VER_REVIS=5510
set O2K3_VER_BUILD=0
set O2K3_SP_VER=0
set O2K3_ARCH=x86
set O2K3_LANG_CODE=0x409
set O2K3_LANG=enu
set AU_SVC_STATE_INITIAL=Running
set AU_SVC_START_MODE=Auto
set OS_ACTIVATION_REQUIRED=0


[harry]

Does the problem also exist without executing custom initialization hook (by renaming [client]\cmd\custom\InitializationHook.cmd)?

And a Microsoft link, which may help http://support.microsoft.com/kb/949140/en-us

[mrmkamath]

Hi Harry,

Even if we rename InitializationHook.cmd to *.cmdt too we are getting this error.

I have tried to install scripten.exe even with /overwriteoem but ends with error "...service pack installed is latest...need not install.."

I guess this should be related to some OS hardening. I have requested for the Hardening script which I am expecting today.

Till then any other Reg key/Group Policy setting which can resolve this ?

Regards

mrmkamath

[Denniss]

Below is the info from my XP Prof using a VirtualBox VM.

Code: Select all

set OS_CAPTION=Microsoft Windows XP Professional
set OS_VER_MAJOR=5
set OS_VER_MINOR=1
set OS_VER_REVIS=2600
set OS_VER_BUILD=0
set OS_SP_VER_MAJOR=3
set OS_SP_VER_MINOR=0
set OS_LANG_CODE=0x407
set OS_LANG=deu
set OS_LANG_SHORT=de
set SystemDirectory=C:\WINDOWS\system32
set OS_ARCH=x86
set OS_DOMAIN_ROLE=0
set FS_TYPE=VBoxSharedFolderFS
set PWR_POL_IDX=0
set WUA_VER_MAJOR=7
set WUA_VER_MINOR=4
set WUA_VER_REVIS=7600
set WUA_VER_BUILD=226
set MSI_VER_MAJOR=4
set MSI_VER_MINOR=5
set MSI_VER_REVIS=6001
set MSI_VER_BUILD=22159
set WSH_VER_MAJOR=5
set WSH_VER_MINOR=8
set WSH_VER_REVIS=6001
set WSH_VER_BUILD=23141
set IE_VER_MAJOR=8
set IE_VER_MINOR=0
set IE_VER_REVIS=6001
set IE_VER_BUILD=18702
set MDAC_VER_MAJOR=2
set MDAC_VER_MINOR=81
set MDAC_VER_REVIS=1132
set MDAC_VER_BUILD=0
set DX_CORE_VER_MAJOR=4
set DX_CORE_VER_MINOR=09
set DX_CORE_VER_REVIS=00
set DX_CORE_VER_BUILD=0904
set DX_NAME=9.0c
set DOTNET35_VER_MAJOR=0
set DOTNET35_VER_MINOR=0
set DOTNET35_VER_REVIS=0
set DOTNET35_VER_BUILD=0
set DOTNET4_VER_MAJOR=0
set DOTNET4_VER_MINOR=0
set DOTNET4_VER_REVIS=0
set DOTNET4_VER_BUILD=0
set PSH_VER_MAJOR=0
set PSH_VER_MINOR=0
set PSH_VER_REVIS=0
set PSH_VER_BUILD=0
set MSSE_INSTALLED=0
set MSSEDEFS_VER_MAJOR=0
set MSSEDEFS_VER_MINOR=0
set MSSEDEFS_VER_REVIS=0
set MSSEDEFS_VER_BUILD=0
set WD_INSTALLED=0
set WDDEFS_VER_MAJOR=0
set WDDEFS_VER_MINOR=0
set WDDEFS_VER_REVIS=0
set WDDEFS_VER_BUILD=0
set RCERTS_VER_MAJOR=35
set RCERTS_VER_MINOR=0
set RCERTS_VER_REVIS=2195
set RCERTS_VER_BUILD=0
set TSC_VER_MAJOR=6
set TSC_VER_MINOR=0
set TSC_VER_REVIS=6001
set TSC_VER_BUILD=18589
set WMP_VER_MAJOR=9
set WMP_VER_MINOR=0
set WMP_VER_REVIS=0
set WMP_VER_BUILD=4510
set AU_SVC_STATE_INITIAL=Running
set AU_SVC_START_MODE=Auto
set OS_ACTIVATION_REQUIRED=0


set OS_DOMAIN_ROLE=1 is this computer is in a domain? It may have some restrictions and require an admin/domain admin acount for the operation.
set WD_INSTALLED=1 does it have Windows Defender installed? If yes it somehow failed to detect the WD definition version.

[mrmkamath]

Thanks Denniss, you are right system is connected to domain, but the issue is different in different system.

I am working on a different system today and getting error "Unsupported Operating system Language"

OS language is english. In this system SetSystemEnvVars.cmd is created empty. When I removed //B from below line of code from doUpdate.cmd file

Code: Select all

%CSCRIPT_PATH% //Nologo //B //E:vbs DetermineSystemProperties.vbs


I am getting error as below

Code: Select all

Starting WSUS Offline Update (v. 7.3) at 12:02:37.29...
Checking user's privileges...
Determining system's properties...
D:\wsus\wsusoffline73\wsusoffline\client\cmd\DetermineSystemProperties.vbs(405,1) Microsoft VBScript runtime error: ActiveX component can't create object: 'GetObject'

ERROR: Unsupported Operating System language.

Ending WSUS Offline Update at 12:03:20.93...


Kindly help......

[mrmkamath]

Sorry missed to post results of WMI Diag

Code: Select all

.1415 12:16:42 (0) ** WMIDiag v2.1 started on Monday, April 23, 2012 at 12:08.
.1416 12:16:42 (0) **
.1417 12:16:42 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1418 12:16:42 (0) **
.1419 12:16:42 (0) ** This script is not supported under any Microsoft standard support program or service.
.1420 12:16:42 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1421 12:16:42 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1422 12:16:42 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1423 12:16:42 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1424 12:16:42 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1425 12:16:42 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1426 12:16:42 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1427 12:16:42 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1428 12:16:42 (0) ** of the possibility of such damages.
.1429 12:16:42 (0) **
.1430 12:16:42 (0) **
.1431 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1432 12:16:42 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1433 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1434 12:16:42 (0) **
.1435 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1436 12:16:42 (0) ** Windows XP - Service pack 3 - 32-bit (2600) - User 'BLR-9330-DT2003\ING1' on computer 'BLR-9330-DT2003'.
.1437 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1438 12:16:42 (0) ** Environment: ........................................................................................................ OK.
.1439 12:16:42 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1440 12:16:42 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1441 12:16:42 (0) ** WMI repository state: ............................................................................................... NOT TESTED.
.1442 12:16:42 (0) ** AFTER running WMIDiag:
.1443 12:16:42 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
.1444 12:16:42 (0) ** - Disk free space on 'C:': .......................................................................................... 5109 MB.
.1445 12:16:42 (0) **   - INDEX.BTR,                     1482752 bytes,      16/08/2010 15:40:09
.1446 12:16:42 (0) **   - INDEX.MAP,                     768 bytes,          16/08/2010 16:23:13
.1447 12:16:42 (0) **   - MAPPING.VER,                   4 bytes,            16/08/2010 16:23:14
.1448 12:16:42 (0) **   - MAPPING1.MAP,                  3740 bytes,         16/08/2010 16:23:12
.1449 12:16:42 (0) **   - MAPPING2.MAP,                  3740 bytes,         16/08/2010 16:23:14
.1450 12:16:42 (0) **   - OBJECTS.DATA,                  5947392 bytes,      16/08/2010 15:40:09
.1451 12:16:42 (0) **   - OBJECTS.MAP,                   2972 bytes,         16/08/2010 16:23:14
.1452 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1453 12:16:42 (2) !! WARNING: Windows Firewall Service: .................................................................................. STOPPED.
.1454 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1455 12:16:42 (0) ** DCOM Status: ........................................................................................................ OK.
.1456 12:16:42 (0) ** WMI registry setup: ................................................................................................. OK.
.1457 12:16:42 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1458 12:16:42 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1459 12:16:42 (0) ** - Windows Firewall/Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Manual')
.1460 12:16:42 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1461 12:16:42 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1462 12:16:42 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1463 12:16:42 (0) **          this can prevent the service/application to work as expected.
.1464 12:16:42 (0) **
.1465 12:16:42 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1466 12:16:42 (0) ** WINMGMT service: .................................................................................................... Failed to start.
.1467 12:16:42 (0) ** => The WINMGMT service can't be started. This could be due to the following reasons:
.1468 12:16:42 (0) **    - The service is DISABLED. You can re-enable the service with the command:
.1469 12:16:42 (0) **      i.e. 'SC.EXE CONFIG WINMGMT START= AUTO'
.1470 12:16:42 (0) **    Note: The SC.EXE command is available in the Windows Resource Kit.
.1471 12:16:42 (0) **    - The WINMGMT service depends on RPCSS service which is DISABLED or unable to start.
.1472 12:16:42 (0) **    - If the service is ENABLED but can't start, then the service registry may contains bad data.
.1473 12:16:42 (0) **    Note: Registry setup errors should be reported. Follow the steps related to registry issues.
.1474 12:16:42 (0) ** => After verifying the registry, if the WMI service does not start yet, you can try to
.1475 12:16:42 (0) **    to run the service as a STANDALONE service host or as a SHARED service host (SvcHost)
.1476 12:16:42 (0) **    You can achieve this by running ONE of the following commands (case sensitive):
.1477 12:16:42 (0) **    - to configure the service to run as a SHARED service host (recommended):
.1478 12:16:42 (0) **      i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToShared'
.1479 12:16:42 (0) **    - if you have issue to get it running as a SHARED service host, the WMI service
.1480 12:16:42 (0) **      can be configured to run as a STANDALONE service host:
.1481 12:16:42 (0) **      i.e. 'RUNDLL32.EXE C:\WINDOWS\SYSTEM32\WBEM\WMISVC.DLL,MoveToAlone'
.1482 12:16:42 (0) ** => If the registry is correct and the WMI service does not start yet, the WMI repository could be inconsistent.
.1483 12:16:42 (0) **    - Under Windows XP SP2 and SP3, you can validate the repository consistency by:
.1484 12:16:42 (0) **      executing the following command:
.1485 12:16:42 (0) **      i.e. 'WMIDiag CheckConsistency'
.1486 12:16:42 (0) **    Note: Under Windows XP SP2 and SP3, when the repository is checked and detected INCONSISTENT,
.1487 12:16:42 (0) **          a new repository is automatically re-created based on Auto-Recovery mechanism.
.1488 12:16:42 (0) **          Note that some information can be lost during this process (i.e. static data, CIM registration).
.1489 12:16:42 (0) **          However, the original repository is located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
.1490 12:16:42 (0) **          The computer must be rebooted for the system to work with the re-created repository.
.1491 12:16:42 (0) **    - The repository can be recovered from a previous backup.
.1492 12:16:42 (0) **    Note: The System State backup or the System Restore snapshot contain a backup of
.1493 12:16:42 (0) **          of the WMI repository.
.1494 12:16:42 (0) ** => If no backup is available, you must rebuild the repository.
.1495 12:16:42 (0) **    - Re-run WMIDiag with the ShowMOFErrors, this will show any MOF file issues.
.1496 12:16:42 (0) **      i.e. 'WMIDiag ShowMOFErrors'
.1497 12:16:42 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1498 12:16:42 (0) **          otherwise some applications may fail after the reconstruction.
.1499 12:16:42 (0) **          This can be achieved with the following command:
.1500 12:16:42 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1501 12:16:42 (0) **    Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1502 12:16:42 (0) **          registry key will be excluded from the WMI repository reconstruction.
.1503 12:16:42 (0) **          This may imply the lost of WMI registration information.
.1504 12:16:42 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1505 12:16:42 (0) **          ALL fixes previously mentioned.
.1506 12:16:42 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1507 12:16:42 (0) **    - To rebuild the WMI repository, you must:
.1508 12:16:42 (0) **    - Stop the WMI Service.
.1509 12:16:42 (0) **      i.e. 'NET.EXE STOP WINMGMT'
.1510 12:16:42 (0) **    - Move the existing WMI repository files to another location.
.1511 12:16:42 (0) **      i.e. MOVE C:\WINDOWS\SYSTEM32\WBEM\Repository\FS\*.* %TEMP%
.1512 12:16:42 (0) **    - Start the WMI Service.
.1513 12:16:42 (0) **      i.e. 'NET.EXE START WINMGMT'
.1514 12:16:42 (0) **    WMI will rebuild the WMI repository based the auto-recovery mechanism.
.1515 12:16:42 (0) **
.1516 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1517 12:16:42 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1518 12:16:42 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1519 12:16:42 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1520 12:16:42 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1521 12:16:42 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1522 12:16:42 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1523 12:16:42 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1524 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1525 12:16:42 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1526 12:16:42 (0) ** Overall WMI security status: ........................................................................................ OK.
.1527 12:16:42 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1528 12:16:42 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1529 12:16:42 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1530 12:16:42 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1531 12:16:42 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1532 12:16:42 (0) **    the performance counters with the WMI performance classes with the following commands:
.1533 12:16:42 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1534 12:16:42 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1535 12:16:42 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1536 12:16:42 (0) **    More information can be found on MSDN at:
.1537 12:16:42 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1538 12:16:42 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1539 12:16:42 (0) ** - Root, 0x1AD - ActiveX component can't create object.
.1540 12:16:42 (0) **
.1541 12:16:42 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1542 12:16:42 (0) ** - Root, 0x80080005 - Server execution failed.
.1543 12:16:42 (0) ** - Root, 0x80080005 - Server execution failed.
.1544 12:16:42 (0) ** - Root/Default, 0x80080005 - Server execution failed.
.1545 12:16:42 (0) ** - Root/CIMv2, 0x80080005 - Server execution failed.
.1546 12:16:42 (0) ** - Root/WMI, 0x80080005 - Server execution failed.
.1547 12:16:42 (0) **
.1548 12:16:42 (0) ** WMI GET operations: ................................................................................................. OK.
.1549 12:16:42 (0) ** WMI MOF representations: ............................................................................................ OK.
.1550 12:16:42 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1551 12:16:42 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1552 12:16:42 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1553 12:16:42 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1554 12:16:42 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1555 12:16:42 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1556 12:16:42 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1557 12:16:42 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1558 12:16:42 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1559 12:16:42 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1560 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1561 12:16:42 (0) **
.1562 12:16:42 (0) ** 1 error(s) 0x1AD - (WBEM_UNKNOWN) This error code is external to WMI.
.1563 12:16:42 (0) **
.1564 12:16:42 (0) ** 5 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
.1565 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1566 12:16:42 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1567 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1568 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1569 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1570 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1571 12:16:42 (0) **
.1572 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1573 12:16:42 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1574 12:16:42 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1575 12:16:42 (0) **
.1576 12:16:42 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ING1\LOCAL SETTINGS\TEMP\WMIDIAG-V2.1_XP___.CLI.SP3.32_BLR-9330-DT2003_2012.04.23_12.08.19.LOG' for details.
.1577 12:16:42 (0) **
.1578 12:16:42 (0) ** WMIDiag v2.1 ended on Monday, April 23, 2012 at 12:16 (W:22 E:15 S:1).


[harry]

I have tried to install scripten.exe even with /overwriteoem but ends with error "...service pack installed is latest...need not install.."

Did you also tried "Method 2: Register the scripting components on your computer" or "Let me fix it myself" from this site http://support.microsoft.com/kb/949140/en-us ?
Here's a (german) thread, where it helps viewtopic.php?f=4&t=1479&start=50#p8349

Greetings, harry

[mrmkamath]

Hi Harry

Tried by re-registering all 7 system files as in http://support.microsoft.com/kb/949140/en-us

But still same error as below with SetSystemEnvVars.cmd is created empty

Code: Select all

Starting WSUS Offline Update (v. 7.3) at 12:02:37.29...
Checking user's privileges...
Determining system's properties...
D:\wsus\wsusoffline73\wsusoffline\client\cmd\DetermineSystemProperties.vbs(405,1) Microsoft VBScript runtime error: ActiveX component can't create object: 'GetObject'

ERROR: Unsupported Operating System language.

Ending WSUS Offline Update at 12:03:20.93...


If i run DetermineSystemProperties.vbs by double click I get the same error in UI