Bork Tuesday, Any Problems Yet?

Discussion in 'other software & services' started by Daveski17, Nov 12, 2014.

  1. XIII

    XIII Registered Member

    Joined:
    Jan 12, 2009
    Posts:
    1,383
    I already ran sfc (no errors), but should try DISM...

    BTW: Another attempt failed after manually installing the Arial Nova font. Now it's complaining that the "Compact" key is missing in \MACHINE\SYSTEM\Setup...
     
  2. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    @XIII,

    The last one means absolutely nothing. It's a vague registry path.
    Where do you get all these errors? Do they display on-screen or are you looking at the logs?

    First things first, Arial Nova font is part of optional features if you have any of the Pan-European languages installed (this is the term for all official languages of the current members of the EU). What do you have installed in 'optional features'? (Apps & Features -> Manage Optional Features).

    [EDIT] Reference:
    https://docs.microsoft.com/en-us/wi...cture/desktop/features-on-demand-language-fod
     
  3. XIII

    XIII Registered Member

    Joined:
    Jan 12, 2009
    Posts:
    1,383
    I checked in the logs.

    Currently doing another attempt, so can't check anything now...
     
  4. __Nikopol

    __Nikopol Registered Member

    Joined:
    Aug 13, 2008
    Posts:
    630
    Location:
    Germany
    Did DISM not do anything?
     
  5. JRViejo

    JRViejo Super Moderator

    Joined:
    Jul 9, 2008
    Posts:
    97,440
    Location:
    U.S.A.
  6. XIII

    XIII Registered Member

    Joined:
    Jan 12, 2009
    Posts:
    1,383
    All was fine according to both sfc and DISM...

    This is the remaining setuperr.log from my last attempt (for a while):

    2018-12-09 17:09:09, Error SP pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
    2018-12-09 17:11:15, Error CSI 00000001 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #64184# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 6e006c002d004e004c000000 })
    [gle=0x80004005]
    2018-12-09 17:12:36, Error CSI 00000002 (F) 80220008 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=8] #128318# from CWcmScalarInstanceCore::GetCurrentValue(options = 393216, status = '(null)', value = { type: 40972, bytes ( 12 ): 6e006c002d004e004c000000 })
    [gle=0x80004005]
    2018-12-09 17:13:22, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __thiscall Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
    2018-12-09 17:18:21, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
    2018-12-09 17:18:21, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
    2018-12-09 17:26:21, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __thiscall Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
    2018-12-09 17:34:50, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: offline key (new) = '$OFFLINE_RW_003ADB7E$SYSTEM\Setup\Upgrade\Bridge'
    2018-12-09 17:34:50, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
    2018-12-09 17:34:57, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
    2018-12-09 17:34:57, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
    2018-12-09 17:34:59, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment}. Error: 0x80070002
    2018-12-09 17:34:59, Error SP Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
    2018-12-09 17:35:50, Error [0x0803eb] MIG Error: 3 Message: Error opening the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator\InstallAtShutdown: Het systeem kan het opgegeven pad niet vinden. [0x00000003]
    2018-12-09 17:35:50, Error [0x0803eb] MIG Error: 3 Message: Error opening the key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Orchestrator\InstallAtShutdown: Het systeem kan het opgegeven pad niet vinden. [0x00000003]
    2018-12-09 17:35:59, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-feclient[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:35:59, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-feclient[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [EfsLocalConfig]. Will return 2
    2018-12-09 17:35:59, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-feclient[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:35:59, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-feclient[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [EfsLocalConfig]. Will return 2
    2018-12-09 17:36:01, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-Dot3svc[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:01, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-Dot3svc[@version="10.0.17134.1" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:03, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-OfflineFiles-Core[@version="10.0.17134.228" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:03, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-OfflineFiles-Core[@version="10.0.17134.228" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:03, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft-Windows-OfflineFiles-Core[@version="10.0.17134.228" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [DriverStartType]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [ConfigVersion]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [EventMessageFile]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [ProviderGuid]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [TypesSupported]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [WinHttpSettings]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [ConfigVersion]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [EventMessageFile]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [ProviderGuid]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [TypesSupported]. Will return 2
    2018-12-09 17:36:04, Error SP Error WRITE, 0x0000065E while gathering/applying object: State, Microsoft.Windows.WinHTTP[@version="5.1.17134.441" and @arch="x86" and @culture="neutral" and @context="allUsers"]/settings [WinHttpSettings]. Will return 2
    2018-12-09 17:36:40, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
    2018-12-09 17:36:40, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
    2018-12-09 17:44:44, Error MOUPG Finalize: Error reading narrator reg key: [0x80070002]

    The error on screen is still 0xC1900101 - 0x20017.

    Does anybody have a clue what else I could try?
     
  7. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,592
    Location:
    U.S.A.
    The only thing I can think of at this point is you do a "Reset" install on your existing 1803 build. The main question is if Win Update would download 1803 or 1809? I suspect it would still be 1803.

    All your data will be retained but most of your apps will have to be manually reinstalled. You could wait on the app reinstall till the 1809 upgrade, if successful, is installed. This would eliminated any possible app conflicts with the 1809 Upgrade.

    Also make sure you take an image backup that could be used to rollback to your existing 1803 build if the above results in a complete bork of your system.
     
  8. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    Looking at the article I linked to a few days ago more closely, they don't explain this very well at all...
    In the example there, they showed how you should search for the result code in log files and this will reveal another code.
    They used 0x8007042B as an example and showed these results -
    Code:
    27:08, Error           SP     Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]
    27:08, Error           MIG    Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570]
    27:08, Error                  Gather failed. Last error: 0x00000000
    27:08, Error           SP     SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C
    27:09, Error           SP     CMigrateFramework: Gather framework failed. Status: 44
    27:09, Error           SP     Operation failed: Migrate framework (Full). Error: 0x8007042B[gle=0x000000b7]
    27:09, Error           SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
    27:09, Error           SP     CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007042B[gle=0x000000b7]
    The line they specifically poined out as culprit is the first one, but this line does not contain the above result code.
    This is what is not explained well - the line ends with 'will return 0'. In python, a return of 0 is a failure (false).
    However, I can't see that any of the functions in the above spoiler returns 0.
    Are these the entire contents of setuperr? When you search for the "will return 0" string in the setupact what comes up? If anything.
     
  9. __Nikopol

    __Nikopol Registered Member

    Joined:
    Aug 13, 2008
    Posts:
    630
    Location:
    Germany
    Why do you assume python?
     
  10. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    I mixed it up. I thought that this is pyhon as I thought that the folder where the log files are located is named that. But the folder is panther.
    My bad.
    Nevertheles a return of 0 is a failure as the codes suggest (0x....)
    This whole block of text refers to one result code, so the code should be searched for as well. They suggest to search both setuperr and setupact.
     
  11. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,937
    Location:
    UK
    Regarding Windows 10 cumulative update KB4467682 for Windows 10 version 1803 (April 2018 Update)

    Also
    https://news.softpedia.com/news/win...67682-breaks-down-the-start-menu-524190.shtml
     
  12. act8192

    act8192 Registered Member

    Joined:
    Nov 9, 2006
    Posts:
    1,789
    Windows10-1803 64bit - strange Adobe Flash stuff.
    Two days ago I had a pending update for Adobe Flash. KB4477029. Agreed to install.
    Today I had a pending update with a lower number, KB4471331. Agreed to install.
    This is totally weird. Any idea what's going on?

    Edit: corrected KB numbers per next post.
     
    Last edited: Dec 11, 2018
  13. paulderdash

    paulderdash Registered Member

    Joined:
    Dec 27, 2013
    Posts:
    4,639
    Location:
    Under a bushel ...
    No idea. I see the same (447 not 477) in update history.
    KB4477029 installed 21 Nov.
    KB4471331 installed 6 Dec.
     
  14. act8192

    act8192 Registered Member

    Joined:
    Nov 9, 2006
    Posts:
    1,789
    Surry for mistyping. They are 447 as you wrote. I just corrected by post. Thanks :)
     
  15. stapp

    stapp Global Moderator

    Joined:
    Jan 12, 2006
    Posts:
    23,937
    Location:
    UK
    Win 10 1809... 3 Updates.

    Malicious Software Removal Tool
    Cumulative for .Net KB4470502
    Cumulative for 1809 KB4471332

    All installed first time of asking.
    After restart build is 17763.194
     
  16. Minimalist

    Minimalist Registered Member

    Joined:
    Jan 6, 2014
    Posts:
    14,881
    Location:
    Slovenia, EU
    I updated Windows 7, Office 2010 and .NET and so far didn't notice any problems.
     
  17. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,592
    Location:
    U.S.A.
    Check for Win Updates today on 1803 served up 1809 Feature Update. So we'll see if it is able to install this time ………………...
     
  18. Azure Phoenix

    Azure Phoenix Registered Member

    Joined:
    Nov 22, 2014
    Posts:
    1,556
    Got an error with that. Will try again in a while.
     
  19. Osaban

    Osaban Registered Member

    Joined:
    Apr 11, 2005
    Posts:
    5,614
    Location:
    Milan and Seoul
    Same here, fast and flawless as usual...
     
  20. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    In case anyone reads these (I'm guessing not) -
    https://support.microsoft.com/uz-latn-uz/help/4471332/windows-10-update-kb4471332
     
  21. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,592
    Location:
    U.S.A.
    Only God knows how this 1809 Upgrade is going to turn out.

    Mine got stuck at 100% downloaded. Got fed up and rebooted. Windows Update status showed entire updating failed with a retry later option. A short time later checked again and all Office and MRT updates were installed or installing. Then the 1809 install started and is currently running.

    My gut is telling me a 1809 Feature upgrade MCF is in-process ………………..
     
  22. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    No fails this time. Good.
    I also does not have my 'silent fail' EventIDs 20 in the logs.
    All is fine.
     
  23. Seer

    Seer Registered Member

    Joined:
    Feb 12, 2007
    Posts:
    2,068
    Location:
    Serbia
    It's his time of year, so the chances are on your side :thumb:
    If this goes well, you will get rid of that Remediation thing. But you'll still have the Medic service.
     
  24. Floyd 57

    Floyd 57 Registered Member

    Joined:
    Mar 17, 2017
    Posts:
    1,296
    Location:
    Europe
    v1803, I just installed:

    KB4477137 - 17134.471
    KB4471324 - Servicing Stack Update
    KB4023057 - Update Reliability update

    Ofc, I made a full macrium backup, I learnt my lesson not to blindly install updates without a backup :D

    The last update created a new task "C:\WINDOWS\SysWOW64\schtasks.exe -create -tn Microsoft\Windows\rempl\shell -xml rempl.xml -F", then ran reg.exe twice for each of these cmd lines:

    C:\WINDOWS\SysWOW64\reg.exe delete HKLM\SOFTWARE\Microsoft\rempl /v HasUpgraded /f /reg:64
    C:\WINDOWS\SysWOW64\reg.exe delete HKLM\SOFTWARE\Microsoft\rempl\Cleanup /va /f /reg:64
    C:\WINDOWS\SysWOW64\reg.exe delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\rempl\appr /va /f /reg:64
    C:\WINDOWS\SysWOW64\reg.exe delete HKLM\Software\Microsoft\Windows\CurrentVersion\rempl\Settings /va /f /reg:64
    C:\WINDOWS\SysWOW64\reg.exe delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\rempl\shell /va /f /reg:64

    17134.471 brought new searchfilterhost and sppsvc exes, possibly searchui too cuz I deleted that one but it reappeared (or maybe it was just sfc /scannow - like? I'll check going forward)

    Judging by some other posts, such as in this thread and here https://www.tenforums.com/general-support/99580-scheduled-task-keeps-waking-my-computer-rempl.html and here https://www.reddit.com/r/Windows10/...know_what_this_is_in_my_task_manager/e465bty/ , I have decided to disable this thing until further notice (when I decide I want to upgrade to 1809)

    Opening taskschd.msc and disabling the \microsoft\windows\rempl shell task is probably not going to be enough, knowing windows likes to reactivate the tasks, so I deleted the task. I did a backup of the .xml file in case I need the task back. However, knowing windows, the service will likely just re-create the task (or at least annoy me with schtasks.exe prompts which I'd have to block). So I used subinacl to deny (revoke) anyone any permissions for the Windows Remediation Service, meaning windows won't be able to enable (and start) the service back (unless, it changes the permissions, but it's too dumb to do that) I first stopped the service and disabled it from services.msc, then I ran "subinacl /service sedsvc" to check the current permissions of the service. I then made a backup of that in case I need the service later. I then ran the following commands:

    subinacl /service sedsvc /revoke=system
    subinacl /service sedsvc /revoke=interactive
    subinacl /service sedsvc /revoke=service
    subinacl /service sedsvc /setowner=MyUsername
    subinacl /service sedsvc /revoke=everyone
    subinacl /service sedsvc /sdeny=everyone
    subinacl /service sedsvc /audit
    subinacl /service sedsvc /revoke=administrators
    (this is done as administator in cmd, not as TI or System, thus revoking administrators permissions last)

    Now since we no longer have permissions to read the permissions of the service using subinacl (we removed all permissions), we can use "sc sdshow sedsvc" with result "D:S:", meaning no permissions (sacl or dacl) for anyone. In fact, if we refresh services.msc, we'll see the service disappeared, simply because we don't have permissions to "see" it. Then, last thing left to do is to make sure windows can't re-enable the service by changing the registry key. First, we make sure the Start value is set to 4, thus the service is disabled: reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc" /v "Start" , we should get 0x4 dword as result. Then, we change the permissions and ownership of the registry key:

    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc /revoke=system
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc /grant=system=r
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc /setowner=MyUsername
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc /revoke="creator owner"
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc /grant=administrators=r

    Now, the most anyone can do with the registry key is read it. The start value can't be modified (unless, again, the system changes the permissions back)

    Since now no one has any permissions for sedsvc, subinacl will give us access denied when using it, and so will sc sdset (we essentially denied everyone permissions to the service, including ourselves) We can, however, delete the reg key Security under sedsvc, which is what holds the information about the sacl and dacl of the service. So, we're gonna restrain windows from touching this key as well, just in case:

    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc\Security /setowner=MyUsername
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc\Security /grant=system=r
    subinacl /keyreg HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sedsvc\Security /grant=administrators=r

    And this, is how I completely destroyed windows' chances to ever run sedsvc or sedlauncher.exe ever again (in a way that doesn't involve blocking the processes or deleting them, not running a process is faster than having to block it)
     
    Last edited: Dec 11, 2018
  25. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,592
    Location:
    U.S.A.
    It crapped out again with the same error, 0xC1900101, as received in the last failed update in Oct.. My best guess at this time as to failure is the Win 10 Realtek audio driver I downloaded from the Win Catalog site to get 1803 Core Insolation Memory Protection to work on my old Gigabyte AMD motherboard. When I get time, I will reinstall the original MB driver for it and disable 1803 Memory Protection. Then will try again to install 1809 via Win Update.

    As far as this recent 1809 Feature update failure, here is where it gets weird. Unlike the Oct. failures, Win Update status shows it is up to date. No retry status as occurred in the Oct. failures. Also Win Updates never applied the Dec. 1803 Cumulative Security update. I had to download it manually and install it.

    So the question now going forward is if every time one checks for Win Updates is the dirty rotten 1809 Feature update going to try to reinstall itself?
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.