>Hi all of you,
>
>We have an application which VFP-based and has started to behaved very badly on machines that run the latest WIN10 version. There is already some public feedback on this 1803 version. But nothing specific to VFP.
>
>The issues we ran into for VFP are quite serious and also difficult to track. Why? because the application that refused to worked is indeed VFP-9 (latest patches of course). But it it fully virtualized (both the vfp and its VFP*.dll and the related dlls and ocx-es).
>
>I have formally verified that the Windows 10 Version 1709 works flawlessly - I understand most corporations would not used the advanced 1803... But well our application has already stopped working properly on home PCs with an "aggressive" auto-update pattern.
>
>We are eagerly looking for solutions. That may possibly include changing a number of stuff, including dropping our shellExecute (SHELL32.dll) commands that display a curious behavior and - more serious issue - changing the virtualizer we use for a new one (replacing molebox virtual box with the enigma virtualizing engine).
>
>Any feedback on issues with this recent windows update is welcome, VFP-related OR NOT!
>
>Daniel

Only issue I have encountered (so far) is folder and files that DO exist not appearing in the Windows File Explorer. And, then VFP will sometimes see them (via FILE()) and other times report that they are there when in fact they are not. My application would write to them with new files, but they would not show up in File Explorer. I had to delete them to recycle bin from within VFP and recreate them to get VFP and Windows back in sync. I am not sure if relates to any of the other issue mentioned, but it took me half the day yesterday to resolve.