These applications will not support non-elevated environments. This can also happen when you try to logon using a non admin account in a PC that had some applications or drivers that were installed with admin privileges before. A bad shutdown or startup process can also cause this issue. Usually, this is caused by system updates and upgrades that might mess with the registry. This could be due to bad registry calls or a corrupt registry. Therefore this error is caused by a group policy that fails to respond or if it stops running. Because communications have already been established before the service isolation, Winlogon can no longer contact the Group Policy service, and this results in the error message that is described in the Symptoms section.
The Group policy service then isolates itself into a separate SVCHOST process (it is originally running in a shared process with other services).
Winlogon communicates with the Group Policy service (GPSVC) through a call upon system startup for computer policy and with user logon for user policy. How logging in works and why a login error occurs We will then give you solutions to this problem. This article will explain to you how logging in works and why this problem occurs.
