Windows 10: Error ID 1060 in Event Viewer: How to Fix "Application Popup" Issue at Startup?

Hello everyone,I've been encountering an error every time I start my laptop and check the Event Viewer. The error message is as follows:"The description for Event ID 1060 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.

:)

 

How to fix Application Error in Event Viewer

Hi, I recently installed Wacom Cintiq 16 driver from Wacom website (that latest one), up on restart my PC It appears on Event Viewer as Application Error that the application has an issue, last time this happens It froze my PC and had to forces shutdown, the froze were not just monitor but also mouse and keyboard the keyboard was unable to Num-Lock or Ctrl+Alt+Del, at first I thought I had a faulty components but that was not the case

Here what It listed for me in general this time in Event Viewer:

Faulting application name: WacomCenterUI.exe, version: 6.4.5.5005, time stamp: 0x656f0000

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3996, time stamp: 0xb756c9ff

Exception code: 0xc000027b

Fault offset: 0x000000000012d952

Faulting process id: 0x2394

Faulting application start time: 0x01da7694ff1c4ab7

Faulting application path: C:\Program Files\Tablet\Wacom\WacomCenter\WacomCenterUI.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 43c874f8-807f-4f4c-883d-12301c4461a9

Faulting package full name:

Faulting package-relative application ID:

Thank in advance,

 

Event viewer error with event id 10016

Hello,

Thank you for posting your query on Microsoft Community forum.

I understand that you are getting an error “DistributedCOM 10016” in the event viewer logs.

• Do you face any issues on the computer?
  
• Have you made any recent changes to the computer?

This problem may occur if either of the following conditions is true:

• A program with the class ID (CLSID) that appears in the message tries to start the COM component by using the DCOM infrastructure. However, the user does not have the required permissions to start the COM component.

• The Network Service account does not have the correct permissions.

Event logs are special files that record significant events on your computer, such as when a user logs on to the computer or when a program encounters an error. Whenever these types of events occur, Windows records the event in
an event log that you can read by using Event Viewer. Advanced users might find the details in event logs helpful when troubleshooting problems with Windows and other programs.

If you do not have any issues with app or any other program I would suggest you to ignore it.

Keep us posted if you face any issues related to Windows in future. We will be glad to help you.

 

Startup Error in Event Viewer

Hi

Welcome to Microsoft community.

The error you're seeing in the Event Viewer, "Session 'Microsoft.Windows.WindowsUpdate.RUXIMLog' failed to start with the following error: 0xC0000035," is generally not something that should cause immediate concern. This specific error code, 0xC0000035, often indicates a situation of "STATUS_OBJECT_NAME_COLLISION," which means that a file or object with the same name already exists. In the context of Windows Update or its logging mechanism, this can happen during normal operations and doesn't necessarily indicate a critical problem with your system or its ability to receive updates.

However, if you're experiencing issues with Windows Update not functioning correctly (e.g., updates not downloading, installing, or getting stuck), or if this error is accompanied by other system performance issues, you might want to perform some troubleshooting steps:

1. Run Windows Update Troubleshooter:
   
   • Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters.
     
   • Run the Windows Update troubleshooter and follow any recommendations it provides.
     
2. Check for Updates Manually:
   
   Sometimes, simply checking for updates manually can resolve issues. Go to Settings > Update & Security > Windows Update and click on Check for updates.
   
3. Clear the Windows Update Cache:
   
   • Sometimes corrupted files in the Windows Update cache can cause issues. You can clear the cache by stopping the Windows Update service, deleting files in the C:\Windows\SoftwareDistribution directory, and then restarting the Windows Update service.
     
4. Check System Files:
   
   • Corrupted system files can lead to all sorts of issues, including update problems. Run the System File Checker tool by opening Command Prompt as an administrator and typing sfc /scannow
     
5. Review Other Event Logs:
   
   • Check for other errors or warnings in the Event Viewer that might indicate more serious issues. Pay special attention to the System and Application logs around the same time as the WindowsUpdate.RUXIMLog errors.
     
6. System Restore:
   
   • If the issue started recently and you can't find another way to fix it, consider using System Restore to roll back your system to a point in time before the problem began, if available.
     

If after these steps the issue persists but your system seems to be updating and operating normally, it's likely that the error can be safely ignored.

Let me know if you need further assistance.

Best regards

Derrick Qian | Microsoft Community Support Specialist