Windows 10 not applying Startup GPOs - not waiting for network

[ass17]

Hi all,

 

Anybody else overcome the issue we’re having above?

 

We have just installed windows 10 edu 1709 and the PCs don’t wait for the network and thus fail to load startup scripts.

 

I’ve tried the usual startup delay network stuff in the GPOs, UNC hardening paths, netbios dns record to a DC IP etc, turned off the Hibernation/fast startup stuff, all no good.

 

The only way I can solve it is to put a delay script as a local startup GPO on each PC.

 

This is not ideal, and the issue only seems to happen on PCs with SSD drives.

 

Any help?

Thanks

Edited July 11, 2019 by ass17

[Oaktech]

I'm out... Turning off faststart did the trick for us. Sorry!

 

As a side note, I skipped 1709 as a deployment because I found it broke/had weird behaviour with redirected start menus. You might do better trying 1803 which I have found the be the most stable of the lot so far.

[ass17]

Ok thanks, going to upgrade one pc to 1903 and see what happens. We do have a policy turned on regarding cached logins so if we turn it off it may improve things a little...

[Duke5A]

Saw this in June with 1903.

 

Computer Configuration > Administrative Templates > System / Group Policy: Specify startup policy processing wait time

 

Set it to enabled and give it a value of 30 seconds.

 

What baffles me is 30 seconds is the default waiting period if this policy isn't configured, but Windows just ignores the default. Enabling and setting the default value then magically Windows pays attention to it.

[ass17]

Will take a look thanks, how do you know if the 30 secs elapses? Eventlogs? Please wait on blue screen stays on for longer?

[Oaktech]

You don't. It just makes sure it receives a full gpo sync and fully evaluates it before it moves on.

 

The other setting that might help is the setting to fully evaluate even if policy hasn't changed.

[ass17]

Ok great thanks, will have a play. Will set them in a GPO and apply then to both 1709 and 1903 to see if works on both..

[browolf]

What does it mean when you enable "Always wait for the network...." and it doesn't work? I've watched the registry key change in the registry with process monitor and gpupdate /force. (reg info)

 

and every reboot the same 1129 & 1130 events.

 

edit: must have been a bad image or something. reimaged it and suddenly works fine.

Edited October 15, 2019 by browolf