Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

January/February security patches fail configuring at 98% with 0x80070057, error


  • Please log in to reply
3 replies to this topic

#1 QwertyChouskie

QwertyChouskie

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 22 February 2018 - 08:48 PM

I reset Windows Update in every way imaginable.  I ran every imaginable utility/cleaner (https://github.com/bmrf/tron, etc.), every imaginable troubleshooter (SURT, sfc /scannow, https://github.com/jdickson289/Print-Reset-Tool in full mode, etc.)... What do I do now?  CBS.log shows this:


2018-02-22 16:30:26, Info                  CSI    00000083 Begin executing advanced installer phase 38 (0x00000026) index 64 (0x0000000000000040) (sequence 103)
    Old component: [ml:328{164},l:326{163}]"Microsoft-Windows-Printing-Spooler-Core, Culture=neutral, Version=6.1.7601.17777, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    New component: [ml:328{164},l:326{163}]"Microsoft-Windows-Printing-Spooler-Core, Culture=neutral, Version=6.1.7601.24000, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
    Installer name: [6]"Events"
2018-02-22 16:30:27, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 75.
2018-02-22 16:30:27, Error                 CSI    00000001 (F) Logged @2018/2/23:00:30:26.973 : [ml:292{146},l:290{145}]"events installer: online=1, install=1, component=amd64_Microsoft-Windows-Printing-Spooler-Core_31bf3856ad364e35_6.1.7601.24000_neutral_release__."
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000002 (F) Logged @2018/2/23:00:30:27.143 : [ml:144{72},l:142{71}]"WmiCmiPlugin (-1): InstrumentationManifestAssert failed. HR=0x80070057."
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000003 (F) Logged @2018/2/23:00:30:27.143 : [ml:166{83},l:164{82}]"WmiCmiPlugin eventloghandler.cpp(192): ProcessEventsInstall failed. HR=0x80070057."
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000004 (F) Logged @2018/2/23:00:30:27.143 : [ml:170{85},l:168{84}]"WmiCmiPlugin eventloghandler.cpp(212): EventLogHandlerInstall failed. HR=0x80070057."
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000005@2018/2/23:00:30:27.143 (F) CMIADAPTER: Inner Error Message from AI HRESULT = E_INVALIDARG
 [
[29]"The parameter is incorrect.

"
]
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000006@2018/2/23:00:30:27.144 (F) CMIADAPTER: AI failed. HRESULT = E_INVALIDARG
    Element:
    [134129]"<bunch of xml>"
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000084@2018/2/23:00:30:27.158 (F) d:\w7rtm\base\wcp\cmiadapter\installers.cpp(352): Error E_INVALIDARG originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::ResolveAndInvokeInstaller expression: hr
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000007@2018/2/23:00:30:27.475 (F) CMIADAPTER: Exiting with HRESULT code = E_INVALIDARG.
[gle=0x80004005]
2018-02-22 16:30:27, Error                 CSI    00000085@2018/2/23:00:30:27.475 (F) d:\w7rtm\base\wcp\cmiadapter\installers.cpp(123): Error E_INVALIDARG originated in function Windows::WCP::CmiAdapter::CMIWrapperBasicInstaller::Install expression: hr
[gle=0x80004005]
2018-02-22 16:30:27, Info                  CSI    00000086@2018/2/23:00:30:27.520 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};Microsoft-Windows-Printing-Spooler-Core, Version = 6.1.7601.24000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;1049776
2018-02-22 16:30:27, Info                  CSI    00000087 Performing 1 operations; 1 are not lock/unlock and follow:
  LockComponentPath (10): flags: 0 comp: {l:16 b:aaf4a8803dacd3013100000010045c04} pathid: {l:16 b:aaf4a8803dacd3013200000010045c04} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.1.7600.16385_none_3868158f24725705" pid: 410 starttime: 131638193002792420 (0x01d3ac3d34ce45e4)
2018-02-22 16:30:27, Error      [0x01802b] CSI    00000088 (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT E_INVALIDARG.  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2018-02-22 16:30:27, Info                  CSI    00000089 Creating NT transaction (seq 1), objectname [6]"(null)"
2018-02-22 16:30:27, Info                  CSI    0000008a Created NT transaction (seq 1) result 0x00000000, handle @0x280
2018-02-22 16:30:28, Info                  CSI    0000008b@2018/2/23:00:30:28.266 CSI perf trace:
CSIPERF:TXCOMMIT;896550
2018-02-22 16:30:28, Info                  CSI    0000008c End executing advanced installer (sequence 103)
    Completion status: HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)




Full relevant excerpt: https://pastebin.com/ZV7McTvb

Full CBS.log: https://cloud.brainstormz.tk:10298/index.php/s/zgxB3ERNq7MNuch



Halp?!?



BC AdBot (Login to Remove)

 


#2 OldPhil

OldPhil

    Doppleganger


  • Members
  • 4,130 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Long Island New York
  • Local time:10:22 PM

Posted 22 February 2018 - 09:05 PM

Curious I just updated two laptops and my tower with no obvious issues, your problem may very well in your system.


Honesty & Integrity Above All!


#3 DavidLMO

DavidLMO

  • Members
  • 50 posts
  • OFFLINE
  •  
  • Local time:09:22 PM

Posted 23 February 2018 - 12:52 AM

January updates Hosed zillions of machines.  February Borked a lot as well.  Mine included.

You were trying to install All the Updates for January and February?  Did you try to install all of them at once or one at a time?

 

Did you shut down all Anti-virus and Anti-malware?

 

Does your machine boot up to normal mode?



#4 QwertyChouskie

QwertyChouskie
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:02:22 AM

Posted 27 March 2018 - 06:26 PM

I finally got it fixed.  For anyone else who is having a similarly mysterious issue, check Event Log.  Not for hints as to why it's failing, but for hints that event log is *causing* the issue.  That's right, event log *caused* the issue!

 

The thing to look for is any log folders in "Applications and Services\Microsoft\Windows" that have slashes in their name.  This indicates that the registration for the provider for that event log is missing in the registry.  In my case this was what I needed:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\{747ef6fd-e535-4d16-b510-42c90f6873a1}]
@="Microsoft-Windows-PrintService"
"ResourceFileName"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,\
  00,6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\
  5c,00,6e,00,74,00,70,00,72,00,69,00,6e,00,74,00,2e,00,64,00,6c,00,6c,00,00,\
  00
"MessageFileName"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
  6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
  00,6e,00,74,00,70,00,72,00,69,00,6e,00,74,00,2e,00,64,00,6c,00,6c,00,00,00
"Enabled"=dword:00000001

(Note that the hex sections show up as text when viewed in regedit.)

 

In my case I just re-entered the data using regedit while looking at the data on a working system.

 

No idea how it got deleted in the first place, but re-adding seemed to do the trick.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users