Good question although it might be better answered in a Windows Update forum.

I will wander over there......

If someone gives you a good answer, please link it here -- as mentioned, it's a good question and it would be great if there is something better.

I will. I'm guessing that other SCCM admins might be looking for ideas on this. Up until now, I've always seen value in looking at this log for my SCCM issues.

If you run Get-WindowsUpdateLog with no parameters, it appears to retrieve all the necessary files (like symbols), place them in %temp%\WindowsUpdateLog and then spit out a WindowsUpdate.log file on the Desktop. The contents of that log file appear to be largely the same as WU logs from previous versions of Windows. Is there anything specific you see missing in the Windows 10 log? Genuinely curious.

Thanks for the note back. I just setup a brand new VM with Windows 10 Enterprise and ran the Powershell command.  It seems to run but then sticks at this. The WindowsUpdate.log created on the desktop only has one line

Checking write access

I ran the command from an Admin PS prompt

PS C:\Windows\system32> Get-WindowsUpdateLog

Converting C:\Windows\logs\WindowsUpdate into C:\Users\myname\Desktop\WindowsUpdate.log ...

Input
----------------
File(s):
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150710.052208.397.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150710.052210.960.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.083306.853.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.084809.054.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.104507.924.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.111707.676.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.113601.873.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.124625.007.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.132920.694.1.etl
     C:\Windows\logs\WindowsUpdate\WindowsUpdate.20150812.134756.824.1.etl

You'll get a prompt first and then it'll take a while. I just tried it and it worked fine. It does not update dynamically though.

I restarted and ran it again and it went through pretty quick this time. It does have what I need to see so and reads well with CMTrace but it's a step backwards for administering lots of machines.