Код события 1010 windows 10

• Remove From My Forums

Появление следующих ошибок в логах

• Общие обсуждения

• Процесс, обслуживающий пул приложений «MSExchangeSyncAppPool», обнаружил неустранимую ошибку связи со службой активации Windows.
  

  Так же в это же время аналогично для:

  «MSExchangeAutodiscoverAppPool»
  «MSExchangeOABAppPool»
  «MSExchangeServicesAppPool»
  «MSExchangeMapiFrontEndAppPool»
  «MSExchangeRpcProxyAppPool»
  Ошибка пока одноразовая но возникают вопросы.
  С чем это может быть связано и как лечить.

  • Изменен тип

    28 октября 2013 г. 7:41
    нет действий

1. Error modern deployement diagnostic provider id 1010

   Hi all, Since todays i’ve notice that i got this report in the task event manager. In some sub group someone as talk about office account from a school or work organisation. So i got an msi laptop since 2019 a gp76leopard with win11 since i was able to get it.So i do have an account from a university in montreal and i did not register my office program related to that university. In 2022 i got to some college and i did got an account form them for office school stuff. Now i’ve deleted this account because i was getting anoying to entre my password at each 5 minute or in some case at reboot. No

   

2. Event Viewer Errors: Autopilot.dll WIL error was reported; Event ID: 1010; Source: Microsoft-Windows-ModernDeployment-Diagnostics-Provider

   Lots of continuing event viewer errors.

   Autopilot.dll WIL error was reported;

   Event ID: 1010;

   Source: Microsoft-Windows-ModernDeployment-Diagnostics-Provider

   Brand new HP computer running Windows Home 11 v21H2 OS 22000.832

   What causes these errors?

   How do I stop them?

   What is Autopilot?

   I have home computer, Windows is installed, and I don’t think I need further «deployment» or «provisioning».

3. EVENT ERROR provisioning-diagnostics-provider ID 12 Go through and do what is suggested at EVENT ERROR provisioning-diagnostics-provider Fehler ID 12. Everything you need is in that link.

4. Error modern deployement diagnostic provider id 1010

   EVENT ERROR provisioning-diagnostics-provider ID 12 Hallo,
   the errors that are described there I have not or already solved some time ago, so unfortunately I can not apply any solutions. The strange thing is that the error has not occurred so far, probably because I left windows for a long time and the automatic maintenance repaired the error itself.
   I will report back for new problems.
   Best Regards *Smile

This week another new blog post related to Windows 10 MDM. In the recent weeks I’ve discussed policy refresh, some configurations and now some troubleshooting. This post is also triggered by my previous as I used the MDM Diagnostics Tool (MdmDiagnosticsTool.exe) as an example. Based on that example I’ve received some requests for more information. There are more useful tools like dsregcmd, but this post will focus on the MDM Diagnostics Tool, as there’s not that much information available. In this post I’ll provide information about the usage and results of the MDM Diagnostics Tool as having the right information is really useful for troubleshooting Windows 10 MDM managed devices.

Introduction of the MDM Diagnostics Tool

The MDM Diagnostics Tool is a command line tool that can be used to gather information. Information related to specific MDM areas. Depending on the chosen MDM area, the MDM Diagnostics Tool will gather the related events, registry, logs and more, all consolidated into a single folder or single file. The MDM Diagnostics Tool is one of the best starting points for the IT admin, for a consolidated source for troubleshooting.

Usage of the MDM Diagnostics Tool

The MDM Diagnostics Tool can has four different usage options. The first usage option is the generic option to output MDM diagnostics info only, to a given folder.

MdmDiagnosticsTool.exe -out <output folder path>

The second usage option is to collect predefined area logs and to create a cab file with the results. The possible areas are available in the registry under: HKLMSOFTWAREMicrosoftMdmDiagnosticsArea. At this moment those areas are Autopilot, DeviceEnrollment, DeviceProvisioning and TPM (as shown below).

MdmDiagnosticsTool.exe -area <area name(s)> -cab <output cab file path>

The third usage option is to collect predefined area logs and to create a zip file with the results. The possible areas are the same as for the second usage option. Only the file type of the result is different.

