[0x7FFFBB83E044] ANOMALY: use of REX.w is meaningless (default operand size is 64) #8876

Closed
opened 2026-01-31 01:40:13 +00:00 by claunia · 14 comments
Owner

Originally created by @Cppowboy on GitHub (Jun 7, 2020).

Environment

win10 professional, 19041.264
for powershell and ubuntu wsl
windows terminal version 1.0.1401.0
no other softwares

Steps to reproduce

Just open windows terminal, and an error message appears on the top of the terminal.
[0x7FFFBB83E044] ANOMALY: use of REX.w is meaningless (default operand size is 64)
This problem only happens when using powershell and ubuntu wsl.

Expected behavior

The terminal should not show this error message.

Actual behavior

An error message appears on the top of the terminal when you start a new terminal tab(powershell or ubuntu wsl).

Originally created by @Cppowboy on GitHub (Jun 7, 2020). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none win10 professional, 19041.264 for powershell and ubuntu wsl windows terminal version 1.0.1401.0 no other softwares ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Just open windows terminal, and an error message appears on the top of the terminal. [0x7FFFBB83E044] ANOMALY: use of REX.w is meaningless (default operand size is 64) This problem only happens when using powershell and ubuntu wsl. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The terminal should not show this error message. # Actual behavior <!-- What's actually happening? --> An error message appears on the top of the terminal when you start a new terminal tab(powershell or ubuntu wsl).
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:40:14 +00:00
Author
Owner

@DHowett commented on GitHub (Jun 7, 2020):

My team does not own any code that would print this message. Do you have a hook library on your system that is injecting into these processes?

@DHowett commented on GitHub (Jun 7, 2020): My team does not own any code that would print this message. Do you have a hook library on your system that is injecting into these processes?
Author
Owner

@lovanya commented on GitHub (Sep 21, 2020):

I have this problem on Windows 10 Professional 19041.508 too.
Before I updated to 19041.508, I didn't have this problem.
image

@lovanya commented on GitHub (Sep 21, 2020): I have this problem on Windows 10 Professional 19041.508 too. Before I updated to 19041.508, I didn't have this problem. ![image](https://user-images.githubusercontent.com/16385444/93727815-84ae6a80-fbef-11ea-87a3-f06c445dbbdd.png)
Author
Owner

@DHowett commented on GitHub (Sep 21, 2020):

My team does not own any code that would print this message. Do you have a hook library on your system that is injecting into these processes?

I used an internet search engine to look this up and found that it's coming from TrendMicro OfficeScan.

@DHowett commented on GitHub (Sep 21, 2020): > My team does not own any code that would print this message. Do you have a hook library on your system that is injecting into these processes? I used an internet search engine to look this up and found that it's coming from TrendMicro OfficeScan.
Author
Owner

@Cppowboy commented on GitHub (Sep 21, 2020):

I have this problem on Windows 10 Professional 19041.508 too.
Before I updated to 19041.508, I didn't have this problem.
image

https://blog.davidz.cn/inspur-ip-guard-uninstallation/

I hope this can help.

@Cppowboy commented on GitHub (Sep 21, 2020): > I have this problem on Windows 10 Professional 19041.508 too. > Before I updated to 19041.508, I didn't have this problem. > ![image](https://user-images.githubusercontent.com/16385444/93727815-84ae6a80-fbef-11ea-87a3-f06c445dbbdd.png) https://blog.davidz.cn/inspur-ip-guard-uninstallation/ I hope this can help.
Author
Owner

@lovanya commented on GitHub (Sep 22, 2020):

I have this problem on Windows 10 Professional 19041.508 too.
Before I updated to 19041.508, I didn't have this problem.
image

https://blog.davidz.cn/inspur-ip-guard-uninstallation/

I hope this can help.

I read the blog too, but don't have the permission to uninstall TrendMicro. I tried to turn off it, but this doesn't help.
Before I updated windows, I didn't have this problem.
BTW, this problem will bring problems to git x64. so I switched git to x86, it works normally now.

@lovanya commented on GitHub (Sep 22, 2020): > > I have this problem on Windows 10 Professional 19041.508 too. > > Before I updated to 19041.508, I didn't have this problem. > > ![image](https://user-images.githubusercontent.com/16385444/93727815-84ae6a80-fbef-11ea-87a3-f06c445dbbdd.png) > > https://blog.davidz.cn/inspur-ip-guard-uninstallation/ > > I hope this can help. I read the blog too, but don't have the permission to uninstall TrendMicro. I tried to turn off it, but this doesn't help. Before I updated windows, I didn't have this problem. BTW, this problem will bring problems to git x64. so I switched git to x86, it works normally now.
Author
Owner

@Cppowboy commented on GitHub (Sep 24, 2020):

I have this problem on Windows 10 Professional 19041.508 too.
Before I updated to 19041.508, I didn't have this problem.
image

https://blog.davidz.cn/inspur-ip-guard-uninstallation/
I hope this can help.

I read the blog too, but don't have the permission to uninstall TrendMicro. I tried to turn off it, but this doesn't help.
Before I updated windows, I didn't have this problem.
BTW, this problem will bring problems to git x64. so I switched git to x86, it works normally now.

I deleted all the *.dll files in the system related to the company T.E.C, and the annoying log is gone.

@Cppowboy commented on GitHub (Sep 24, 2020): > > > I have this problem on Windows 10 Professional 19041.508 too. > > > Before I updated to 19041.508, I didn't have this problem. > > > ![image](https://user-images.githubusercontent.com/16385444/93727815-84ae6a80-fbef-11ea-87a3-f06c445dbbdd.png) > > > > > > https://blog.davidz.cn/inspur-ip-guard-uninstallation/ > > I hope this can help. > > I read the blog too, but don't have the permission to uninstall TrendMicro. I tried to turn off it, but this doesn't help. > Before I updated windows, I didn't have this problem. > BTW, this problem will bring problems to git x64. so I switched git to x86, it works normally now. I deleted all the *.dll files in the system related to the company T.E.C, and the annoying log is gone.
Author
Owner

