This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After every reboot , we get id=1108 in the eventviewer , how (?) to stop these errors ?
There are everytime 20 errors , with id=1108 .
How to get rid of it??
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
On my system, the 1108 events stopped after updating to 22621.900.
But, some 4688 (Process creation event) entries are appearing now.
From November 29, 2022—KB5020044 (OS Build 22621.900) Preview:
"It addresses an issue that affects process creation. It fails to create security audits for it and other related audit events."
Hi, " I think the original setting should be fine; it should provide enough data for us. " , ok , so will not change the standard settings .
The option "clean Install " is a big operation , and these id=1108 errors not worth.
Very much software , incl. Office 21 , etc, on it , so will search for the cause of the error.
A solution within a next WU-update , is possible still ( ?)
Rest me to thank you very much for your fine support , hope to contact you again in a few days , while collecting some more event-info.
Untill next week,Tuesday !
fr.gr.P.Sponselee
I think the original setting should be fine; it should provide enough data for us. But if you want to archive the logs, in Event Viewer, expand Windows logs, right-click "Security," and click Properties. You'll see the archive option in that dialog.
//Searched the internet , lots of people have the same problem , though many of them , with a clean install (!) , dont have this problem.//
Yes, I saw that too. Let's see if we can identify the root cause. 🤞 However, if you're ready to do a clean install, that would be the hassle-free option.
Hi, " But you can choose "Archive the log when full, do not overwrite events" if required. " , how(?) to do this , dont want to make the same mistake twice , by deleting info , we may need for solving the ID=1108 problem !
I have a second ( new) desktop , just upgraded to 22H2 also .
They both have the same id=1108 errors.
Searched the internet , lots of people have the same problem , though many of them , with a clean install (!) , dont have this problem.
Will wait for your reply...
fr.gr. P.Sponselee
Windows will purge the oldest entries in the log once the log reaches 20 MB. But you can choose "Archive the log when full, do not overwrite events" if required.
//Is there anything we can do in the meantime , untill next week/tuesday ?//
Don't know. But you can try clean-booting Windows to see if the entries stop.
