KB926436 MS07-011

After the updates released on 13 Feb 2007 were automatically installed on my
computer, I now receive the following error when trying to run a third-party
application: "The procedure entry point _resetstkoflw could not be located in
the dynamic link library msvcrt.dll"

After carrying out some testing, I have isolated patch KB926436 as the cause
of this problem. After removing this patch (and leaving all of the other
patches that were rleased on 13 Feb installed) the software starts fine.

I'm guessing that this patch replaces msvcrt.dll (though the documentation
only mentions Oledlg.dll being replaced).

There are several knowledge base articles that mention the above error
message and most seem to state that the problems are caused by incorrect
versions of the msvcrt.dll file.

Has anyone else encountered similar problems ?

Darrell,

Not here. Check the msvcrt.dll to see which version it is, please. My
system, XP Pro SP2, shows it at Version 7.0.2600.2180. It was last
modified August 03, 2004, so I think it was installed with SP2.

Not sure what oledlg.dll has to do with this issue as that's the only
file 'updated' from KB926436.

Just what is this 3rd party application and can it run with the above
mentioned msvcrt.dll ?


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Darrell Haslam wrote:

> After the updates released on 13 Feb 2007 were automatically installed on my
> computer, I now receive the following error when trying to run a third-party
> application: "The procedure entry point _resetstkoflw could not be located in
> the dynamic link library msvcrt.dll"
>
> After carrying out some testing, I have isolated patch KB926436 as the cause
> of this problem. After removing this patch (and leaving all of the other
> patches that were rleased on 13 Feb installed) the software starts fine.
>
> I'm guessing that this patch replaces msvcrt.dll (though the documentation
> only mentions Oledlg.dll being replaced).
>
> There are several knowledge base articles that mention the above error
> message and most seem to state that the problems are caused by incorrect
> versions of the msvcrt.dll file.
>
> Has anyone else encountered similar problems ?
>

Sorry, I forgot to make a note of the version number of this file AFTER
KB926436 was installed. I have removed the patch and can confirm that the
present version is the same as the one that you quoted below.

The present version of the oledlg.dll file is 5.1.2600.0 and the file is
dated 23/08/2001.

The software in question is called "WinCats" - it is used to control a HPTLC
scanner (lab equipment). I have contacted the vendor of this software to see
if there is an updated version that addresses the problem.

The software is currently working fine now the patch has been removed.




"MowGreen [MVP]" wrote:

> Darrell,
>
> Not here. Check the msvcrt.dll to see which version it is, please. My
> system, XP Pro SP2, shows it at Version 7.0.2600.2180. It was last
> modified August 03, 2004, so I think it was installed with SP2.
>
> Not sure what oledlg.dll has to do with this issue as that's the only
> file 'updated' from KB926436.
>
> Just what is this 3rd party application and can it run with the above
> mentioned msvcrt.dll ?
>
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> Darrell Haslam wrote:
>
> > After the updates released on 13 Feb 2007 were automatically installed on my
> > computer, I now receive the following error when trying to run a third-party
> > application: "The procedure entry point _resetstkoflw could not be located in
> > the dynamic link library msvcrt.dll"
> >
> > After carrying out some testing, I have isolated patch KB926436 as the cause
> > of this problem. After removing this patch (and leaving all of the other
> > patches that were rleased on 13 Feb installed) the software starts fine.
> >
> > I'm guessing that this patch replaces msvcrt.dll (though the documentation
> > only mentions Oledlg.dll being replaced).
> >
> > There are several knowledge base articles that mention the above error
> > message and most seem to state that the problems are caused by incorrect
> > versions of the msvcrt.dll file.
> >
> > Has anyone else encountered similar problems ?
> >
>

Same problem here (different app, mut same error msg), but doesn't seem to be related to the version of MSVCRT.DLL. It is same 7.0.2600.2180 before and after istalling KB926436.

I could not find a workaround, other than uninstalling the fix..

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Thanks for your insight and suggestion, Darrell, I had similar problems and removing the patch seems to have fixed them. With me, the issue was confused by the fact that I had a recent power supply problem following a power outage (not completely diagnosed yet), and so I am just as happy to find that Microsoft caused this particular problem and not anything internal here. I only don't like the string of warnings I got about other programs possibly not running right if I removed the patch, and so that remains to be seen. I wonder what Microsoft intends to do about this problem they obviously caused, and I hope we don't get this same or similar download slipped to us again with the next batch of updates.

I also have another error that has popped up along this same time, something similar with WKSSFRM.DLL, wonder if this is related and now fixed too.


EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Just for information: I have installed the latest version of WinCATs (the
software used for controlling a HPTLC scanner that had a problem with
MS07-011) and this runs OK with MS07-011 installed. I am not seeing any other
problems.


"Darrell Haslam" wrote:

> After the updates released on 13 Feb 2007 were automatically installed on my
> computer, I now receive the following error when trying to run a third-party
> application: "The procedure entry point _resetstkoflw could not be located in
> the dynamic link library msvcrt.dll"
>
> After carrying out some testing, I have isolated patch KB926436 as the cause
> of this problem. After removing this patch (and leaving all of the other
> patches that were rleased on 13 Feb installed) the software starts fine.
>
> I'm guessing that this patch replaces msvcrt.dll (though the documentation
> only mentions Oledlg.dll being replaced).
>
> There are several knowledge base articles that mention the above error
> message and most seem to state that the problems are caused by incorrect
> versions of the msvcrt.dll file.
>
> Has anyone else encountered similar problems ?
>

[anguilla]

I have found the same issue on an app we repackaged where we put a copy of MSVCRT.DLL into another folder and the app ran that version - not the one in the system32 directory. Updating the version to the current version in the system32 directory fixed the error.

I would suggest scanning the c: drive to see if there are copies of msvcrt.dll in other locations and doing a replace to see if this cures the issue.