Excessive Security Log Events - Event ID 5379 - Windows 10

@SMichaelH3 - The "black popup window" is actually the CMD (command shell window) - used to be called the "DOS prompt". However, many older (and some newer) WIN32 programs (.EXE executable programs), such as photo or video editors, music file editors and old utilities, will often use a batch file (.BAT file type) that runs, often just after booting up, that will check that you have a valid current licence key, and if there are any updates needed. Batch files can run very quickly, and they do NOT leave the CMD prompt open, hence you see it appear and go very quickly. I saw a post that certain AMD based PC/Laptops have the AMD Catalyst Control centre that can do that CMD thing as well.
Given the speed of modern CPU and harware, and the likelyhood that several BILLION instructions and I/O calls are made during a typical boot and PC initialise, AND probably Billions more during the "post-boot phases" (checking PC health, programs checking for valid licences, onedrive and Dropbox sync checks, Ant-Virus definition update checks etc), then unless you are running a special "debug windows build", and have trace and log analysis tools, then is NO possible way that you will be able to KNOW and PROVE, that a bunch of 5379 events were EXACTLY coincidental, and the root cause (or effect of) of the CMD windows appearing. Actually ANY activity that uses your user profile (your login account environment files basically, plus related "system" account activity) will trigger the "audit success" event 5379, plus some other similar types for running services. Because of the "parallel" overlapping core/thread activities, many things can appear to be happening very close together, and in a microsecond, MANY CPU operations and instructions happen, running on behalf of many active processes. In additon, those processes that execute an I/O (input/output operation) can be "context switched" out and in a wait state, allowing other processes to get some "CPU time" for their instruction sequences.

Yes, it is a problem. My computer ran all night doing successful audits (5379). It's doing it now. It does it ceaselessly.

@RemoteComputerTechnician:

Do you regularly check your Event Logs for the 5379 "Audit Success" events?

If so, are you stating that after your profile change, these have stopped completely, or have they just reduced to an acceptable level?

I am also curious how you "moved" all of your required profile items, as quite often, profile manipulation of files INTO an active loaded (logged in) profile can be blocked. Was it done via a manual "drag and drop", or a PowerShell script, CMD/DOS script, or a third party product?

Did ALL of your normal/expected win32 programs and APPS work as normal with your new profile. Was this a LOCAL account or Microsoft Account profile by the way?

I can confirm these steps do not resolve the issue.

so does anyone have a fix for this or nah? is it as simple as updating or is this something I have to live with now.