>Hi Martina,
>
>Thanks for dropping in :-)
>
>>Please, can you better specify "the issues"?!?
>
>Sorry, at this stage - early in my case - I just cannot. Neither can MS can by the way. Googling "Windows 10 Version 1803 issue" will deliver you a host of "issues" of various natures. From driver failures to antiviruses, specifically avast and other stuff including on what appeared to possibly be VB-classic applications.
>
>I am currently trying to identify the ones that afflicts our application. As I said, the deployed application is virtualized. So the deployed executable (a bundle with a virtual registry) is quite different from the initial VFP executable.

First step for me would be to create a non-Registry-virtualized VM of pre-1803, verify it working pre- and after update.
Then define the reasons for your current solution (IP security, deployment ease...) and prepare a list of alternatives to test :-(