sparkeh Posted January 25, 2016 Posted January 25, 2016 It appears that we are having an intermittent issue with initial logons with Win 10. Basically, every so often, when a user logs onto a machine for the first time they get a blue screen with "System cannot connect to notification service" and then get logged out again. If they try and log in again, the logon takes ages (a few minutes) and they get a desktop but with no group policy applied. If rather than trying to login again they reboot the machine they can login fine with all GPs applied. Anyone else seen this?
Michael Posted January 25, 2016 Posted January 25, 2016 Can't say I have to be honest. What Windows 10 build/version are you using?
sparkeh Posted January 25, 2016 Author Posted January 25, 2016 Can't say I have to be honest. What Windows 10 build/version are you using? Build 10586 Can't say I remember it happening with the previous build. If I look in the event log I can see a long list of services crashing and trying to restart but no clue as to why causing it.
Michael Posted January 25, 2016 Posted January 25, 2016 I'm using build 10240 with the latest January 2016 update and haven't had any reports of such issues. If it's just the one device, you could try re-imaging it. Typically many core services that are unable to start can be caused by registry issues.
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