The WPP trace info is in the NDIS pdb symbol file on Windows 10. I think the .tmf files can be extracted from it, but that shouldn’t be needed. (The checked build also isn’t needed for WPP logging.)
In WinDbg run
!wmitrace.start ndis -kd
!wmitrace.enable ndis {DD7A21E6-A651-46D4-B7C2-66543067B869} -level 4 -flag 0x31f3
as per https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-ndiskd-dbgsystems
If only ‘No Format Information found’ messages are displayed, sometimes I find running !wmitrace.logdump ndis fixes it. As ever with WPP, YMMV.
It should also be possible view the messages by loading the correct ndis.pdb in TraceView. I haven’t often, however, found NDIS logging to be that useful with the issues I’ve tried using it to look into.