sturgeo

I found the solution to this for us, IE setting -> "Internet Options -> Advanced -> Security -> Do no save encrypted pages to disk" was ticked, once unticked the videos work fine.

Pretty sure everything was in the root of C:

Have you got any impero error log files on the C drive that match up timewise? We had to remotely browse to the C$ (whilst the machine had the post login black screen) and saw some timestamped errors, they had miraculously been overwritten by less useful information upon the next boot. Still, 2+ weeks of being free of impero software and not a single reported black screen. We're currently setting up an entirely new impero server and will be deploying it to just a single IT room, time will tell!

I upgraded dirsync to azure AD connect and i guess its still set to using password hash, is this correct? Not sure why it thinks im not using an Azure AD account as all accounts sync, not done anything with certificates though. Azure AD portal doesn't show my internal domain at all, only my public one & the onmicrosoft one, all users login to office 365 with their email address which is username@... CHiLL, try manually running the Automatic-Device-Join scheduled task, although it is set to run at logon it doesn't trigger.

Right after manually triggering the task dsregcmd /status is showing my machine as AzureAdJoined, all looks ok however all User States are no.

Are you using ADFS? I've upgraded to AD Connect & ran various powershell scripts, set the GPO to enable the scheduled task, running dsregcmd /status claims the device isnt AzureAdJoined, however in the event log i can see warnings saying that the device is joined but the current logged in user isn't I can see what you mean about the documentation being sparse!

Might give this a try since we use O365 authentication for FireFly and apparently having to log in again is hugely inconvenient

I'd say it was an impero issue for us, we had this happening tens of times (reported to us) a day on machines across the site, uninstalled impero and now the machines are working perfectly. We also have had test machines in our office for well over a year now, not one single black screen, these have never had impero installed on them.

Not so long ago, in an office far away, a microsoft employee decided to make our lives very difficult... So, like many others we build our machines using WDS. I took the install.WIM straight off the installation media, ran the removeapps.ps1 script to take out all the rubbish, sorted, a nice clean install. Now comes the time to upgrade to 1607, partially to try and sort some issues and partially as i was a bit overzealous with the removeapps.ps1 script and removed the built in photos app... oops Get our WSUS server sorted and push the update out, sure enough the photos app is back, yay, but so is all the other crap I've tried the SetupConfig.ini PostOObe tricks, startup scripts, everything. Windows Store, Skype, 3DBuilder, etc keep coming back Has anyone successfully done this update and managed to clean the system back up?

We uninstalled impero (across the whole site) last monday and i've not had any reports since... We also had numerous issues with it stopping applications from working, adding "TRUE" to the bottom of printed pages and severly effecting performance of our view machines.

We use folder redirection (inc AppData), no roaming profiles, and most GPOs are blocked for admins as we disabled inheritance on the OU.

Nope not yet, thats interesting, are you trying the same accounts on the same machine? that'll narrow it down to either a machine or user policy

Just to add, we also recieve the DistributedCOM messages at the time and also these: Service Control Manager - 7009 A timeout was reached (120000 milliseconds) while waiting for the Sync Host_571ac service to connect.

We're running Dell machines, this issue is/was affecting models such as E5420/30 Opti 7440, 9030 and quite a few others. Legacy as we use WDS.

Not sure about the timeout messages in event viewer but we have lots of client error files on the C drive & a message like "x64 failed dll injection" in a file at the time we had the black screen issue. We've removed impero from that room to see if it has resolved the issue.