MdmDiagnosticsTool.exe -area <area name(s)> -zip <output zip file path>

The fourth usage option is to collect information specified in a XML-file and to create a zip file with the results. I haven’t found out (and not really looked at) how to construct a working XML-file for that option. To use the MDM Diagnostics Tool in combination with Microsoft Intune, have a look at my previous post.

MdmDiagnosticsTool.exe -xml <xml file of information to gather> -zip <output zip file path> -server <MDM Server to alert>

Output of the MDM Diagnostics Tool

The output of the different usage options of the MDM Diagnostics Tool is also different. As usage option 2 and 3 contain the same information and I can’t really use option 4, let’s have a look at the output of option 1 and 2. Below is a quick overview of the output, followed by an explanation of the diagnostic data that is available in the output.

Output of usage option 1

The first usage option provides the generic MDM diagnostics that contains the following information:

• DeviceManagement-Enterprise-Diagnostics-Provider.evtx – This event log contains the information (and errors) regarding the MDM sessions of the device. It also shows the MDM PolicyManager errors.
• MDMDiagReport.html (and related xml) – This is the same report that can be generated by using the Settings panel and generating the Advanced Diagnostics Report. That report shows the applied configuration states of the devices, including Policy CSP settings, certificates, configuration sources, and resource information.
• Microsoft-Windows-AAD.evtx – This event log contains information (and errors) related to Azure AD communications. From device registration until token requests.
• Microsoft-Windows-Shell-Core.evtx – This event log contains a lot of information mainly related to logon tasks and runonce actions on the device.

Output of usage option 2 (Autopilot)

The second usage option, with the Autopilot area specified, provides generic MDM diagnostics and specific Autopilot related diagnostics that contains the following information:

• AgentExecutor.log – This log file contains information about the PowerShell scripts that are executed by the Intune Management Extention.
• AutopilotConciergeFile.json – This json file contains the language and keyboard configuration information during a self deployment.
• AutopilotDDSZTDFile.json – This json file contains the configuration information during a regular deployment.
• ClientHealth.log – This log file contains the health information of the Intune Management Extention.
• DeviceHash_DESKTOP-U1JNF0E.csv – This csv file contains the device hash information of the device.
• DiagnosticLogCSP_Collector_Autopilot.etl – This event trace log file contains trace information of the Autopilot process of the device.
• DiagnosticLogCSP_Collector_DeviceEnrollment.etl – This event trace log file contains trace information of the device enrollment process of the device.
• DiagnosticLogCSP_Collector_DeviceProvisioning.etl – This event trace log file contains trace information of the device provisioning process of the device.
• IntuneManagementExtension.log – This log file contains information about the Win32 app deployments that are performed by the Intune Management Extension.
• LicensingDiag.cab (and related LicensingDiag_Output.txt) – These files contain licensing and diagnostic information.
• MDMDiagReport.html (and related xml) – This is the same report that can be generated by using the Settings panel and generating the Advanced Diagnostics Report. That report shows the applied configuration states of the devices, including Policy CSP settings, certificates, configuration sources, and resource information.
• MdmDiagReport_RegistryDump.reg – This registry file contains exported registry information related to Autopilot, but also related to the provisioning of the device and the policy manager. Basically everything related to MDM management.
• microsoft-windows-aad-operational.evtx – This event log contains operational information (and errors) related to Azure AD communications. From device registration until token requests.
• microsoft-windows-appxdeploymentserver-operational.evtx – This event log contains operational information (and errors) related to packaging, deploying, or querying app packages.
• microsoft-windows-assignedaccess-admin.evtx – This event log contains admin information (and errors) related to assigned access (kiosk mode).
• microsoft-windows-assignedaccessbroker-admin.evtx – This event log contains admin information (and errors) related to the broker of assigned access (kiosk mode).
• microsoft-windows-assignedaccessbroker-operational.evtx – This event log contains operational information (and errors) related to the broker of assigned access (kiosk mode).
• microsoft-windows-assignedaccess-operational.evtx – This event log contains operational information (and errors) related to assigned access (kiosk mode).
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx – This event log contains admin information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-debug.evtx – This event log contains debug information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-operational.evtx – This event log contains operational information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-moderndeployment-diagnostics-provider-autopilot.evtx – This event log contains the operational information (and errors) regarding the Autopilot profile settings and OOBE flow of the device.
• microsoft-windows-moderndeployment-diagnostics-provider-managementservice.evtx – This event log contains the operational information (and errors) regarding the management service of the device.
• microsoft-windows-provisioning-diagnostics-provider-admin.evtx – This event log contains the admin information (and errors) regarding adding packages to the device.
• microsoft-windows-shell-core-operational.evtx – This event log contains a lot of information mainly related to logon tasks and runonce actions on the device.
• microsoft-windows-user device registration-admin.evtx – This event log contains admin information (and errors) regarding the device registration (status).
• setupact.log – This log file contains information about the errors that occur during the Windows installation process of the device.
• TpmHliInfo_Output.txt – This file contains information about the support of TPM 2.0 for the TPM of the device.

