Root cimv2 ошибка

  • Remove From My Forums

  • Question

  • I’m trying to set up HyperV Manager (6.1.7601.17514) on a x64 Win7 machine, connecting to a 6.1.7600 server (Hyper-V core server?) The Win7 is itself a VM, freshly minted for the sole purpose of providing HV Management to the existing server. I have a physical
    Win7 system on which Manager is running fine, but that machine is destined for retirement soon — so I’m trying to replace it with a Win7 VM (hosted on a Win 8.1 system.)

    I’m using HVRemote 1.08 and all machines involved are in the same workgroup; i.e., no domains involved at all. I’m using the same logon credentials on the Win7 VM that I’m using on the old Win7 machine so I didn’t think I’d need to add another user on the
    server; nevertheless after receiving the rootcimv2 error I went ahead and tried it. Got an «error» saying there was already a user by that name.

    So, I’m at a loss as to how to proceed at this point. Running (from the Win7 VM)
    HVRemote /show /target:<servername> shows me the failure to connect to rootcimv2 namespace. Name resolution does seem to be working in both directions.

    I’d appreciate any pointers on how to fix or troubleshoot this issue.

    Thanks in advance,

    Bill

    Bill Cohagan

Источник

Некоторые пользователи Windows 7 время от времени могут сталкиваться с ошибкой 0x80041003. Ее предвестником, например, может быть зависание ПК, от которого можно избавиться лишь его перезагрузкой. В Просмотре событий вы можете найти следующую информацию по ошибке:

Event filter with query “SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA “Win32_Processor” AND TargetInstance.LoadPercentage > 99″ could not be reactivated in namespace “//./root/CIMV2” because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected

В сегодняшней статье мы рассмотрим два метода, которые – по заявлению многих пользователей – могут разрешить ошибку 0x80041003 в Windows 7. Первый метод – применение скрипта VBS, а второй – использование средства, разработанного самой компанией Майкрософт.

Ошибка 0x80041003 в Windows 7: методы решения

Метод №1 Выполнение скрипта VBS

  • Создайте на своем рабочем столе простой текстовый документ;
  • откройте документ и вставьте в него следующий скрипт:
    • strComputer = “.”
      Set objWMIService = GetObject(“winmgmts:” _
      & “{impersonationLevel=impersonate}!\” _
      & strComputer & “rootsubscription”)Set obj1 = objWMIService.Get(“__EventFilter.Name=’BVTFilter’”)

      set obj2set = obj1.Associators_(“__FilterToConsumerBinding”)

      set obj3set = obj1.References_(“__FilterToConsumerBinding”)

      For each obj2 in obj2set
      WScript.echo “Deleting the object”
      WScript.echo obj2.GetObjectText_
      obj2.Delete_
      next

      For each obj3 in obj3set
      WScript.echo “Deleting the object”
      WScript.echo obj3.GetObjectText_
      obj3.Delete_
      next

      WScript.echo “Deleting the object”
      WScript.echo obj1.GetObjectText_
      obj1.Delete_

  • переименуйте данный документ в fixeventid10 и замените его расширение на .VBS – получиться у вас должен файл fixeventid10.vbs;
  • дважды кликните на этот файл, чтобы запустить его;
  • в Просмотре событий Windows 7 удалите все логи события 10, которые относятся к ошибке 0x80041003, чтобы те больше не мешались вам в будущем.

Метод №2 Запуск Fix It от Майкрософт

  • Скачайте с официального сайта Майкрософт средство Fix It;
  • запустите его и следуйте указаниям на своем экране;
  • протестируйте систему и проверьте, была ли устранена ошибка 0x80041003.

Мы надеемся, что данный материал помог вам избавиться от ошибки 0x80041003, и вы продолжили спокойно использовать Windows 7.

Источник

Hi all,

I’ve been having troubles running a particular installer which runs fine on one machine, but errors out on another.  After a lot of digging through logs, I’m  sure that the issue boils down to the WMI failing during Initialization.  When I go to My Computer >Manage > WMI Control >Properties, the general tab displays an error stating «Failed to connect to <local computer> because WMI:  Initialization failure».   If I try to connect using wbemtest.exe, I get a similar error when connecting to rootcimv2 (Number: 0x80041014    Facility: WMI   Description: Initialization failure).

