Unsupported Operating System x64 win 8.1

Unsupported Operating System x64 win 8.1

Postby pandablu » 23.02.2019, 13:14

hi....i have problem with winupdate ....i have download wsus offline 11.6...after download when i launch update generator it's present this message :

Starting WSUS Offline Update (v. 11.6) at 12.59.49,36...
Checking user's privileges...
Determining system's properties...

ERROR: Unsupported Operating System ( x64).

Ending WSUS Offline Update at 12.59.49,61...

can you help me for resolve my problem?
pandablu
 
Posts: 6
Joined: 23.02.2019, 13:08

Re: Unsupported Operating System x64 win 8.1

Postby Dalai » 23.02.2019, 16:31

Please double click on wsusoffline\client\cmd\DetermineSystemProperties.vbs and post the contents of WOUSystemProperties.txt on your desktop.

Furthermore, please check if WSH (Windows Script Host) is disabled on your system in the following registry keys:
Code: Select all
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows Script Host\Settings
HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings
Look for a value named Enabled and see if it's set to 0.

Regards
Dalai
Dalai
 
Posts: 1025
Joined: 12.07.2016, 21:00

Re: Unsupported Operating System x64 win 8.1

Postby pandablu » 23.02.2019, 17:38

hi....i have control.... the value is on 1, on one key (HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings), on other two it's not present...if i double click on DetermineSystemProperties.vbs there is an error that i attach....i wait your reply.... thanks advance

Error screenshot
Last edited by Dalai on 23.02.2019, 17:45, edited 1 time in total.
Reason: Made the link to the screenshot clickable
pandablu
 
Posts: 6
Joined: 23.02.2019, 13:08

Re: Unsupported Operating System x64 win 8.1

Postby Dalai » 23.02.2019, 17:48

The error occurs when trying to create an object via WMI (Windows Management Instrumentation); specifically in line 404 of script DetermineSystemProperties.vbs. So you have an issue with WMI on your system. You should try to diagnose, and maybe even repair, that with the WMI Diagnosis Utility.

Regards
Dalai
Dalai
 
Posts: 1025
Joined: 12.07.2016, 21:00

Re: Unsupported Operating System x64 win 8.1

Postby pandablu » 23.02.2019, 18:42

i have download wmi diagnostic, and attach log... i think that not resolve my problem...help me please.