Output of usage option 2 (DeviceEnrollment)

The second usage option, with the DeviceEnrollment area specified, provides generic MDM diagnostics and specific device enrollment related diagnostics that contains the following information:

• DiagnosticLogCSP_Collector_DeviceEnrollment.etl – This event trace log file contains trace information of the device enrollment process of the device.
• MDMDiagHtmlReport.html (and related xml) – This is the same report that can be generated by using the Settings panel and generating the Advanced Diagnostics Report. That report shows the applied configuration states of the devices, including Policy CSP settings, certificates, configuration sources, and resource information.
• MdmDiagReport_RegistryDump.reg – This registry file contains exported registry information related to Autopilot, but also related to the provisioning of the device and the policy manager. Basically everything related to MDM management.
• microsoft-windows-aad-operational.evtx – This event log contains operational information (and errors) related to Azure AD communications. From device registration until token requests.
• microsoft-windows-appxdeploymentserver-operational.evtx – This event log contains operational information (and errors) related to packaging, deploying, or querying app packages.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx – This event log contains admin information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-debug.evtx – This event log contains debug information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-operational.evtx – This event log contains operational information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-moderndeployment-diagnostics-provider-managementservice.evtx – This event log contains the operational information (and errors) regarding the management service of the device.
• microsoft-windows-provisioning-diagnostics-provider-admin.evtx – This event log contains the admin information (and errors) regarding adding packages to the device.

Output of usage option 2 (DeviceProvisioning)

The second usage option, with the DeviceProvisiong area specified, provides generic MDM diagnostics and specific device provisioning related diagnostics that contains the following information:

• DiagnosticLogCSP_Collector_DeviceProvisioning.etl – This event trace log file contains trace information of the device provisioning process of the device.
• MDMDiagHtmlReport.html (and related xml) – This is the same report that can be generated by using the Settings panel and generating the Advanced Diagnostics Report. That report shows the applied configuration states of the devices, including Policy CSP settings, certificates, configuration sources, and resource information.
• MdmDiagReport_RegistryDump.reg – This registry file contains exported registry information related to Autopilot, but also related to the provisioning of the device and the policy manager. Basically everything related to MDM management.
• microsoft-windows-aad-operational.evtx – This event log contains operational information (and errors) related to Azure AD communications. From device registration until token requests.
• microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx – This event log contains admin information (and errors) regarding the MDM sessions of the device.
• microsoft-windows-provisioning-diagnostics-provider-admin.evtx – This event log contains the admin information (and errors) regarding adding packages to the device.
• microsoft-windows-shell-core-operational.evtx – This event log contains a lot of information mainly related to logon tasks and runonce actions on the device.

Output of usage option 2 (TPM)

The second usage option, with the TPM area specified, provides generic MDM diagnostics specific certificate and TPM related diagnostics that contains the following information:

• CertReq_enrollaik_Output.txt – This file contains information about an attempt to enroll an AIK key for the device.
• CertUtil_tpminfo_Output.txt – This file contains information about the TPM of the device.
• MDMDiagHtmlReport.html (and related xml) – This is the same report that can be generated by using the Settings panel and generating the Advanced Diagnostics Report. That report shows the applied configuration states of the devices, including Policy CSP settings, certificates, configuration sources, and resource information.
• MdmDiagReport_RegistryDump.reg – This registry file contains exported registry information related to Autopilot, but also related to the provisioning of the device and the policy manager. Basically everything related to MDM management.