I ran the WMIDIAG util, and have copied the resulting output.  Can anyone please help me decode this output?  Any ideas on how to get the WMI to initialize normally?

This is on Windows 2003

Thanks,
wrguy

.1428 05:43:29 (0) ** WMIDiag v2.0 started on 22 September 2009 at 05:43.
.1429 05:43:29 (0) ** 
.1430 05:43:29 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
.1431 05:43:29 (0) ** 
.1432 05:43:29 (0) ** This script is not supported under any Microsoft standard support program or service.
.1433 05:43:29 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1434 05:43:29 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1435 05:43:29 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1436 05:43:29 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1437 05:43:29 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1438 05:43:29 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1439 05:43:29 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1440 05:43:29 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1441 05:43:29 (0) ** of the possibility of such damages.
.1442 05:43:29 (0) ** 
.1443 05:43:29 (0) ** 
.1444 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1445 05:43:29 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1446 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1447 05:43:29 (0) ** 
.1448 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1449 05:43:29 (0) ** Windows Server 2003 - No service pack - 32-bit (3790) - User 'DELLSC1420ADMINISTRATOR' on computer 'DELLSC1420'.
.1450 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1451 05:43:29 (0) ** Environment: ........................................................................................................ OK..
.1452 05:43:29 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1453 05:43:29 (0) ** There are no missing WMI repository files: .......................................................................... OK.
.1454 05:43:29 (0) ** WMI repository state: ............................................................................................... N/A.
.1455 05:43:29 (0) ** BEFORE running WMIDiag:
.1456 05:43:29 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1457 05:43:29 (0) ** - Disk free space on 'C:': .......................................................................................... 7913 MB.
.1458 05:43:29 (0) **   - INDEX.BTR,                     2326528 bytes,      13/01/2008 17:41:33
.1459 05:43:29 (0) **   - MAPPING.VER,                   4 bytes,            13/01/2008 17:41:33
.1460 05:43:29 (0) **   - MAPPING1.MAP,                  7464 bytes,         22/09/2009 05:29:16
.1461 05:43:29 (0) **   - MAPPING2.MAP,                  7464 bytes,         13/01/2008 17:41:33
.1462 05:43:29 (0) **   - OBJECTS.DATA,                  12779520 bytes,     13/01/2008 17:41:32
.1463 05:43:29 (0) ** AFTER running WMIDiag:
.1464 05:43:29 (0) ** The WMI repository has a size of: ................................................................................... 14 MB.
.1465 05:43:29 (0) ** - Disk free space on 'C:': .......................................................................................... 7912 MB.
.1466 05:43:29 (0) **   - INDEX.BTR,                     2326528 bytes,      13/01/2008 17:41:33
.1467 05:43:29 (0) **   - MAPPING.VER,                   4 bytes,            13/01/2008 17:41:33
.1468 05:43:29 (0) **   - MAPPING1.MAP,                  7464 bytes,         22/09/2009 05:29:16
.1469 05:43:29 (0) **   - MAPPING2.MAP,                  7464 bytes,         13/01/2008 17:41:33
.1470 05:43:29 (0) **   - OBJECTS.DATA,                  12779520 bytes,     13/01/2008 17:41:32
.1471 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1472 05:43:29 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
.1473 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1474 05:43:29 (0) ** DCOM Status: ........................................................................................................ OK.
.1475 05:43:29 (0) ** WMI registry setup: ................................................................................................. OK.
.1476 05:43:29 (0) ** WMI Service has no dependents: ...................................................................................... OK.
.1477 05:43:29 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1478 05:43:29 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1479 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1480 05:43:29 (0) ** WMI service DCOM setup: ............................................................................................. OK.
.1481 05:43:29 (0) ** WMI components DCOM registrations: .................................................................................. OK.
.1482 05:43:29 (0) ** WMI ProgID registrations: ........................................................................................... OK.
.1483 05:43:29 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1484 05:43:29 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1485 05:43:29 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1486 05:43:29 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1487 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1488 05:43:29 (0) ** Overall DCOM security status: ....................................................................................... OK.
.1489 05:43:29 (0) ** Overall WMI security status: ........................................................................................ OK.
.1490 05:43:29 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1491 05:43:29 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1492 05:43:29 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1493 05:43:29 (1) !! ERROR: WMI ADAP status: ............................................................................................. NOT AVAILABLE.
.1494 05:43:29 (0) **    You can start the WMI AutoDiscovery/AutoPurge (ADAP) process to resynchronize
.1495 05:43:29 (0) **    the performance counters with the WMI performance classes with the following commands:
.1496 05:43:29 (0) **    i.e. 'WINMGMT.EXE /CLEARADAP'
.1497 05:43:29 (0) **    i.e. 'WINMGMT.EXE /RESYNCPERF'
.1498 05:43:29 (0) **    The ADAP process logs informative events in the Windows NT event log.
.1499 05:43:29 (0) **    More information can be found on MSDN at:
.1500 05:43:29 (0) **    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/wmi_adap_event_log_events.asp
.1501 05:43:29 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1502 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1503 05:43:29 (0) ** 
.1504 05:43:29 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 5 ERROR(S)!
.1505 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1506 05:43:29 (0) ** - Root, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1507 05:43:29 (0) ** - Root/Default, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1508 05:43:29 (0) ** - Root/CIMv2, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1509 05:43:29 (0) ** - Root/WMI, 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons.
.1510 05:43:29 (0) ** 
.1511 05:43:29 (0) ** WMI GET operations: ................................................................................................. OK.
.1512 05:43:29 (0) ** WMI MOF representations: ............................................................................................ OK.
.1513 05:43:29 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1514 05:43:29 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1515 05:43:29 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1516 05:43:29 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1517 05:43:29 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1518 05:43:29 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1519 05:43:29 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1520 05:43:29 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1521 05:43:29 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1522 05:43:29 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1523 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1524 05:43:29 (0) ** 
.1525 05:43:29 (0) ** 6 error(s) 0x80041014 - (WBEM_E_INITIALIZATION_FAILURE) Component such as a provider failed to initialize for internal reasons
.1526 05:43:29 (0) ** => This error is typically a WMI system error. WMI system errors can find their origin in:
.1527 05:43:29 (0) **    - Failing WMI system components (see any missing WMI system files or DCOM registration
.1528 05:43:29 (0) **      issues previously mentioned).
.1529 05:43:29 (0) **    - Failing WMI providers (see any DCOM registration issues previously mentioned).
.1530 05:43:29 (0) **    - a WMI repository corruption.
.1531 05:43:29 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
.1532 05:43:29 (0) **      to validate the WMI repository operations.
.1533 05:43:29 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
.1534 05:43:29 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
.1535 05:43:29 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
.1536 05:43:29 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
.1537 05:43:29 (0) **      the WMI repository must be reconstructed.
.1538 05:43:29 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1539 05:43:29 (0) **          otherwise some applications may fail after the reconstruction.
.1540 05:43:29 (0) **          This can be achieved with the following command:
.1541 05:43:29 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1542 05:43:29 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1543 05:43:29 (0) **          ALL fixes previously mentioned.
.1544 05:43:29 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1545 05:43:29 (0) ** 
.1546 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1547 05:43:29 (0) ** WMI Registry key setup: ............................................................................................. OK.
.1548 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1549 05:43:29 (1) !! ERROR: MOF file(s) present in the WBEM folder not referenced in the Auto-Recovery list: ............................. 15 ERROR(S)!
.1550 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMCLIEGALIASES.MFL (*)
.1551 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMCLIEGALIASES.MOF (*)
.1552 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMDNSETW.MOF
.1553 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMIISWMI.MFL
.1554 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMNCPROV.MFL (*)
.1555 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMNCPROV.MOF (*)
.1556 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSCRCONS.MFL (*)
.1557 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSCRCONS.MOF (*)
.1558 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSMTPCONS.MFL (*)
.1559 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSMTPCONS.MOF (*)
.1560 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMVDSHBAAPI.MOF
.1561 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMVDSHBAREM.MOF
.1562 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWBEMCONS.MFL (*)
.1563 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWBEMCONS.MOF (*)
.1564 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWLBSPROV.MFL
.1565 05:43:29 (0) ** => After fixing all other issues previously mentioned, if the WMI repository is rebuilt,
.1566 05:43:29 (0) **    the listed MOF file(s) will not be recompiled, and therefore the definition they contain
.1567 05:43:29 (0) **    will not be available in the WMI repository.
.1568 05:43:29 (0) ** => You must manually recompile the MOF file(s) with the 'MOFCOMP.EXE <FileName.MOF>' command.
.1569 05:43:29 (0) ** => If you want the MOF file(s) to be part of the Auto-Recovery list, make sure the
.1570 05:43:29 (0) **    statement '#PRAGMA AUTORECOVER' is included.
.1571 05:43:29 (0) **    Note: MOF file(s) marked with (*) are NEVER included AT SETUP in the auto-recovery process.
.1572 05:43:29 (0) **          MOF file(s) containing UNINSTALL statements (i.e. '#PRAGMA DELETECLASS') should NEVER be included in the auto-recovery process.
.1573 05:43:29 (0) **          Refer to the list of MOF files below NOT containing the '#PRAGMA AUTORECOVER' statement' for more information.
.1574 05:43:29 (0) ** 
.1575 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1576 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1577 05:43:29 (1) !! ERROR: MOF file(s) not containing the '#PRAGMA AUTORECOVER' statement: .............................................. 17 FILE(S)!
.1578 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMDNSETW.MOF
.1579 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMNCPROV.MFL (DELETE)
.1580 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMNCPROV.MOF (DELETE)
.1581 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSCRCONS.MFL
.1582 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSCRCONS.MOF
.1583 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSMTPCONS.MFL
.1584 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSMTPCONS.MOF
.1585 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMVDSHBAREM.MOF (DELETE)
.1586 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWBEMCONS.MFL
.1587 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWBEMCONS.MOF
.1588 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMSCM.MOF (DELETE) (*)
.1589 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWMITIMEP.MOF (*)
.1590 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWMITIMEP.MFL (*)
.1591 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMCLUSWMI.MOF (*)
.1592 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMNLBMPROV.MOF (*)
.1593 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMCMDEVTGPROV.MOF (*)
.1594 05:43:29 (0) ** - C:WINDOWSSYSTEM32WBEMWHQLPROV.MOF (*)
.1595 05:43:29 (0) ** => MOF file(s) marked with (*) are INCLUDED in the AUTO-RECOVERY LIST even if they do NOT contain the '#PRAGMA AUTORECOVER' statement.
.1596 05:43:29 (0) **    If the WMI repository is rebuilt, the listed MOF files not included in the AUTO-RECOVERY LIST and
.1597 05:43:29 (0) **    missing the '#PRAGMA AUTORECOVERY' statement when they are compiled the first time will NOT
.1598 05:43:29 (0) **    be recompiled during the repository reconstruction.
.1599 05:43:29 (0) **    Note: If you want the MOF file to be part of the AUTO-RECOVERY LIST, make sure the statement '#PRAGMA AUTORECOVER'
.1600 05:43:29 (0) **          is included and recompile the MOF/MFL with the following command:
.1601 05:43:29 (0) **          i.e. 'MOFCOMP.EXE <FileName.MOF>'
.1602 05:43:29 (0) ** ac
.1603 05:43:29 (0) ** => MOF file(s) marked with (DELETE) contains class and instance DELETE statements.
.1604 05:43:29 (0) **    Usually, MOF with DELETE statements are used to UNinstall components and they should NOT be listed in the AUTORECOVERY LIST
.1605 05:43:29 (0) **    and therefore they should NOT specify the '#PRAGMA AUTORECOVER' statement.
.1606 05:43:29 (0) **    Note: It happens that some MOF files do contain DELETE statements for installation purposes to delete
.1607 05:43:29 (0) **          existing information before it is recreated.
.1608 05:43:29 (0) ** 
.1609 05:43:29 (0) **    Note: It is also possible that the application implemented its own recovery mechanism.
.1610 05:43:29 (0) **          In that case, no action is required. You must verify with the application vendor
.1611 05:43:29 (0) **          if the application has this capability (i.e. Microsoft SMS)
.1612 05:43:29 (0) ** 
.1613 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1614 05:43:29 (0) ** 
.1615 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1616 05:43:29 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1617 05:43:29 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1618 05:43:29 (0) ** 
.1619 05:43:29 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:DOCUMENTS AND SETTINGSADMINISTRATORLOCAL SETTINGSTEMPWMIDIAG-V2.0_2003_.SRV.RTM.32_DELLSC1420_2009.09.22_05.42.52.LOG' for details.
.1620 05:43:29 (0) ** 
.1621 05:43:29 (0) ** WMIDiag v2.0 ended on 22 September 2009 at 05:43 (W:27 E:15 S:1).

