That's not nice! (disappearing files)
-
Yesterday, I got called onto a remote with a customer where some really crazy things are happening with one of our executables. Starting this particular exe manually causes a command window to pop up and quickly disappear. The exe is deleted without any warning...just gone! OK, so that's weird, but weirder still is the fact that when the exe is started from our main program, (normal) the main program gets shut down immediately and the main program executable gets deleted! In this case, the called exe is not deleted. :wtf: Some troubleshooting revealed that the same file renamed, would run without a problem. :confused: It looks live an anti-virus problem, but the only a/v showing in the taskbar is windows MSE and I know that I don't have a problem with it. Also, I find it hard to believe that an a/v would rely on filename alone...besides, the same filename with 'test' appended works fine. (btw, the files in question are digitally signed...if that matters) The customer's tech guy has no clue. Once he saw that it would work after renaming, he announced that his job was done. :| To be continued...
"Go forth into the source" - Neal Morse
-
Yesterday, I got called onto a remote with a customer where some really crazy things are happening with one of our executables. Starting this particular exe manually causes a command window to pop up and quickly disappear. The exe is deleted without any warning...just gone! OK, so that's weird, but weirder still is the fact that when the exe is started from our main program, (normal) the main program gets shut down immediately and the main program executable gets deleted! In this case, the called exe is not deleted. :wtf: Some troubleshooting revealed that the same file renamed, would run without a problem. :confused: It looks live an anti-virus problem, but the only a/v showing in the taskbar is windows MSE and I know that I don't have a problem with it. Also, I find it hard to believe that an a/v would rely on filename alone...besides, the same filename with 'test' appended works fine. (btw, the files in question are digitally signed...if that matters) The customer's tech guy has no clue. Once he saw that it would work after renaming, he announced that his job was done. :| To be continued...
"Go forth into the source" - Neal Morse
I've seen Norton do this on my wife's machine. It can really be annoying and difficult to make Norton stop it. I wrote an app for my wife and Norton deletes it every time you start it. And, it's difficult to find the place in Norton to tell Norton that the exe is safe. And, I've even marked it as safe and then Norton decided to delete it again. :sigh: Finally got it. But it's annoying.:mad:
-
Yesterday, I got called onto a remote with a customer where some really crazy things are happening with one of our executables. Starting this particular exe manually causes a command window to pop up and quickly disappear. The exe is deleted without any warning...just gone! OK, so that's weird, but weirder still is the fact that when the exe is started from our main program, (normal) the main program gets shut down immediately and the main program executable gets deleted! In this case, the called exe is not deleted. :wtf: Some troubleshooting revealed that the same file renamed, would run without a problem. :confused: It looks live an anti-virus problem, but the only a/v showing in the taskbar is windows MSE and I know that I don't have a problem with it. Also, I find it hard to believe that an a/v would rely on filename alone...besides, the same filename with 'test' appended works fine. (btw, the files in question are digitally signed...if that matters) The customer's tech guy has no clue. Once he saw that it would work after renaming, he announced that his job was done. :| To be continued...
"Go forth into the source" - Neal Morse
Is it called "Program.exe"? (Because most AV identify this name as a virus attempt and just delete it - it is due to the directory \Program Files\ having a space in the name and some dodgyness in the shell command IIRC)
-
Is it called "Program.exe"? (Because most AV identify this name as a virus attempt and just delete it - it is due to the directory \Program Files\ having a space in the name and some dodgyness in the shell command IIRC)
-
Yesterday, I got called onto a remote with a customer where some really crazy things are happening with one of our executables. Starting this particular exe manually causes a command window to pop up and quickly disappear. The exe is deleted without any warning...just gone! OK, so that's weird, but weirder still is the fact that when the exe is started from our main program, (normal) the main program gets shut down immediately and the main program executable gets deleted! In this case, the called exe is not deleted. :wtf: Some troubleshooting revealed that the same file renamed, would run without a problem. :confused: It looks live an anti-virus problem, but the only a/v showing in the taskbar is windows MSE and I know that I don't have a problem with it. Also, I find it hard to believe that an a/v would rely on filename alone...besides, the same filename with 'test' appended works fine. (btw, the files in question are digitally signed...if that matters) The customer's tech guy has no clue. Once he saw that it would work after renaming, he announced that his job was done. :| To be continued...
"Go forth into the source" - Neal Morse
Maybe it's the new iOS feature that deletes apps when you are running low on space? :-D
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
Maybe it's the new iOS feature that deletes apps when you are running low on space? :-D
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
:laugh: :laugh: :laugh:
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Yesterday, I got called onto a remote with a customer where some really crazy things are happening with one of our executables. Starting this particular exe manually causes a command window to pop up and quickly disappear. The exe is deleted without any warning...just gone! OK, so that's weird, but weirder still is the fact that when the exe is started from our main program, (normal) the main program gets shut down immediately and the main program executable gets deleted! In this case, the called exe is not deleted. :wtf: Some troubleshooting revealed that the same file renamed, would run without a problem. :confused: It looks live an anti-virus problem, but the only a/v showing in the taskbar is windows MSE and I know that I don't have a problem with it. Also, I find it hard to believe that an a/v would rely on filename alone...besides, the same filename with 'test' appended works fine. (btw, the files in question are digitally signed...if that matters) The customer's tech guy has no clue. Once he saw that it would work after renaming, he announced that his job was done. :| To be continued...
"Go forth into the source" - Neal Morse
That doesn't sound familiar, but I've had Stored Procedures disappear from SQL Server before.