More information

For more information related to troubleshooting Windows 10 MDM related issues, please refer to the following documentation:

• Diagnose MDM failures in Windows 10: https://docs.microsoft.com/en-us/windows/client-management/mdm/diagnose-mdm-failures-in-windows-10
• Troubleshooting Windows Autopilot: https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/troubleshooting
• Windows Performance Analyzer: https://docs.microsoft.com/en-us/windows-hardware/test/wpt/windows-performance-analyzer

Let’s check how to Troubleshoot Windows Autopilot Issues with MDM Diagnostics Tool Windows Autopilot Issues. Let’s discuss Windows MDM Diagnostics Tool benefits, usage, and examples in this post.

In my previous post, Windows Autopilot Troubleshooting basics, we discussed different troubleshooting areas like Network Activity, Registry, and Event Viewer.

[Related Posts – Windows Autopilot Step by Step Guides, Windows 10 Deployment Process Flow and Logs]

What is Windows MDM Diagnostics Tool?

MDM Diagnostics is a command-line tool that can collate Windows Autopilot related events. Most Windows Autopilot-related events, registries, and logs are consolidated into a single folder or single file.

This tool helps IT Admins focus on one consolidated source for troubleshooting.

What are the Benefits of the MDM Diagnostics Tool?

Let’s understand how to troubleshoot Windows Autopilot Issues with MDM Diagnostics Tool as the first step, then understand its benefits.

• Automatically collect predefined logs and save them as zipping or Cab files.

• Remote users to run the command and share the logs with IT to troubleshoot.

• Use the Pre or Post OOBE stage of Windows Autopilot.

How to Use MDM Diagnostics Tool

How to use the Windows MDM diagnostics tool? I recommend using the latest Windows 10 (1803 or later) version of the MDM Diagnostics tool. I have not tested the previous version of Windows 10 with this MDM diag tool.

Usage 1: Syntax: MdmDiagnosticsTool.exe -out < output folder path >

Example: MdmDiagnosticsTool.exe -out c:temp

Usage 2: Syntax: MdmDiagnosticsTool.exe -area <area name(s)> -cab <output cab file path>

Execute below command line to collect Windows autopilot related events from the system for troubleshooting.

Example: MdmDiagnosticsTool.exe -area Autopilot -cab C:LOGS.zip

3 (Three) Troubleshooting Areas of MDM Diagnostics Tool

THE Windows MDM Diagnostics tool can be used below 3 (three) troubleshooting areas to collect pre-defined areas and logs. But, in this post, we will focus only on Windows Autopilot.

1. Autopilot
2. DeviceProvisioning
3. TPM

[Related Posts – Windows Autopilot Step by Step Guides, Windows 10 Deployment Process Flow and Logs]

The output of the MDM Diagnostics Tool

The diagnostics tool generates output in ZIP / CAB file format with the below files. We will go through each of the down output files and their purpose.

Deep Dive – Troubleshoot Windows Autopilot Issues with MDM Diagnostics Tool

You can understand more details about MDM Diagnostic tools in this section. Hopefully, the following troubleshooting steps will help you in Windows Autopilot deployment scenarios.

Event Viewer

MDM Diagnostics tool collects the below list of the event viewer. Event viewer includes client-side events like Autopilot events, policy actions, etc.

• Microsoft-windows-aad-operational
• devicemanagement-enterprise-diagnostics-provider
• microsoft-windows-assignedaccess-admin
• microsoft-windows-assignedaccess-operational
• microsoft-windows-moderndeployment-diagnostics-provider-autopilot
• microsoft-windows-provisioning-diagnostics-provider-admin
• microsoft-windows-shell-core-operational
• microsoft-windows-user device registration-admin

The below registry entries tells you a list of event viewer logs captured by the MDM Diagnostics tool.

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftMdmDiagnosticsAreaAutopilotEventViewerEntry 

Diagnostic Logs – Autopilot and Device Provisioning

The below-listed ETL files are captured by the tool. What is ETL? It’s an Event tracing log created by Windows. This tool is used for in-depth analysis of the events.