Open in new window

Источник

Как исправить ошибку 0x80041003 в Windows 7?

Некоторые пользователи Windows 7 время от времени могут сталкиваться с ошибкой 0x80041003. Ее предвестником, например, может быть зависание ПК, от которого можно избавиться лишь его перезагрузкой. В Просмотре событий вы можете найти следующую информацию по ошибке:

Event filter with query “SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA “Win32_Processor” AND TargetInstance.LoadPercentage > 99″ could not be reactivated in namespace “//./root/CIMV2” because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected

В сегодняшней статье мы рассмотрим два метода, которые — по заявлению многих пользователей — могут разрешить ошибку 0x80041003 в Windows 7. Первый метод — применение скрипта VBS, а второй — использование средства, разработанного самой компанией Майкрософт.

Ошибка 0x80041003 в Windows 7: методы решения

0x80041003.png

Метод №1 Выполнение скрипта VBS

  • Создайте на своем рабочем столе простой текстовый документ;
  • откройте документ и вставьте в него следующий скрипт:
    • strComputer = «.»Set objWMIService = GetObject(«winmgmts:» _& «{impersonationLevel=impersonate}!» _& strComputer & «rootsubscription»)Set obj1 = objWMIService.Get(«__EventFilter.Name=’BVTFilter’»)

      set obj2set = obj1.Associators_(«__FilterToConsumerBinding»)

      set obj3set = obj1.References_(«__FilterToConsumerBinding»)

      For each obj2 in obj2setWScript.echo «Deleting the object»WScript.echo obj2.GetObjectText_obj2.Delete_next

      For each obj3 in obj3setWScript.echo «Deleting the object»WScript.echo obj3.GetObjectText_obj3.Delete_next

      WScript.echo «Deleting the object»WScript.echo obj1.GetObjectText_obj1.Delete_

  • переименуйте данный документ в fixeventid10 и замените его расширение на .VBS — получиться у вас должен файл fixeventid10.vbs;
  • дважды кликните на этот файл, чтобы запустить его;
  • в Просмотре событий Windows 7 удалите все логи события 10, которые относятся к ошибке 0x80041003, чтобы те больше не мешались вам в будущем.

