Fail installing updates event log

%3CLINGO-SUB%20id%3D%22lingo-sub-677895%22%20slang%3D%22en-US%22%3EFail%20installing%20updates%20event%20log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677895%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20there%20is%20no%20event%20log%20error%20for%20fail%20installing%20Windows%20updates%20in%20clients%3F%3C%2FP%3E%3CP%3ESCCM%20push%20updates%20using%20ADR%20that%20create%20new%20software%20Update%20group%20each%20time.%20I%20noticed%20that%20some%20updates%20are%20failed%20to%20install%20in%20some%20servers%20because%20of%20maximum%20run%20time%20(it%20seems%20some%20servers%20take%20much%20time%20to%20install%20the%20update)%2C%20however%20there%20is%20no%20event%20log%20shows%20this%20in%20windows%20event%20log.%20I%20checked%20Systems%20logs%20and%20filtered%20based%20on%20source%20of%20WindowsUpdateClient.%20the%20only%20log%20i%20got%20is%20event%20ID%2043%20(Installation%20Started%3A%20Windows%20has%20started%20installing%20the%20following%20update%3A%20).%20and%20this%20keep%20repeating%20every%20time%20the%20update%20agent%20try%20to%20re-install%20the%20same%20update%20and%20it%20failed.%20I%20can%20see%20this%20in%20Updates%20History%20in%20Windows%20Updates%20settings%20window.%3C%2FP%3E%3CP%3E%26nbsp%3BAny%20idea%20how%20to%20catch%20this%20failure%20in%20event%20log%20in%20client%20machines%3F%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EBachar%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-677895%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESoftware%20Update%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736481%22%20slang%3D%22en-US%22%3ERe%3A%20Fail%20installing%20updates%20event%20log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736481%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356566%22%20target%3D%22_blank%22%3E%40bacharbader%3C%2FA%3E%26nbsp%3BIn%20Event%20Viewer%2C%20under%20Application%20and%20Services%20Logs%5CMicrosoft%5CWindows%5CWindowsUpdateClient%20should%20show%20you%20return%20errors.%26nbsp%3B%20With%20not%20knowing%20what%20version%20of%20the%20OS%20you%20referring%20to%20you%20can%20try%20running%20the%20PowerShell%20command%20%22Get-WindowsUpdateLog%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-743039%22%20slang%3D%22en-US%22%3ERe%3A%20Fail%20installing%20updates%20event%20log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-743039%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F356566%22%20target%3D%22_blank%22%3E%40bacharbader%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EDid%20you%20check%20the%20Config%20Mgr%20logs%3F%26nbsp%3B%3CBR%20%2F%3Ewuahandler.log%3CBR%20%2F%3Eupdatesdeployment.log%3C%2FP%3E%3CP%3Erebootcoordinator.log%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20typically%20check%20those%203%20in%20CMTrace%20(merged%20view)%20and%20can%20find%20errors%20with%20the%20updates%20installing.%20Sometimes%20they%20are%20general%2C%20non-specific%20errors%20that%20aren't%20helpful%2C%20but%20other%20times%2C%20it%20will%20tell%20you%20error%20%22time-out%20exceeded%22%20etc.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20may%20need%20to%20run%20a%20PS%20script%20against%20your%20Software%20Updates%20Catalog%20to%20set%20the%20max%20run%20time.%20By%20default%20it%20should%20be%2060mins%20but%20we've%20caught%20a%20bunch%20that%20were%20reset%20to%205mins.%20We%20have%20a%20script%20that%20we%20run%20now%20to%20increase%20it%20to%2090%20or%20120mins%20for%20CU's%20etc.%20(if%20required).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20check%20in%20those%20places%20and%20then%20hit%20the%20Google%20machine%20for%20the%20update%20run%20time%20change.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EDrew%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-743307%22%20slang%3D%22en-US%22%3ERe%3A%20Fail%20installing%20updates%20event%20log%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-743307%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F372849%22%20target%3D%22_blank%22%3E%40drewfortey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%20the%20original%20problem%20of%20fail%20installing%20updates%20is%20the%20max%20run%20time%20and%20I%20can%20find%20the%20error%20code%20in%20Software%20center%20or%20SCCM%20logs%20(as%20you%20mentioned).%20can%20you%20please%20share%20with%20me%20the%20script%20you%20mentioned.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehowever%2C%20my%20post%20was%20about%20catching%20such%20an%20issue%20using%203rd%20party%20monitoring%20tool%20that%20is%20not%20integrated%20with%20SCCM%20and%20its%20logs.%20this%20monitoring%20tool%20is%20looking%20for%20any%20event%20log%20in%20client%20by%20event%20ID%20or%20any%20other%20criteria%20but%20this%20(max%20run%20time)%20doesn't%20log%20any%20error%20in%20client%20machine.%20I%20think%20Widows%20update%20agent%20terminate%20the%20installation%20once%20max%20run%20time%20finish.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EBachar%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Why there is no event log error for fail installing Windows updates in clients?

SCCM push updates using ADR that create new software Update group each time. I noticed that some updates are failed to install in some servers because of maximum run time (it seems some servers take much time to install the update), however there is no event log shows this in windows event log. I checked Systems logs and filtered based on source of WindowsUpdateClient. the only log i got is event ID 43 (Installation Started: Windows has started installing the following update: ). and this keep repeating every time the update agent try to re-install the same update and it failed. I can see this in Updates History in Windows Updates settings window.

 Any idea how to catch this failure in event log in client machines? 

Regards

Bachar

3 Replies
Highlighted

@bacharbader In Event Viewer, under Application and Services Logs\Microsoft\Windows\WindowsUpdateClient should show you return errors.  With not knowing what version of the OS you referring to you can try running the PowerShell command "Get-WindowsUpdateLog"

Highlighted

@bacharbader 

Did you check the Config Mgr logs? 
wuahandler.log
updatesdeployment.log

rebootcoordinator.log

We typically check those 3 in CMTrace (merged view) and can find errors with the updates installing. Sometimes they are general, non-specific errors that aren't helpful, but other times, it will tell you error "time-out exceeded" etc. 

You may need to run a PS script against your Software Updates Catalog to set the max run time. By default it should be 60mins but we've caught a bunch that were reset to 5mins. We have a script that we run now to increase it to 90 or 120mins for CU's etc. (if required).

I would check in those places and then hit the Google machine for the update run time change.


Drew

Highlighted

@drewfortey 

Thanks. the original problem of fail installing updates is the max run time and I can find the error code in Software center or SCCM logs (as you mentioned). can you please share with me the script you mentioned.

 

however, my post was about catching such an issue using 3rd party monitoring tool that is not integrated with SCCM and its logs. this monitoring tool is looking for any event log in client by event ID or any other criteria but this (max run time) doesn't log any error in client machine. I think Widows update agent terminate the installation once max run time finish.

 

Regards

Bachar