No Griff, not since Vista, the difference of starting processes as administrative user is that an elevation prompt only asks you to confirm running the process, while a normal user gets a login prompt.īut processes started by an elevated process still don't get elevated themselves and if they have no embedded manifest asking for such elevation will run with normal elevation and not be able to register OCXes, for example. RE: 'Visual FoxPro 9.0 executable file has stopped working' GriffMG (Programmer) 19 Nov 18 17:00 You can run old OCXEes like the MS common controls even in Win10, but you likely need an additional C++ runtime dll even older than that for VFP9, not instead but side by side. OCXes might also need some support libraries, DLLs, if that all isn't known this sounds like the vendor has lost some knowledge they once had, is the original developer still working there? Is this software so old, that it's not maintained anymore?

That's a mechanism which was introduced for compatibility reasons, the official way for an executable to ask for elevation is via an embedded manifest declaring the need for elevation.įrom what year is the setup and what target OS was it created for? You can't expect things to run forever, that also applies to setups themselves.Ĭhecking OCX registration: Hardly doable without knowing the OLE Classnames, but in short, you would need to find registry keys in the HKEY_CLASSES_ROOT branch. You get that elevation dialog, when starting the admin shell, too, but processes you start from it run elevated.Ī setup will ask for elevation itself if its name contains the word setup or update. You might get this going, when you first start cmd.exe in adminstrator elevetion and run the setup from there.Įven if you run an EXE 'as administrator' you get the elevation prompt dialog (or admin login, if your account is no admin). It sounds like secondary setup processes started by the main setup don't run elvated.

Visual foxpro runtime download