Метод №2 Запуск Fix It от Майкрософт

  • Скачайте с официального сайта Майкрософт средство Fix It;
  • запустите его и следуйте указаниям на своем экране;
  • протестируйте систему и проверьте, была ли устранена ошибка 0x80041003.

Мы надеемся, что данный материал помог вам избавиться от ошибки 0x80041003, и вы продолжили спокойно использовать Windows 7.

Нашли опечатку? Выделите текст и нажмите Ctrl + Enter

Сообщение об ошибке в разделе Просмотр событий -> Журналы Windows -> Приложение :

Event filter with query “SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA “Win32_Processor” AND TargetInstance.LoadPercentage > 99″ could not be reactivated in namespace “//./root/CIMV2” because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

wmi-error-300x214.png

Ошибка WMI (код события: 10)

Как исправить:

  1. Отключаем контроль учетных записей.
  2. Перезагружаемся в безопасный режим.
  3. Останавливаем службу Инструментарий управления Windows (Windows Management Instrumentation).
  4. Открываем папку c:windowssystem32wbemrepository. На всякий случай содержимое папки копируем в безопасное место, а затем удаляем.
  5. Перезагружаемся.
  6. При первой загрузке возможны проблемы: торможение, подвисания и т.п. Ничего страшного – перезагружаемся еще раз.
  7. Вторая загрузка должна пройти быстро и без помех. Проверяем логи – больше никаких ошибок WMI во время загрузки системы!
  8. Включаем контроль учетных записей обратно.

