It sounds like you can just log out and back in to fix it? For a local system, the article says it only occurs for “First time user logon after a cumulative update was applied.”