For several years I have successfully installed software through the use of Group Policy to remotely install (distribute) software to our computers. I have run into an issue where a new computer hardware configuration for our Windows 10 clients is not installing software referenced in the GPO. The result is:
'Software Installation Pending 172 Millisecond(s) 11/18/2015 4:32:35 PM View Log
Software Installation did not complete policy processing because a system restart is required for the settings to be applied. Group Policy will attempt to apply the settings the next time the computer is restarted.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 11/18/2015 4:32:35 PM and 11/18/2015 4:32:35 PM. '
Obviously the install never completes no mater how many times the computer is rebooted.![Policy Policy](x-raw-image:///ac7c6fd252dd2249a25ad2818831d8a17ebe42038190b72baad7b55a0d7cd089)
The most obvious reason for the issue is that the NIC is not online, or the network is not yet available when the GPO is being processed on the client. Unfortunately (in a good way) the Group Policy Events log shows that the computer is connected.
The issue is currently isolated to a ne HP EliteDesk 800 G1 with a Samsung SSD. The computer boots to a login prompt in about 9 seconds or less. Similar computers that take longer to boot with our without an SSD are not exhibiting the issue.
Group Policy Events Log
4016 11/18/2015 4:32:35 PM Starting Software Installation Extension Processing. List of applicable Group Policy objects: (Changes were detected.) PrismCleanInstall2010 Jredist64 Event XML![Policy Policy](https://content.spiceworksstatic.com/service.community/p/how_to_step_attachments/0000071556/539b2de0/attached_file/7aea681383a14b5dc0bd985eafd3c7169c215f27ff757b591f7d18114aa197bd_ADUC_adFeatures.jpg)
1112 11/18/2015 4:32:35 PM The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance. Event XML
6016 11/18/2015 4:32:35 PM Completed Software Installation Extension Processing in 172 milliseconds. Event XML
6035 11/18/2015 4:32:35 PM Software Installation Extension deferred processing until next synchronous foreground. Refer to a Resultant Set of Policy report for more information. Event XML
8016 11/18/2015 4:32:35 PM Software Installation Extension ({C6DC5466-785A-11D2-84D0-00C04FB169F7}) requests a sync mode process.
More information can be provided if a direction on where the issue may exist can be identified.
T his section explains why in some cases the policy settings apply successfully, but in other cases they do not. Security group policy is driven by the Userenv.dll library running within the Winlogon.exe process, or on Windows Vista and later, the Group Policy Service (GPSvc).
'Software Installation Pending 172 Millisecond(s) 11/18/2015 4:32:35 PM View Log
Software Installation did not complete policy processing because a system restart is required for the settings to be applied. Group Policy will attempt to apply the settings the next time the computer is restarted.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 11/18/2015 4:32:35 PM and 11/18/2015 4:32:35 PM. '
Obviously the install never completes no mater how many times the computer is rebooted.
The most obvious reason for the issue is that the NIC is not online, or the network is not yet available when the GPO is being processed on the client. Unfortunately (in a good way) the Group Policy Events log shows that the computer is connected.
The issue is currently isolated to a ne HP EliteDesk 800 G1 with a Samsung SSD. The computer boots to a login prompt in about 9 seconds or less. Similar computers that take longer to boot with our without an SSD are not exhibiting the issue.
Group Policy Events Log
4016 11/18/2015 4:32:35 PM Starting Software Installation Extension Processing. List of applicable Group Policy objects: (Changes were detected.) PrismCleanInstall2010 Jredist64 Event XML
![Policy Policy](https://content.spiceworksstatic.com/service.community/p/how_to_step_attachments/0000071556/539b2de0/attached_file/7aea681383a14b5dc0bd985eafd3c7169c215f27ff757b591f7d18114aa197bd_ADUC_adFeatures.jpg)
1112 11/18/2015 4:32:35 PM The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance. Event XML
6016 11/18/2015 4:32:35 PM Completed Software Installation Extension Processing in 172 milliseconds. Event XML
6035 11/18/2015 4:32:35 PM Software Installation Extension deferred processing until next synchronous foreground. Refer to a Resultant Set of Policy report for more information. Event XML
8016 11/18/2015 4:32:35 PM Software Installation Extension ({C6DC5466-785A-11D2-84D0-00C04FB169F7}) requests a sync mode process.
More information can be provided if a direction on where the issue may exist can be identified.
Well this is just as annoying as can be but it turns out to be pretty quick to resolve. If you reboot your client PC’s but find some software you pushed via Group Policy did not install, you likely are in Asyncronous Policy Processing Hell.
First verify that the policy did make it to your test PC by launching a CMD window (don’t forget to RUN AS ADMINISTRATOR) and typing GPRESULT. Just look for your GPO under COMPUTER. Also check the event log of your test PC and look for The error was : %%1274
Since Windows Server 2003, XP and newer clients don’t wait for the network components to fully load before allowing a user to login. This makes boot times faster but means that Software Deployments via Group Policy almost always require TWO reboots. Also, you can get the dreaded:
System Event 108 “The error was : %%1274”
and never get an install completed.
- Delete the GP Key from the client PC’s registry: HKLM/SOFTWARE/Microsoft/Windows/CurrentVersion/Group Policy
- Turn Asyncronous Policy Processing off by creating a new GPO (or editing an existing one) with the following setting:
Computer Settings > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon – Enabled
I figured this out using several blogs but the most useful and the one deserving the most credit is THIS ONE, in case you want to read more about it.