Hi Mark, Thanks for you advice. I just hope this issue will eventually go away instead of growing bigger!

David

>Hi David,
>
>If the patch cann't be uninstalled, I don't know what else there is to do. I think this uninstalling of the patch is a temporary solution at best. SP3 (not yet announced) will probably include this patch so at that time you will have the same problem again. Upgrading the W9x machines is the only other solution I know. I still don't know why this problem is only present with VFP8 or 9 exe's, maybe someone from MS can jump in and explain that part (if someone does, pleas let me know)
>
>You're second question is easier: make sure your settings for the automatic update are not set to automatic installation. The automatic update will now detect the patch and will alert you to download/install it. You can now choose not to do that and in that messagebox there is a checkbox for not being bothered by this patch again. After having checked that you can set the automatic updates to autoinstall again, it wil no longer do this patch.
>
>
>>Hi Mark, thanks for your reply. Here are some more questions.
>>
>>1. By deinstalling KB885250 did fix the problem, but some of the computers running XP SP2 saying that KB885250 cannot be uninstalled. Do you know if there is a workaround?
>>
>>2. How can I make sure automatic upadates will not re-install it?
>>
>>Thanks!
>>David
>>
>>
>>>Deinstall Security patch KB885250 from your XP machine and make sure automatic updates doesn't install it again.
>>>
>>>>Hi Sergey,
>>>>
>>>>I have the same problem as Alan and after uninstalling WinXP SP2, still have the same error on launching the foxpro exe. One thing I would like to point out is that this happens to only one of my projects which have this error when I compiled it with Fox8 and Fox9, but when I use Fox8 and Fox9 to compile another project, the resulting exe run fine. Sounds like something project specific...
>>>>
>>>>David
>>>>
>>>>
>>>>>Hi Alan,
>>>>>
>>>>>I've seen a few posts about WinXP SP2 causing such problem. Didn't see any solutions besides uninstalling SP2, though.
>>>>>
>>>>>>
>>>>>>This doesn't seem to be the same problem. In this office we just had nother computer that has been running the program start to get the message. It also is XP Pro. There are other computers that seem to be the same that are still running fine. Just as this one was yesterday. No apparent changes on either computer or on the application. Obviously something changed, but not intentionally.
>>>>>>
>>>>>>No new program installed or intentional program or software changes. Is there some new Microsoft XP update that has been causing problems. I think both of these may be set to get automatic updates to Windows.