Windows 10 Event 10016 Fix: 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 AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.I a

Ran into a lot of DCOM (DistributedCOM) errors on Windows 10 machines after upgrades.  Looks like the TrustedInstaller from a previous application and the RunTime Broker did not give System and Local Administrators permission during a Windows 10 upgrade.  It just an annoying thing but also slows down a windows 10 Login.

The Error

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 AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.

Background

It would appear that an Apple application was installed on these machines at some point and that it did not do a proper install.  The W10 upgrade exacerbated the issue due to missing security accounts after a W10 upgrade.  The fix is to give local administrators and System rights to the DCOM.  To do this you have to modify premissions on two registry keys and then change the DCOM premissions.  Pretty easy to do.

FIX

Regedit Take Ownership

You will need to take ownership then set rights against two different keys.  The keys are:

HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}
HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}
  1. Open Regedit with Administrators privileges and navigate to the keys above (remember you have to do this twice)
    1. WinKey + X >> Command Prompt (Admin) >> Type in Regedit
  2. Right click the key >> permissions
  3. Click advanced
  4. At the top change the Owner to COMPUTERNAME\Administrators
    1. Please note if you are domain joined you’ll have to change where you are searching from to your local computer
  5. Look in the Permission Entries field
    1. If the local system administrators group is listed ensure it has full control
    2. if the administrators group is not listed add it and give it full control.  (note you can only do this if you are a member of the administrators group and it is now the owner)
  6. Click okay a lot >> Ensure you apply permissions to all child objects

Change DCOM Permissions

Need to ensure DCOM permissions are setup

  1. Open DCOMCNFG as an Administrator
    1. WinKey + X >> Command Prompt (Admin) >> Type in DCOMCNFG
  2. Navigate to Component Services >> Computers >> My Computer >> DCOM Config
  3. Find the RunTimeBroker  >> Right Click >> Properties >> Security Tab
  4. Launch and Activation Permissions >> Edit >> Add System and give it full control
    1. I also added the Administrators group just for testing

While changing permissions I was prompted several times to remove bad account references.  I did this as the computer knows which accounts have been removed.

Summary

At this point you should have sorted the DCOM errors.  Give your computer a reboot and away you can go.

Advertisements

Author: shauncassells

Shaun Cassells, Senior Solutions Engineer, 1E Shaun is a Microsoft MVP Windows Insider MVP and executive at Central Texas Systems Management User Group (CTSMUG). Shaun is a frequent speaker at conferences like MMS, Gartner, TechEd Europe, TechEd North America, IT Dev Connections, System Center Rallies, and Systems Management User Groups (SMUGs). Shaun is an award winning blogger syndicated from www.shauncassells.com. Shaun specializes in analysis, optimization, and design of Tactical Solutions to Strategic Business Goals. Prior to joining 1E in 2010, he worked for a Global 100 company as the Configuration Manager Service Owner and Architect. Recently as a Principle Consultant at 1E, he accomplished design, review, and improvements to a variety of Configuration Manager environments from the very small to sites with a half million seats. He provided leadership that created a patented automated application rationalization and usage based OSD mapping solution in use by multiple fortune 500 companies. These days you can find Shaun traveling to help discover, review, and improve business productivity across the world.

