CameronDuclos Posted June 20, 2018 Posted June 20, 2018 Hello Everyone, I'm just posting to find out if anyone else is having this issue. I have started to see an issue arise after upgrading the PCs to Windows 10. Basically, what happens is it will all be working fine then a different student will log on and it will just have a black screen but the cursor showing. If they log on somewhere else its fine so it cant be a profile issue. I have a temp fix for the issue which is to log them off and log back on. That works but I'm just wondering why it's doing it in the first place. Thanks Cameron
free780 Posted June 20, 2018 Posted June 20, 2018 Which build of Windows 10 do you have deployed? Which profile type are you using? 1
CameronDuclos Posted June 21, 2018 Author Posted June 21, 2018 Windows 10 pro 1803. We use roaming user profiles
Oaktech Posted June 21, 2018 Posted June 21, 2018 Got Impero? Add DLLHost.exe to injection exclusions... 1
CameronDuclos Posted June 21, 2018 Author Posted June 21, 2018 Yes I do have Impero but I'm new to it. Where do I manage the injection exclusions?
Steve21 Posted June 21, 2018 Posted June 21, 2018 Under the Impero Server (not console) go to tools -> injection exclusions Steve 1
DCUK6 Posted June 21, 2018 Posted June 21, 2018 Having the same issue here, http://www.edugeek.net/forums/windows-10/196616-black-screen-cursor-new-image-2.html#post1684433 Uninstalled impero and it worked fine. Event viewer gave no errors. Just got of the phone with a impero tech and we checked the impero logs. For some reason the AV exclusions havnt been applied and impero was unable to uninstall the injection.
mullet_man Posted June 21, 2018 Posted June 21, 2018 Am having this issue with Windows 1703 but we use NetSupport, it's not happening very often and if I restart the PC and get the same kid to log back in it logs in fine. All local profiles I should add.
CameronDuclos Posted June 21, 2018 Author Posted June 21, 2018 So your solution was to remove Impero fully or just uninstall then re-install?
Sheridan Posted June 21, 2018 Posted June 21, 2018 We've had this on 1703 and 1803, and we've never used Impero. It seems random and unrelated to hardware or user so we've added it to the list of W10 'features'!
mullet_man Posted June 21, 2018 Posted June 21, 2018 We've had this on 1703 and 1803, and we've never used Impero. It seems random and unrelated to hardware or user so we've added it to the list of W10 'features'! We have NetSupport and have this issue. Seems to a feature like you say!
free780 Posted June 21, 2018 Posted June 21, 2018 I found this issue with 1607 on PCs without impero. Traced the issue to the per user firewall rules created on first login. Looks like roaming profiles are deprecated. You can also get issues with modern apps and roaming profiles/ user profile disks.
Arthur Posted June 21, 2018 Posted June 21, 2018 We've had this on 1703 and 1803, and we've never used Impero. It seems random and unrelated to hardware or user so we've added it to the list of W10 'features'! Avast antivirus is known to cause black screens. Do you have the latest cumulative update installed? https://support.microsoft.com/en-gb/help/4284835 Addresses an issue that caused the system to start up to a black screen. This issue occurs because previous updates to the Spring Creators Update were incompatible with specific versions of PC tune-up utilities after installation. https://www.zdnet.com/article/windows-10-april-2018-update-problems-knock-users-but-adoption-still-soars-to-50-percent/ Last week saw a surge in complaints from users stuck on a black screen after updating to 1803. Some users blamed the issue on Avast antivirus, but the security company denied it was the cause. However, Microsoft has since confirmed that the issue is caused by a clash between 1803 and Avast antivirus. The upgrade appears to complete but, after signing in, users running Avast see a blank screen with only the Recycle Bin and a taskbar. Also, the Start menu doesn't function and nor does Task Manager. The other thing that may occur is that Windows restarts to a 'Choose your keyboard layout' screen and gets stuck from there. "In cooperation with Avast, Microsoft has identified an element of the Avast Behavior Shield that conflicts with the April 2018 Update, and that may result in this experience," Microsoft notes on its user forum. "Avast has released an update to prevent this issue from occurring. Once you've restored your system, make sure your Avast antivirus is up to date." It has also provided instructions for restoring Windows machines affected by that glitch.
Sheridan Posted June 21, 2018 Posted June 21, 2018 Hmm well we use Sophos and have had the issue for a while. Just added Netsupport Notify so we will have to see if it gets any worse
free780 Posted June 21, 2018 Posted June 21, 2018 I'd stay clear of any 3rd party AV when using Windows 10. But granted not everyone can make that change to defender. If you can replicate the issue try running procmon and review the results.
DCUK6 Posted June 22, 2018 Posted June 22, 2018 (edited) Eset here. Our black screens are just that. No recycle bin or anything. Had a session with eset support yesterday. Currently all logs on diagnostics mode. Its annoying because it hasnt happened in the last few logins. Only two things being blocked is csrss and the synaptics as they both try to access the ESET files and self defense blocks. We have 1709 and 1803 laptops doing it. I think im going to get rid of the profile paths for all students. Normally add it in so our slow computers dont have to create a new profile but im wondering if its a issue logging into different windows versions. edit:removed all profile paths. 1.6ghz,4gb ram, 500gb hdd. 1min 30 for first logon, did its welcome to windows thing 30 seconds for repeat logons on that computer Edited June 22, 2018 by DCUK6
mullet_man Posted June 22, 2018 Posted June 22, 2018 It’s not profile related to different versions as we don’t have the profile path here. Plus students are all 1703 here. I did see this happen first hand today, a pupil brought me a laptop which didn’t have a printer mapped (seemed to have happened a lot today for some reason) so I logged them off to ask them to log back in to see if the printer mapped, i didn’t even get that far as logging back in just went to a black screen. No idea what’s happening
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