View original (French)

Cmd issue!

Doder Posted messages 6 Status Member -  
soulsy Posted messages 2939 Status Member -
Hello everyone. I just opened my command prompt to type the command dir/s, and when I execute the command, I receive this message: the message text associated with number 0x2331 cannot be found in the application file.

It is therefore impossible to execute any command..

I look forward to your solutions with great pleasure :)

3 answers

  1.
    soulsy Posted messages 2939 Status Member 367
     
    Hello,

    Maybe an environment variable has been lost.
    Type the following command: echo %path%

    In output, you should have at least this (there may be more depending on the installed components):
    C:\Windows\system32;C:\Windows;C:\Windows\system32\wbem

    If the command echo %path% doesn't work, we can access the environment variables in the advanced system settings.
    1
    1. Doder Posted messages 6 Status Member
       
      I understand what you're saying :). What should we do next ^^?
      0
    2. soulsy Posted messages 2939 Status Member 367
       
      Which version of Windows is it?
      0
    3. Doder Posted messages 6 Status Member
       
      Windows 7 64-bit
      0
    4. soulsy Posted messages 2939 Status Member 367
       
      Did the echo command work?
      If the command prompt is run as an administrator, is the problem the same?
      0
  2. Doder Posted messages 6 Status Member
     
    The command worked. Yes, even as an administrator there is the issue.
    0
  3. soulsy Posted messages 2939 Status Member 367
     
    You can try to check the integrity of Windows files with the following command as an administrator:
    sfc /verifyonly
    Hopefully, this command works...

    You can also try to create a new text file on the desktop, for example. Inside, put the following 2 lines:
    dir/s
    pause
    Save the file by adding the file extension .cmd (instead of .txt).
    Double-click on the file to see if you still get the same error message.

    I think I've covered all the ideas I had... just one more to finish. If the problem appeared recently, you can try to perform a system restore to a date before the problem.
    0
    1. Doder Posted messages 6 Status Member
       
      For the first technique: "Windows Resource Protection found integrity violations. Details are provided in the CBS.log windir\Logs\CBS\CBS.log. For example C:Windows\Logs\CBS\CBS.logs"

      I tried this command and it tells me: 3The message text associated with the number 0x3 is not found in the message file for system. --'
      0
    2. soulsy Posted messages 2939 Status Member 367
       
      To try to repair, use the following command:
      sfc /scannow
      Always as an administrator.
      0