Code: Select all
.1502 18:37:16 (0) ** WMIDiag v2.2 started on sabato 23 febbraio 2019 at 18.37.
.1503 18:37:16 (0) **
.1504 18:37:16 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
.1505 18:37:16 (0) **
.1506 18:37:16 (0) ** This script is not supported under any Microsoft standard support program or service.
.1507 18:37:16 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
.1508 18:37:16 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
.1509 18:37:16 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
.1510 18:37:16 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
.1511 18:37:16 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
.1512 18:37:16 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
.1513 18:37:16 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
.1514 18:37:16 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
.1515 18:37:16 (0) ** of the possibility of such damages.
.1516 18:37:16 (0) **
.1517 18:37:16 (0) **
.1518 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1519 18:37:16 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
.1520 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1521 18:37:16 (0) **
.1522 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1523 18:37:16 (0) ** Windows 8.1 - No Service Pack - 64-bit (9600) - User 'BENEDETTA\UTENTE_2' on computer 'BENEDETTA'.
.1524 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1525 18:37:16 (0) ** Environment: ........................................................................................................ OK.
.1526 18:37:16 (0) ** There are no missing WMI system files: .............................................................................. OK.
.1527 18:37:16 (1) !! ERROR: The following WMI repository file(s) is/are missing: ......................................................... 4 ERROR(S)!
.1528 18:37:16 (0) ** - INDEX.BTR
.1529 18:37:16 (0) ** - MAPPING1.MAP
.1530 18:37:16 (0) ** - MAPPING2.MAP
.1531 18:37:16 (0) ** - OBJECTS.DATA
.1532 18:37:16 (0) ** => To fix this issue:
.1533 18:37:16 (0) **    - ENSURE you have all access rights to the WMI repository folder.
.1534 18:37:16 (0) **    - ENSURE you run WMIDiag as an Administrator.
.1535 18:37:16 (0) ** => If the issue is not due to a lack of privileges, and folder/files are really missing, while
.1536 18:37:16 (0) **    the WMI service successfully started, then WMI will rebuild the repository based on the
.1537 18:37:16 (0) **    auto-recovery mechanism. In such a case, WMI repository files shoud be available after the execution
.1538 18:37:16 (0) **    of WMIDiag. Check WMIDiag LOG.
.1539 18:37:16 (0) ** => If the issue is NOT due to a lack of privileges, and folder/files are really missing, while
.1540 18:37:16 (0) **    the WMI service does not start, then additional errors should be displayed (i.e. registry, DCOM, service hosts).
.1541 18:37:16 (0) **    You must fix those issues first!
.1542 18:37:16 (0) ** => After fixing issues, if the files are still missing and if you do not want WMI to rebuild
.1543 18:37:16 (0) **    the WMI repository, then you must restore the WMI repository from a previous backup.
.1544 18:37:16 (0) **    Note: The System State backup or the System Restore snapshot contain a backup of
.1545 18:37:16 (0) **          of the WMI repository.
.1546 18:37:16 (0) ** => If no backup is available, you must rebuild the repository.
.1547 18:37:16 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
.1548 18:37:16 (0) **          otherwise some applications may fail after the reconstruction.
.1549 18:37:16 (0) **          This can be achieved with the following command:
.1550 18:37:16 (0) **          i.e. 'WMIDiag ShowMOFErrors'
.1551 18:37:16 (0) **    Note: Any missing MOF files, or existing MOF files not listed in the Auto-recovery
.1552 18:37:16 (0) **          registry key will be excluded from the WMI repository reconstruction.
.1553 18:37:16 (0) **          This may imply the lost of WMI registration information.
.1554 18:37:16 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
.1555 18:37:16 (0) **          ALL fixes previously mentioned.
.1556 18:37:16 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
.1557 18:37:16 (0) ** => To rebuild the WMI repository, you must:
.1558 18:37:16 (0) **    - Reset the WMI repository
.1559 18:37:16 (0) **      (The WMI repository rebuilt is based on auto-recovery)
.1560 18:37:16 (0) **      i.e. 'WINMGMT /ResetRepository'
.1561 18:37:16 (0) **    OR
.1562 18:37:16 (0) **    - Salvage the WMI repository if you want to attempt the retrieval of good data from the
.1563 18:37:16 (0) **      inconsistent repository
.1564 18:37:16 (0) **      (The repository rebuilt is based on auto-recovery + salvage)
.1565 18:37:16 (0) **      i.e. 'WINMGMT /SalvageRepository'
.1566 18:37:16 (0) **
.1567 18:37:16 (0) ** WMI repository state: ............................................................................................... N/A.
.1568 18:37:16 (0) ** AFTER running WMIDiag:
.1569 18:37:16 (0) ** The WMI repository has a size of: ................................................................................... 28 MB.
.1570 18:37:16 (0) ** - Disk free space on 'C:': .......................................................................................... 103890 MB.
.1571 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1572 18:37:16 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
.1573 18:37:16 (0) ** Windows Firewall Profile: ........................................................................................... PUBLIC.
.1574 18:37:16 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
.1575 18:37:16 (0) ** => This will prevent any WMI remote connectivity to this computer except
.1576 18:37:16 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
.1577 18:37:16 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
.1578 18:37:16 (0) **    - 'Windows Management Instrumentation (WMI-In)'
.1579 18:37:16 (0) **    - 'Windows Management Instrumentation (ASync-In)'
.1580 18:37:16 (0) **    Verify the reported status for each of these three inbound rules below.
.1581 18:37:16 (0) **
.1582 18:37:16 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
.1583 18:37:16 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
.1584 18:37:16 (0) **    - You can adjust the configuration by executing the following command:
.1585 18:37:16 (0) **    i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
.1586 18:37:16 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
.1587 18:37:16 (0) **       You can also enable each individual rule instead of activating the group rule.
.1588 18:37:16 (0) **
.1589 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1590 18:37:16 (0) ** DCOM Status: ........................................................................................................ OK.
.1591 18:37:16 (0) ** WMI registry setup: ................................................................................................. OK.
.1592 18:37:16 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
.1593 18:37:16 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
.1594 18:37:16 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
.1595 18:37:16 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
.1596 18:37:16 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
.1597 18:37:16 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
.1598 18:37:16 (0) **          this can prevent the service/application to work as expected.
.1599 18:37:16 (0) **
.1600 18:37:16 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
.1601 18:37:16 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
.1602 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1603 18:37:16 (1) !! ERROR: WMI service DCOM setup: ...................................................................................... ERROR!
.1604 18:37:16 (0) ** => You can correct the WMI service DCOM configuration by executing the two following commands:
.1605 18:37:16 (0) **    i.e. 'REGSVR32.EXE WMISVC.DLL'
.1606 18:37:16 (0) **    i.e. 'UNSECAPP.EXE /REGSERVER'
.1607 18:37:16 (0) **    i.e. 'FOR %i IN ("C:\WINDOWS\SYSTEM32\WBEM\WBEM*.DLL") DO REGSVR32.EXE /S %i'
.1608 18:37:16 (0) **    Once completed, stop and restart the WMI Service with the following commands:
.1609 18:37:16 (0) **    i.e. 'NET STOP WINMGMT'
.1610 18:37:16 (0) **    i.e. 'NET START WINMGMT'
.1611 18:37:16 (0) ** => Check any additional registry setup errors at the bottom of this report.
.1612 18:37:16 (0) **
.1613 18:37:16 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 8 WARNING(S)!
.1614 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{172BDDF8-CEEA-11D1-8B05-00600806D9B6}\InProcServer32)
.1615 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{47DFBE54-CF76-11D3-B38F-00105A1F473A}\InProcServer32)
.1616 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{5791BC26-CE9C-11D1-97BF-0000F81E849C}\InProcServer32)
.1617 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{75718C9A-F029-11D1-A1AC-00C04FB6C223}\InProcServer32)
.1618 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}\InProcServer32)
.1619 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{9AED384E-CE8B-11D1-8B05-00600806D9B6}\InProcServer32)
.1620 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{C2FEEEAC-CFCD-11D1-8B05-00600806D9B6}\InProcServer32)
.1621 18:37:16 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL (\CLSID\{D269BF5C-D9C1-11D3-B38F-00105A1F473A}\InProcServer32)
.1622 18:37:16 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
.1623 18:37:16 (0) **    fail depending on the operation requested.
.1624 18:37:16 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
.1625 18:37:16 (0) **
.1626 18:37:16 (2) !! WARNING: WMI ProgID registrations missing: .......................................................................... 7 ProgID(S)!
.1627 18:37:16 (0) ** - WBemscripting.SWBemlocator -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1628 18:37:16 (0) ** - WbemScripting.SWbemDateTime -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1629 18:37:16 (0) ** - WbemScripting.SWbemObjectPath -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1630 18:37:16 (0) ** - WbemScripting.SWbemSink -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1631 18:37:16 (0) ** - WbemScripting.SWbemLocator -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1632 18:37:16 (0) ** - WbemScripting.SWbemNamedValueSet -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1633 18:37:16 (0) ** - WbemScripting.SWbemRefresher -> C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL
.1634 18:37:16 (0) ** => Missing WMI ProgID(s) could prevent WMI applications to run properly!
.1635 18:37:16 (0) **    To correct this problem, you must re-register the DLL(s) corresponding to the missing ProgID(s)
.1636 18:37:16 (0) **    with the following command:
.1637 18:37:16 (0) **    i.e. 'REGSVR32.EXE C:\WINDOWS\SYSTEM32\WBEM\WBEMDISP.DLL'
.1638 18:37:16 (0) **
.1639 18:37:16 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
.1640 18:37:16 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
.1641 18:37:16 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
.1642 18:37:16 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
.1643 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1644 18:37:16 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
.1645 18:37:16 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
.1646 18:37:16 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
.1647 18:37:16 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
.1648 18:37:16 (0) **         selecting 'Run as Administrator'.
.1649 18:37:16 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
.1650 18:37:16 (0) **         in the Task Scheduler within the right security context.
.1651 18:37:16 (0) **
.1652 18:37:16 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
.1653 18:37:16 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
.1654 18:37:16 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
.1655 18:37:16 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
.1656 18:37:16 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
.1657 18:37:16 (0) **
.1658 18:37:16 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
.1659 18:37:16 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
.1660 18:37:16 (0) **        - REMOVED ACE:
.1661 18:37:16 (0) **          ACEType:  &h0
.1662 18:37:16 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1663 18:37:16 (0) **          ACEFlags: &h0
.1664 18:37:16 (0) **          ACEMask:  &h3
.1665 18:37:16 (0) **                    DCOM_RIGHT_EXECUTE
.1666 18:37:16 (0) **                    DCOM_RIGHT_ACCESS_LOCAL
.1667 18:37:16 (0) **
.1668 18:37:16 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1669 18:37:16 (0) **    Removing default security will cause some operations to fail!
.1670 18:37:16 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1671 18:37:16 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1672 18:37:16 (0) **
.1673 18:37:16 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1674 18:37:16 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
.1675 18:37:16 (0) **        - REMOVED ACE:
.1676 18:37:16 (0) **          ACEType:  &h0
.1677 18:37:16 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1678 18:37:16 (0) **          ACEFlags: &h0
.1679 18:37:16 (0) **          ACEMask:  &h1F
.1680 18:37:16 (0) **                    DCOM_RIGHT_EXECUTE
.1681 18:37:16 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1682 18:37:16 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1683 18:37:16 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1684 18:37:16 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1685 18:37:16 (0) **
.1686 18:37:16 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1687 18:37:16 (0) **    Removing default security will cause some operations to fail!
.1688 18:37:16 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1689 18:37:16 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1690 18:37:16 (0) **
.1691 18:37:16 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
.1692 18:37:16 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
.1693 18:37:16 (0) **        - REMOVED ACE:
.1694 18:37:16 (0) **          ACEType:  &h0
.1695 18:37:16 (0) **                    ACCESS_ALLOWED_ACE_TYPE
.1696 18:37:16 (0) **          ACEFlags: &h0
.1697 18:37:16 (0) **          ACEMask:  &h1F
.1698 18:37:16 (0) **                    DCOM_RIGHT_EXECUTE
.1699 18:37:16 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
.1700 18:37:16 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
.1701 18:37:16 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
.1702 18:37:16 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
.1703 18:37:16 (0) **
.1704 18:37:16 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
.1705 18:37:16 (0) **    Removing default security will cause some operations to fail!
.1706 18:37:16 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
.1707 18:37:16 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
.1708 18:37:16 (0) **
.1709 18:37:16 (0) **
.1710 18:37:16 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
.1711 18:37:16 (0) ** DCOM security error(s) detected: .................................................................................... 3.
.1712 18:37:16 (0) ** WMI security warning(s) detected: ................................................................................... 0.
.1713 18:37:16 (0) ** WMI security error(s) detected: ..................................................................................... 0.
.1714 18:37:16 (0) **
.1715 18:37:16 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
.1716 18:37:16 (0) ** Overall WMI security status: ........................................................................................ OK.
.1717 18:37:16 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
.1718 18:37:16 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE.
.1719 18:37:16 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
.1720 18:37:16 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
.1721 18:37:16 (0) ** - Root, 0x1A8 - Necessario oggetto.
.1722 18:37:16 (0) **
.1723 18:37:16 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 17 ERROR(S)!
.1724 18:37:16 (0) ** - Root, 0x1A8 - Necessario oggetto.
.1725 18:37:16 (0) ** - Root, 0x1A8 - Necessario oggetto.
.1726 18:37:16 (0) ** - Root/subscription, 0x1A8 - Necessario oggetto.
.1727 18:37:16 (0) ** - Root/DEFAULT, 0x1A8 - Necessario oggetto.
.1728 18:37:16 (0) ** - Root/CIMV2, 0x1A8 - Necessario oggetto.
.1729 18:37:16 (0) ** - Root/CIMV2/Security, 0x1A8 - Necessario oggetto.
.1730 18:37:16 (0) ** - Root/CIMV2/Applications, 0x1A8 - Necessario oggetto.
.1731 18:37:16 (0) ** - Root/nap, 0x1A8 - Necessario oggetto.
.1732 18:37:16 (0) ** - Root/SECURITY, 0x1A8 - Necessario oggetto.
.1733 18:37:16 (0) ** - Root/STANDARDCIMV2, 0x1A8 - Necessario oggetto.
.1734 18:37:16 (0) ** - Root/WMI, 0x1A8 - Necessario oggetto.
.1735 18:37:16 (0) ** - Root/directory, 0x1A8 - Necessario oggetto.
.1736 18:37:16 (0) ** - Root/directory/LDAP, 0x1A8 - Necessario oggetto.
.1737 18:37:16 (0) ** - Root/SecurityCenter, 0x1A8 - Necessario oggetto.
.1738 18:37:16 (0) ** - Root/Microsoft, 0x1A8 - Necessario oggetto.
.1739 18:37:16 (0) ** - Root/Microsoft/HomeNet, 0x1A8 - Necessario oggetto.
.1740 18:37:16 (0) ** - Root/aspnet, 0x1A8 - Necessario oggetto.
.1741 18:37:16 (0) **
.1742 18:37:16 (0) ** WMI GET operations: ................................................................................................. OK.
.1743 18:37:16 (0) ** WMI MOF representations: ............................................................................................ OK.
.1744 18:37:16 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
.1745 18:37:16 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
.1746 18:37:16 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
.1747 18:37:16 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
.1748 18:37:16 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
.1749 18:37:16 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
.1750 18:37:16 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
.1751 18:37:16 (0) ** WMI static instances retrieved: ..................................................................................... 0.
.1752 18:37:16 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
.1753 18:37:16 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
.1754 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1755 18:37:16 (0) **
.1756 18:37:16 (0) ** 18 error(s) 0x1A8 - (WBEM_UNKNOWN) This error code is external to WMI.
.1757 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1758 18:37:16 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
.1759 18:37:16 (1) !! ERROR: Missing registry key value:
.1760 18:37:16 (0) **   - HKLM\SOFTWARE\Classes\CLSID\{172BDDF8-CEEA-11D1-8B05-00600806D9B6}\VersionIndependentProgID\ (REG_SZ) -> WINMGMTS
.1761 18:37:16 (0) **     From the command line, the registry configuration can be corrected with the following command:
.1762 18:37:16 (0) **
.1763 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1764 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1765 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1766 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1767 18:37:16 (0) **
.1768 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1769 18:37:16 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
.1770 18:37:16 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
.1771 18:37:16 (0) **
.1772 18:37:16 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\USERS\UTENTE_2\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_BENEDETTA_2019.02.23_18.37.05.LOG' for details.
.1773 18:37:16 (0) **
.1774 18:37:16 (0) ** WMIDiag v2.2 ended on sabato 23 febbraio 2019 at 18.37 (W:36 E:54 S:1).
Last edited by Dalai on 23.02.2019, 20:10, edited 1 time in total.
Reason: Enclosed log output in CODE tags for better readability
pandablu
 
