Describes an issue that triggers event 7031 or 7034. Occurs when you log off and then log back on to a device that's running Windows 10. A workaround is provided. Event ID 7034 from source Service Control Manager. The Message Queuing service unexpectedly quits and event IDs 7034 and 4355 are logged in Windows Server 2003.
Over the past few days, an error seems to have developed on my Windows 10 Professional (anniversary update) workstation, whereby when opening the Update section of the Modern Settings app, loads of services instantly crash.
NOTE: No updates were installed over the weekend, and I have made no changes within the past week or two. Download mortal kombat deception pc.
It seems that opening the update page within settings, it causes the Windows Update service to crash with (Faulting application name: svchost.exe_wuauserv) a faulting DLL of ntdll.dll, exception code: 0xc0000409. This is an 'Application Error' event, event ID 1000.
Immediately after this, the following services also terminate unexpectedly (Service Control manager events, ID 7034, 7031):
Application Information Service
Computer Browser
Certificate Propogation
Group Policy Client
IKE and AuthIP Keying Modules
IP Helper Service
Server Service
Geolocation Service
User Profile Service
System event notification
Remote desktop configuration
Shell hardware detection
Themes
User manager
Update Orchestrator for Windows Update
Windows management instrumentation
I have run SFC /Scannow, which reports corruption was found and repaired. If I run it again straight away, it returns the same response. I am not really sure what to look for in the CBS.log file, but there doesn't appear to be anything too major, other than some directory ownership mismatches.
I have run DISM with the scanhealth and restorehealth switches, both of which complete successfully without errors. Ran SFC again and the same corruption message.
I have tried downloading the Windows 10 ISO, and doing an in place 'Upgrade', but the same issue exists.
Is there anything else I can try without having to wipe the machine and start over? Being my workstation, there are a lot of management applications on here that I don't really want to have to set up again from scratch. (System restore not available as for some reason it is disabled by default in Windows 10?!).
I've had a similar problem with Windows Update on two Windows 10 computers. I think I've fixed it on one computer. Windows Update is working again and the relevant error messages are not appearing in the Windows logs.
However there are a raft of other problems seemingly caused by the anniversary update, including problems with Task Scheduler, the Start Menu, and Azure Recovery Services agent.
These are the steps I took to get Windows Update working:
Fix two event ID 10016 DCOM errors.
Install the missing Windows Updates manually, using the Microsoft Update Catalog to download stand-alone packages. These are: KB3176929 (Aug 2, 2016), KB3176495 (Aug 9, 2016), and KB3176934 (Aug 23, 2016). See this Microsoft Support article: https://support.microsoft.com/en-us/help/12387/windows-10-update-history
Run SFC and DISM, but I don't think they helped. No errors were reported.
Disable OneSyncSvc using Task Manager.
Uninstall Bonjour.
Windows Update then obligingly installed a few more updates including KB3176934.
I hope this helps, however I'm sorry I can't say for definite which step fixed the problem.
UPDATE: Windows Update is working on the second computer now. I discovered one more 10016 error, fixed it, and restarted the computer.
This is the message in the system event log and the name of the component in Component Services is RuntimeBroker.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITYSYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
This article explains how to fix 10016 errors: http://www.eightforums.com/performance-maintenance/11951-numerous-event-id-10016-errors-win-8-pro-64-bit.html
RichardCLRichardCL
I came up with my own solution for the same issues as described above. I will also document some of the attempted fixes initially.
Attempts:
1) Restart windows update service 2) Disable windows update service, clear c:windowssoftwaredistributiondownloads 3) Reboot machine with combinations of the above 4) Manual installations from the update library - not effective whatsoever. 5) dism /online /cleanup-image /scanhealth (and restorehealth)
Final fix (where the machine is currently rebooting after installing about 30 updates, including the oct 27 2016 1607 cumulative update)
Ran disk cleanup utility. Hit button for cleanup system files. Check off all boxes. Remove all files. Reboot. Run windows update, click 'check online for updates from microsoft' (NB: I had synchronized and approved all updates on WSUS internally yesterday). It did the usual crunch time, followed by installs, then some weird logs that I didn't want to dive into. Prompted for a reboot from windows update. Appears successful will edit post if it failed.
Edit:
Had to resolve the same issue on another computer. Steps solidified:
1) note the inherent issue in syslogs 2) Stop the windows update service 3) Set the update service to disabled 4) Clear the softwaredistributiondownloads folder 5) Run the disk cleanup utility, hit the clean system files button, check off anything and everything I am willing to nuke 6) REboot 7) enable the WU service 8) Open up windows update, tell the machine to check online (because I normally use WSUS) 9) watch the update carefully in task man to ensure that it's getting the updates online instead of from WSUS 10) machine successfully updated, reboot.
browningitbrowningit
I was fighting to fix this annoying issue on my work machine. I have tried RichardCL's solution + all comments and browningit's steps to no avail.
What actually fixed the problem for me was installing all cumulative updates listed for Windows 10 1607 on Windows 10 and Windows Server 2016 update history page. Notably the updates that I have manually installed are (in the listed order):
KB3176929
KB3176495
KB3176934
KB3176938
KB3193494
KB3200970
KB3194798
KB3197954
KB3206632
KB3201845
KB3213986
I have downloaded them from Microsoft Update Catalog site. You don't need to reboot after each update. Reboot at the the end is sufficient.
Community♦
rikrik
We had the same issue in a corporate environment. Once we summited Windows 10 build 1607 to the WSUS server, the eventlog became red, Service Control Manager events 7031, 7032 and 7034.
Apparently the windows update mechanism in build 1607 is broken, and we had to;
Manually download and install patch; windows10.0-kb3216755 fromhttps://catalog.update.microsoft.com
Reboot windows 10
After this, Windows 10 could normally update from WSUS
LectereLectere
Not the answer you're looking for? Browse other questions tagged servicewindows-updatewindows-10dism or ask your own question.
MUST TRY: Click here to fix Windows errors and improve Computer performance
Event ID 10016 DistributedCOM Windows 10 Error is one of the most notorious issues that users confront in the System log. This error triggers when certain processes do not contain permissions to the DCOM components that are mentioned in the event logs. It restricts the computer to run flawlessly which eventually annoys the users.
The system immediately clogs the Event Viewer with thousands of events after showing the message. The investigation reveals that when you try to start the DCOM server using an application while you don’t have any permission to do so, you will get the below-given error in Event Viewer –
“The application-specific permission settings do not grant Local Activation permission for the COM Server application”.
In addition to this, some users, also get to encounter the following message for the same error –
“The %1 permission settings do not grant %2 %3 permission for the COM Server application”
In order to have clear conception and avoid making mistakes, we will divide the full procedure into four successive sections. Let’s move on to them straight away. We will focus on solving this annoying Event ID 10016 DistributedCOM Windows 10 Error by following below instructions.
Be patient and follow the guidelines.
Fix: Event ID 10016 DistributedCOM Windows 10 Error
Checking of the Process
Step 1 – First of all, we have to sort out the process or the service linked with the CLASS ID from the list of errors. Proceeding ahead, you will find a list in the event description. From the list, copy the CLSID. It may appear like {D63B10C5. Ensure that you have copies both the curly brackets too.
Step 2 – Go to the Start Menu on your computer, type regedit in the search field and depress the Enter key. Click Yes to continue when UAC evokes up on the screen. Registry Editor immediately opens up.
You can explore more ways to Access Registry Editor in Windows 10.
Step 3 – Now, click Edit on the menu barof Registryand selectthe option Find.
Step 4 – Paste the copied CLSID in the box shown here and press Enter key. Once you successfully complete the above steps, you will get a search result under the HKEY_CLASSES_ROOTCLSID key.
Step 5 – There will be two string values on the right side. One of these is a Default string and it holds the name of the service. Its name should be RuntimeBroker.
The next task is to Run a script in order to make some changes in the permission section found in Component Services for this service.
Running PowerShell Script
In order to bypass this error, you need to edit some of the permissions in the Component Service section of the key RuntimeBroker. Before you go for the modification, you need to run a script which will help you to change the permissions.
We will discuss the procedure to Run PowerShell Script in this section.
Step 1 – Use the combination of hotkeys Windows-X and select “Windows PowerShell (admin)” from the menu that shows up.
Step 2 – Proceed forward and Download the text file by clicking the below button. Copy all the codes then paste all of these in the PowerShell window.
Step 3 – Finally, hit the Enter key to get the task done.
Opening Component Services
The opening of the Component Services is as same as to open PowerShell we mentioned above.
Step 1 – Launch the Start Menu from your computer and in the search box, type Component Services. When the search result appears, select the Component Services moreover put a right click on it. After that, select the option “Run as administrator“.
Step 2 – Now navigate to the following file location –
Component Services – Computers – My Computer – DCOM Config
Step 3 – Slowly scroll down to find Runtime Broker.
Note – In some cases, there might be two files with this name. You need to find out which file is responsible for the error. So do this,
Step 4 – Hit a right-click on both of them and select Properties. In the General section, you can notice Application ID. This particular ID should be matched with the AppID mentioned in the error message. If the error is associated with the Event Viewer having an ID of “10016” as well as more than a single CLSID, you need to resolve both of the RuntimeBrokers. In some other cases, it can be only one to fix.
Correcting Permissions
Lastly, we need to modify the permissions, so, in order to accomplish the work, the steps are as follows:
Step 1 – Go to the RuntimeBrokerProperties dialog. Switch to the Security tab to see the related details.
Step 2 – You can find an option Edit below the section “Launch and Activation Permissions“. This button should be clickable. If you see it is in gray color, it indicates that the PowerShell script didn’t function properly.
Step 3 – After clicking on the Edit button, a popup dialog warning may appear showing about unrecognized permissions. In the popup, do not click on Remove, click on Cancel instead. You can see a list of default accounts as well as unknown accounts.
Step 4 – Leave the Account Unknown untouched means kindly don’t remove it. There are two more accounts in the name of ALL APPLICATION PACKAGES and SELF. Instead of making a change in these, add two more new accounts. You can click on Add followed by typing System. Proceeding further click on Check Names and then Enter for adding a new account to the list.
Step 5 – In the same way, Click Add again furthermore type Local Service. Add an account by following the guidelines mentioned above.
Step 6 – If you have finished adding both of the accounts, click one at a time. Check the boxes located underneath “Allowoption in the name of Local Launch” including “Local Activation” and lastly click on Ok.
Event Id 7034 Windows 10 Update
Therefore, all the steps are done. Finally, Restart Windows 10 PC to save all the changes and start afresh.
Windows Event Id 7031
All the users irrespective of professional or semiprofessional as well as the beginners want their computers to be running smoothly without having any error. Unfortunately, this thing is not maintained always hence they go through some difficulties. It is hard on the part of a professional user to accept. Event ID 10016 DistributedCOM Windows 10 Error is such a troublesome thing which most of the users commonly faces in their system probably every day.
Event Id 7034 Print Spooler Service Terminated Unexpectedly Windows 10
Conclusion
Event Id 7034 Windows 10 Windows 10
While working with computer and applications, users will face different errors frequently. But all the problems come with a solution. Instructions elaborated above will help the users to fix Event ID 10016 DistributedCOM Windows 10 Error smoothly. Ensure that you read the steps properly and applied in the right places. Any mistake in the process will not dismiss the Event ID 10016 DistributedCOM Windows 10 Errorrather it will be waste of time.
Event Id 7034 Windows 10 7
STRONGLY SUGGESTED: Click here to fix Windows errors