63 thoughts on “Windows 10 Event 10016 Fix: 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 AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.I a”

  1. Even opening regedit as Administrator, Win 10 will not allow any changes in Permissions to HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}. I have not tried your other remedies assuming this is an all or nothing solution.

    Like

      1. Hello,

        I have a similar problem. I’ve try your step but i hit a wall .

        When trying to take ownership of the key i got a window security warning in a red circle saying: unable to save permission changes on key. Access is denied.

        I’ve try to select my computer as administrator, i ‘m sure i’ve select full control and all sub file and yet it’s not working. can i get your help thanks

        I’ll give you the full detail of the two event

        Event 1:
        Log Name: System
        Source: Microsoft-Windows-DistributedCOM
        Date: 2016-05-22 9:22:37 PM
        Event ID: 10016
        Task Category: None
        Level: Error
        Keywords: Classic
        User: METALINFERNO\Maxim
        Computer: MetalInferno
        Description:
        The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
        {C2F03A33-21F5-47FA-B4BB-156362A2F239}
        and APPID
        {316CDED5-E4AE-4B15-9113-7055D84DCC97}
        to the user METALINFERNO\Maxim SID (S-1-5-21-4232364380-3243645253-3604380675-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.FeatureOnDemand.InsiderHub_10.0.10586.0_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-4016783169-893401051-2237370320-274899566-412088533-2398988950-2155762795). This security permission can be modified using the Component Services administrative tool.
        Event Xml:

        10016
        0
        2
        0
        0
        0x8080000000000000

        2299

        System
        MetalInferno

        machine-default
        Local
        Activation
        {C2F03A33-21F5-47FA-B4BB-156362A2F239}
        {316CDED5-E4AE-4B15-9113-7055D84DCC97}
        METALINFERNO
        Maxim
        S-1-5-21-4232364380-3243645253-3604380675-1001
        LocalHost (Using LRPC)
        Microsoft.Windows.FeatureOnDemand.InsiderHub_10.0.10586.0_neutral_neutral_cw5n1h2txyewy
        S-1-15-2-4016783169-893401051-2237370320-274899566-412088533-2398988950-2155762795

        Event 2:
        Log Name: System
        Source: Microsoft-Windows-DistributedCOM
        Date: 2016-05-22 9:19:43 PM
        Event ID: 10016
        Task Category: None
        Level: Error
        Keywords: Classic
        User: SYSTEM
        Computer: MetalInferno
        Description:
        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 AUTHORITY\SYSTEM 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.
        Event Xml:

        10016
        0
        2
        0
        0
        0x8080000000000000

        2243

        System
        MetalInferno

        application-specific
        Local
        Activation
        {D63B10C5-BB46-4990-A94F-E40B9D520160}
        {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
        NT AUTHORITY
        SYSTEM
        S-1-5-18
        LocalHost (Using LRPC)
        Unavailable
        Unavailable

        Like

      2. Shaun, I was able to make all the reg changes but not the Change DCOM Permissions, when I open security tab on Runtimebrooler all options is grayed out. Any help would be greatly appreciated.

        Like

    1. I was getting a lot of these (30) per hour. I tried everything that I could think of. Being unable to go through the last step of launching DCOM. I found a MS patch with KB3118754 and KB3120677. The MS patch does not fix all but I’m down too 1 DCOM error per session on the computer.

      Like

  2. Thank you very much for this solution! I’m also receiving a “Bowser” 8003 Event Error described as “The master browser has received a server announcement from the computer XYZ that believes that it is the master browser for the domain on transport NetBT_Tcpip_{3E7371BC-5FA1-4B5D-8633-4C40F5C6A276}. The master browser is stopping or an election is being forced.” Would these two problems be related? I have read elsewhere to search the registry for “isdomainmaster” to ensure it is set to “false”. I did so on computer XYZ. On the Win10 computer that is displaying error 8003, the registry hangs in the search and eventually stops responding! 😦

    Like

  3. Are they related is it is possible. Good news 3E7371BC-5FA1-4B5D-8633-4C40F5C6A276 will be in your registry so you can look up what application is causing the lockout. Be aware that putting an object under you ownership will not break the app. only limit it to notify you of admin level changes.

    Like

  4. Hi, thanks a lot for your explanations. When modifying autorisations for RunTimeBroker,I could not find “System” (not recognized why? on Windows10) so I put “mycomputer/Administrators” and it works fine. No more 10016 :-

    Like

  5. Hi, I am experiencing this exact same error and other very similar errors under Win 10 Pro x64. The User is sometimes NTAuthority, as in your case, but often it is another user that is logged into the computer. I followed your instructions and this seemed to resolve the problem for my main account, which is a member of the Administrator’s Group; however, the “fix” caused serious issues with another account that is not a member of the Administrator’s Group. The account that is not a member of the Administrator’s Group lost access to the Start button, the Edge browser could no longer start, login took an extremely long time, and many other errors and oddities presented. Can you suggest why this might not work for an account that is not a member of the Administrator’s Group and how it could be enhanced to work for such accounts?

    Like

    1. Turns out this is a repeated GUID and that is as well causing issues. The root cause appears to be an orphanded security token upon install. The fix in this blog will only remediate some errors. It will not remove the possibility in the future.

      Like

  6. I’m in Windows 10 Home 64-bit and the lone user, listed as Administrator in User Accounts. I had no problem taking ownership of the keys, but the buttons and edit boxes of the Security tab in RuntimeBroker Properties of DCOM Config are grayed out and inaccessible to me. Any ideas on how I can proceed?

    Like

    1. An account that is AN Administrator is not (necessarily) the same thing as THE Administrator account. You need to give the access rights to the AdminstratorS Group of which both you and the specially defined (THE) Administrator account are members. So, you need to assign right to Administrators, with an S on the end, not the Administrator, with no S. You successfully assigned right to a special windows account that you are not using… or, at least it sounds like tht is what you did based on the info provided. Reply to confirm this applied and was helpful.

      Like

    2. you should right-click RuntimeBroker object from the main area to open Properties dialog where you’re resetting permissions. if you click RuntimeBroker on the left tree pane you’ll see mostly same dialog, but with most controls grayed out. find RuntimeBroker object icon and repeat same steps in its context menu.

      Like

  7. Adding my thanks to this. In some other threads, they suggest returning ownership to TrustedInstaller, which I did. I only added SYSTEM to the DCOM permissions, and that was enough to get rid of the 10016 error on shutdown/restart. That fixed up the last of the error messages in event viewer.

    Like

  8. Does any one know if this error in the event log actually causes any issues for the App Store or Store Applications? We would need to figure out a way to automate this fix (maybe powershell) across hundreds of machines to address this in our environment.

    Like

    1. Oremac, all I Can suggest is automate installing Linux. I really like Windows 10 for a lot of reasons but it runs my surveillance system and when I was out of town it crashed and left me without a surveillance system until I got home. Between sporadic BSODs and just the forced reboot after patching with no way to turn it off, I’m just about ready to move to CentOS or Mint.

      Like

      1. I like to call this the nuclear option. You are not really fixing the problem just replacing the root cause with something that will have other issues. 🙂 Might be a great option though.

        Like

    1. It is more complicated than that. What I originally thought was exclusive to apple products has now turned out to be a core issue of Windows Store loaded software losing rights to the Trusted Installer account. This is a bug that I think has been fixed in some of the insider builds.

      Like

  9. so when i changed promissions in the registry i on accident changed all the promissions for h-key_classes_root. I wasnt reading ahead and thats something im working on. So my question is. will the system and the admins having full control cause other issues. thank you in advance for reading this and any help that can be given on the subject.

    Like

  10. Hi all, im having similar issues and followed what has been put and can change keys owner but of the list cant give me full control on this key just say denied. Im on w10 if that helps thx

    Like

  11. Hi, Shaun! Thanks a bunch for helping me to dig through Component services snap-in.
    Knowing AppID this snap-in allows to resolve notorious DCOM security isues.

    Like

  12. Thank you a million times for this fix! It has been happening to me since the Windows 10 1607 update and only for one user of this PC. I tried your fix several times before I was successful, but that was only because I didn’t read your instructions properly and follow them exactly. Very well explained and detailed …. others should learn from my mistakes and follow *precisely* and it will work.

    Like

      1. Here is the game. Tracing what this event is generated from is difficult. If you can find the originator and it is able to be removed from ARP. Then by all means. However, if you are unable to find the source, uninstall it, or be sure it is no longer needed the security changes might be easier.

        This whole area needs more digging but my focus has been on other W10 issues recently.

        Like

  13. First, a warning: DO NOT FOLLOW THESE INSTRUCTIONS FOR ANY REASON! YOU WILL CAUSE IRREPARABLE DAMAGE TO YOUR WINDOWS INSTALLATION!

    There is a passing reference up there to removing ACL entries: “While changing permissions I was prompted several times to remove bad account references. I did this as the computer knows which accounts have been removed.”

    The “bad account references” are nothing of the sort. They are actually “callback ACEs”, a particular type of access control that the standard security dialog does not know how to handle. They are perfectly valid. You can recognize them by their different icon. With the built-in ACL editor, there is apparently no way to edit an ACL that contains this kind of entry.

    Now, the “IRREPARABLE DAMAGE” I mentioned above may not be very severe, particularly since it only extends to this one DCOM application. Still, these are bad instructions and should not be followed.

    Second, some observations:

    1. This error happens “out of the box” after a clean installation. There is no need to have upgraded from anything or have installed any applications whatsoever.
    2. Why is granting the “missing” permissions the correct fix? If the registry as shipped does not give that access to LocalService etc., might there not be a reason for that?

    Like

    1. Hi Christian,
      Very good point that this may be by design. However the irreperable damage claim is a bit extreme. Good tag line like 8 things to do to fix your W10, #7 will really suprise you.
      This error code can be completely ignored most of the time. However, would you agree that having entries that throw errors on purpose and are unowned by ACE is probably not best practice in a modern software lifecycle. What I am getting at it is.. just because software can do this… it is probably NOT a good idea

      Like

    2. You are quite right, these instructions should not be followed. You end up with a broken system that cannot load Edge or any Win 10 App. Even trying to reverse the instructions does not work as the damage has been done, presumably by other associated permissions getting screwed. There are loads more Dcom errors also, so the method is self defeating!

      Like

    3. I second that. The default launch permissions for RuntimeBroker, allow callback access for the interactive user. It’s that access that one has to remove to apply the suggested “fix”.

      The interactive user obviously isn’t a “bad account reference”. Removing its callback access to the Runtime Broker _will_ cause all sorts of problems with UWP apps.

      Like

    4. Here’s a better solution, in the sense that it will resolve the error. I’m not sure we’re actually supposed to resolve it, though. Note also that this solution will not restore permissions for the interactive user (it will leave them untouched if present).

      1. Compile DCOMperm from https://msdn.microsoft.com/en-us/library/aa242178(v=vs.60).aspx
      2. Open a command prompt as TrustedInstaller (you can use RunAsTI for that, see https://github.com/jschicht/RunAsTI).
      3. Execute the following (replace “SYSTEM” with “LOCAL SERVICE” if appropriate):

      DCOMperm -al {9CA88EE3-ACB7-47c8-AFC4-AB702511C276} set “NT AUTHORITY\SYSTEM” permit level:la

      Like

      1. There are numerous utilities that will let you start a process as TrustedInstaller, I just use RunAsTi and it’s open source so you can see what it does exactly. You don’t have to use RunAsTI in other words, you can use it if you don’t have any other similar solution available and don’t want to search for one.

        Like

      2. Note also, that you cannot use a powershell script, instead of DCOMperm, to update the permissions for RuntimeBroker. I’ve seen solutions similar to this:

        $app = Get-WmiObject -Query (‘SELECT * FROM Win32_DCOMApplicationSetting WHERE AppId = “{0}”‘ -f $appId) -EnableAllPrivileges
        $sd = $app.GetLaunchSecurityDescriptor().Descriptor

        but the problem is that $sd.DACL will be NULL if the descriptor includes callback access permissions. It’s pretty much the same problem dcomcnfg has, you can’t handle callbacks with powershell either.

        Like

  14. Shaun,
    For the Component Services > Computers > My Computer > DCOM Config > Runtimebroker Icon > right-clicking on it > RuntimeBroker Properties > Security Tab > Launch and Activation Permissions > Edit. The Edit icon is grayed out. In fact all three Edit icons are grayed out on the security tab. I have Windows 10 Home Edition. I suspect the DCOM problem is what is causing me to hear that peculiar sound of Microsoft’s Windows when a device like my mouse is disconnected/or connected to a computer. It happens occasionally, sometimes repeatedly, and I lose control of my mouse, sometimes briefly, sometimes permanently requiring a reboot. My keyboard has not been affected at all.

    I already had Ownership as far as I could see in that Gus-HP/Administrators was the name in the name block already conferring ownership on me and the Administrators. So why is the Edit icon grayed out for “Launch and Activation Permissions?” My problem seems to be the same as listed here in your wonderful post i.e., “! DistributedCom Event ID 10016” is what is in my Event Viewer.
    Thanks,
    Gus

    Like

      1. By “take ownership”, I assume that you mean the CLSID and APPID entries.
        I did this first but still came up with the greyed out problem. I tried a suggestion from Vladimir Nikotin (23 Dec 2016) to access the RunTimeBroker from the middle panel but I still got the same problem, whichever panel I used.
        By the way, I got this Event Id 10016 three times in fairly quick succession today. One of them was different from the other two.
        CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
        APPID {F72671A9-012C-4725-9D2F-2A4D32D65169}

        CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
        APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

        I changed the Registry entries for both to give Full permissions to Administrators (with an “S”) but still got the greying out in RunTimeBroker.
        The fact that I got two different versions of the error on the same day suggests that there may be many more yet to be encountered. Even if I overcome the greying out problem, do you think that this will mean that I shall have to go through all this again for future occurrences?
        I have been trying to sort out this error to clear up all “Errors” in my Event Log. It has not been causing me any obvious problem but (probably nothing to do with this), my PC has been freezing quite often and I am trying to clear the decks for diagnosis of that problem. I’m on Windows 10 (64) Home and the “freezing” seems to be endemic among such users.

        Like

    1. It’s because you opened context menu of RuntimeBroker node from the tree navigation pane in the left.
      Move your mouse further to the right – you have to right-click RuntimeBroker object from the main screen area to open fully functional properties dialog.

      Like

  15. When editing the DCOM Launch and Activation permissions I get a warning saying:

    One or more of the permission entries attached to Registry Value has an unrecognized or application-specific (callback) type and can not be displayed.
    -To remove the unrecognized and callback permission entries, click Remove. Note that inherited permission entries will not be removed, because they can be removed only on the corresponding ancestor’s level or inheritance can be disabled for this object.
    – To leave the permissions unchanged and display only the recognized permission entries in a read-only view, click Cancel.

    Buttons are Remove and Cancel.

    Suggestion on how to proceed? Thanks!!

    Like

  16. I have tried your fix and as soon as i get the file working i get another error with a different ID is there a way to track down the offending software to uninstall to reinstall ??? it causes the system to lock up once it goes into sleep mode and i have to do a hard shut down every time …. such a pain …

    Like

  17. After following you instruction I am at the point add users to RUNTIMEBROKER, but I am unable to add a user, it is grayed out.

    I have been in regedit and modified the following 4 keys so that SYSTEM has full access>

    HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

    HKEY_CLASSES_ROOT\AppID\RuntimeBroker.exe

    HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}

    HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}\LocalServer32

    But when I go into > DCOMCNFG > Component Serv – DCOM Config – RUNTIMEBROKER -> Properties-> Security ->{Launch & Activation Permissions} I am unable to add a user, it is grayed out.

    I also went into Local User Groups and added myself, SELF and SYSTEM to the group Dist COM users so they would be allowed to launch, activate and use Distributed COM objects on this machine, but to no avail.

    Any ideas where to turn next?

    Win10 x64

    Like

  18. Thanks to the guide, I had to reformat the computer, because the guide is destroying the computer
    Any action, including running Task Manager, running application, restart, take a minute to operate -2
    Search through the start of “event log” for example does not work in the Hebrew language, in English it finds

    Like

  19. Thanks for this recommandation. I have Windows 10 Home on my Acer laptop and have had these Distributed.com errors for a long time. Approximately 2 months ago my Motherboard collapsed and was changed. After that change I had severe difficulties in access to WiFi. I got the message that I needed to activate Windows in order to change settings on my PC. My Windows is activated and I have found no way to “activate”.One of my errors was this 10016 as described here. S I went through the instructions. I can now open my WiFi connection (before it was cosed and unaccessible) but the red warning about “activation” is still there. But now I have new errors that occured atthe moment of my rebooting: –
    System – Provider

    [ Name] Microsoft-Windows-DistributedCOM
    [ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
    [ EventSourceName] DCOM
    – EventID 10016
    [ Qualifiers] 0
    Version 0
    Level 2
    Task 0
    Opcode 0
    Keywords 0x8080000000000000
    -TimeCreated
    [ SystemTime] 2017-03-01T13:42:14.926706900Z
    EventRecordID 20797
    Correlation
    – Execution
    [ ProcessID] 76
    [ ThreadID] 460
    Channel System
    Computer olgisl
    – Security
    [ UserID] S-1-5-19
    – EventData
    param1 application-specific
    param2 Local
    param3 Activation
    param4 {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
    param5 {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
    param6 NT AUTHORITY
    param7 LOCAL SERVICE
    param8 S-1-5-19
    param9 LocalHost (Using LRPC)
    param10 Unavailable
    param11 Unavailable

    I do not know what this means or how it is related to my Registry changes or how it will affect my PC, but anyhow I have access to WiFi for the moment. Thanks for your precise instructions.

    Like

  20. I had several issues with no rights granted to system and administrators. Solved problems like explained above.
    BUT: when I run Microsoft solitairecollection I still get the 1016 event. I was able to transfer the rights of the CLSID and the APPID, but I could not find the APPID or CLSID in the DCOMCNFG.
    Here’s the event text:
    “{316CDED5-E4AE-4B15-9113-7055D84DCC97}”

    Any suggestions how to solve this?

    Like

  21. Taking ownership of the registry keys is completely unnecessary if you open the Component Services tool with the user SYSTEM. By using this special “user” it’s possible to add and alter access rights for every DCOM component.

    This is possible by using a tool like PowerRun (from sordum.de), or AdvancedRun (from nirsoft.net).

    Thorsten

    Like

  22. Great instructions. Works for me.
    New installation of Server 2016, and got this Event ID #10016 as described in this post.
    Went through the instructions above, including the deletion of the “bad account references” in order to get to the Edit screen of the RunTimeBroker object. First tried to add the System to the permission list – no go – still getting the event notification after boot.

    Then added my username (I am in the administrators group) to the permission list, and since this DCOM innerworking is way above me, I also added, for a good measure, my username to the permission list of the Access and Configuration Persission blocks. No more notifications after boot. Happy dance.

    Heeding the warning above by Christian Ullrich, I will keep an eye for any anomalous behavior and report it back here.

    Thanks.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s