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: Most helpful
Most helpful Newest Oldest
  1. Ramesh 181.8K Reputation points Volunteer Moderator
    2022-10-21T14:51:51+00:00

    No security event entries were recorded during the trace. Perhaps you can re-run a trace for an even longer duration. Please Zip the file before uploading.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-21T14:35:24+00:00

    Here you are ; " https://www.upload.ee/files/14603151/Logfile.PML.html "

    Just rund from Sysinternals , about 1 to 2 minutes .........

    Will wait for answer.

    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-21T14:06:17+00:00

    HI , just tested ; " See if that stops the logging of security event 1108.

    The above is not a final solution. It's a way to test if the audit settings are causing the issue. "

    The id=1108 issue still present !

    No solution still , lots of people are reporting the same id=1108 .

    Wonder if its possible to fix it , after trying several things , maybe MS is the only one who can fix it , coz it seems to be a bug...........

    Waiting for solution still.......

    fr.gr.P.Sponselee

    Was this answer helpful?

    0 comments