Posts: 6
Joined: 23.02.2019, 13:08

Re: Unsupported Operating System x64 win 8.1

Postby Dalai » 23.02.2019, 20:13

Did you run WMI Diagnosis Utility as administrator?

Regards
Dalai
Dalai
 
Posts: 1025
Joined: 12.07.2016, 21:00

Re: Unsupported Operating System x64 win 8.1

Postby pandablu » 24.02.2019, 21:48

there is no present the voice start with administrator when i click with right push....
pandablu
 
Posts: 6
Joined: 23.02.2019, 13:08

Re: Unsupported Operating System x64 win 8.1

Postby Dalai » 24.02.2019, 22:15

You can right-click on the downloaded WMIDiag.exe and select "Run As Administrator". I don't see any problem there.

[EDIT]
OK, I see the issue now. The downloaded WMIDiag.exe is just an SFX CAB that extracts its files to a location specified by the user.
To run this thing as administrator, open a CMD as administrator and run this command from there:
Code: Select all
cscript.exe WMIDiag.vbs
.
[/EDIT]

Regards
Dalai
Dalai
 
Posts: 1025
Joined: 12.07.2016, 21:00

Re: Unsupported Operating System x64 win 8.1

Postby pandablu » 27.02.2019, 22:47

Dalai wrote:You can right-click on the downloaded WMIDiag.exe and select "Run As Administrator". I don't see any problem there.

