Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

unable to access internet connection, and firewall ics error 2


  • Please log in to reply
No replies to this topic

#1 explicit

explicit

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:07 AM

Posted 23 November 2009 - 07:14 PM

A couple days ago, i was hit with a virus. Used mb to get rid of it. Now my firewall(ics) wont turn on and i cant connect to the net. I Raned a wmidiag scan and a hijack this scan. Also when i go to network connections , nothing is there.

16330 04:13:45 (0) ** WMIDiag v2.0 started on Monday, November 23, 2009 at 04:05.
16331 04:13:45 (0) **
16332 04:13:45 (0) ** Copyright © Microsoft Corporation. All rights reserved - January 2007.
16333 04:13:45 (0) **
16334 04:13:45 (0) ** This script is not supported under any Microsoft standard support program or service.
16335 04:13:45 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
16336 04:13:45 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
16337 04:13:45 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
16338 04:13:45 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
16339 04:13:45 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
16340 04:13:45 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
16341 04:13:45 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
16342 04:13:45 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
16343 04:13:45 (0) ** of the possibility of such damages.
16344 04:13:45 (0) **
16345 04:13:45 (0) **
16346 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16347 04:13:45 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
16348 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16349 04:13:45 (0) **
16350 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16351 04:13:45 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'MATTHEW\OWNER' on computer 'MATTHEW'.
16352 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16353 04:13:45 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
16354 04:13:45 (0) ** INFO: => 1 incorrect shutdown(s) detected on:
16355 04:13:45 (0) ** - Shutdown on 22 November 2009 20:39:54 (GMT+6).
16356 04:13:45 (0) **
16357 04:13:45 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
16358 04:13:45 (0) ** Drive type: ......................................................................................................... IDE (WDC WD1200BB-22RDA0).
16359 04:13:45 (0) ** There are no missing WMI system files: .............................................................................. OK.
16360 04:13:45 (0) ** There are no missing WMI repository files: .......................................................................... OK.
16361 04:13:45 (0) ** WMI repository state: ............................................................................................... N/A.
16362 04:13:45 (0) ** BEFORE running WMIDiag:
16363 04:13:45 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
16364 04:13:45 (0) ** - Disk free space on 'C:': .......................................................................................... 72640 MB.
16365 04:13:45 (0) ** - INDEX.BTR, 1196032 bytes, 11/23/2009 1:24:24 AM
16366 04:13:45 (0) ** - INDEX.MAP, 636 bytes, 11/23/2009 1:24:24 AM
16367 04:13:45 (0) ** - OBJECTS.DATA, 6201344 bytes, 11/23/2009 1:24:23 AM
16368 04:13:45 (0) ** - OBJECTS.MAP, 3100 bytes, 11/23/2009 1:24:24 AM
16369 04:13:45 (0) ** AFTER running WMIDiag:
16370 04:13:45 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
16371 04:13:45 (0) ** - Disk free space on 'C:': .......................................................................................... 72633 MB.
16372 04:13:45 (0) ** - INDEX.BTR, 1196032 bytes, 11/23/2009 1:24:24 AM
16373 04:13:45 (0) ** - INDEX.MAP, 636 bytes, 11/23/2009 1:24:24 AM
16374 04:13:45 (0) ** - OBJECTS.DATA, 6201344 bytes, 11/23/2009 1:24:23 AM
16375 04:13:45 (0) ** - OBJECTS.MAP, 3100 bytes, 11/23/2009 1:24:24 AM
16376 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16377 04:13:45 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
16378 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16379 04:13:45 (0) ** DCOM Status: ........................................................................................................ OK.
16380 04:13:45 (0) ** WMI registry setup: ................................................................................................. OK.
16381 04:13:45 (0) ** WMI Service has no dependents: ...................................................................................... OK.
16382 04:13:45 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
16383 04:13:45 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
16384 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16385 04:13:45 (0) ** WMI service DCOM setup: ............................................................................................. OK.
16386 04:13:45 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
16387 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
16388 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
16389 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
16390 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
16391 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
16392 04:13:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
16393 04:13:45 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
16394 04:13:45 (0) ** fail depending on the operation requested.
16395 04:13:45 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
16396 04:13:45 (0) **
16397 04:13:45 (0) ** WMI ProgID registrations: ........................................................................................... OK.
16398 04:13:45 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
16399 04:13:45 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
16400 04:13:45 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
16401 04:13:45 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
16402 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16403 04:13:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
16404 04:13:45 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
16405 04:13:45 (0) ** - REMOVED ACE:
16406 04:13:45 (0) ** ACEType: &h0
16407 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16408 04:13:45 (0) ** ACEFlags: &h0
16409 04:13:45 (0) ** ACEMask: &h1
16410 04:13:45 (0) ** DCOM_RIGHT_EXECUTE
16411 04:13:45 (0) **
16412 04:13:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
16413 04:13:45 (0) ** Removing default security will cause some operations to fail!
16414 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
16415 04:13:45 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
16416 04:13:45 (0) **
16417 04:13:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
16418 04:13:45 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
16419 04:13:45 (0) ** - REMOVED ACE:
16420 04:13:45 (0) ** ACEType: &h0
16421 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16422 04:13:45 (0) ** ACEFlags: &h0
16423 04:13:45 (0) ** ACEMask: &h1
16424 04:13:45 (0) ** DCOM_RIGHT_EXECUTE
16425 04:13:45 (0) **
16426 04:13:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
16427 04:13:45 (0) ** Removing default security will cause some operations to fail!
16428 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
16429 04:13:45 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
16430 04:13:45 (0) **
16431 04:13:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
16432 04:13:45 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
16433 04:13:45 (0) ** - REMOVED ACE:
16434 04:13:45 (0) ** ACEType: &h0
16435 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16436 04:13:45 (0) ** ACEFlags: &h0
16437 04:13:45 (0) ** ACEMask: &h1
16438 04:13:45 (0) ** DCOM_RIGHT_EXECUTE
16439 04:13:45 (0) **
16440 04:13:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
16441 04:13:45 (0) ** Removing default security will cause some operations to fail!
16442 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
16443 04:13:45 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
16444 04:13:45 (0) **
16445 04:13:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
16446 04:13:45 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
16447 04:13:45 (0) ** - ACTUAL ACE:
16448 04:13:45 (0) ** ACEType: &h0
16449 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16450 04:13:45 (0) ** ACEFlags: &h2
16451 04:13:45 (0) ** CONTAINER_INHERIT_ACE
16452 04:13:45 (0) ** ACEMask: &h1
16453 04:13:45 (0) ** WBEM_ENABLE
16454 04:13:45 (0) ** - EXPECTED ACE:
16455 04:13:45 (0) ** ACEType: &h0
16456 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16457 04:13:45 (0) ** ACEFlags: &h12
16458 04:13:45 (0) ** CONTAINER_INHERIT_ACE
16459 04:13:45 (0) ** INHERITED_ACE
16460 04:13:45 (0) ** ACEMask: &h13
16461 04:13:45 (0) ** WBEM_ENABLE
16462 04:13:45 (0) ** WBEM_METHOD_EXECUTE
16463 04:13:45 (0) ** WBEM_WRITE_PROVIDER
16464 04:13:45 (0) **
16465 04:13:45 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
16466 04:13:45 (0) ** This will cause some operations to fail!
16467 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
16468 04:13:45 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
16469 04:13:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
16470 04:13:45 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
16471 04:13:45 (0) ** A specific WMI application can always require a security setup different
16472 04:13:45 (0) ** than the WMI security defaults.
16473 04:13:45 (0) **
16474 04:13:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
16475 04:13:45 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
16476 04:13:45 (0) ** - ACTUAL ACE:
16477 04:13:45 (0) ** ACEType: &h0
16478 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16479 04:13:45 (0) ** ACEFlags: &h2
16480 04:13:45 (0) ** CONTAINER_INHERIT_ACE
16481 04:13:45 (0) ** ACEMask: &h1
16482 04:13:45 (0) ** WBEM_ENABLE
16483 04:13:45 (0) ** - EXPECTED ACE:
16484 04:13:45 (0) ** ACEType: &h0
16485 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16486 04:13:45 (0) ** ACEFlags: &h12
16487 04:13:45 (0) ** CONTAINER_INHERIT_ACE
16488 04:13:45 (0) ** INHERITED_ACE
16489 04:13:45 (0) ** ACEMask: &h13
16490 04:13:45 (0) ** WBEM_ENABLE
16491 04:13:45 (0) ** WBEM_METHOD_EXECUTE
16492 04:13:45 (0) ** WBEM_WRITE_PROVIDER
16493 04:13:45 (0) **
16494 04:13:45 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
16495 04:13:45 (0) ** This will cause some operations to fail!
16496 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
16497 04:13:45 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
16498 04:13:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
16499 04:13:45 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
16500 04:13:45 (0) ** A specific WMI application can always require a security setup different
16501 04:13:45 (0) ** than the WMI security defaults.
16502 04:13:45 (0) **
16503 04:13:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
16504 04:13:45 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
16505 04:13:45 (0) ** - REMOVED ACE:
16506 04:13:45 (0) ** ACEType: &h0
16507 04:13:45 (0) ** ACCESS_ALLOWED_ACE_TYPE
16508 04:13:45 (0) ** ACEFlags: &h12
16509 04:13:45 (0) ** CONTAINER_INHERIT_ACE
16510 04:13:45 (0) ** INHERITED_ACE
16511 04:13:45 (0) ** ACEMask: &h13
16512 04:13:45 (0) ** WBEM_ENABLE
16513 04:13:45 (0) ** WBEM_METHOD_EXECUTE
16514 04:13:45 (0) ** WBEM_WRITE_PROVIDER
16515 04:13:45 (0) **
16516 04:13:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
16517 04:13:45 (0) ** Removing default security will cause some operations to fail!
16518 04:13:45 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
16519 04:13:45 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
16520 04:13:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
16521 04:13:45 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
16522 04:13:45 (0) ** A specific WMI application can always require a security setup different
16523 04:13:45 (0) ** than the WMI security defaults.
16524 04:13:45 (0) **
16525 04:13:45 (0) **
16526 04:13:45 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
16527 04:13:45 (0) ** DCOM security error(s) detected: .................................................................................... 3.
16528 04:13:45 (0) ** WMI security warning(s) detected: ................................................................................... 0.
16529 04:13:45 (0) ** WMI security error(s) detected: ..................................................................................... 3.
16530 04:13:45 (0) **
16531 04:13:45 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
16532 04:13:45 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
16533 04:13:45 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
16534 04:13:45 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
16535 04:13:45 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
16536 04:13:45 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
16537 04:13:45 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
16538 04:13:45 (0) ** 'select * from MSFT_SCMEventLogEvent'
16539 04:13:45 (0) **
16540 04:13:45 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
16541 04:13:45 (0) ** WMI ADAP status: .................................................................................................... OK.
16542 04:13:45 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
16543 04:13:45 (0) ** - ROOT/SERVICEMODEL.
16544 04:13:45 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
16545 04:13:45 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
16546 04:13:45 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
16547 04:13:45 (0) ** i.e. 'WMIC.EXE /NODE:"MATTHEW" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
16548 04:13:45 (0) **
16549 04:13:45 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
16550 04:13:45 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
16551 04:13:45 (0) ** WMI GET operations: ................................................................................................. OK.
16552 04:13:45 (0) ** WMI MOF representations: ............................................................................................ OK.
16553 04:13:45 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
16554 04:13:45 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 4 ERROR(S)!
16555 04:13:45 (0) ** - Root/CIMv2, InstancesOf, 'Win32_PerfRawData_Tcpip_IP' did not return any instance while AT LEAST 1 instance is expected.
16556 04:13:45 (0) ** MOF Registration: 'No located MOF file (exception)'
16557 04:13:45 (0) ** - Root/CIMv2, InstancesOf, 'Win32_PerfRawData_Tcpip_TCP' did not return any instance while AT LEAST 1 instance is expected.
16558 04:13:45 (0) ** MOF Registration: 'No located MOF file (exception)'
16559 04:13:45 (0) ** - Root/CIMv2, InstancesOf, 'Win32_PerfRawData_Tcpip_UDP' did not return any instance while AT LEAST 1 instance is expected.
16560 04:13:45 (0) ** MOF Registration: 'No located MOF file (exception)'
16561 04:13:45 (0) ** - Root/CIMv2, InstancesOf, 'Win32_PerfRawData_Tcpip_ICMP' did not return any instance while AT LEAST 1 instance is expected.
16562 04:13:45 (0) ** MOF Registration: 'No located MOF file (exception)'
16563 04:13:45 (0) **
16564 04:13:45 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 2 ERROR(S)!
16565 04:13:45 (0) ** - Root/CIMv2, 'Select * From Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport"' did not return any instance while AT LEAST 1 instance is expected.
16566 04:13:45 (0) ** - Root/WMI, Select * From MSNdis_MediaConnectStatus, 0x8004100C - (WBEM_E_NOT_SUPPORTED) Feature or operation is not supported.
16567 04:13:45 (0) **
16568 04:13:45 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
16569 04:13:45 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
16570 04:13:45 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
16571 04:13:45 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
16572 04:13:45 (0) ** WMI static instances retrieved: ..................................................................................... 574.
16573 04:13:45 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
16574 04:13:45 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
16575 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16576 04:13:45 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
16577 04:13:45 (0) ** DCOM: ............................................................................................................. 19.
16578 04:13:45 (0) ** WINMGMT: .......................................................................................................... 0.
16579 04:13:45 (0) ** WMIADAPTER: ....................................................................................................... 0.
16580 04:13:45 (0) ** => Verify the WMIDiag LOG at line #15853 for more details.
16581 04:13:45 (0) **
16582 04:13:45 (0) ** # of additional Event Log events AFTER WMIDiag execution:
16583 04:13:45 (0) ** DCOM: ............................................................................................................. 0.
16584 04:13:45 (0) ** WINMGMT: .......................................................................................................... 0.
16585 04:13:45 (0) ** WMIADAPTER: ....................................................................................................... 0.
16586 04:13:45 (0) **
16587 04:13:45 (0) ** 1 error(s) 0x8004100C - (WBEM_E_NOT_SUPPORTED) Feature or operation is not supported
16588 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16589 04:13:45 (0) ** WMI Registry key setup: ............................................................................................. OK.
16590 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16591 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16592 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16593 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16594 04:13:45 (0) **
16595 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16596 04:13:45 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
16597 04:13:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
16598 04:13:45 (0) **
16599 04:13:45 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\OWNER\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_MATTHEW_2009.11.23_04.05.39.LOG' for details.
16600 04:13:45 (0) **
16601 04:13:45 (0) ** WMIDiag v2.0 ended on Monday, November 23, 2009 at 04:13 (W:73 E:29 S:1).

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users