Recent Oculus v63 update generates warnings in Unreal about dbgeng.dll / StackWalk2

[marc.176173]

Using Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361) we are now seeing repeated warnings when loading an Unreal application (or even just the Unreal Editor). The Unreal application copies a version of dbghelp.dll across to the ThirdParty binaries folder, but this was always the case, and the warnings did not appear before the Oculus update. If the Oculus app is uninstalled, these warnings do not appear. Are any Oculus developers looking into this? Thanks.

Possibly related to https://communityforums.atmeta.com/t5/OpenXR-Development/OpenXR-hand-body-tracking-extensions-not-wo... 

[Spikeenick]

replied to the link but can confirm the same issue. 
Fits the time line of the update for me 
I'm running windows 11 if you can confirm the same. 
others running windows 10 do not seem to be having the same issue 

[Khebab]

@Ryanality 

[Khebab]

Victor Lerp is looking into it

https://forums.unrealengine.com/t/entry-point-not-found-dbgeng/1775727

[Gavin69]

In your 'Path' System variable, is the oculus-runtime location specified before or after your windows/System32 entry? I'm not getting this error on Windows 11, my oculus-runtime folder is pathed before the System32. 
(I'm just hunting around for possible causes, so this might not be significant) 

[Khebab]

Mine is set before

If this doesn't happen for you on Win11 with Meta Link v63/v64, are you using UE4 or UE5?

[Gavin69]

UE5.3.2
Meta Quest Link 63.0.0.216.361 (seems to be the version people are reporting an issue with?)
dbgeng.dll and dbghelp.dll are both 10.0.22621.2506 in system32 folder. 
The versions in the oculus-runtime folder are,
dbgeng.dll 10.0.17763.1
dbghelp.dll 10.0.17763.132

[Gavin69]

Ah, ok I get the issue with a VR Template project in UE5.2 
My main development is in 5.3.2 at the moment. 
A non-VR app opens with no problems in 5.2. 

[Gavin69]

What's slightly confusing is, when you initially create the VR Template project in 5.2 the error message doesn't come up. It's only when you double-click the uproject (after closing) you start to get the error. (so is possible to miss while testing). 

[Khebab]

The error shows up even in an empty non-VR project in UE4, just launching the editor to create a new project causes the error to pop up, and as the OP mentioned uninstalling the Oculus app fixes it