Event 1096 The processing of Group Policy failed

In case you see event 1096 (The processing of Group Policy failed) in your eventviewer, you’re experiencing problems with your group policies. The following event occurs several times in your SYSTEM LOG:

Log Name:     System
Source:       Microsoft-Windows-GroupPolicy
Event ID:     1096
Level:         Error
User:         SYSTEM
Description:
The processing of Group Policy failed. Windows could not apply the registry-based policy settings for the Group Policy object LocalGPO. Group Policy settings will not be resolved until this event is resolved. View the event details for more information on the file name and path that caused the failure.

 

To solve this issue, check the last modified date of the following file:

C:\Windows\System32\GroupPolicy\Machine\   and C:\Windows\System32\GroupPolicy\User\ 
(note: GroupPolicy is a hidden folder, you may need to enable hidden folders to navigate to this path)

 

 

An Attempt was to modify an object to include an attribute that is not legal for its class

Cause:
This problem comes when you are using a mixed-mode of OS in your AD environment such as you have Windows Server 2012 and Windows Server 2019 AD. If you have enabled the AD Recycle bin in mixed-mode of OS then this problem may come during the restore due to the schema version.


Solution:
In such environment where you are using mixed-mode of OS, always use the newer version of OS to perform any task. So in this case, you might be using the Win 2012 AD to restore the object. Use the latest OS AD, your restore should work fine.

Autoadminlogon is set to 0 when rebooting

To use Registry Editor to turn on automatic logon, follow these steps:

1. Click Start, and then click Run.
2. In the Open box, type Regedt32.exe, and then press Enter.
3. Locate the following subkey in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
4. Double-click the DefaultUserName entry, type your user name, and then click OK.
5. Double-click the DefaultPassword entry, type your password, and then click OK.

If you open regedit.exe and browse to HKLM:\Software\Microsoft\Windows NT\Current Version\Winlogon which is where you will also be storing the autologon username / password / domain, you should check for a DWORD called AutoLogonCount.... If this is set to 0, then on next reboot it will strip the password and set the AutoAdminLogon value back to 0. If you up the number, or simply delete the DWORD, all should come back to life as you'd expect.