Weird message when running anything from CMD prompt - W10 1607


Recommended Posts

Getting this weird error in bold when running any type of cmd prompt application, WIN32 apps work fine and launch with no error. And the cmd prompt app works fine, just shows that error prior.

Doesn't matter if it's a regular cmd prompt or elevated. Could be related to the latest version of OfficeScan

 

Anyone else able to reproduce or have any ideas?

 

C:\WINDOWS\system32>ping 172.16.50.254
[0x7FFE573C70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64)

Pinging 172.16.50.254 with 32 bytes of data:
Reply from 172.16.50.254: bytes=32 time<1ms TTL=64

 

C:\WINDOWS\system32>dism
[0x7FFE573C70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64)

Deployment Image Servicing and Management tool
Version: 10.0.14393.0

 

  On 05/09/2016 at 22:36, Gary7 said:

But you are getting that error no matter what you input right?

Expand  

The error is, [0x7FFE573C70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64), no matter the usage in CMD. The request timing out has nothing to do with his error, you got that error because like OP mentioned the address isnt routeable via public internet. 

 

If I understand correctly, the message shows up but the task in CMD completes just fine? Have you tried running sfc /scannow to see if there are integrity problems? Might need to rebuild the image health and restore via dism

  On 05/09/2016 at 22:40, Circaflex said:

The error is, [0x7FFE573C70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64), no matter the usage in CMD. The request timing out has nothing to do with his error, you got that error because like OP mentioned the address isnt routeable via public internet. 

 

If I understand correctly, the message shows up but the task in CMD completes just fine? Have you tried running sfc /scannow to see if there are integrity problems? Might need to rebuild the image health and restore via dism

Expand  

Exactly, and yes SFC/DISM shows clean. I think I have narrowed it down to TrendMicro OfficeScan. If I open a CMD prompt and type ping, I get it, if I unload OfficeScan, type ping again in the same prompt, it doesn't do it. 

I just pushed out a new update to TrendMicro Office Scan that fixes Firewall/Antivirus Status reporting in W10 Redstone, so this must be causing it.  Hopefully this will help others when they start Googling it. And I guess we will wait for TrendMicro to issue a fix/update.

  On 05/09/2016 at 22:43, xendrome said:

Exactly, and yes SFC/DISM shows clean. I think I have narrowed it down to TrendMicro OfficeScan. If I open a CMD prompt and type ping, I get it, if I unload OfficeScan, type ping again in the same prompt, it doesn't do it. 

I just pushed out a new update to TrendMicro Office Scan that fixes Firewall/Antivirus Status reporting in W10 Redstone, so this must be causing it.  Hopefully this will help others when they start Googling it. And I guess we will wait for TrendMicro to issue a fix/update.

Expand  

Good to know, I will keep an eye on my corporate laptop as we also run trendmicro office scan.

I'm assuming you've installed something and a non-Microsoft component has extended itself into the cmd prompt environment with the REXX interpreter.  What could it be ... dunno.  Third party Anti virus maybe?  Graphics driver?

 

Did you install anything prior to receiving the error?

  On 05/09/2016 at 22:44, Circaflex said:

Good to know, I will keep an eye on my corporate laptop as we also run trendmicro office scan.

Expand  

Yeah this is the update here - http://downloadcenter.trendmicro.com/index.php?clk=tbl&clkval=4554&regs=NABU&lang_loc=1 under the product patch and titled "osce-11-sp1-5010-6125-win-all-criticalpatch.exe
Supports Windows 10 Red Stone 1" released 8-29-2016

 

It def wasn't doing it prior to this.

  • 2 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't get why you care how thin your phone is. Most people slap a giant case on it anyway, so it doesn't mean much in the long run.
    • Yay it finally made it to openSUSE Tumbleweed. Installed on the rest of my PCs/laptops and also working just fine. Was also available before for KDE Neon and Fedora. And I hear Arch also already has it.
    • Yeah basically family safety is tied to your sons acc and your be the manager of it right and can see what they view and can control it. However open edge and you can actually signin to another account while on the windows account you are monitoring and bypass the restrictions. It was different to this on Windows 7 all the stuff was local not in cloud, so didn't matter if you signed out the browser. Chrome can usually still be installed even when blocked, my son used to use other acc in browser and download chrome and then use that freely and install apps and stuff as webapps. None of the tracking stuff would work. I originally ended up blocking downloads via group policy, microsoft store, winget, and loads of other stuff via group policy. But yeah as i said he just got to the point he reset the pc. I stopped that with bios password but he yanked the cmos battery (restores bios and removes password) and reinstalled windows. Other than physically locking the case away and watching him like a hawk its gameover now. It was kinda self inflicted, i did teach my son some cybersecurity stuff and i used to encourage him to try get past my blocking (so he learnt some skills for the future), he can actually lockpick interesting how you bring that up lol (another thing i got him into) I agree with the parenting thing locking stuff down is not the only solution.
    • PC gaming market is being killed by the high prices of GPU's and all these smaller LLM's that people are playing with are causing it. That and greed. AMD is still way behind NVIDIA. The number of games that still does not support FRS3 is bad, FRS4 is a even worse, and on the flip side you have to look far and wide to find a game that does not support DLSS (newer games). Then there is power consumption which AMD always lags behind in.
  • Recent Achievements

    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      659
    2. 2
      ATLien_0
      268
    3. 3
      Michael Scrip
      222
    4. 4
      Steven P.
      167
    5. 5
      +FloatingFatMan
      163
  • Tell a friend

    Love Neowin? Tell a friend!