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

    • Now I may not quite understand this, so someone tell me if I'm off the mark here, but does this mean they'll be potentially removing drivers for now unsupported systems, such as old processors and chipsets? In the past 15 years, Windows has been amazing at just installing on any device, and often having zero, or just a few unessential drivers missing on first install. It would be a shame for that experience to go, though I understand the reasoning, or at least their financial reasoning for it!
    • Microsoft is removing legacy drivers from Windows Update by Usama Jawad Last month, we learned that Microsoft is making major changes to the development of hardware drivers in Windows. This included the retirement of Windows Metadata and Internet Services (WMIS), along with the process for pre-production driver signing. Now, the Redmond tech firm has informed partners that it will be getting rid of old drivers in Windows Update. In what is being described as a "strategic" move to improve the security posture and compatibility of Windows, Microsoft has announced that it will be performing a cleanup of legacy drivers that are still being delivered through Windows Update. Right now, the first phase only targets drivers that already have modern replacements present in Windows Update. As a part of its cleanup process, Microsoft will expire legacy drivers so that it is not offered to any system. This expiration involves removing audience segments in the Hardware Development Center. Partners can still republish a driver that was deemed as legacy by Microsoft, but the firm may require a justification. Once the Redmond tech giant completes its first phase of this cleanup, it will give partners a six-month grace period to share any concerns. However, if no concerns are brought forward, the drivers will be permanently eradicated from Windows Update. Microsoft has emphasized that this will be a regular activity moving forward and while the current phase only targets legacy drivers with newer replacements, the next phases may expand the scope of this cleanup and remove other drivers too. That said, each time the company takes a step in this direction, it will inform partners so that there is transparency between both parties. Microsoft believes that this move will help improve the security posture of Windows and ensure that an optimized set of drivers is offered to end-users. The firm has asked partners to review their drivers in Hardware Program so that there are no unexpected surprises during this cleanup process.
    • No idea, but I had a client the other week that lost the entire drive to it. I suggested relying on the Samsung T7's instead. The Sandisk Extreme's had reliability issues too.
    • I use it every day so personally yes I need it, or rather I want it. I use OpenShell though, not the garbage modern Start Menu. I just counted and at the moment I have a total of 92 program shortcuts organized into six folders almost exactly the way I did back in Windows 95. I can get to any program I want to run very quickly. I never use Search to find or run programs.
    • I do miss the Apps view from Windows 8.1 Update.
  • Recent Achievements

    • One Month Later
      KynanSEIT earned a badge
      One Month Later
    • One Month Later
      gowtham07 earned a badge
      One Month Later
    • Collaborator
      lethalman went up a rank
      Collaborator
    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      682
    2. 2
      ATLien_0
      274
    3. 3
      Michael Scrip
      220
    4. 4
      +FloatingFatMan
      171
    5. 5
      Steven P.
      160
  • Tell a friend

    Love Neowin? Tell a friend!