The below ETL file will include system activity captured during Autopilot and Intune device provisioning stage.

• DiagnosticLogCSP_Collector_Autopilot.etl
• DiagnosticLogCSP_Collector_DeviceProvisioning.etl

ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftMdmDiagnosticsAreaAutopilotFileEntry

You need to use the Windows performance analyzer tool to deep dive and analyze these ETL files.

CloudExperienceHostOobe Windows Autopilot logs

Where is the location of CloudExperienceHost? It is part of system apps within the c:windowssystemapps folder.

In Windows Autopilot deployment, the CloudExperienceHost process communicates with Azure.

To trace CloudExperienceHost process activity, MDM Diagnostics Tool generates Event Tracing Logs (ETW – Event Tracing for Windows). You can use a Windows performance analyzer to analyze the log, as shown below.

Setupact.log

This log file records actions or activity during the OOBE Phase of Autopilot.

Registry Dump

MdmDiagReport_RegistryDump.reg captures the HKLM and HKCU registry values associated with autopilot device provisioning.

Autopilot related
values are written to HKLMSOFTWAREMicrosoftProvisioningDiagnosticsAutoPilot

Intune CSP based configurations are written to HKEY_LOCAL_MACHINEsoftwaremicrosoftpolicymanager

MDMDiag Report

MDMDiagReport.xml report provides resultant Autopilot settings applied from Intune.

MDMDiagHtmlReport.html report provides complete details on the applied Intune Policy CSP Settings, certificates, applications, etc., on the autopilot device.

Resources

• Windows Autopilot Deployment Scenarios – On-Prem Hybrid Domain Join
• Step by Step Guide Windows AutoPilot Process with Intune 
• Beginners Guide Setup Windows AutoPilot Deployment 
• Windows Autopilot Video Starter Kit

Author

Vimal has more than ten years of experience in SCCM device management solutions. His main focus is on Device Management technologies like Microsoft Intune, ConfigMgr (SCCM), OS Deployment, and Patch Management. He writes about the technologies like SCCM, Windows 10, Microsoft Intune, and MDT.

Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx

Распространенные сообщения об ошибках в Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx

Проблемы, возникающие с Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx и Windows, включают:

• «Ошибка: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx. «
• «Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx перемещен или отсутствует. «
• «Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx не найден.»
• «Не удалось загрузить Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx.»
• «Не удалось зарегистрироваться: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx. «
• «Ошибка Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx во время выполнения. «
• «Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx не может загрузиться. «

Обычно ошибки Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx с Windows возникают во время запуска или завершения работы, в то время как приложения, связанные с Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx, выполняются, или редко во время последовательности обновления ОС. Документирование случаев ошибок Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx является ключевым для определения причины проблемы и сообщения о них Microsoft для исправлений.

Источники проблем Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx

Большинство проблем Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx связаны с отсутствующим или поврежденным Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx, вирусной инфекцией или недействительными записями реестра Windows, связанными с Windows.

В частности, проблемы Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx, созданные:

• Недопустимый раздел реестра Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx (или поврежденный).
• Вирус или вредоносное ПО поврежден Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx.
• Другая программа (не связанная с Windows) удалила Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx злонамеренно или по ошибке.
• Другая программа, конфликтующая с Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx или другой общей ссылкой Windows.
• Некомплектная установка приложения, связанного с Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx, или поврежденная загрузка.

In Windows 10 1709 – Creators Update Fall, Microsoft has made it much easier to troubleshoot what policies, application an more – this is done in the new “MDM Diagnostic Information” both in overview and in Advanced Diagnostic Report.

This is one of the greatest news in Windows 10 1709 seen from a modern management perspective in my opinion. It is more detailed then it has been in the previous versions of Windows 10, and the Advanced Diagnostic Report is being formatted so it is readable by default – where in previous versions of Windows 10 we need to converted from XML into HTML.

It can be found in the settings app:

Press Windows + I to start the settings App – click on Accounts

Click on Access work or School

Click on Connected to “Your Organisation” and click Info

The “Managed by…” is divided into 3 sections

The first section is Device sync status:

Under “Last Attempted Sync:” you can see if the last sync with the MDM backend was successful or if it has failed. You can also see when the last sync was attempted.

