soorya wrote:

Hello,

Even i have encountered the same problem
using symantec endpoint protection old version 32 bit with windows 7 enterprise :|

Hello,

What version of Symantec Endpoint Protection are you running?

Make sure you are running the Latest version of either SEP 11.0.7300 OR SEP 12.1.3001

Hope that helps!!

Hello,

Even i have encountered the same problem
using symantec endpoint protection old version 32 bit with windows 7 enterprise :|

On Win7 My issue with the latest version of WinSCP was bad protocol errors, and suggesting I use a different version of bash ??.

I went back to 4.2.5 and could could login to my FC16 server ok, but kept getting no response and will time out in 15sec messages.
On symantec used disable firewall, got further, still hit that message eventually. On symantec disabled antivirus protection, that let me get as far as starting a file copy, back to will timeout in 15sec messages again.

As these posts pointed to a symantec problem I just killed it.

I was using "Norton Internet Security 2011" that came with my Toshiba laptop, I completely uninstalled that and rebooted.

WinSCP, I am still using 4.2.5, now works perfectly. Just copied a 3Gb file uo with no problems.

I also would be interested in a symantec response, it seems to be their problem.
I won't be reinstalling the norton suite.

i also have windows 7 , but winscp downloads fine for me but i get the 15 second timeout message i have ipod touch 4th gen ios 5 can any one help me? email please nellspearsjob@yahoo.com

was this SEP issue ever resolved beyond running an older version of winscp?

hemant shinde wrote:

I had the same problem.
I have windows 7 and SEP intalled.
The winscp_4.2.9 pkg did not work, neither did the binary executable.
Workaround was to use 4.2.4 executable which works perfectly fine.

I had the same problem and I can confirm 4.2.4 work for me as well

I had the same problem.
I have windows 7 and SEP intalled.
The winscp_4.2.9 pkg did not work, neither did the binary executable.
Workaround was to use 4.2.4 executable which works perfectly fine.

i am having a problem on sep v11.06 device control policy, specifically the usb device where sep program cannot block the usb port on windows 7 64bit machines, i spoke with symantec customer care (india) and they admit that sep apps is not supported windows 7 platform YET! which is unacceptable reason! does anyone can help me on this problem? since SYMANTEC itself dont know the answer.

your immediate response is really appreciated

Cheers!
Dante

I am having the same issue with the 0xc0000005 error. I went out to Symantec and contacted them (since I work for Symantec) and downloaded the new patch which brought me up to Sep 11.0.6000.550 and this did not correct my issue. Can you please help?

Pechter wrote:

Symantec has a fix.

<invalid hyperlink removed by admin>

Thanks for sharing this information!

Pechter wrote:

martin wrote:

Can others confirm that 4.2.5 and 4.2.6 are working? I find it confusing as the original post reported that 4.2.4 is not working.

Same problem here with 4.2.7 and 4.2.8.
Just replaced WinXP with Win7 on the office supplied laptop.
Ugh.

Symantec has a fix.

<invalid hyperlink removed by admin>

martin wrote:

Can others confirm that 4.2.5 and 4.2.6 are working? I find it confusing as the original post reported that 4.2.4 is not working.

Same problem here with 4.2.7 and 4.2.8.
Just replaced WinXP with Win7 on the office supplied laptop.
Ugh.

I just tried 4.2.6 and it also gave same error.

Where is the "application and device control" in SEP?

Tried 4.2.5 - it errors also. Will try to download 4.2.6 and try it too.

Can others confirm that 4.2.5 and 4.2.6 are working? I find it confusing as the original post reported that 4.2.4 is not working.

Whatanut wrote:

I have the same setup as the rest of the posters and the same problem. The suggested fix did not work using the latest binaries. I had to go back to version 4.25. 4.26 on doesn't work in this environment.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

I have the same setup as the rest of the posters and the same problem. The suggested fix did not work using the latest binaries. I had to go back to version 4.25. 4.26 on doesn't work in this environment.

Anonymous wrote:

Same issue on my system installing winscp
"The application was unable to start correctly (0xc0000005). Click OK to close the application."
I tried disablng SEP but it still fails.
Any update on this?

Just upgraded my laptop to windows 7 Professional and having the same error

Anonymous wrote:

Same issue on my system installing winscp
"The application was unable to start correctly (0xc0000005). Click OK to close the application."
I tried disablng SEP but it still fails.
Any update on this?

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Same issue on my system installing winscp
"The application was unable to start correctly (0xc0000005). Click OK to close the application."
I tried disablng SEP but it still fails.
Any update on this?

I am having the same problem that others mentioned like application error. Does anyone got winscp working in windows 7?

Disabled "Application and Device Control" component of Symantec SEP, fixed problem.

Thanx!

Josh

Hello,

I'm also concerned by this problem : Windows 7 Enterprise 32 bits, SEP 11.0.5 with latest def files and application and device control launched.
I've got the error message with the install version and the standalone version.

Have anyone found a workaround oh heard news from Symantec ?

Regards

DanB wrote:

I've got the same problem, only the suggested fix is not working. I downloaded the latest version of the portable executable and when I run it, I still receive the same error as mentioned above. I am running Windows 7 and Symantec Endpoint Protection 11.0.5002.333.

