Sheridan Posted October 29, 2018 Posted October 29, 2018 We’ve got a bunch of around 20 pcs, of differing hardware but all the same 1703 w10 images that are really frustrating me with a login problem. Randomly, a users login will just hang at the Welcome stage, and stay there indefinitely. Rebooting may work, and it affects all users including admins, although it seems less so with admins. We’ve tried updating some of them to 1803, but it made no difference and the event logs show nothing significant, just the normal messages you’d see during a login, but it just stops at that stage. This is on 4 different types of hardware, and this is where is gets a bit weird, if we move one of the pcs to another room and another switch it seems to work, but moving any pc into its place also works fine as well! Our switch configs are identical anyway as the switches are all the same so I’m doubting a network issue, and we do have other pcs on the same switch that work fine, but using a different image, and even pcs on the same subnet but a different switch work fine as well. So it’s the combo of this image on this switch cabinet that I can’t fathom, anyone seen anything like this before? Ironically when the pcs were all running w7 previously they were absolutely fine!
mavhc Posted October 29, 2018 Posted October 29, 2018 anything in the event log? https://superuser.com/questions/594625/how-can-i-analyze-performance-issues-before-during-the-logon-process
Sheridan Posted October 29, 2018 Author Posted October 29, 2018 Nothing in the standard event logs, just the normal group policy processing messages, the same set of events appear for a normal login as for a failed one. I’ll try and get some verbose logging and see if it reveals anything.
Sheridan Posted October 30, 2018 Author Posted October 30, 2018 Well it looks like this one is down to printers - which is a depressingly familiar problem with W10. It seems that because these PCs have 2 shared printers deployed to them (using User GPP deployed printers and item targetting) it causes the problem - and the only reason I can see is that the two shared printers are the same model/driver, which seems to cause the logins to 'lock' when the drivers are being installed, perhaps stuck in a race state? Changing the driver on one of the printers to a Universal driver and we haven't had a failed login since. Verbose logging hangs on the Group Policy Printers stage. The Register is right, W10 is a sh-t shower - this problem would actually cause the PC to hang at the Welcome stage (and it would never recover, we even left one for 24 hours) and a cold boot is the only solution. It was random, but presumably that was just down to the printer driver installer overlapping itself sometimes, other times they maybe completed synchronously and therefore worked. We still have the same problem of the printers not appearing until the second login, but that won't ever be resolved unless we go back to Windows 7!
Arthur Posted October 30, 2018 Posted October 30, 2018 We still have the same problem of the printers not appearing until the second login, but that won't ever be resolved unless we go back to Windows 7! Could your anti-virus (Sophos?) be causing the printer drivers to not install properly on the first attempt?
Sheridan Posted October 30, 2018 Author Posted October 30, 2018 Could your anti-virus (Sophos?) be causing the printer drivers to not install properly on the first attempt? We do use Sophos but only for AV, not the malicious software stuff? We're still having logins freeze occasionally on other PCs as well, so my 'fix' isn't working everywhere. I guess staff here have got used to rebooting their PCs when a login hangs so often they just don't tell me anymore! It looks like I'll have to revert back to the old scripted printer installs, printers don't work with GPPs in W10 anymore it seems
Sheridan Posted October 30, 2018 Author Posted October 30, 2018 And it gets weirder - still happening randomly even though I thought I'd found a reason, and I've now noticed that some of the PCs show mutiple (i.e 5+) copies of the shared printers! So if they have 3 printers assigned to them in GPP they can see 15-20 of them in the Printers control panel - but only the 3 show up in an application such as Word.
mavhc Posted October 30, 2018 Posted October 30, 2018 Sounds like your drivers are broken. If your printers are the same model you only need 1 driver
Sheridan Posted October 30, 2018 Author Posted October 30, 2018 That’s the thing, the multiple copies of the same printer are all showing exactly the same driver, down to the version number!
Sheridan Posted October 31, 2018 Author Posted October 31, 2018 (edited) This is turning into a nightmare, its happening in random places, PCs just hang at Welcome, and the last thing logged was "The winlogon notification subscriber is taking long time to handle the notification event (Logon)." But you can browse the C: drive remotely, connect to the event viewer etc, but you can't login and once its stuck in this state you can only recover with a cold boot. I'm really looking forward this when everyone is back next week! The detailed gpsvc.log shows its hanging during the printer preferences stage - but no real clue as to why, it just stop dead and no more logging happens either. GPSVC(198.23c) 10:39:23:483 ProcessGPOList:++ Entering for extension Group Policy Printers GPSVC(198.23c) 10:39:23:483 UserPolicyCallback: Setting status UI to Applying Group Policy Printers policy GPSVC(198.23c) 10:39:23:489 LogExtSessionStatus: Successfully logged Extension Session data GPSVC(198.23c) 10:39:23:490 ProcessGPOList: lpGPOInfo->lpGPInfoHandle->dwExtnCount is 2 for Group Policy Printers. GPSVC(c14.c34) 10:39:23:740 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000005BC GPSVC(c14.c34) 10:39:23:740 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c34) 10:39:23:761 CGPNotify::RegisterForNotification: Entering with target Machine and event 000000000000060C GPSVC(c14.c34) 10:39:23:761 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.15bc) 10:39:23:784 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000007AC GPSVC(c14.15bc) 10:39:23:785 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(240.1c4) 10:39:25:512 CGPNotify::RegisterForNotification: Entering with target Machine and event 000000000000022C GPSVC(240.1c4) 10:39:25:512 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(240.1c4) 10:39:25:513 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000284 GPSVC(240.1c4) 10:39:25:513 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c30) 10:39:28:682 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000CD8 GPSVC(c14.c30) 10:39:28:682 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c30) 10:39:28:683 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000D20 GPSVC(c14.c30) 10:39:28:684 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(580.4cc) 10:39:33:782 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000214 GPSVC(580.4cc) 10:39:33:782 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(580.4cc) 10:39:33:783 CGPNotify::RegisterForNotification: Entering with target User and event 000000000000026C GPSVC(580.4cc) 10:39:33:783 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(e78.df4) 10:40:21:609 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000438 GPSVC(e78.df4) 10:40:21:609 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(e78.df4) 10:40:23:622 CGPNotify::UnregisterNotification: Entering with event 0000000000000438 GPSVC(e78.df4) 10:40:23:622 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0 GPSVC(eb4.c84) 10:40:25:081 EnterCriticalPolicySectionEx: Machine from process 3764. GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Entering with usersid = (null), timeout 600000 and flags 0x30000000 GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Making Aync RPC LockPolicySection call GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Beginning WaitForSingleObject. GPSVC(198.548) 10:40:25:082 bMachine = 1 GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Completed WaitForSingleObject. GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Machine critical section has been claimed. Handle = 0x00000235FC6865C0 GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Leaving successfully. GPSVC(eb4.c84) 10:40:25:273 Client_UnLockPolicySection: Starting UnLock Call GPSVC(198.548) 10:40:25:274 Setting lock state as notLocked GPSVC(198.548) 10:40:25:274 CPolicyCriticalSectionCollection: Deleting critical section for UserSid <(null)> GPSVC(198.548) 10:40:25:274 Deleting machine GPSVC(eb4.c84) 10:40:25:274 Client_UnLockPolicySection: Unlocked successfully GPSVC(eb4.c84) 10:40:25:275 LeaveCriticalPolicySectionInternal: Critical section 00000235FC6865C0 has been released. GPSVC(398.1224) 10:40:33:196 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002EC GPSVC(398.1224) 10:40:33:196 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(398.1224) 10:40:33:197 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000338 GPSVC(398.1224) 10:40:33:198 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(15d8.c68) 10:40:33:436 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002CC GPSVC(15d8.c68) 10:40:33:437 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(15d8.c68) 10:40:33:438 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000318 GPSVC(15d8.c68) 10:40:33:438 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(ce4.bfc) 10:40:33:486 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002CC GPSVC(ce4.bfc) 10:40:33:486 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(ce4.bfc) 10:40:33:488 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000318 GPSVC(ce4.bfc) 10:40:33:488 CGPNotify::RegisterForNotification: Exiting with status = 0 Edited October 31, 2018 by Sheridan
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now