@520jefferson commented on GitHub (Oct 11, 2020):

i have the same problem when i update to 2004

[0x7FF9F0CAE044] ANOMALY: use of REX.w is meaningless (default operand size is 64)
2020/10/11 17:32:18 failed to install wsl2host: service wsl2host already exists

@520jefferson commented on GitHub (Oct 11, 2020): i have the same problem when i update to 2004 [0x7FF9F0CAE044] ANOMALY: use of REX.w is meaningless (default operand size is 64) 2020/10/11 17:32:18 failed to install wsl2host: service wsl2host already exists
Author
Owner

@bluehymn commented on GitHub (Feb 23, 2021):

if your problem coursed by T.E.C ip-guard but you have not permission to remove it, we can modify Regedit to exclude some application monitored by ip-guard.
First, create a key 'hookapi_filterproc_external' in 'HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config' if does not exist, then add 'cmd.exe; wsl.exe, etc.' or '*.exe' to the value;

image

@bluehymn commented on GitHub (Feb 23, 2021): if your problem coursed by T.E.C ip-guard but you have not permission to remove it, we can modify Regedit to exclude some application monitored by ip-guard. First, create a key 'hookapi_filterproc_external' in 'HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config' if does not exist, then add 'cmd.exe; wsl.exe, etc.' or **'*.exe'** to the value; ![image](https://user-images.githubusercontent.com/15361704/108812287-d2d5f880-75e9-11eb-86f7-49cd5459d619.png)
Author
Owner

@frankfancode commented on GitHub (Mar 4, 2021):

https://github.com/microsoft/terminal/issues/6391#issuecomment-783969254
I solve this puzzle use this way

@frankfancode commented on GitHub (Mar 4, 2021): https://github.com/microsoft/terminal/issues/6391#issuecomment-783969254 I solve this puzzle use this way
Author
Owner

@KalleOlaviNiemitalo commented on GitHub (Mar 4, 2021):

I wonder if the REX prefix in question is part of the "rex.w jmp reg" required for a tail call via a function pointer, as documented in RtlVirtualUnwind function (winnt.h) and Quick note about x64 Tail call.

@KalleOlaviNiemitalo commented on GitHub (Mar 4, 2021): I wonder if the REX prefix in question is part of the "rex.w jmp reg" required for a tail call via a function pointer, as documented in [RtlVirtualUnwind function (winnt.h)](https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlvirtualunwind) and [Quick note about x64 Tail call](https://docs.microsoft.com/en-us/archive/blogs/freik/quick-note-about-x64-tail-call).
Author
Owner

@azhi09 commented on GitHub (Mar 26, 2021):

if your problem coursed by T.E.C ip-guard but you have not permission to remove it, we can modify Regedit to exclude some application monitored by ip-guard.
First, create a key 'hookapi_filterproc_external' in 'HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config' if does not exist, then add 'cmd.exe; wsl.exe, etc.' or '*.exe' to the value;

image

I create this new key but auto remove after reboot. @bluehymn

@azhi09 commented on GitHub (Mar 26, 2021): > if your problem coursed by T.E.C ip-guard but you have not permission to remove it, we can modify Regedit to exclude some application monitored by ip-guard. > First, create a key 'hookapi_filterproc_external' in 'HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config' if does not exist, then add 'cmd.exe; wsl.exe, etc.' or **'*.exe'** to the value; > > ![image](https://user-images.githubusercontent.com/15361704/108812287-d2d5f880-75e9-11eb-86f7-49cd5459d619.png) I create this new key but auto remove after reboot. @bluehymn
Author
Owner

@bluehymn commented on GitHub (Mar 26, 2021):

重启以后 ip-guard 应该会恢复注册表,需要再改回来 @azhi09

@bluehymn commented on GitHub (Mar 26, 2021): 重启以后 ip-guard 应该会恢复注册表,需要再改回来 @azhi09
Author
Owner

@azhi09 commented on GitHub (Mar 26, 2021):

重启以后 ip-guard 应该会恢复注册表,需要再改回来 @azhi09

这么说来,如果我改了注册表这个地方后没解决问题,就可能不是 ip-guard 导致的了?

@azhi09 commented on GitHub (Mar 26, 2021): > 重启以后 ip-guard 应该会恢复注册表,需要再改回来 @azhi09 这么说来,如果我改了注册表这个地方后没解决问题,就可能不是 ip-guard 导致的了?
Author
Owner

@KeithChao commented on GitHub (May 26, 2025):

[HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config]
Add "hookapi_disins"="1" to stop it temporary.

Then search "Ocular" with regedit.
You will find two services: winrdgv3.exe and THlpDrv64.sys.
Locate the folder of these two files, rename all those files with same date/time.

They causes my Qt installation and Qt Creator fail.
They looks like Trojan. THlpDrv64.sys will recover winrdgv3.exe installation.

@KeithChao commented on GitHub (May 26, 2025): [HKEY_LOCAL_MACHINE\SOFTWARE\TEC\Ocular.3\agent\config] Add "hookapi_disins"="1" to stop it temporary. Then search "Ocular" with regedit. You will find two services: winrdgv3.exe and THlpDrv64.sys. Locate the folder of these two files, rename all those files with same date/time. They causes my Qt installation and Qt Creator fail. They looks like Trojan. THlpDrv64.sys will recover winrdgv3.exe installation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8876