This message was deleted.

I’ve seen this ctxkb numerous times in the last days and I’m quite confused. This policy would have to be enabled on purpose to trigger this specific error, hasn’t it? I wonder how this could affect many different environments?

hmm thanks to you, I reread it...initally thought you had to ENABLE that setting to fix it but you're right...we never had that enabled and encountered the problem.