Updating to 1903 killing networking and permissions/10016 errors


  1. Posts : 22
    Win 10, Win 7, Debian
       #1

    Updating to 1903 killing networking and permissions/10016 errors


    3 months ago I upgraded 1803 to 1903 via the installation medium due to constant update problems and it all but destroyed the OS. There were permissions issues due to MS changing, deleting or not installing accounts which caused 10016 errors, so no networking whatsoever. I couldn't even restart DHCP, no permissions. I restored from a backup image.

    I just upgraded using the installation assistant, lo and behold same BS. Same 10016's. No networking. More permissions errors.

    Last time I attempted to fix it through component services but it was just too screwed up, it caused too many problems. Once again an "Account unknown" exists and the installation process botched whatever it was trying to do.

    Is there a way to fix this screwup without a clean-install? I really don't have the time to start over again. I can't afford the downtime.
    Last edited by Aki PC; 15 Oct 2019 at 12:46.
      My Computer


  2. Posts : 8,699
    Mac OS Catalina
       #2

    You need to do a clean install at this point.
      My Computer


  3. Posts : 6,977
    windows 10
       #3

    What exactley permissions are wrong if your using something to connect say to a mapped drive and you do a full update its a new system so if you connected as fred to a pc that would actually be a SID a new upgrrade you still are fred but the SID is not the same
      My Computer


  4. Posts : 22
    Win 10, Win 7, Debian
    Thread Starter
       #4

    Samuria said:
    What exactley permissions are wrong if your using something to connect say to a mapped drive and you do a full update its a new system so if you connected as fred to a pc that would actually be a SID a new upgrrade you still are fred but the SID is not the same
    Launch and activation permissions for various DCOM components do not exist or like CLSID and APPID permissions are linked to an account that does not exist.

    It's not networking connections that have incorrect account settings but various internal components the cannot be executed or controlled as nothing owns them. Trustedinstaller did not grant permissions to system accounts during install. This would normally be repairable except now I have components that only the unknown account owns and I cannot set up that account.

    I guess I am going to have to fresh install, such a waste of time. The system was working fine until the update struck.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 02:00.
Find Us




Windows 10 Forums