There is a Sync button that the end-user can sync there Windows 10 device with Intune – the sync button is also in the Intune Company Portal under settings. A MDM managed devices does not need the Company Portal to be managed.

The second section is Areas managed by…:

This section is divided up into 2 – policies where you can see what areas of policies that are set on the device from Intune

And a Applications where you can see what applications that are installed on the device from Intune, both MSI installations and Windows Apps.

In the last section you can see Connection info.

You also have the possibility to create a Advanced Diagnostic Report by clicking “Creat Report”

Click Export

Windows will then create MDMDiagReport.html in C:UsersPublicDocumentsMDMDiagnostics

The MDMDiagReport.html is divided up to sections:

• Device info
• Connection info
• Device Management Account
• Certificates
• Enrolled configuration sources and target resources
• Managed policies

Device info, Connection info and Device Management Account is overview information on the devices and MDM system information

At the Enrolled configuration sources and target resources section you can see Windows Hallo for Business settings from Intune

You can also see the applications that are installed per device or user

In the managed policies section, you can see the CSP policies that are set on the devices.

Here is a full list of CSP policies that can be set on a Windows 10 device Full list of Windows 10 CSP policies

In the list you can also see the default value for the CSP settings and what the settigns is changed into with Intune.

It is still possible to get a detailed log on setting set from the MDM system in the Windows Event Log – it can be found here:

Applications and Services Logs – Microsoft – Windows – DeviceManagement-Enterprise-Diagnostics-Provider

1. Failed to start service WMS — Error Id 1010

   «Failed to start service WMS. Program C:\Windows\wmi\WmiPrvSE.exe couldn’t be launched. CreateProcess() failed: The system cannot find the file specified.»

   The above event code/message has been been plaguing me in the event log for the last few weeks.

   Can anybody shed any light on this please with some possible solutions/directions ect.

   Thanks

   

2. PC freeze fully after update once a day

   Hello.

   After I updated my pc to the newest version of windows 10 my pc is getting fully freezed once a day at different times. When that happens I stop hearing sounds, my keyboard and mouse are not responsive and I cant do anything I must restart the pc. I went
   to the event viewer to see what is going on. Then I saw that everytime this happanes I got the same errors going on:

   The Windows Process Activation Service (WAS) failed to execute initialization for offline setup. The data field contains the error number. ID 5215

   Windows Process Activation Service (WAS) is stopping because it encountered an error. The data field contains the error number. ID 5005

   The WAS service terminated with the following error: ID 7023

   The data is invalid.

   The NetPipeActivator service depends on the WAS service which failed to start because of the following error: ID 7001

   The data is invalid.

   The W3SVC service depends on the WAS service which failed to start because of the following error:

   The data is invalid

   The NetMsmqActivator service depends on the WAS service which failed to start because of the following error:

   The data is invalid.

   The NetTcpActivator service depends on the WAS service which failed to start because of the following error:

   The data is invalid.

   ** Moved from: Windows / Windows 10 / Windows update, recovery, & backup **

3. WM6 Hang!

   Hi Support,

   For the second issue, the error message is «operation failed». That is all… And the GMS phone service is not available.Is there any place that WM will keep a log on any error message ? ?

4. Failed to start service WMS — Error Id 1010

   Are you perchance trying to access an older SQL Server? If so, you may find this support note from MS interesting and informative: https://support.microsoft.com/en-us/…exe-process-st. Otherwise, I don’t see anything about a failure to launch the WMI Service Provider that really makes sense.
   HTH,
   —Ed—

5. Many thanks for the reply Ed. Although I am familiar with the purpose of an SQL server I’m struggling to understand how that applies in this particular case.

   A few days ago my PC became unresponsive whilst in general use. I brought up the Task Manager to see if there was any issues causing this and noticed that WMiPRvSE.exe was hogging over 60% of available CPU. This continued for approx 30min until I got scared something was amiss so I took drastic action……….. I pressed ‘restart’.

   Now for the next 3 days I have been getting the above error message in Event Manager and it keeps repeating every 3min. I had assumed the best thing to do was either «find the missing file» indicated in the message or, try to stop the error message repeating. Both options of which at this time are beyond my understanding. I am also at a lose to understand why there seems to be very little information on this error or the error ID 1010 related to this event?

   Am I the only person ever to have suffered this?

