I saw this on some of my initial win2016 builds a few years ago
My issue was with patching running the systems out of real memory and required paging.
At the time the paging was set to system managed and it started lests than a gig and grown on demand. Since this was the final boot and updates were being applied service failed to start due to lack of memory. Because systems slowly grew their page space the issues randomly stopped for some while on others it started.
MS in their great paging algorithms - when a process needs memory and the paging space needs to grow to compensate for not enough free real memory, it does not pause the request and grow the space - instead it fails the process and grows the space. The solution was to not have paging set to system managed and set most of my systems with hard Min 7g max 8g page spaces.
We don’t ever want to page but some times you cant see it coming, and need to provide for that one off scenario, otherwise I would rather fail the system then live day to day with paging