Windows Update Verbose logging

Question

_{Tuesday, May 3, 2016 5:22 PM}

Hi,

How do I enable verbose logging for Windows Update with Windows 10? I've tried the same method as used on 8.1 (Trace key in registry with Flags and Level set), but it's not working.

Getting the wonderful 0x8024000F error and need more detail.

Thanks

All replies (5)

_{Monday, May 9, 2016 1:52 AM ✅Answered}

OffColour1972,

Have you checked the Windowsupdate.log and the CBS.log?

We could also find errors there if happened.

In addition, if you have any backups available, try to restore to one that the issue didn't happen.

Regards

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Wednesday, May 4, 2016 3:06 AM}

Hi OffColour1972,

Would you please share about the steps to enable Verbose logging under Windows 8.1?

Is it the same as described in the article below?

https://support.microsoft.com/en-us/kb/2545723

By the way, could you please share the detailed error message here, or the Windows Update log?

0x8024000F

Circular update relationships were detected in the metadata.

From:

https://technet.microsoft.com/en-us/library/cc720442(v=ws.10).aspx

How to read Windowsupdate.log in Windows 10:

https://support.microsoft.com/en-us/kb/3036646

Regards

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Wednesday, May 4, 2016 7:36 AM}

Hi Michael,

Yes, tried those same instructions.

It's the same circular reference issue I've had in the past caused by publishing the Dell catalogue via SCUP and I know how to solve it, but I can't do so until I can find out which ones are causing the problem.

Usually I can find the update causing the problem by looking for the word "cycle" in the verbose log, but I can't see any reference to that. Leads me to think that either verbose logging now works differently or the wording for the error is now different.

_{Tuesday, January 2, 2018 5:30 PM}

OffColour1972,

What was the solution here? Those two log files do not contain any data in Windows 10.

_{Tuesday, January 2, 2018 7:15 PM}

OffColour1972,

What was the solution here? Those two log files do not contain any data in Windows 10.

This is an old thread and things move on. Try from a Windows PowerShell prompt

Get-WindowsUpdateLog -Verbose

That by default put a WindowsUpdate.log on the Desktop. See what that shows (older builds do not do so well at that as the newest ones)