Login to start a new topic
Answered

Windows 10. Error on start

Hello,

I try to start new Fiddler Everywhere, but after start this app i see this  error:

image


What i tried (Didn't help):


- Re-install
- Clean %appdata% and %localappdata%, and re-install (after restart PC)
- Compatibility mode
- Run as administrator



Best Answer

SOLUTION:

" The problem is that some program has been set to autorun when you run cmd.exe. In my case it was ANSICON that was installed... and then I moved the file without properly uninstalling.

I found a solution in this blog post:

http://carol-nichols.com/2011/03/17/the-system-cannot-find-the-path-specified/

The short version is to find

HKCU\Software\Microsoft\Command Processor\AutoRun

and clear the value. "  © s3v1




Hey Duastronix,


Could you try to run the failing command (see below) in your Windows command prompt and let us know the output?


cmd.exe /c ver



Hi Nick,

Translate: The system cannot find the path specified

image


I found a solution :

https://stackoverflow.com/questions/13316682/windows-cmd-exe-the-system-cannot-find-the-path-specified

 

The problem is that some program has been set to autorun when you run cmd.exe. In my case it was ANSICON that was installed... and then I moved the file without properly uninstalling.

I found a solution in this blog post:

http://carol-nichols.com/2011/03/17/the-system-cannot-find-the-path-specified/

The short version is to find
HKCU\Software\Microsoft\Command Processor\AutoRun
and clear the value


Answer

SOLUTION:

" The problem is that some program has been set to autorun when you run cmd.exe. In my case it was ANSICON that was installed... and then I moved the file without properly uninstalling.

I found a solution in this blog post:

http://carol-nichols.com/2011/03/17/the-system-cannot-find-the-path-specified/

The short version is to find

HKCU\Software\Microsoft\Command Processor\AutoRun

and clear the value. "  © s3v1




1 person likes this

Glad to hear that you were able to resolve your issue! Meanwhile, I wanted to let you know that the team just improved the flow that was causing the problem, and with the next official version of Fiddler Everywhere (1.3), the issue should not be present.

Login to start a new topic