![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 15%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,589 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 9%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWL%3C/text%3E%3C/svg%3E)
Hello
It seems like you're encountering an issue with logging the "setthreadcontext" API usage for 32-bit processes using the "Microsoft-Windows-Kernel-Audit-API-Calls" provider. This issue is specific to 32-bit processes on both Windows 10 and 11 64-bit OS.
From the information I found, it appears that the "Microsoft-Windows-Kernel-Audit-API-Calls" provider is designed to log various API calls, including "setthreadcontext" for 64-bit processes. However, there might be limitations or specific configurations required for 32-bit processes.
Here are a few things you might consider:
Check Provider Configuration: Ensure that the provider is correctly configured to capture events for 32-bit processes. Sometimes, specific flags or settings might be needed to enable logging for 32-bit processes.
ETW Stack Crawling Support: There might be differences in how ETW stack crawling is supported for 32-bit and 64-bit processes.
Consult Documentation: The GitHub repository for ETW providers might have additional information or updates regarding the "Microsoft-Windows-Kernel-Audit-API-Calls" provider. You can check the repository for any relevant details.