I'd appreciate any assistance that can be given.

This is true also for me.
Windows 7, SEP 11.0.5002.333.
It doesn't works with the portable executable.

There are news from Symantec?
Thank you!

I've got the same problem, only the suggested fix is not working. I downloaded the latest version of the portable executable and when I run it, I still receive the same error as mentioned above. I am running Windows 7 and Symantec Endpoint Protection 11.0.5002.333.

I'd appreciate any assistance that can be given.

For whom it may concern:

I can confirm that I had the same problems as described above.
The likely to be "configuration with problems" (Win7 - 32-bit - Endpoint 11.0.5002.333) is also my config.
The solution as suggested by Lee K. (replace executable with the separately downloaded file) seemed to help. Thanks.

justinjpln wrote:

has anyone figured out how to make winscp work on windows7?

The guy before you told you the answer.....

"Download the standalone executable..." - i.e. the one on the download page referred to as the "Portable executable". The file can/should then be renamed from "winSCP4xx.exe" to "WinSCP.exe" so that existing shortcuts work. Just put the renamed version into your "C:\Program Files\WinSCP3" folder and you should be good to go....

Hope that helps,

Mark.

has anyone figured out how to make winscp work on windows7?

LeeK wrote:

Thanks for the information. I just found a way to get it to work, download the stand-alone executable. The standalone runs without any problems, while the installable version does not.
I even copied it into the installed directory and renamed it so my quick launch shortcuts would work.

can u tell me how to do this?

Thanks for the information. I just found a way to get it to work, download the stand-alone executable. The standalone runs without any problems, while the installable version does not.
I even copied it into the installed directory and renamed it so my quick launch shortcuts would work.

Hi Lee,

I meant to post an update to this thread last week...but forgot all about it.

Anyway, we were getting all the details together to log a call with Symantec but couldn't reproduce the problem. We have tried many combinations to recreate the problem but still can't.

All the workstations that were failing are now working (with all the SEP components installed).

We have ruled out many possibilities as to the cause of the problem; such as Microsoft hotfixes/patches and/or configuration.

We have concluded that it must have been one of the Symantec definitions that were causing this problem. Unlikely to be the Anti-Virus definitions...more likely to be the Proactive Threat Protection definitions.

From our testing at the time, disabling all the Symantec options did not solve the problem...only removing the "Application and Device Control" component worked.

Lee

I just rebooted in safe mode to disable SEP and WinSCP ran perfectly fine.
So definitely seems to be related to SEP on my machine too.

leewilmott wrote:

Lee,

- Which version of SEP are you using?
- Are you using a 32-bit operating system?
- Are you using Windows 7?
- Which edition of Windows 7 are you using?

I have version 11.0.5002.333 of SEP.
I'm running Windows 7 Enterprise 32-bit
I was previously running Windows Vista 32-bit with the same SEP and WinSCP worked fine. I have tried uninstalling and reinstalling WinSCP. I have also "disabled" as much of the SEP as I am allowed to and still had the problem (I am unable to stop the Symantec Management Client and Settings Manager).

Lee,

I will let you know what happens.

Out of interetest, is your environment 'exactly' the same as ours?

- Which version of SEP are you using?
- Are you using a 32-bit operating system?
- Are you using Windows 7?
- Which edition of Windows 7 are you using?

The more people that have this 'identical' problem, then it may kick Symantec into doing something about it.

BTW...if anyone else has this problem please can you answer the above questions; so that I can report them to Symantec?

Regards,

Lee

Could you post here if Symantec gets back to you with a solution.
I am in the same situation.

Lee K.

My apologies to Martin for wasting his time...but I think I've found the problem.

I thought I would post my findings just in case others experience the same problem.

Anyway, WinSCP does NOT work if 'all' of the following are true...

- Windows 7 is installed
- The Operating System is 32-bit
- Symantec Endpoint Protection v11.0.5002.333 x86 is installed with "Application and Device Control" component

This problem does not occur when using Symantec Endpoint Protection v11.0.5002.333 "x64".

If the "Application and Device Control" component is NOT installed then WinSCP works perfectly.

Obviously, this problem may occur in earlier (and later) versions of Symantec Endpoint Protection.

We are planning to log a support call with Symantec shortly.

Lee

Martin,

I have sent you an email.

Lee

Many thanks Martin...I have sent you an email.

Lee

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

I have installed Windows 7 Enterprise Edition on a number of our workstations throughout our organisation.

I have installed about 5 64-bit machines and about 2 32-bit machines.

WinSCP (v4.1.9) seems to work perfectly on the 64-bit machines, but doesn't work at all on the 32-bit machines.

The error I am getting (on the 32-bit machines) is...

WinSCP.exe - Application Error
The application was unable to start correctly (0xc0000005). Click OK to close the application.

I receive this error on different occasions...

- at the end of the installation process
- and whenever I click on the WinSCP shortcut.

Has anyone else expereinced this problem?...Alternatively, does anyone else have any idea why I'm getting this error?

Incidentally, I get the same error when I tried WinSCP v4.2.4.

Many thanks,

Lee