В заключение следует сказать о том, что данная ошибка классифицируется в Микрософт как некритичная и не влияющая на работоспособность системы. И это действительно так, два года проработал с ней без проблем. Но если есть способ исправить, почему бы это не сделать? ))

Задайте вопрос Быстрый доступ

Администрирование клиентских ОС Windows > Администрирование Windows Vista

  • Вопрос

  • Добрый день!Постоянно в событиях появляется запись об ошибке:

    Event filter with query «SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA «Win32_Processor» AND TargetInstance.LoadPercentage > 99″ could not be reactivated in namespace «//./root/CIMV2» because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

    С чем это связанно и можно ли это победить?3 августа 2009 г. 3:13 Ответить | Цитировать

Ответы

  • Воспользуйтесь скриптом, описанным в данной статье — http://support.microsoft.com/?id=950375
    • Помечено в качестве ответа3 августа 2009 г. 4:09

    3 августа 2009 г. 3:54 Ответить | Цитировать

Все ответы

  • Воспользуйтесь скриптом, описанным в данной статье — http://support.microsoft.com/?id=950375
    • Помечено в качестве ответа3 августа 2009 г. 4:09

    3 августа 2009 г. 3:54 Ответить | Цитировать

  • Спасибо, проверю

    3 августа 2009 г. 4:10 Ответить | Цитировать

