This was caused by our antivirus, SentinelOne agent. Disabling it got rid of this error printout, reenabling it brought it back.