6. I have the exact same issue. I restarted WmiPrvSE.exe as well in an attempt to reduce the CPU usage (bad mistake). Now WMI won’t launch, because it can’t find WmiPrvSE.exe at C:\Windows\wmi, even though the .exe is still located in that location. I’m also getting the error 1010 in Event Viewer.

   Currently trying to see if the WmiPrvSE.exe is corrupted by replacing it with a WmiPrvSE.exe file from a clean system. Besides that, I haven’t found a fix for it yet, but I’ll keep you up to date if I do find one.

7. Thank goodness I’m not alone with this. I was beginning to think this was yet another ‘clitch’ that only I had and once more (it has happened several times in the past) there is no solution.

   I did read one thread which tried what you are suggesting but this didn’t seem to work either. It appears that the Wmi file needs to be specific to your OS.

   Please, please keep me informed of anything you find.

   Thnx

8. Failed to start service WMS — Error Id 1010

   I can’t find any info on this anywhere, either — except for this thread! I’m going to post up on the MVP forums and see if anybody else knows anything there. I’ll report back, yea or nay, but am hopeful that the group may come up with something, in its collective wisdom.
   Stay tuned!
   —Ed—

9. Thanks so much! I’ve not found much myself, especially no fix, but event manager refers to not being able to find C:\Windows\wmi\WmiPrvSE.exe, while I previously found WmiPrvSE.exe in the location C:\Windows\System32\wbem\WmiPrvSE.exe.

   Turns out there are other locations for WmiPrvSE.exe (one more in C:\Windows\SysWOW64\wbem\WmiPrvSE.exe), all of which give an error message when activated: «Windows cannot find ‘C:\location of WmiPrvSE.exe’. Make sure you’ve typed the name in correctly, then try again». All versions of WmiPrvSE.exe seem to not be found by Windows, even though I can physically see them in File Explorer.

   Hence, I’d assume that the problem we’re experiencing with WMI (or WMS) is definitely caused by WmiPrvSE.exe. It could maybe be a directory issue, as Windows can’t find them? Anyhow, I’m still looking, but Google doesn’t come up with much except for this thread.

   I checked with another computer that wasn’t experiencing this issue (also running the latest version of Win 10), but I can’t even seem to find the C:\Windows\wmi folder on that PC. Don’t think that’s relevant though.

   I downloaded the WMI Diagnosis tool from here, and ran it. It came up with a pretty long log, showing a bunch of errors that I can’t fully understand. What I have gathered from it is that there’s files missing in the WMI repository, which I’ve already verified and reset according to these instructions (I’m unsure of what else to do). I’ve also ran the sfc /scannow command in hopes to repair corrupted files, but it couldn’t find any files in need of repair.

   I’ve attached it to this post if anyone’s interested. There’s a lot of There’s a lot of WMI connection errors in that seem to be caused by invalid permissions, but these are for ROOT/ ‘namespaces’, which I’m totally unfamiliar with so I won’t touch them.

10. According to fellow MVP Nick Pellatt here’s what may be up:

    So, I did then what I should’ve done with the original post — namely search out all the places where the WmiPrvSE.exe file resides on my healthy system(s). Here’s how I responded: So, on a 64-bit system the one in SysWOW64 is the one that should matter. So now I find myself asking instead «Why is the error complaining about a directory that doesn’t exist?» Whoever’s seeing this might want to try setting up the C:\Windows\WMI folder and populating it with the file, and see if that does anything.

    It’s even stranger than it looks and sounds, I’m afraid. Shoot me a link to that WMI diagnostic tool, please, and I will poke around with that as well. Odd!

    —Ed—

11. Here’s the link to the diagnostics tool that I used. It says it isn’t compatible with Win 10, but when run as a command it works just fine.

    https://www.microsoft.com/en-us/down…s.aspx?id=7684

    It spits out a lengthy log that I’m still going through to see what I can gather (to the best of my abilities).

    It’s really strange though, because the C:\Windows\wmi folder on my PC doesn’t only exist, but is populated with two executables: WmiPrvSE.exe and netmon.exe. I checked with another healthy PC, and the folder doesn’t exist there either. So I’m even more confused about that folder.

    I greatly appreciate the help so far, thank you very much!

