timbo343 Posted September 20, 2016 Posted September 20, 2016 (edited) Every now and then we see machines plauged with the black screen issue after the user has logged in to the machine. Looking in Event Viewer we are seeing the following messages on machines. We are running LTSB2015. The description for Event ID 10010 from source Microsoft-Windows-DistributedCOM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: {7006698D-2974-4091-A424-85DD0B909E23} The handle is invalid The description for Event ID 7000 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: UAC File Virtualization %%1275 The handle is invalid The description for Event ID 41 from source Microsoft-Windows-Kernel-Power cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 0 0 0 0 0 0 131188339616501558 0 The handle is invalid I thought fast startup was the problem but it turns out it isnt. Can anyone help on this issue please. Im thinking it might be a re-image job but i'm clutching at straws on this one as its something i really want to beat. These machines haven't got the latest CU from september and as the problem is so random, it would mean applying the latest CU to all machines across the network. If a machine has the black screen the only way to get round it is to hold in the power button, wait for the machine to switch off. Power it back on and login as usual and the issue goes away. Edited September 20, 2016 by timbo343
sturgeo Posted September 20, 2016 Posted September 20, 2016 We're using x64 Enterprise 1511 and get the same issue sometimes, a collegue believes its to do with updates but i've not looked into it yet. 1
timbo343 Posted September 20, 2016 Author Posted September 20, 2016 We're using x64 Enterprise 1511 and get the same issue sometimes, a collegue believes its to do with updates but i've not looked into it yet. Hmmm, im not too sure, we have updates turned off on these machines. At least we're not the only one who is having this issue . I did see in the event logs a service trying to start, it was onedrive, so a quick reg hack disabled this but still the DCOM error messages are still there.
alfatec Posted September 20, 2016 Posted September 20, 2016 Same issue here on Windows 10 1511. Had it before updates and after. Seems to be a common problem which is more common when the workstation first switch's on.
timbo343 Posted September 20, 2016 Author Posted September 20, 2016 Got another event viewer entry relating to the DCOM 10010 error The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout along with The server {7006698D-2974-4091-A424-85DD0B909E23} did not register with DCOM within the required timeout on the same machine
sturgeo Posted October 3, 2016 Posted October 3, 2016 Are you using Impero? We've had a few sporadic issues with it lately and wonder if its related.
timbo343 Posted October 3, 2016 Author Posted October 3, 2016 Are you using Impero? We've had a few sporadic issues with it lately and wonder if its related. Yep we are using Impero. Would it be related?
FragglePete Posted October 3, 2016 Posted October 3, 2016 We too are experiencing the odd issue and also use Impero..... uh oh! Pete
timbo343 Posted October 3, 2016 Author Posted October 3, 2016 Id be interested to know what others are seeing in the event viewer of the local machine when this happens as we are seeing: EVENT 10010 DistributedCOM The server {7006698D-2974-4091-A424-85DD0B909E23} did not register with DCOM within the required timeout.
sturgeo Posted October 3, 2016 Posted October 3, 2016 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.
disk Posted October 3, 2016 Posted October 3, 2016 What is the make/model of the PCs you have that are exhibiting this behavior? Are these systems running legacy BIOS or UEFI? Have you checked for an update to the BIOS?
DMcCoy Posted October 3, 2016 Posted October 3, 2016 The DCOM errors are normal and appear on a fresh 1607 install, a number of the permissions are incorrect, I haven't been prompted about black screens so far (lots of other issues though :| ) Not using impero.
sturgeo Posted October 4, 2016 Posted October 4, 2016 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.
timbo343 Posted October 4, 2016 Author Posted October 4, 2016 We are running a range of machines and its happening on them all. Gateway DS10, HP 8000, Dell optiplex 380 / 390.
sturgeo Posted October 4, 2016 Posted October 4, 2016 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.
timbo343 Posted October 4, 2016 Author Posted October 4, 2016 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. I think the sync host is to do with onedrive. I've completely disabled onedrive by stopping the service through group policy as we used to get this too. I thought this might be the problem but turns out it isnt.
FragglePete Posted October 11, 2016 Posted October 11, 2016 Just had 3 machines do this today, all after running the latest rollup update (KB3197356) - these are Stone machines albeit the oldest of the desktops I have running here (Core 2 Duo's, 120GB SSD, 4Gb RAM). I'm just trawling the event logs at the moment when a student logged. Errors of note in the System log are: Event ID: 7009 - A timeout was reached (60000 milliseconds) while waiting for the CDPUserSvc_37cd7a service to connect. Event ID: 7000 - The CDPUserSvc_37cd7a service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Event ID: 10010 - The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. The last error shows up 4 times in the window that the student logged in with. Can this really still be a Microsoft issue after all these roll ups or something else? - as I said before, we run Impero here like many others who seem to be having similar issues here; could this be the issue? I've lost faith in Impero as of late because of the numerous issues we've had (and would appear others are having on the later releases). Pete
sturgeo Posted October 11, 2016 Posted October 11, 2016 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.
FragglePete Posted October 11, 2016 Posted October 11, 2016 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. Interesting. Would @Mic_Impero care to comment on this? Is it something that needs to be investigated by Impero. The issue is that the it seems so inconsistent and random as to when it happens it's going to make it difficult to prove if its a Microsoft or an Impero issue. Pete 1
timbo343 Posted October 11, 2016 Author Posted October 11, 2016 Just had 3 machines do this today, all after running the latest rollup update (KB3197356) - these are Stone machines albeit the oldest of the desktops I have running here (Core 2 Duo's, 120GB SSD, 4Gb RAM). I'm just trawling the event logs at the moment when a student logged. Errors of note in the System log are: Event ID: 7009 - A timeout was reached (60000 milliseconds) while waiting for the CDPUserSvc_37cd7a service to connect. Event ID: 7000 - The CDPUserSvc_37cd7a service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Event ID: 10010 - The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. The last error shows up 4 times in the window that the student logged in with. Can this really still be a Microsoft issue after all these roll ups or something else? - as I said before, we run Impero here like many others who seem to be having similar issues here; could this be the issue? I've lost faith in Impero as of late because of the numerous issues we've had (and would appear others are having on the later releases). Pete Interesting to see you get the 10010 errors too. We're still getting these when the problem occurs. What version of windows 10 are you running? EDU or LTSB?
FragglePete Posted October 11, 2016 Posted October 11, 2016 Interesting to see you get the 10010 errors too. We're still getting these when the problem occurs. What version of windows 10 are you running? EDU or LTSB? Running Edu - 1607 with the latest cumulative updates installed. Pete
sturgeo Posted October 11, 2016 Posted October 11, 2016 The issue is that the it seems so inconsistent and random as to when it happens it's going to make it difficult to prove if its a Microsoft or an Impero issue. 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.
FragglePete Posted October 11, 2016 Posted October 11, 2016 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. Well - this is interesting. If it is indeed Impero causing this then I won't be too chuffed in the slightest. I'm of the view that Impero will not be renewed next year and am actively looking elsewhere now...... Pete
timbo343 Posted October 11, 2016 Author Posted October 11, 2016 Impero should now be aware of the problem as ive let one of their customer support guys know this morning.
FragglePete Posted October 11, 2016 Posted October 11, 2016 Impero should now be aware of the problem as ive let one of their customer support guys know this morning. I think I'm going to log a call this week as well - can't go around pointing the finger at them until at least they've had a chance to look into it. Pete
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