Windows 10: Application popup: : Error 0xd000006a: Failed to stop sensor. Why this event occurs?

Application popup: : Error 0xd000006a: Failed to stop sensor.

:)

 

Event ID 26 Application popup, Application error

Hello,

I have some servers that are still running under windows 2012r2.

Sometimes, users get a popup with the following errors :

Application popup: WerFault.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application.



Application popup: RdrCEF.exe - Application Error : The application was unable to start correctly (0xc0000022). Click OK to close the application.

I updated adobe reader and still get the error.

Is it related to user profile ?

Can we disabled those application popup ?

Regards

Rweiss

 

Event Error 56 -Application Popup

I recently upgraded to Version 1803 (OS Build 17134.48), for Windows 10. While basically pleased that everything went well with and following the version update, I am left with one unresolved Event error ID 56, that I cannot find a solution for. Below is
a copy of the Event Details;

Log Name: System

Source: Application Popup

Date: 5/19/2018 6:56:41 AM

Event ID: 56

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP

Description:

The description for Event ID 56 from source Application Popup cannot be found. Either the

component that raises this event is not installed on your local computer or the installation

is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the

event.
The following information was included with the event:
ACPI

5
The message resource is present but the message was not found in the message table

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Popup" Guid="{47bfa2b7-bd54-4fac-b70b-29021084ca8f}"

EventSourceName="Application Popup" />

<EventID Qualifiers="49156">56</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2018-05-19T13:56:41.273175700Z" />

<EventRecordID>3514</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="208" />

<Channel>System</Channel>

<Computer>DESKTOP</Computer>

<Security />

</System>

<EventData>

<Data>

</Data>

<Data>ACPI</Data>

I have traced the GUID{47bfa2b7-bd54-4fac-b70b-29021084ca8f} referred to in the event log, changed permissions and ownership applied to the key, but that did not help. I also made a copy of the specific registry key, saved it, and deleted the key value
from the registry. The same event error 56 appeared at the following restart (boot up), so replaced deleted key value with saved copy. The full text of the indicated GUID={47bfa2b7-bd54-4fac-b70b29021084ca8f}, is :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\ CurrentVersion\WINEVT\Publishers\{47bfa2b7-bd54-4fac-b70b-29021084ca8f} . While I have read this event is non-critical, it is the last and only event error I continually find, after resolving the continual
reappearance of Event Errors 10016, by changing permissions, and would be appreciative of any help in resolving this last annoying issue.

 

Event ID 56 Application Popup not found error

• Event ID 41 isn't recorded or the bug check code is zero. This behavior might indicate a power supply problem. If the power to a computer is interrupted, the computer might shut down without generating a Stop error. If it does generate a Stop error, it might not finish writing the error codes to disk. The next time the computer starts, it might not log Event ID 41. Or, if it does, the bug check code is zero. The following conditions might be the cause:
  
  • In the case of a portable computer, the battery was removed or drained.
    
  • In the case of a desktop computer, the computer was unplugged or experienced a power outage.
    
  • The power supply is underpowered or faulty.
    

(Src: Event ID 41 The system has rebooted without cleanly shutting down first)





So, in all probability, it's the power supply.