Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

problem with replacing exe-files after run/quit

9 views
Skip to first unread message

henry albrecht

unread,
May 18, 2013, 2:40:41 PM5/18/13
to

Hi.

I observe a strange behaviour here on Win7 32 Bit.

The system behaves normal, except the following: I can copy files over
another files with
the same name. But if i start an exe-file and stop it, then i cannot
replace this file for
a little while. After a moment it works normal. This is new. I never had
this problem before.

And it does not matter, if i let the program for this minute active or
stop it immediately and
wait a moment, before i try to replace it.




Anyone with an idea ?


--


Shadow

unread,
May 18, 2013, 4:42:17 PM5/18/13
to
Maybe you have some kind of malware protection that detects
that the checksum changed and uploads it to a server for scanning ?
[]'s
--
Don't be evil - Google 2004
We have a new policy - Google 2012

henry albrecht

unread,
May 18, 2013, 5:24:34 PM5/18/13
to
Shadow <S...@dow.br> schrieb:


>
> Maybe you have some kind of malware protection that detects
> that the checksum changed and uploads it to a server for scanning ?
> []'s
>

No. The only security-software here is Avast. And when i deinstall
Avast, the problem still remains.



--


FromTheRafters

unread,
May 18, 2013, 6:10:19 PM5/18/13
to
henry albrecht expressed precisely :
All exe files, or only ones that came with the OS?
Are you using the indexing service?


henry albrecht

unread,
May 18, 2013, 6:23:51 PM5/18/13
to
FromTheRafters <err...@nomail.afraid.org> schrieb:



> All exe files, or only ones that came with the OS?

all exe-files. Even a simple compiled hello-world.


> Are you using the indexing service?

No.


--


David H. Lipman

unread,
May 18, 2013, 8:54:26 PM5/18/13
to
From: "henry albrecht" <h...@gmx.de>
The OS keeps the File Handle open. You have to wait until the OS releases
that File Handle.


--
Dave
Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
http://www.pctipp.ch/downloads/dl/35905.asp

FromTheRafters

unread,
May 18, 2013, 8:57:43 PM5/18/13
to
henry albrecht explained :
Grasping at straws, sorry.

Maybe this would help?

http://www.thewindowsclub.com/fix-program-exe-file-stays-open-task-manager-closed


henry albrecht

unread,
May 18, 2013, 9:24:50 PM5/18/13
to
David H. Lipman <DLipman~nospam~@Verizon.Net> schrieb:


> The OS keeps the File Handle open. You have to wait until the OS
> releases that File Handle.

This behaviour is new. And especially while programming it is very
annoying. Because i have to wait before i can continue compiling.


--


Geoff

unread,
May 18, 2013, 9:37:17 PM5/18/13
to
On Sat, 18 May 2013 20:40:41 +0200, henry albrecht <h...@gmx.de> wrote:

>
I suspect this is the OS keeping the file locked for paging.

Windows memory management (MMS) optimizes paging for executables by
loading the executable binary and loading it into memory, if it needs
to discard a page it uses the LRU algorithm to discard executable
pages and rather than write them out to the page file it simply
discards them since reloading it from the executable image is a
convenient source and immutable. (Windows has done it this way since
its first inception.)

In the mean time, the file is locked so that it can't be discarded or
moved out from under the MMS while the program is running. Once a
process exits, the paging system unlocks all open resources and frees
the memory and since the system can't know if you are going to invoke
the program again, it takes its time getting rid of those locks.

A page is 4kB on Windows so even a small executable like
helloworld.exe is subject to this behavior.

henry albrecht

unread,
May 18, 2013, 9:21:48 PM5/18/13
to
FromTheRafters <err...@nomail.afraid.org> schrieb:
Thank you. I will do some experiments with Processexplorer.





--


David H. Lipman

unread,
May 18, 2013, 9:49:41 PM5/18/13
to
From: "henry albrecht" <h...@gmx.de>
No, it really isn't new.

henry albrecht

unread,
May 18, 2013, 9:54:29 PM5/18/13
to
David H. Lipman <DLipman~nospam~@Verizon.Net> schrieb:


>> This behaviour is new. And especially while programming it is very
>> annoying. Because i have to wait before i can continue compiling.
>>
>
> No, it really isn't new.

?

It IS new !

I never had this problem before. I have to wait more than a minute.



--


Geoff

unread,
May 18, 2013, 10:11:26 PM5/18/13
to
That is unusual. What development tools are you using?

Check your SMART status on your hard disk or the event log to see if
something is being detected.

henry albrecht

unread,
May 18, 2013, 10:07:20 PM5/18/13
to
Geoff <ge...@invalid.invalid> schrieb:



> I suspect this is the OS keeping the file locked for paging.

[...]

Thank you for the explanation.

As i said in the other reply, this is new. I dont talk about a few
seconds. I have to wait a minute.

Processexplorer does not show the program, after i started and ended it.
So this problem has to do with the file on the harddisk.



--


henry albrecht

unread,
May 18, 2013, 11:02:39 PM5/18/13
to
Geoff <ge...@invalid.invalid> schrieb:


>
> That is unusual. What development tools are you using?
>

It has nothing to do with this tools. (Watcom and VC++ 2010 Express)



> Check your SMART status on your hard disk or the event log to see if
> something is being detected.
>

SMART is ok. And i cannot find any entry in the event-logs.

I did the test with activated and deactivated write-cache: Same behaviour.

At the moment i have no clue. The most important question is: Is there
any known malware, that could cause this problem?
--


Message has been deleted
0 new messages