Windows Caching Programs

Here is a wierd one, just wondering if anyone else has ever come
across this.

I write custome programs for the company I work for. A couple years
ago and again recently, I update a program, released it to production
and one computer still runs the old exe.

Both times my first thought is I released the old exe back into
production thinking i had copied the new one. In both cases I
recompile the exe and make sure I post out the new exe to the server,
but when I fire the new exe from these computers, the computer is
displaying the old exe, even thought the old exe is no longer in the
folder or anywhere to be launched. I reboot the computers and now the
new exe is running.

I am unable to repeat this in any way, like I said, the first time was
a couple years ago and then again recently. This is even on two
different computers.

My only thought is that windows is saving the old exe to some temp
location and just using it not the new one on the server. Any
thoughts from anybody?

Have you checked the registry for bogus entries?

JS

"infobound" <infobound@gmail.com> wrote in message
news:3cf3444b-8a9f-4317-afdc-cd0278f98d9f@u69g2000hse.googlegroups.com...
> Here is a wierd one, just wondering if anyone else has ever come
> across this.
>
> I write custome programs for the company I work for. A couple years
> ago and again recently, I update a program, released it to production
> and one computer still runs the old exe.
>
> Both times my first thought is I released the old exe back into
> production thinking i had copied the new one. In both cases I
> recompile the exe and make sure I post out the new exe to the server,
> but when I fire the new exe from these computers, the computer is
> displaying the old exe, even thought the old exe is no longer in the
> folder or anywhere to be launched. I reboot the computers and now the
> new exe is running.
>
> I am unable to repeat this in any way, like I said, the first time was
> a couple years ago and then again recently. This is even on two
> different computers.
>
> My only thought is that windows is saving the old exe to some temp
> location and just using it not the new one on the server. Any
> thoughts from anybody?

"JS" <@> wrote:

>Have you checked the registry for bogus entries?

Could you enlighten the rest of us how to do that?

On Mar 21, 3:27*pm, "JS" <@> wrote:
> Have you checked the registry for bogus entries?
>
> JS
>
> "infobound" <infobo...@gmail.com> wrote in message
>
> news:3cf3444b-8a9f-4317-afdc-cd0278f98d9f@u69g2000hse.googlegroups.com...
>
>
>
> > Here is a wierd one, just wondering if anyone else has ever come
> > across this.
>
> > I write custome programs for the company I work for. *A couple years
> > ago and again recently, I update a program, released it to production
> > and one computer still runs the old exe.
>
> > Both times my first thought is I released the old exe back into
> > production thinking i had copied the new one. *In both cases I
> > recompile the exe and make sure I post out the new exe to the server,
> > but when I fire the new exe from these computers, the computer is
> > displaying the old exe, even thought the old exe is no longer in the
> > folder or anywhere to be launched. *I reboot the computers and now the
> > new exe is running.
>
> > I am unable to repeat this in any way, like I said, the first time was
> > a couple years ago and then again recently. *This is even on two
> > different computers.
>
> > My only thought is that windows is saving the old exe to some temp
> > location and just using it not the new one on the server. *Any
> > thoughts from anybody?- Hide quoted text -
>
> - Show quoted text -

bogus entries of what? what am I looking for?

Search the registry for all entries that contain the name of your .exe
program.
For each entry found check the path pointing to the .exe,
there should be only one path (directory location found - the correct path)
and no other locations.

JS

"infobound" <infobound@gmail.com> wrote in message
news:4066fddd-1e33-401a-9e4d-0edfdb12182a@a70g2000hsh.googlegroups.com...
On Mar 21, 3:27 pm, "JS" <@> wrote:
> Have you checked the registry for bogus entries?
>
> JS
>
> "infobound" <infobo...@gmail.com> wrote in message
>
> news:3cf3444b-8a9f-4317-afdc-cd0278f98d9f@u69g2000hse.googlegroups.com...
>
>
>
> > Here is a wierd one, just wondering if anyone else has ever come
> > across this.
>
> > I write custome programs for the company I work for. A couple years
> > ago and again recently, I update a program, released it to production
> > and one computer still runs the old exe.
>
> > Both times my first thought is I released the old exe back into
> > production thinking i had copied the new one. In both cases I
> > recompile the exe and make sure I post out the new exe to the server,
> > but when I fire the new exe from these computers, the computer is
> > displaying the old exe, even thought the old exe is no longer in the
> > folder or anywhere to be launched. I reboot the computers and now the
> > new exe is running.
>
> > I am unable to repeat this in any way, like I said, the first time was
> > a couple years ago and then again recently. This is even on two
> > different computers.
>
> > My only thought is that windows is saving the old exe to some temp
> > location and just using it not the new one on the server. Any
> > thoughts from anybody?- Hide quoted text -
>
> - Show quoted text -

bogus entries of what? what am I looking for?

infobound <infobound@gmail.com> wrote:

>On Mar 21, 3:27*pm, "JS" <@> wrote:
>> Have you checked the registry for bogus entries?
>>
>
>bogus entries of what? what am I looking for?

I doubt that "JS" has a clue.

PD43 wrote:
> "JS" <@> wrote:
>
>> Have you checked the registry for bogus entries?
>
> Could you enlighten the rest of us how to do that?

No. (Enlightenment comes from within, grasshopper).

Your are correct, I did not develop the program or the install method, but
since the old version apparently keeps on going then a registry search is a
place to start.

JS

"PD43" <pauld1943@comcast.net> wrote in message
news:gr68u35i4lqtht29c56ojphqfe0lsv51qn@4ax.com...
> infobound <infobound@gmail.com> wrote:
>
>>On Mar 21, 3:27 pm, "JS" <@> wrote:
>>> Have you checked the registry for bogus entries?
>>>
>>
>>bogus entries of what? what am I looking for?
>
> I doubt that "JS" has a clue.

"infobound" <infobound@gmail.com> wrote in message
news:3cf3444b-8a9f-4317-afdc-cd0278f98d9f@u69g2000hse.googlegroups.com...
> Here is a wierd one, just wondering if anyone else has ever come
> across this.
>
> I write custome programs for the company I work for. A couple years
> ago and again recently, I update a program, released it to production
> and one computer still runs the old exe.
>
> Both times my first thought is I released the old exe back into
> production thinking i had copied the new one. In both cases I
> recompile the exe and make sure I post out the new exe to the server,
> but when I fire the new exe from these computers, the computer is
> displaying the old exe, even thought the old exe is no longer in the
> folder or anywhere to be launched. I reboot the computers and now the
> new exe is running.
>
> I am unable to repeat this in any way, like I said, the first time was
> a couple years ago and then again recently. This is even on two
> different computers.
>
> My only thought is that windows is saving the old exe to some temp
> location and just using it not the new one on the server. Any
> thoughts from anybody?

Is there a copy of it in C:\Windows\System32\dllcache?

--
Frank Saunders MS-MVP IE,OE/WM
www.fjsmjs.com
Do not reply with email

I found a couple of interesting things out while running some searches
on the victim machine. I found two different copies of the program in
the "PreFetch" folder. I am researching what this folder does exactly
but it looks like it might have been the culprit. I will post back
what I find, if you have any suggestions I would appretiate them.