SOLVED

How do I get windowsupdate.log from a remote device without psremoting enabled?

%3CLINGO-SUB%20id%3D%22lingo-sub-1572177%22%20slang%3D%22en-US%22%3EHow%20do%20I%20get%20windowsupdate.log%20from%20a%20remote%20device%20without%20psremoting%20enabled%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1572177%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Before%20I%20get%20started%2C%20I%20should%20point%20out%20that%20the%20error%20message%20shown%20in%20the%20Wuahandler.log%20(0x8024000e)%20is%20one%20I%20have%20tried%20troubleshooting%20and%20not%20found%20a%20solution%20to%2C%20so%20for%20this%20post%2C%20I%20am%20just%20wanting%20to%20know%20how%20to%20get%20windowsupdate.log%20from%20a%20remote%20computer%20without%20powershell.%26nbsp%3B%20We%20regularly%20get%20messages%20on%20machines%20that%20have%20failed%20updates%20in%20Wuahandler.log%20that%20say%20I%20need%20to%20check%20windowsupdate.log%20for%20more%20information%2C%20however%20as%20we%20know%20you%20can't%20check%20windowsupdate.log%20in%20the%20windows%20directory%20because%20it%20hasn't%20contained%20anything%20for%20a%20long%20time%20now.%20(I%20have%20included%20a%20copy%20of%20the%20message%20at%20the%20end%20of%20this%20post)%3C%2FP%3E%3CP%3EPSRemoting%20is%20disabled%20on%20our%20network%20for%20security.%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question%20is%2C%20how%20can%20I%20gather%20the%20data%20that%20powershell%20would%20normally%20collect%20from%20the%20remote%20machines%20that%20makes%20up%20windowsupdate.log.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20could%20set%20up%20a%20Script%20in%20MECM%20to%20run%20from%20there%2C%20something%20simple%20like%3C%2FP%3E%3CP%3EGet-WindowsUpdateLog%20-LogPath%20%22%5C%5C%24LogFileTargetServer%5CTEMP%5CWindowsUpdateLogs%5CLogs%5C%24Hostname-WindowsUpdateLog.log%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20just%20checking%20before%20I%20complicate%20things%20that%20there%20isn't%20already%20an%20option%20I'm%20not%20aware%20of%20like%20a%20command%20line%20maybe%20or%20something%20similar.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20same%20error%20appears%20in%20the%20logs%20on%20various%20machines%3C%2FP%3E%3CP%3E****************************************************************************%3C%2FP%3E%3CP%3EThis%20is%20the%20message%20seen%20in%20Wuahandler.log%2C%20repeated%20regularly.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EReceived%20'SucceededWithErrors'%20code%20from%20WUA%20during%20search.%20Check%20WindowsUpdate.log%20in%20Windows%20directory.%20WUAHandler%205%2F08%2F2020%2010%3A10%3A50%20AM%205728%20(0x1660)%3CBR%20%2F%3EWU%20Agent%20reported%20the%20following%201%20warning%20messages%3A%20WUAHandler%205%2F08%2F2020%2010%3A10%3A50%20AM%205728%20(0x1660)%3CBR%20%2F%3EHResult%3A%200x8024000e%20Context%3A%20uecWindowsDriver%20Msg%3A%20(null).%20WUAHandler%205%2F08%2F2020%2010%3A10%3A50%20AM%205728%20(0x1660)%3C%2FP%3E%3CP%3E*********************************************************************************%3C%2FP%3E%3CP%3EIt%20reports%20back%20with%20varying%20error%20messages%20in%20the%20deployment%20logs%20of%20the%20console%2C%20none%20of%20which%20appear%20to%20be%20very%20useful%20-%20some%20shown%20below%20-%20I'm%20hoping%20WindowsUpdate.log%20might%20have%20more%20info.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B-%20%22unspecified%20error%22%200x80004005%3C%2FP%3E%3CP%3E-%20%22Success%22%200x00000000%3C%2FP%3E%3CP%3E-%20%22Unknown%20Error%20(-2146994854)%22%200x8007755A%3C%2FP%3E%3CP%3E-%20%22Unknown%20Error%20(-2146994704)%22%200x800775F0%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1609999%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20get%20windowsupdate.log%20from%20a%20remote%20device%20without%20psremoting%20enabled%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1609999%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F304933%22%20target%3D%22_blank%22%3E%40PaulKlerkx%3C%2FA%3E%26nbsp%3BWithout%20being%20able%20to%20use%20PS%20Remoting%20(or%20something%20like%20the%20SysInternals%20PSExec%20tool%2C%20I%20presume)%2C%20a%20ConfigMgr%20console%20script%20is%20probably%20the%20easiest%20solution.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20what%20it's%20worth%2C%20the%26nbsp%3B%3CSPAN%3E0x8024000e%20return%20code%20translates%20to%26nbsp%3BWU_E_XML_INVALID%3A%20%22Windows%20Update%20Agent%20found%20invalid%20information%20in%20the%26nbsp%3Bupdate's%20XML%20data%22.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi, Before I get started, I should point out that the error message shown in the Wuahandler.log (0x8024000e) is one I have tried troubleshooting and not found a solution to, so for this post, I am just wanting to know how to get windowsupdate.log from a remote computer without powershell.  We regularly get messages on machines that have failed updates in Wuahandler.log that say I need to check windowsupdate.log for more information, however as we know you can't check windowsupdate.log in the windows directory because it hasn't contained anything for a long time now. (I have included a copy of the message at the end of this post)