12. Hey TMSharks,
    If you haven’t already, try running the following see what/if anything they show ?

    sfc /scannow
    Dism /Online /Cleanup-Image /RestoreHealth

13. Failed to start service WMS — Error Id 1010

    Dear TMSharks:
    Here’s another, very interesting response from fellow MVP Greg Carmack:

    This looks worth digging into: I’ve found the HowToGeek enormously helpful over the years.
    —Ed—

14. I’ve run sfc /scannow again, just to be sure, but I hadn’t ran Dism /Online /Cleanup-Image /RestoreHealth yet.

    Having done so, it unfortunately seems that neither commands find anything. sfc /scannow comes up with no corrupted files, and Dism /Online /Cleanup-Image /RestoreHealth does its thing but the issue persists. I do appreciate the suggestions, though!

    Edit: Am currently trying the HowToGeek fix. I can already say that the process ID in the errors links to the MalwareBytes application. I’ll try uninstalling that, see how it goes

15. Okay, so the HowToGeek method didn’t fully solve my issue, but did give some insight. I uninstalled MalwareBytes, but now a new process is identified by Event Viewer in the errors for Windows Management Instrumentation: svchost.exe. I’d assume that this is the Service Host for WMI. Unsure what could be done to fix that error.

    But here’s the thing I’m confused about. In Services, I can three relevant separate services: Windows Management Instrumentation, WMI and WMI Performance Adapter. Windows Management Instrumentation starts and stops without problem. However, it is the Service called WMI that cannot be started, giving the aforementioned «WmiPrvSE.exe cannot be found». Yet, when I click on properties for this WMI service, it says that the display name is WMI, yet its service name is WMS.

    So here’s where I’m stuck, is this WMI (or WMS) different from Windows Management Instrumentation? This WMI (I’ll call it WMS from now on to avoid confusion) has a path to C:\Windows\wmi\netmon.exe. Yet, this folder doesn’t exist on any PC but my own. Do you guys see the WMS service (with a display name of WMI), or is me seeing that service maybe indicative of the larger problem?

    

    Screenshot of the WMS process with its path to executable. This is the Service that gives the error «WmiPrvSE.exe not found» when I attempt to start it (which always fails)

    UPDATE: Source of the error for WMS (WMI display name) comes from «nssm», shown below:

    

    Doing some research, that’s something called the «Non-Sucking Service Manager». Now, I’m not sure if that comes with Windows 10, but I don’t remember installing it. Is this program the cause of the issues, or may it just be the program reporting the error?

Read these next…

• 
  

  Secure USB drives without software

  Data Storage, Backup & Recovery

  Due to the ever changing ISO requirements I’m looking for options on secure USB drives.  These could be used on anything, e.g. Windows, Power, Linux, heck plugged into different hardware depending on the need.Just wondering if any one has any recommandati…

• 
  

  Nerd Journey # 235 — The Best Bad Option with Al Elliott (1/2)

  Best Practices & General IT

  There may be some experience you’ve had which makes you uniquely positioned to help someone out of that same situation.  After going bankrupt when his first business venture went under and learning everything he could about the things bankruptcy involved,…

• 
  

  Spark! Pro series – 9th October 2023

  Spiceworks Originals

  October, the month of Pumpkin Spice, Scary Movies and
  Halloween.  I love Halloween, it is the
  one day a year that I fit in (and I don’t wear a mask! LOL).  Anyway, grab a pizza and a beer and sit back
  and enjoy t…

• 
  

  What kind of workspace do you have?

  Spiceworks

  I bought a new desk recently, and I had to make sure that it was deep enough for monitor stands, laptop plus keyboard, wrist rest, etc.  I don’t know how people can live with those shallow little desks that you can’t even fit an external keyboard onto.  O…

• 
  

  Which network diagram (SAN to LAN) would you say is correct?

  Networking

  Which is best practice and why? Is it done one way over the other to avoid potential issues or is it just good housekeeping . . . or both?Edit for context . . . To the left — 3-node Hyper-V failover cluster connected to shared dual-controller storage via …