[EDIT]
OK, I see the issue now. The downloaded WMIDiag.exe is just an SFX CAB that extracts its files to a location specified by the user.
To run this thing as administrator, open a CMD as administrator and run this command from there:
Code: Select all
cscript.exe WMIDiag.vbs
.
[/EDIT]

Regards
Dalai


i i'm trying to command as administrator, but now cmd not open... how i do?
pandablu
 
Posts: 6
Joined: 23.02.2019, 13:08

Re: Unsupported Operating System x64 win 8.1

Postby Dalai » 28.02.2019, 01:20

Open the Windows Start menu (or Start screen or whatever MS calls it), search for "cmd" or "command prompt", right-click it and select "Run As Administrator". In the open CMD window, navigate to the directory you extracted WMIDiag to (copy the path by setting the cursor in the address bar in Explorer and selecting the whole path):
Code: Select all
cd /D path
replace "path" with the copied path; use right-click to paste text into a CMD window.

Then you can run the command I mentioned in my previous post.

I hope this is detailed enough, and correct as well (I neither use the Windows Start menu nor Explorer).

Regards
Dalai
Dalai
 
Posts: 1025
Joined: 12.07.2016, 21:00

Next

Return to Installation / Updating

Who is online

Users browsing this forum: Google [Bot] and 21 guests