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 can tell you I don't need one. I use Start11 to make it Win10 styled and custom game tiles so it's essentially an easier way to launch games than opening Steam but I definitely don't 'need' it and don't use it to launch any applications.
    • I was replying to a user comment that literally started with "So, user error then."
    • Is the Start menu in Windows actually useful? Do we even need it? by Usama Jawad A few days ago, I shared my viewpoint regarding how Microsoft hasn't been able to convince me to migrate to Windows 11 as my sole daily driver, despite the OS being available for roughly four years. Within that piece, I highlighted the fact that even though the Start menu has been completely revamped in the latest version of Windows, it's not something that I use regularly. And that got me thinking: is the Start menu really a crucial piece of my Windows experience? I get it, I know that the Start menu is an iconic Windows element that has existed in the operating system for as long as many of us can remember. And yet, I can't really tell you about the last time I actually used the Start menu. The reason for italicizing the word "used" above is that while the Start menu can be launched when you click on the Windows icon in the Taskbar or the Windows key, I am not counting that as actual usage for the purpose of this piece. This is because I do launch the Start menu several times a day, I actually use it to get to Windows Search. I don't actually use the list of apps, app folders, and recently opened files. I simply tap the Windows key and start typing the search query for the item that I am looking for. For example, if I want to open Power BI, I don't open the Start menu and find the pinned app. I just tap on the Windows key and start typing "Po..." and quickly hit Enter as soon as the right option comes up, which is usually after a couple of keystrokes. Similarly, if I want to open "Gifts.xlsx", I don't open Excel from the Start menu or even peruse my list of recently opened files, I just start typing "Gi..." and press Enter. I feel like this is a much faster experience and you don't need to rely on muscle memory to find the item that you are looking for. And as your list of installed software grows, it only becomes more tedious to keep track of where you pinned an app or the folder that you kept it in. Windows Search gets rid of that problem completely. Additionally, the Start menu detracts me from whatever else I may be focusing on in parallel. If I am using Word and now want to open PowerPoint, I would probably get distracted by the Start menu as I launch it and try to locate the PowerPoint icon. Instead, I can just get to PowerPoint within a few keystrokes without even realizing the effort involved. I'd also like to highlight that I am not inherently against the idea of pinning stuff that you use frequently or recently, but I do think that the Taskbar and Desktop view already solves that problem to some extent. Right now, my Taskbar contains my most used software, while my desktop contains other secondary software and files. I understand that people have their fair share of complaints against Windows Search, but it works quite well for my use-cases. As it currently stands, my actual usage of the Start menu is nil. And although this popular Windows UX is always the subject of debate each time Microsoft makes even a minor change to it, I simply couldn't care less. That said, while the Start menu in its traditional use is dead to me, I am not sure how many people actively utilize this UX. Any evidence I have is purely anecdotal, but I would be very interested in seeing the telemetry that Microsoft tracks regarding its usage. Seeing how frequently Microsoft makes changes to the Start menu and the ensuing debate that follows, I feel like I am in the minority. But I just can't imagine opening the Start menu and then relying on muscle memory or a fixed grid of icons to get to the app I need, when I can do more with a couple of keystrokes.
    • >Fixed: Certain displays might be unexpectedly green. I believe that this fixed the Windows mishandling Dolby Vision issue in RGB 12 bit Full mode we saw recently.
  • Recent Achievements

    • Week One Done
      Wayne Robinson earned a badge
      Week One Done
    • One Month Later
      Karan Khanna earned a badge
      One Month Later
    • Week One Done
      Karan Khanna earned a badge
      Week One Done
    • First Post
      MikeK13 earned a badge
      First Post
    • Week One Done
      OHI Accounting earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      681
    2. 2
      ATLien_0
      277
    3. 3
      Michael Scrip
      208
    4. 4
      +FloatingFatMan
      172
    5. 5
      Steven P.
      142
  • Tell a friend

    Love Neowin? Tell a friend!