# Failed to load ‘aqProf.dll’ , ‘VtuneApi.dll’ , ‘VtuneApi32e.dll’ 

**URL:** <https://forums.unrealengine.com/t/failed-to-load-aqprof-dll-vtuneapi-dll-vtuneapi32e-dll/2743148>\
**Category:** Platform & Builds\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [July 6, 2026, 8:56pm UTC](https://forums.unrealengine.com/t/failed-to-load-aqprof-dll-vtuneapi-dll-vtuneapi32e-dll/2743148 "2026-07-06T20:56:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [July 6, 2026, 8:56pm UTC](https://forums.unrealengine.com/t/failed-to-load-aqprof-dll-vtuneapi-dll-vtuneapi32e-dll/2743148/1 "2026-07-06T20:56:35Z")

</div>

Hi,

We are trying to clean up unnecessary logs, errors in particular, as they cause confusion for some of our users. Whenever we run our packaged project, the engine always logs the following errors:

```auto
LogWindows: Failed to load 'aqProf.dll' (GetLastError=126)
LogWindows: File 'aqProf.dll' does not exist
LogProfilingDebugging: Loading WinPixEventRuntime.dll for PIX profiling (from ../../../Engine/Binaries/ThirdParty/Windows/WinPixEventRuntime/x64).
LogWindows: Failed to load 'VtuneApi.dll' (GetLastError=126)
LogWindows: File 'VtuneApi.dll' does not exist
LogWindows: Failed to load 'VtuneApi32e.dll' (GetLastError=126)
LogWindows: File 'VtuneApi32e.dll' does not exist

```

I found this post on EPS: [Log cleanup - missing aqProf.dll, VtuneApi.dll, [Content removed] that suggests modifying the engine’s plugins and using a global definition along with a unique build environment, either of which would require a source build.

Is there any way to disable these messages in our project without building the engine from source (other than adding the unnecessary profiling modules)?

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [July 6, 2026, 8:56pm UTC](https://forums.unrealengine.com/t/failed-to-load-aqprof-dll-vtuneapi-dll-vtuneapi32e-dll/2743148/2 "2026-07-06T20:56:39Z")

</div>

**Steps to Reproduce**  
Launch any packaged project without the relevant profiling modules enabled.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![Svegn2](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/svegn2/32/924220_2.png) [@Svegn2](https://forums.unrealengine.com/u/Svegn2)\
**Post date:** [July 13, 2026, 2:54pm UTC](https://forums.unrealengine.com/t/failed-to-load-aqprof-dll-vtuneapi-dll-vtuneapi32e-dll/2743148/3 "2026-07-13T14:54:31Z")

</div>

Hello!

It is possible to change the verbosity of logging channels but this happens after the external profilers are initialized. There is unfortunately no way to avoid those log entries when the external profiling code is active.

Regards,

Martin

[Attachment Removed]
