Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!  (Read 30417 times)

0 Members and 1 Guest are viewing this topic.

Mr.Hopeless

    Topic Starter


    Rookie

    Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
    « Reply #45 on: September 14, 2010, 06:52:27 AM »
    18424 09:15:45 (0) ** WMIDiag v2.0 started on Tuesday, September 14, 2010 at 09:11.
    18425 09:15:45 (0) **
    18426 09:15:45 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
    18427 09:15:45 (0) **
    18428 09:15:45 (0) ** This script is not supported under any Microsoft standard support program or service.
    18429 09:15:45 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    18430 09:15:45 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    18431 09:15:45 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    18432 09:15:45 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    18433 09:15:45 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    18434 09:15:45 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    18435 09:15:45 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    18436 09:15:45 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    18437 09:15:45 (0) ** of the possibility of such damages.
    18438 09:15:45 (0) **
    18439 09:15:45 (0) **
    18440 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18441 09:15:45 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    18442 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18443 09:15:45 (0) **
    18444 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18445 09:15:45 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'D2PGV571\BRETT' on computer 'D2PGV571'.
    18446 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18447 09:15:45 (0) ** Environment: ... OK..
    18448 09:15:45 (0) ** System drive: ... C: (Disk #0 Partition #1).
    18449 09:15:45 (0) ** Drive type: ... IDE (Maxtor 6Y080M0).
    18450 09:15:45 (0) ** There are no missing WMI system files: ....................................... ....................................... OK.
    18451 09:15:45 (0) ** There are no missing WMI repository files: ....................................... ................................... OK.
    18452 09:15:45 (0) ** WMI repository state: ....................................... ....................................... ................. N/A.
    18453 09:15:45 (0) ** BEFORE running WMIDiag:
    18454 09:15:45 (0) ** The WMI repository has a size of: ....................................... ....................................... ..... 12 MB.
    18455 09:15:45 (0) ** - Disk free space on 'C:': ....................................... ....................................... ............ 29517 MB.
    18456 09:15:45 (0) **   - INDEX.BTR,                     1826816 bytes,      9/14/2010 9:10:23 AM
    18457 09:15:45 (0) **   - INDEX.MAP,                     940 bytes,          9/14/2010 9:10:23 AM
    18458 09:15:45 (0) **   - OBJECTS.DATA,                  10575872 bytes,     9/14/2010 9:10:23 AM
    18459 09:15:45 (0) **   - OBJECTS.MAP,                   5208 bytes,         9/14/2010 9:10:24 AM
    18460 09:15:45 (0) ** AFTER running WMIDiag:
    18461 09:15:45 (0) ** The WMI repository has a size of: ....................................... ....................................... ..... 12 MB.
    18462 09:15:45 (0) ** - Disk free space on 'C:': ....................................... ....................................... ............ 29512 MB.
    18463 09:15:45 (0) **   - INDEX.BTR,                     1826816 bytes,      9/14/2010 9:10:23 AM
    18464 09:15:45 (0) **   - INDEX.MAP,                     940 bytes,          9/14/2010 9:10:23 AM
    18465 09:15:45 (0) **   - OBJECTS.DATA,                  10575872 bytes,     9/14/2010 9:10:23 AM
    18466 09:15:45 (0) **   - OBJECTS.MAP,                   5208 bytes,         9/14/2010 9:10:24 AM
    18467 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18468 09:15:45 (0) ** Windows Firewall: ....................................... ....................................... ..................... NOT INSTALLED.
    18469 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18470 09:15:45 (0) ** DCOM Status: ... OK.
    18471 09:15:45 (0) ** WMI registry setup: ....................................... ....................................... ................... OK.
    18472 09:15:45 (0) ** WMI Service has no dependents: ....................................... ....................................... ........ OK.
    18473 09:15:45 (0) ** RPCSS service: ... OK (Already started).
    18474 09:15:45 (0) ** WINMGMT service: ... OK (Already started).
    18475 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18476 09:15:45 (0) ** WMI service DCOM setup: ....................................... ....................................... ............... OK.
    18477 09:15:45 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
    18478 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
    18479 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
    18480 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
    18481 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
    18482 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
    18483 09:15:45 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
    18484 09:15:45 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
    18485 09:15:45 (0) **    fail depending on the operation requested.
    18486 09:15:45 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
    18487 09:15:45 (0) **
    18488 09:15:45 (0) ** WMI ProgID registrations: ....................................... ....................................... ............. OK.
    18489 09:15:45 (0) ** WMI provider DCOM registrations: ....................................... ....................................... ...... OK.
    18490 09:15:45 (2) !! WARNING: WMI provider CIM registrations missing for the following provider(s): ...................................... 3 WARNING(S)!
    18491 09:15:45 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3VlanEvent')
    18492 09:15:45 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    18493 09:15:45 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3TeamEvent')
    18494 09:15:45 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    18495 09:15:45 (0) ** - ROOT/INTELNCS, NcsEvent (i.e. WMI Class 'IANet_802dot3AdapterEvent')
    18496 09:15:45 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    18497 09:15:45 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
    18498 09:15:45 (0) **    while the CIM registration is wrong or missing. This can be due to:
    18499 09:15:45 (0) **    - a de-installation of the software.
    18500 09:15:45 (0) **    - a deletion of some CIM registration information.
    18501 09:15:45 (0) ** => You can correct the CIM configuration by:
    18502 09:15:45 (0) **    - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
    18503 09:15:45 (0) **    Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
    18504 09:15:45 (0) **          (This list can be built on a similar and working WMI Windows installation)
    18505 09:15:45 (0) **          The following command line must be used:
    18506 09:15:45 (0) **          i.e. 'WMIDiag CorrelateClassAndProvider'
    18507 09:15:45 (0) **    - Re-installing the software.
    18508 09:15:45 (0) ** => If the software has been de-installed intentionally, then this information must be
    18509 09:15:45 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
    18510 09:15:45 (0) **    registration data and its set of associated classes.
    18511 09:15:45 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\INTELNCS path __Win32Provider Where Name='NcsEvent' DELETE'
    18512 09:15:45 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\INTELNCS Class IANet_802dot3AdapterEvent DELETE'
    18513 09:15:45 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,
    18514 09:15:45 (0) **    the namespace and ALL its content can be ENTIRELY deleted.
    18515 09:15:45 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT path __NAMESPACE Where Name='INTELNCS' DELETE'
    18516 09:15:45 (0) **
    18517 09:15:45 (0) ** WMI provider CLSIDs: ....................................... ....................................... .................. OK.
    18518 09:15:45 (0) ** WMI providers EXE/DLL availability: ....................................... ....................................... ... OK.
    18519 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18520 09:15:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    18521 09:15:45 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
    18522 09:15:45 (0) **        - REMOVED ACE:
    18523 09:15:45 (0) **          ACEType:  &h0
    18524 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18525 09:15:45 (0) **          ACEFlags: &h0
    18526 09:15:45 (0) **          ACEMask:  &h1
    18527 09:15:45 (0) **                    DCOM_RIGHT_EXECUTE
    18528 09:15:45 (0) **
    18529 09:15:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    18530 09:15:45 (0) **    Removing default security will cause some operations to fail!
    18531 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
    18532 09:15:45 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    18533 09:15:45 (0) **
    18534 09:15:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    18535 09:15:45 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
    18536 09:15:45 (0) **        - REMOVED ACE:
    18537 09:15:45 (0) **          ACEType:  &h0
    18538 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18539 09:15:45 (0) **          ACEFlags: &h0
    18540 09:15:45 (0) **          ACEMask:  &h1
    18541 09:15:45 (0) **                    DCOM_RIGHT_EXECUTE
    18542 09:15:45 (0) **
    18543 09:15:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    18544 09:15:45 (0) **    Removing default security will cause some operations to fail!
    18545 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
    18546 09:15:45 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    18547 09:15:45 (0) **
    18548 09:15:45 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
    18549 09:15:45 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
    18550 09:15:45 (0) **        - REMOVED ACE:
    18551 09:15:45 (0) **          ACEType:  &h0
    18552 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18553 09:15:45 (0) **          ACEFlags: &h0
    18554 09:15:45 (0) **          ACEMask:  &h1
    18555 09:15:45 (0) **                    DCOM_RIGHT_EXECUTE
    18556 09:15:45 (0) **
    18557 09:15:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    18558 09:15:45 (0) **    Removing default security will cause some operations to fail!
    18559 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
    18560 09:15:45 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
    18561 09:15:45 (0) **
    18562 09:15:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ....................................... .............................. MODIFIED.
    18563 09:15:45 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
    18564 09:15:45 (0) **        - ACTUAL ACE:
    18565 09:15:45 (0) **          ACEType:  &h0
    18566 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18567 09:15:45 (0) **          ACEFlags: &h2
    18568 09:15:45 (0) **                    CONTAINER_INHERIT_ACE
    18569 09:15:45 (0) **          ACEMask:  &h1
    18570 09:15:45 (0) **                    WBEM_ENABLE
    18571 09:15:45 (0) **        - EXPECTED ACE:
    18572 09:15:45 (0) **          ACEType:  &h0
    18573 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18574 09:15:45 (0) **          ACEFlags: &h12
    18575 09:15:45 (0) **                    CONTAINER_INHERIT_ACE
    18576 09:15:45 (0) **                    INHERITED_ACE
    18577 09:15:45 (0) **          ACEMask:  &h13
    18578 09:15:45 (0) **                    WBEM_ENABLE
    18579 09:15:45 (0) **                    WBEM_METHOD_EXECUTE
    18580 09:15:45 (0) **                    WBEM_WRITE_PROVIDER
    18581 09:15:45 (0) **
    18582 09:15:45 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
    18583 09:15:45 (0) **    This will cause some operations to fail!
    18584 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    18585 09:15:45 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
    18586 09:15:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
    18587 09:15:45 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
    18588 09:15:45 (0) **       A specific WMI application can always require a security setup different
    18589 09:15:45 (0) **       than the WMI security defaults.
    18590 09:15:45 (0) **
    18591 09:15:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ....................................... .............................. MODIFIED.
    18592 09:15:45 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
    18593 09:15:45 (0) **        - ACTUAL ACE:
    18594 09:15:45 (0) **          ACEType:  &h0
    18595 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18596 09:15:45 (0) **          ACEFlags: &h2
    18597 09:15:45 (0) **                    CONTAINER_INHERIT_ACE
    18598 09:15:45 (0) **          ACEMask:  &h1
    18599 09:15:45 (0) **                    WBEM_ENABLE
    18600 09:15:45 (0) **        - EXPECTED ACE:
    18601 09:15:45 (0) **          ACEType:  &h0
    18602 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18603 09:15:45 (0) **          ACEFlags: &h12
    18604 09:15:45 (0) **                    CONTAINER_INHERIT_ACE
    18605 09:15:45 (0) **                    INHERITED_ACE
    18606 09:15:45 (0) **          ACEMask:  &h13
    18607 09:15:45 (0) **                    WBEM_ENABLE
    18608 09:15:45 (0) **                    WBEM_METHOD_EXECUTE
    18609 09:15:45 (0) **                    WBEM_WRITE_PROVIDER
    18610 09:15:45 (0) **
    18611 09:15:45 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
    18612 09:15:45 (0) **    This will cause some operations to fail!
    18613 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
    18614 09:15:45 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
    18615 09:15:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
    18616 09:15:45 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
    18617 09:15:45 (0) **       A specific WMI application can always require a security setup different
    18618 09:15:45 (0) **       than the WMI security defaults.
    18619 09:15:45 (0) **
    18620 09:15:45 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ....................................... .............................. MODIFIED.
    18621 09:15:45 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
    18622 09:15:45 (0) **        - REMOVED ACE:
    18623 09:15:45 (0) **          ACEType:  &h0
    18624 09:15:45 (0) **                    ACCESS_ALLOWED_ACE_TYPE
    18625 09:15:45 (0) **          ACEFlags: &h12
    18626 09:15:45 (0) **                    CONTAINER_INHERIT_ACE
    18627 09:15:45 (0) **                    INHERITED_ACE
    18628 09:15:45 (0) **          ACEMask:  &h13
    18629 09:15:45 (0) **                    WBEM_ENABLE
    18630 09:15:45 (0) **                    WBEM_METHOD_EXECUTE
    18631 09:15:45 (0) **                    WBEM_WRITE_PROVIDER
    18632 09:15:45 (0) **
    18633 09:15:45 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
    18634 09:15:45 (0) **    Removing default security will cause some operations to fail!
    18635 09:15:45 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
    18636 09:15:45 (0) **    For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
    18637 09:15:45 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
    18638 09:15:45 (0) **       The security diagnostic is based on the WMI namespace expected defaults.
    18639 09:15:45 (0) **       A specific WMI application can always require a security setup different
    18640 09:15:45 (0) **       than the WMI security defaults.
    18641 09:15:45 (0) **
    18642 09:15:45 (0) **
    18643 09:15:45 (0) ** DCOM security warning(s) detected: ....................................... ....................................... .... 0.
    18644 09:15:45 (0) ** DCOM security error(s) detected: ....................................... ....................................... ...... 3.
    18645 09:15:45 (0) ** WMI security warning(s) detected: ....................................... ....................................... ..... 0.
    18646 09:15:45 (0) ** WMI security error(s) detected: ....................................... ....................................... ....... 3.
    18647 09:15:45 (0) **
    18648 09:15:45 (1) !! ERROR: Overall DCOM security status: ....................................... ....................................... .. ERROR!
    18649 09:15:45 (1) !! ERROR: Overall WMI security status: ....................................... ....................................... ... ERROR!
    18650 09:15:45 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    18651 09:15:45 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ....................................... ....................................... .. 2.
    18652 09:15:45 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
    18653 09:15:45 (0) **   'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
    18654 09:15:45 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    18655 09:15:45 (0) **   'select * from MSFT_SCMEventLogEvent'
    18656 09:15:45 (0) **
    18657 09:15:45 (0) ** WMI TIMER instruction(s): ....................................... ....................................... ............. NONE.
    18658 09:15:45 (0) ** INFO: WMI ADAP status: ....................................... ....................................... ................ 1.
    18659 09:15:45 (0) ** => The WMI ADAP process is currently running (1).
    18660 09:15:45 (0) **    Some WMI performance classes could be missing at the time WMIDiag was executed.
    18661 09:15:45 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: ....................................... ............................. 1 NAMESPACE(S)!
    18662 09:15:45 (0) ** - ROOT/SERVICEMODEL.
    18663 09:15:45 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    18664 09:15:45 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    18665 09:15:45 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    18666 09:15:45 (0) **    i.e. 'WMIC.EXE /NODE:"D2PGV571" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    18667 09:15:45 (0) **
    18668 09:15:45 (0) ** WMI MONIKER CONNECTIONS: ....................................... ....................................... .............. OK.
    18669 09:15:45 (0) ** WMI CONNECTIONS: ... OK.
    18670 09:15:45 (0) ** WMI GET operations: ....................................... ....................................... ................... OK.
    18671 09:15:45 (0) ** WMI MOF representations: ....................................... ....................................... .............. OK.
    18672 09:15:45 (0) ** WMI QUALIFIER access operations: ....................................... ....................................... ...... OK.
    18673 09:15:45 (0) ** WMI ENUMERATION operations: ....................................... ....................................... ........... OK.
    18674 09:15:45 (0) ** WMI EXECQUERY operations: ....................................... ....................................... ............. OK.
    18675 09:15:45 (0) ** WMI GET VALUE operations: ....................................... ....................................... ............. OK.
    18676 09:15:45 (0) ** WMI WRITE operations: ....................................... ....................................... ................. NOT TESTED.
    18677 09:15:45 (0) ** WMI PUT operations: ....................................... ....................................... ................... NOT TESTED.
    18678 09:15:45 (0) ** WMI DELETE operations: ....................................... ....................................... ................ NOT TESTED.
    18679 09:15:45 (0) ** WMI static instances retrieved: ....................................... ....................................... ....... 604.
    18680 09:15:45 (0) ** WMI dynamic instances retrieved: ....................................... ....................................... ...... 0.
    18681 09:15:45 (0) ** WMI instance request cancellations (to limit performance impact): ....................................... ............ 0.
    18682 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18683 09:15:45 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    18684 09:15:45 (0) **   DCOM: ... 0.
    18685 09:15:45 (0) **   WINMGMT: ... 0.
    18686 09:15:45 (0) **   WMIADAPTER: ... 0.
    18687 09:15:45 (0) **
    18688 09:15:45 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    18689 09:15:45 (0) **   DCOM: ... 0.
    18690 09:15:45 (0) **   WINMGMT: ... 0.
    18691 09:15:45 (0) **   WMIADAPTER: ... 0.
    18692 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18693 09:15:45 (0) ** WMI Registry key setup: ....................................... ....................................... ............... OK.
    18694 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18695 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18696 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18697 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18698 09:15:45 (0) **
    18699 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18700 09:15:45 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    18701 09:15:45 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    18702 09:15:45 (0) **
    18703 09:15:45 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\BRETT\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_D2PGV571_2010.09.14_09.11.33.LOG' for details.
    18704 09:15:45 (0) **
    18705 09:15:45 (0) ** WMIDiag v2.0 ended on Tuesday, September 14, 2010 at 09:15 (W:87 E:26 S:1).

    Dr Jay

    • Malware Removal Specialist


    • Specialist
    • Moderator emeritus
    • Thanked: 119
    • Experience: Guru
    • OS: Windows 10
    Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
    « Reply #46 on: September 16, 2010, 04:09:53 AM »
    Please download SystemLook from one of the links below and save it to your Desktop.
    Download Mirror #1
    Download Mirror #2
    • Double-click SystemLook.exe to run it.
    • Copy the content of the following codebox into the main textfield:
    Code: [Select]
    :filefind
    FASTPROX.DLL
    WBEMPROX.DLL
    • Click the Look button to start the scan.
    • When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
    Note: The log can also be found on your Desktop entitled SystemLook.txt
    ~Dr Jay

    Mr.Hopeless

      Topic Starter


      Rookie

      Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
      « Reply #47 on: October 04, 2010, 06:11:26 PM »
      SystemLook 04.09.10 by jpshortstuff
      Log created at 19:47 on 04/10/2010 by Brett
      Administrator - Elevation successful

      ========== filefind ==========

      Searching for "FASTPROX.DLL"
      C:\Documents and Settings\Deborah\Desktop\i386\fastprox.dll   --a---- 472064 bytes   [02:08 22/04/2005]   [10:00 04/08/2004] C28500101BC66FDABD830F8DE51A59A0
      C:\WINDOWS\$hf_mig$\KB956572\SP3QFE\fastprox.dll   --a---- 473600 bytes   [03:14 17/04/2009]   [10:56 09/02/2009] 600519339671DCFA3DD20216A19817BB
      C:\WINDOWS\$NtServicePackUninstall$\fastprox.dll   -----c- 472064 bytes   [23:00 05/10/2008]   [10:00 04/08/2004] C28500101BC66FDABD830F8DE51A59A0
      C:\WINDOWS\$NtUninstallKB956572$\fastprox.dll   -----c- 472064 bytes   [04:58 17/04/2009]   [00:11 14/04/2008] 60027BEA3E76D7DD8D96C02432BFDE82
      C:\WINDOWS\ServicePackFiles\i386\fastprox.dll   ------- 472064 bytes   [16:47 04/09/2008]   [00:11 14/04/2008] 60027BEA3E76D7DD8D96C02432BFDE82
      C:\WINDOWS\system32\dllcache\fastprox.dll   ------- 473600 bytes   [03:14 17/04/2009]   [12:10 09/02/2009] 378A0AEFB11D8B0DC8C27B9F7604B88D
      C:\WINDOWS\system32\wbem\fastprox.dll   --a---- 473600 bytes   [18:01 10/08/2004]   [12:10 09/02/2009] 378A0AEFB11D8B0DC8C27B9F7604B88D

      Searching for "WBEMPROX.DLL"
      C:\Documents and Settings\Deborah\Desktop\i386\wbemprox.dll   --a---- 18944 bytes   [02:08 22/04/2005]   [10:00 04/08/2004] 851547797C2A7F8A04841644C471A567
      C:\WINDOWS\$NtServicePackUninstall$\wbemprox.dll   -----c- 18944 bytes   [23:00 05/10/2008]   [10:00 04/08/2004] 851547797C2A7F8A04841644C471A567
      C:\WINDOWS\ServicePackFiles\i386\wbemprox.dll   ------- 18944 bytes   [16:49 04/09/2008]   [00:12 14/04/2008] 205ADD80FF8099B1A8101EB490B933D1
      C:\WINDOWS\system32\wbem\wbemprox.dll   --a---- 18944 bytes   [18:01 10/08/2004]   [00:12 14/04/2008] 205ADD80FF8099B1A8101EB490B933D1

      -= EOF =-

      carolyny476

      • Guest
      Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
      « Reply #48 on: October 04, 2010, 09:17:20 PM »
      Please visit this webpage for a tutorial on downloading and running ComboFix:

      http://www.bleepingcomputer.com/combofix/how-to-use-combofix

      See the area: Using ComboFix, and when done, post the log back here.

      Thanks for sharing the link!

      Dr Jay

      • Malware Removal Specialist


      • Specialist
      • Moderator emeritus
      • Thanked: 119
      • Experience: Guru
      • OS: Windows 10
      Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
      « Reply #49 on: October 09, 2010, 03:10:52 PM »
      Before we can continue, I need to know how your computer is running, Mr Hopeless.
      ~Dr Jay

      Mr.Hopeless

        Topic Starter


        Rookie

        Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
        « Reply #50 on: October 10, 2010, 01:54:01 PM »
        It's making these ticking noises, they usually start after I turn on the modem.  The sound works okay.  Internet speed seems to be okay, no internet popups, etc.  I'm getting those windows about the WMI change noted above.

        Dr Jay

        • Malware Removal Specialist


        • Specialist
        • Moderator emeritus
        • Thanked: 119
        • Experience: Guru
        • OS: Windows 10
        Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
        « Reply #51 on: October 10, 2010, 01:57:05 PM »
        What I highly recommend now is a reformat and a reinstallation of Windows XP.

        Please let me know if you are prepared to do so.


        So, with that said, do you have your Windows XP CD?

        Guides for format and reinstall: http://www.geekpolice.net/tutorials-guides-f13/how-to-reformat-and-reinstall-your-operating-system-t15119.htm#95115

        http://www.helpmyos.com/tutorials-software-alternatives-to-proprietary-f19/how-to-reformat-and-reinstall-your-operating-system-the-easy-way-t1307.htm#3143
        ~Dr Jay

        Mr.Hopeless

          Topic Starter


          Rookie

          Re: sound goes out, yadaying running, Downloader.Tiny.BB, Help!!!
          « Reply #52 on: November 24, 2010, 08:22:56 PM »
          I have reinstalled Windows.  Thanks for the effort.  This thread can be closed.