Eventviewer ; id=1108

Anonymous
2022-10-17T15:58:19+00:00

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??

Windows for home | Windows 11 | Performance and system failures

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.

0 comments
Answer accepted by question author
Ramesh 181.8K Reputation points Volunteer Moderator
2022-12-04T05:01:36+00:00

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."

Was this answer helpful?

0 comments

63 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-11-13T16:13:33+00:00

    Hi, still no solution...............???

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-27T13:45:43+00:00

    Hi , just received news from the ESET-forum .

    id=1108 is definitly not an ESET-item !

    A forum-member uninstalled ESET completely , after reboot the error id=1108 still persists...........

    So, we have to search in other corners !

    Will wait , untill you know more..........

    fr.gr.P.Sponselee

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2022-10-27T10:40:37+00:00

    Sorry , but uninstalling my defence is going a bit too far , for me.

    I will ESET inform about id=1108 .

    " I've asked other poster who has the same issue if they're running ESET.".... lets hope it will solve the problem !

    After respons , will let you know .

    btw; saw on the internet , it could be an ASUS-problem as well ........

    Im beginning to think ; its impossible to get rid of this buggy id=1108.

    Only an update from MS will solve the problem.

    If theres anything I can do further , let know, please........

    fr.gr.P.Sponselee

    Was this answer helpful?

    0 comments