Solved CMD prompt resulted in (0xc0000142)

[CB]

Anyone can show me why if I tried running command prompt resulted in this?

So then any program that need to run background command will fail at it.
Just happened few days ago, not any event that I can suspect as the cause of it. Just recently changing the windows features, activating the netframework 3.5 and run update as requested.
No way that I can run command sfc /scannow

Help is appreciated

 

[GMan]

Seems like intention behavior caused by malware to me, so that you can't use it to fix anything. Perhaps not.

You can try seeing if command prompt runs in safe mode then try the sfc command.

I would also do a good scan with Malwarebytes to see if anything is up.

 

[CB]

Thanks Gman

Yes, no way to run command prompt to check on file system integrity, not even in safe mode.
I just realize that I haven't installed Malwarebytes (just lately recalled it installed only on my seven system )
I will try to install it and hope it will help.

Thanks.
Kevin

 

[CB]

Installed Malwarebytes. Run full scan, said nothing is suspicious.

Could be something else.

 

[GMan]

Press Windows key+R on the keyboard. Then type the sfc /scannow command in there.

Or use PowerShell.

Must be ran with Administrator privileges. Try safe mode or built in Administrator account.

------

Or extract my shortcut then right click on it and choose Run as administrator.

 

[CB]

GMan.

I do have the same shortcut of the command in my desktop. It won't run though with elevated privilege. It returned that screenshot posted.

Been thinking about refresh it to original state, but I prefer to save it as the last resort.

Thanks
Kevin.

 

[GMan]

Did you try running the sfc command from administrative PowerShell?

 

[Atin90]

Since I do not know what this CMD prompt shortcut points to and/or what the, what I assume is a BAT file, does but one thing I have found is that there is a bug in Windows 8 in regards to running BAT files. If the BAT file is executed in normal fashion, with out Administrators privileges, it runs as intended but it may not execute or access locked files or locked folders and a need for Administrators privileges exists. Running the same BAT file as Administrator runs in to this error that I found.

The error is that the default folder while executing the BAT file should be where ever the BAT file is. So if your BAT file is located let's say on d:\test and you execute this BAT file then a simple command like DIR (directory listing of current folder) should list the directory of D:\test. But if you execute the same BAT file with Administrators privilege, the same DIR command will give you listing of folder where the CMD.EXE resides, not where the BAT file is located, which would normally be c:\Windows\system32.

Therefore, any command in your BAT file that assumes that the current directory is where the BAT file is will now be incorrect and errors will happen.


Here is a simple example:

Create a BAT file with only one CMD command, followed by Pause command (so you could see the result). Execute with and then with out the Administrators privilege and you will see the problem.


Dir
Pause




------

Atin90

 

[CB]

GMan

From what I noticed that any command that utilize the command console won't run. Powershell also fail though I try created xx.lnk or xx.bat and have it run in elevated mode. I'm not familiar with scripting or C#, I tried to run Powershell_ise and run powershell from within also didn't give chance get in, and return the same error.

Atin.
Thanks for the response.
So far that I know windows has included all folders of executable system files in its environment in which I can just type it somewhere then let the system locate it and execute it.
The problem is something is blocking me to get to it. It could probable be undetected adware or malware, or something else beyond my knowledge. I'm not seriously bothered, but my curiosity drives to seek answer.

Kevin

 

[GMan]

Either malicious malware or something innocuous that simply messed up how Windows works.

You could try merging the .exe registry file from Brink's tutorial here. Before doing that though, in case 8 is different than 7 (doubtful), I would backup your current key(s) that this writes to:

Default File Type Associations - Restore - Windows 7 Forums

(You can view the reg file in notepad to see what keys are involved.)


If you have a restore point from before this happened, maybe you can restore to that, if needed.

 

[CB]

I read it. but I don't assume it has something to do with default file type association, besides normally lost association will prompt me to find one or set the new default.

I think I will get back to this thread tomorrow. Now it's midnight here. About time to take some rest.

thanks for all response given.

Kevin

 

[Calico]

If you're unable to run sfc from normal/safe mode, try booting from the Windows 8 DVD, then run the repair option followed by:

Troubleshoot/Advanced Options/Command Prompt

Then enter:

sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

Replace c: with your system partition.

 

[CB]

Calico.
Thanks for the reply.
From that environment I can run any command prompt.
I changed the windir and winboot to Q:. Sfc run smoothly and said no integrity problem found.

When I rebooted it and got back to windows environment. The problem persists. Any attempt to enter command line will fail as I explained at the first post. This a bit weird to me.

Kevin

Edit
Hate to do this, but I eventually run refresh windows, have it back to original state. Thing are running expectedly.
Marked the thread solved but note this as not essentially resolved.

Thanks everyone for the assistance.

 

[Calico]

Sorry you had to Refresh in the end but it was probably the best option. The (0xc0000142) error code has been around for a long time and usually indicates an initialisation failure for one or more dlls. You may have been able to 'fix' the problem by creating a new profile, but that's essentially what you've done with the refresh...

 

[CB]

Well. I didn't create new profile. But did enable Administrator account through computer management and log on to it. But still, windows prevented me from running any command line. It returned me the same error. So then I concluded there were things not related to system files integrity, but something as undetected malware or else that change the setting which returned me that persistent error in reaching command line. But I found most program were running uneventfully.

Kevin.

 

[code91]

((