Используемые источники:

  • https://gamesqa.ru/kompyutery/0x80041003-10007/
  • https://www.q2w3.ru/2011/03/24/3365/
  • https://social.technet.microsoft.com/forums/exchange/ru-ru/366c12ed-8adc-4b41-8159-bb534383ea0f/-wmi-10

Оценка статьи:

1 звезда2 звезды3 звезды4 звезды5 звезд (пока оценок нет)

Загрузка…

Источник

Hi,

If WMI Test fails with below error.

rootcimv2 Remote WMI access test FAILED
     Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

1. Ensure that Windows Management Instrumentation (WMI) Service is running on Remote System
2. Ensure that all Firewalls are turned off (Windows Firewall, Personal Firewall etc) or allow exception for RPC traffic
3. Execute WMI Diag and check for Error Codes, Reasons and solutions for the issue. Most of the times, WMI Diag result itself gives solution to all errors.

For above error, the reason could be as below in WMI Diag result.

32104 00:05:58 (1) !! ERROR: DCOM Status: ……………………………………………………………………………………. ERROR!
32105 00:05:58 (1) !! ERROR: => The DCOM configuration on this computer is DISABLED

This prevents WMI to work correctly.

You can fix the DCOM configuration by

1. Executing the ‘DCOMCNFG.EXE’ command.
2. Expanding ‘Component Services’ and ‘Computers’ nodes.
3. Editing properties of ‘My Computer’ node.
4. Editing the ‘Default properties’ tab.
5. Activate the ‘Enable Distributed COM on this computer’ checkbox.

From the command line, the DCOM configuration can be corrected with the following command:

‘REG.EXE Add HKLMSOFTWAREMicrosoftOle /v EnableDCOM /t REG_SZ

Источник

Понравилась статья? Поделить с друзьями:
  • Rockstar ошибка 104
  • Rockstar ошибка 1024
  • Rockstar код ошибки 237
  • Rockstar support ошибка при загрузке файла
  • Rockstar launcher ошибка 0xc000007b