Windows 10: Event View warning can I ignore this?

I was checking my Event view and evey time I start up my divice i see a warning about the SID not maching for few application and cannot be restarted.event ID 10010Should I ignore this?

:)

 

Export All Administrative Events to Excel

To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.

 

CertificateServicesClient-AutoEnrollment Warning Event ID 64

Hi, this is a new Warning in my laptop, never seen it before with previous versions of Windows 10. During the first 3 days after upgrading to Fall Creators Update, I didn't get any. But yesterday, for the first time, an CertificateServicesClient-AutoEnrollment Warning Event ID 64 was logged in Events viewer. Today, I got another one after starting the laptop.

I searched Google and found that the Warning has something to do with an expired certificate. I know nothing about certificates or how to properly handle something like this, I found this link below, it suggest to use Troubleshooting/System Maintenance. The instructions are easy to follow and carry on.
Expired Certificate - Microsoft Community

But my questions are, Is this something new with FCU? Are other people getting this Warning 64? Should Microsoft fix this on its own or should I run System maintenance? Is this a benign Warning event that can be ignored?

My W10 is running perfect, I cant find nothing wrong with it. I even find less Warning and Errors being logged in Events viewer with this version than before but I never seen this one and it seems its gonna show up every day unless it gets taken care of.

Appreciate your help

Bo

 

Event 8303 warning, System-Restore

Hi Shelseal

Rest assured, this event warning is absolutely nothing to worry about, it basically refers to Windows not being able to create a log entry and this will not affect the performance or stability of your system

Even a fully healthy Windows 10 system is generating these events and errors in the background all the time, Windows is designed to recover form these without the user even being aware that anything has happened, you can safely ignore this type of event . .
.