PSRemoting is disabled on our network for security. 

My question is, how can I gather the data that powershell would normally collect from the remote machines that makes up windowsupdate.log. 

I could set up a Script in MECM to run from there, something simple like

Get-WindowsUpdateLog -LogPath "\\$LogFileTargetServer\TEMP\WindowsUpdateLogs\Logs\$Hostname-WindowsUpdateLog.log"

 

I'm just checking before I complicate things that there isn't already an option I'm not aware of like a command line maybe or something similar.  

 

 

This same error appears in the logs on various machines

****************************************************************************

This is the message seen in Wuahandler.log, repeated regularly.  

Received 'SucceededWithErrors' code from WUA during search. Check WindowsUpdate.log in Windows directory. WUAHandler 5/08/2020 10:10:50 AM 5728 (0x1660)
WU Agent reported the following 1 warning messages: WUAHandler 5/08/2020 10:10:50 AM 5728 (0x1660)
HResult: 0x8024000e Context: uecWindowsDriver Msg: (null). WUAHandler 5/08/2020 10:10:50 AM 5728 (0x1660)

*********************************************************************************

It reports back with varying error messages in the deployment logs of the console, none of which appear to be very useful - some shown below - I'm hoping WindowsUpdate.log might have more info.  

 - "unspecified error" 0x80004005

- "Success" 0x00000000

- "Unknown Error (-2146994854)" 0x8007755A

- "Unknown Error (-2146994704)" 0x800775F0

2 Replies
Highlighted
Best Response confirmed by PaulKlerkx (Contributor)
Solution

@PaulKlerkx Without being able to use PS Remoting (or something like the SysInternals PSExec tool, I presume), a ConfigMgr console script is probably the easiest solution.

 

For what it's worth, the 0x8024000e return code translates to WU_E_XML_INVALID: "Windows Update Agent found invalid information in the update's XML data".

Highlighted

@Michiel Overweel Awesome, thankyou, not sure why I never thought of the MECM script idea, that should work perfectly.   

 

Re the error message, I did find that, but the updates install fine on plenty of other computers, just a small percentage with these messages, can't see how the xml would be dodgy for one, but ok for others.  Seems like it is maybe rather a symptom of something else wrong on the devices.