API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 25th, 2018
214
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 28.23 KB | None | 0 0
raw download clone embed print report
  1. 36206 17:24:08 (0) ** WMIDiag v2.2 started on Sunday, March 25, 2018 at 17:13.
  2. 36207 17:24:08 (0) **
  3. 36208 17:24:08 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
  4. 36209 17:24:08 (0) **
  5. 36210 17:24:08 (0) ** This script is not supported under any Microsoft standard support program or service.
  6. 36211 17:24:08 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
  7. 36212 17:24:08 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
  8. 36213 17:24:08 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
  9. 36214 17:24:08 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
  10. 36215 17:24:08 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
  11. 36216 17:24:08 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
  12. 36217 17:24:08 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
  13. 36218 17:24:08 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
  14. 36219 17:24:08 (0) ** of the possibility of such damages.
  15. 36220 17:24:08 (0) **
  16. 36221 17:24:08 (0) **
  17. 36222 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  18. 36223 17:24:08 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
  19. 36224 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  20. 36225 17:24:08 (0) **
  21. 36226 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  22. 36227 17:24:08 (0) ** Windows 8.1 - No Service Pack - 64-bit (16299) - User "Clipped by GardenMan" on computer "Clipped by GardenMan".
  23. 36228 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  24. 36229 17:24:08 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
  25. 36230 17:24:08 (0) ** INFO: => 8 possible incorrect shutdown(s) detected on:
  26. 36231 17:24:08 (0) ** - Shutdown on 16 November 2017 20:44:30 (GMT-0).
  27. 36232 17:24:08 (0) ** - Shutdown on 17 November 2017 06:15:45 (GMT-0).
  28. 36233 17:24:08 (0) ** - Shutdown on 19 November 2017 20:05:51 (GMT-0).
  29. 36234 17:24:08 (0) ** - Shutdown on 21 November 2017 01:11:33 (GMT-0).
  30. 36235 17:24:08 (0) ** - Shutdown on 26 November 2017 03:10:43 (GMT-0).
  31. 36236 17:24:08 (0) ** - Shutdown on 28 November 2017 23:07:04 (GMT-0).
  32. 36237 17:24:08 (0) ** - Shutdown on 06 February 2018 01:13:23 (GMT-0).
  33. 36238 17:24:08 (0) ** - Shutdown on 15 March 2018 04:08:47 (GMT-0).
  34. 36239 17:24:08 (0) **
  35. 36240 17:24:08 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #2).
  36. 36241 17:24:08 (0) ** Drive type: ......................................................................................................... IDE (VBOX HARDDISK).
  37. 36242 17:24:08 (0) ** There are no missing WMI system files: .............................................................................. OK.
  38. 36243 17:24:08 (0) ** There are no missing WMI repository files: .......................................................................... OK.
  39. 36244 17:24:08 (0) ** WMI repository state: ............................................................................................... N/A.
  40. 36245 17:24:08 (0) ** AFTER running WMIDiag:
  41. 36246 17:24:08 (0) ** The WMI repository has a size of: ................................................................................... 34 MB.
  42. 36247 17:24:08 (0) ** - Disk free space on 'C:': .......................................................................................... 14220 MB.
  43. 36248 17:24:08 (0) ** - INDEX.BTR, 6676480 bytes, 3/25/2018 5:12:47 PM
  44. 36249 17:24:08 (0) ** - MAPPING1.MAP, 92620 bytes, 3/25/2018 5:06:53 PM
  45. 36250 17:24:08 (0) ** - MAPPING2.MAP, 92620 bytes, 3/25/2018 5:12:47 PM
  46. 36251 17:24:08 (0) ** - OBJECTS.DATA, 28352512 bytes, 3/25/2018 5:12:47 PM
  47. 36252 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  48. 36253 17:24:08 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
  49. 36254 17:24:08 (0) ** Windows Firewall Profile: ........................................................................................... PRIVATE.
  50. 36255 17:24:08 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
  51. 36256 17:24:08 (0) ** => This will prevent any WMI remote connectivity to this computer except
  52. 36257 17:24:08 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
  53. 36258 17:24:08 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
  54. 36259 17:24:08 (0) ** - 'Windows Management Instrumentation (WMI-In)'
  55. 36260 17:24:08 (0) ** - 'Windows Management Instrumentation (ASync-In)'
  56. 36261 17:24:08 (0) ** Verify the reported status for each of these three inbound rules below.
  57. 36262 17:24:08 (0) **
  58. 36263 17:24:08 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
  59. 36264 17:24:08 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
  60. 36265 17:24:08 (0) ** - You can adjust the configuration by executing the following command:
  61. 36266 17:24:08 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
  62. 36267 17:24:08 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
  63. 36268 17:24:08 (0) ** You can also enable each individual rule instead of activating the group rule.
  64. 36269 17:24:08 (0) **
  65. 36270 17:24:08 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. DISABLED.
  66. 36271 17:24:08 (0) ** => This will prevent any WMI asynchronous inbound connectivity to this machine.
  67. 36272 17:24:08 (0) ** - You can adjust the configuration of this rule by executing the following command:
  68. 36273 17:24:08 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (ASync-In)" NEW ENABLE=YES'
  69. 36274 17:24:08 (0) **
  70. 36275 17:24:08 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... DISABLED.
  71. 36276 17:24:08 (0) ** => This will prevent any WMI asynchronous outbound connectivity from this machine.
  72. 36277 17:24:08 (0) ** - You can adjust the configuration of this rule by executing the following command:
  73. 36278 17:24:08 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-Out)" NEW ENABLE=YES'
  74. 36279 17:24:08 (0) **
  75. 36280 17:24:08 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ DISABLED.
  76. 36281 17:24:08 (0) ** => This will prevent any WMI inbound connectivity to this machine.
  77. 36282 17:24:08 (0) ** Note: The rule 'Windows Management Instrumentation (WMI-In)' rule must be ENABLED to allow incoming WMI connectivity.
  78. 36283 17:24:08 (0) ** - You can adjust the configuration of this rule by executing the following command:
  79. 36284 17:24:08 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (WMI-In)" NEW ENABLE=YES'
  80. 36285 17:24:08 (0) **
  81. 36286 17:24:08 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... DISABLED.
  82. 36287 17:24:08 (0) ** => This will prevent any DCOM WMI inbound connectivity to this machine.
  83. 36288 17:24:08 (0) ** Note: The rule 'Windows Management Instrumentation (DCOM-In)' rule must be ENABLED to allow incoming DCOM WMI connectivity.
  84. 36289 17:24:08 (0) ** - You can adjust the configuration of this rule by executing the following command:
  85. 36290 17:24:08 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE NAME="Windows Management Instrumentation (DCOM-In)" NEW ENABLE=YES'
  86. 36291 17:24:08 (0) **
  87. 36292 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  88. 36293 17:24:08 (0) ** DCOM Status: ........................................................................................................ OK.
  89. 36294 17:24:08 (0) ** WMI registry setup: ................................................................................................. OK.
  90. 36295 17:24:08 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
  91. 36296 17:24:08 (0) ** - Security Center (WSCSVC, StartMode='Automatic')
  92. 36297 17:24:08 (0) ** - Internet Connection Sharing (ICS) (*) (SHAREDACCESS, StartMode='Manual')
  93. 36298 17:24:08 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
  94. 36299 17:24:08 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
  95. 36300 17:24:08 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
  96. 36301 17:24:08 (0) ** this can prevent the service/application to work as expected.
  97. 36302 17:24:08 (0) **
  98. 36303 17:24:08 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
  99. 36304 17:24:08 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
  100. 36305 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  101. 36306 17:24:08 (0) ** WMI service DCOM setup: ............................................................................................. OK.
  102. 36307 17:24:08 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 3 WARNING(S)!
  103. 36308 17:24:08 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\NETPEERDISTCIM.DLL (\CLSID\{3292A418-BAC2-4BBF-BB07-66A1CB3B8B7D}\InProcServer32)
  104. 36309 17:24:08 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{69D76D1B-B12E-4913-8F48-671B90195A2B}\InProcServer32)
  105. 36310 17:24:08 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\POLICMAN.DLL (\CLSID\{AAEAE72F-0328-4763-8ECB-23422EDE2DB5}\InProcServer32)
  106. 36311 17:24:08 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
  107. 36312 17:24:08 (0) ** fail depending on the operation requested.
  108. 36313 17:24:08 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
  109. 36314 17:24:08 (0) **
  110. 36315 17:24:08 (0) ** WMI ProgID registrations: ........................................................................................... OK.
  111. 36316 17:24:08 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
  112. 36317 17:24:08 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
  113. 36318 17:24:08 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
  114. 36319 17:24:08 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
  115. 36320 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  116. 36321 17:24:08 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
  117. 36322 17:24:08 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
  118. 36323 17:24:08 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command
  119. 36324 17:24:08 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
  120. 36325 17:24:08 (0) ** selecting 'Run as Administrator'.
  121. 36326 17:24:08 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task
  122. 36327 17:24:08 (0) ** in the Task Scheduler within the right security context.
  123. 36328 17:24:08 (0) **
  124. 36329 17:24:08 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
  125. 36330 17:24:08 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
  126. 36331 17:24:08 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
  127. 36332 17:24:08 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
  128. 36333 17:24:08 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
  129. 36334 17:24:08 (0) **
  130. 36335 17:24:08 (0) ** Overall DCOM security status: ....................................................................................... OK.
  131. 36336 17:24:08 (0) ** Overall WMI security status: ........................................................................................ OK.
  132. 36337 17:24:08 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
  133. 36338 17:24:08 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
  134. 36339 17:24:08 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
  135. 36340 17:24:08 (0) ** 'select * from MSFT_SCMEventLogEvent'
  136. 36341 17:24:08 (0) **
  137. 36342 17:24:08 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
  138. 36343 17:24:08 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
  139. 36344 17:24:08 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
  140. 36345 17:24:08 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTVOLUMEENCRYPTION.
  141. 36346 17:24:08 (0) ** - ROOT/SERVICEMODEL.
  142. 36347 17:24:08 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
  143. 36348 17:24:08 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
  144. 36349 17:24:08 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
  145. 36350 17:24:08 (0) ** i.e. 'WMIC.EXE /NODE:"Clipped by GardenMan" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
  146. 36351 17:24:08 (0) **
  147. 36352 17:24:08 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
  148. 36353 17:24:08 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 1 ERROR(S)!
  149. 36354 17:24:08 (0) ** - Root/nap, 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found.
  150. 36355 17:24:08 (0) **
  151. 36356 17:24:08 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 17 ERROR(S)!
  152. 36357 17:24:08 (0) ** - Root/CIMV2, Win32_FloppyDrive, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  153. 36358 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  154. 36359 17:24:08 (0) ** - Root/CIMV2, Win32_FloppyController, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  155. 36360 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  156. 36361 17:24:08 (0) ** - Root/CIMV2, Win32_TerminalService, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  157. 36362 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  158. 36363 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheSettingData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  159. 36364 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  160. 36365 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheHostedCacheServerSettingData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  161. 36366 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  162. 36367 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheNetworkSettingData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  163. 36368 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  164. 36369 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheContentServerSettingData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  165. 36370 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  166. 36371 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheClientSettingData, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  167. 36372 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  168. 36373 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheStatus, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  169. 36374 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  170. 36375 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheCache, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  171. 36376 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  172. 36377 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheSecondaryCache, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  173. 36378 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  174. 36379 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheDataCacheExtension, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  175. 36380 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  176. 36381 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCachePrimaryCache, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  177. 36382 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  178. 36383 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheDataCache, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  179. 36384 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  180. 36385 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheHashCache, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  181. 36386 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  182. 36387 17:24:08 (0) ** - Root/STANDARDCIMV2, MSFT_NetBranchCacheOrchestrator, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  183. 36388 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  184. 36389 17:24:08 (0) ** - Root/WMI, Thread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
  185. 36390 17:24:08 (0) ** MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
  186. 36391 17:24:08 (0) **
  187. 36392 17:24:08 (0) ** WMI MOF representations: ............................................................................................ OK.
  188. 36393 17:24:08 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
  189. 36394 17:24:08 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
  190. 36395 17:24:08 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
  191. 36396 17:24:08 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
  192. 36397 17:24:08 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
  193. 36398 17:24:08 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
  194. 36399 17:24:08 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
  195. 36400 17:24:08 (0) ** WMI static instances retrieved: ..................................................................................... 1842.
  196. 36401 17:24:08 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
  197. 36402 17:24:08 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
  198. 36403 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  199. 36404 17:24:08 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
  200. 36405 17:24:08 (0) ** DCOM: ............................................................................................................. 0.
  201. 36406 17:24:08 (0) ** WINMGMT: .......................................................................................................... 0.
  202. 36407 17:24:08 (0) ** WMIADAPTER: ....................................................................................................... 0.
  203. 36408 17:24:08 (0) **
  204. 36409 17:24:08 (0) ** # of additional Event Log events AFTER WMIDiag execution:
  205. 36410 17:24:08 (0) ** DCOM: ............................................................................................................. 0.
  206. 36411 17:24:08 (0) ** WINMGMT: .......................................................................................................... 0.
  207. 36412 17:24:08 (0) ** WMIADAPTER: ....................................................................................................... 0.
  208. 36413 17:24:08 (0) **
  209. 36414 17:24:08 (0) ** 1 error(s) 0x8004100E - (WBEM_E_INVALID_NAMESPACE) Namespace specified cannot be found
  210. 36415 17:24:08 (0) **
  211. 36416 17:24:08 (0) ** 17 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
  212. 36417 17:24:08 (0) ** => This error is typically a WMI error. This WMI error is due to:
  213. 36418 17:24:08 (0) ** - a missing WMI class definition or object.
  214. 36419 17:24:08 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
  215. 36420 17:24:08 (0) ** You can correct the missing class definitions by:
  216. 36421 17:24:08 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
  217. 36422 17:24:08 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
  218. 36423 17:24:08 (0) ** (This list can be built on a similar and working WMI Windows installation)
  219. 36424 17:24:08 (0) ** The following command line must be used:
  220. 36425 17:24:08 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
  221. 36426 17:24:08 (0) ** - a WMI repository corruption.
  222. 36427 17:24:08 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
  223. 36428 17:24:08 (0) ** to validate the WMI repository operations.
  224. 36429 17:24:08 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
  225. 36430 17:24:08 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
  226. 36431 17:24:08 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
  227. 36432 17:24:08 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
  228. 36433 17:24:08 (0) ** the WMI repository must be reconstructed.
  229. 36434 17:24:08 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
  230. 36435 17:24:08 (0) ** otherwise some applications may fail after the reconstruction.
  231. 36436 17:24:08 (0) ** This can be achieved with the following command:
  232. 36437 17:24:08 (0) ** i.e. 'WMIDiag ShowMOFErrors'
  233. 36438 17:24:08 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
  234. 36439 17:24:08 (0) ** ALL fixes previously mentioned.
  235. 36440 17:24:08 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
  236. 36441 17:24:08 (0) **
  237. 36442 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  238. 36443 17:24:08 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
  239. 36444 17:24:08 (2) !! WARNING: Unexpected registry key value:
  240. 36445 17:24:08 (0) ** - Current: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\ImagePath (REG_EXPAND_SZ) -> %systemroot%\system32\svchost.exe -k netsvcs -p
  241. 36446 17:24:08 (0) ** - Expected: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\ImagePath (REG_EXPAND_SZ) -> %systemroot%\system32\svchost.exe -k netsvcs
  242. 36447 17:24:08 (0) ** From the command line, the registry configuration can be corrected with the following command:
  243. 36448 17:24:08 (0) **
  244. 36449 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  245. 36450 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  246. 36451 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  247. 36452 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  248. 36453 17:24:08 (0) **
  249. 36454 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  250. 36455 17:24:08 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
  251. 36456 17:24:08 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
  252. 36457 17:24:08 (0) **
  253. 36458 17:24:08 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\USERNAME\APPDATA\LOCAL\TEMP\WMIDIAG-V2.2_WIN8.1_.CLI.RTM.64_Clipped by GardenMan-PC_2018.03.25_17.13.38.LOG' for details.
  254. 36459 17:24:08 (0) **
  255. 36460 17:24:08 (0) ** WMIDiag v2.2 ended on Sunday, March 25, 2018 at 17:24 (W:136 E:31 S:1).
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!