Humbird/ConiGL - still good with 1903?[/QUOTE]
Still no 5061. This seems to have been ironed out in 1903 for me. I have been having a few vss errors in 1903 as have a few others.I have only seen them twice where others see them every shut down.
Humbird/ConiGL - Updating to 1903 has solved this problem, as you said. Too bad MS won't fix it for 1803 or 1809.
Thanks.
As I pointed out earlier in the thread, I didn't start to get these audit failures on the laptop until I updated to version 1903; so I really don't think a Version of Windows has anything to do with it at all. It all comes down to if the files exist in the Crypto folder or not and I have already seen that they did not exist in my 1903 upgrade on the laptop.
For the desktop, all the files were there. Something interesting that I also noted about the files in the S-1-5-18 folder; there are never the same amount of files at any given boot time. They fluctuate between or from 590+ files to 634+ files and auto delete or create as needed.
The problem seems to be that the Cryptographic operation of generating the needed files is encountering an error that prevents the files from auto generating again on a boot procedure, thus throwing the audit error.
Just FYI, anything associated with the S-1-5-18 SID is associated with the "Local System" account. It represents working objects the the OS creates and uses as it engages in normal operations. Here's a snip from that ever-so-fascinating MS Support document Well-known security identifiers in Windows operating systems
HTH,
--Ed--
@EdTittel
O.K.- So what is the bottom line best guess you can make on why Cryptographic Audit Failures are occurring only on certain systems?
I had explained earlier in the thread that the S-1-5-18 folder was next to empty on my laptop after the upgrade to 1903; however the desktop when upgraded to 1903 had a full file directory in the S-1-5-18 folder.
Something is not right and grant it no two systems are alike, I want to know why transplanting the files to my laptop from my desktop fixed the Audit Failures.
I just don't understand what is going on with all this Micro-coding Microsoft is pushing to older and newer systems alike trying to match system compatibility issues up with the wave of one magic wand that isn't working.
In other words, this Micro-coding is causing the slow death of systems and it needs to be addressed because it is reaching machines that it should never be on.
Gosh @EyeInTheSky, I wish I could answer your questions. I'm as stumped as you to understand why two different systems sometimes have such different outcomes when Windows 10 installs, upgrades or updates get applied. With 9 machines here -- 6 of them test PCs -- I've seen this many times myself as well for all kinds of situations. Wish I could be of more help.
--Ed--
One of the greatest mysteries of Windows from the very beginning to now. :)
Hey @EdTittel, I noticed your last post was just a little over 16 hours ago and I posted about 13 hours ago quoting you and I woke up this morning to find you still logged into this thread. I figure since you have nine machines, that it is very possible that you forgot to sign-off on one of them because 16 hours eyeballing a thread with only 40 posts is a little long and I figure you have read over it about three or four times by now!
Just checking to see if you are O.K. because I have fallen asleep at my computer many times; but to be still logged into the same thread for over 16 hours, is a little Eye catching.
Last edited by EyeInTheSky; 20 Jun 2019 at 10:55. Reason: scanning
Quote
