Hi Steve, I also want to know... There is this application that i have done which is very useful and its currently working in Windows 10.

Here's information on requirements: https://blogs.windows.com/windows-insider/2021/08/...
All in all the compatibility check is more about hardware than anything else. TPM and CPU restrictions will mean less upgrades from Win10 PCs are possible, but not due to software incompatibilities.

I expect no problems, even if all else fails you could create a VM with windows 10 that surely will run on Win11.

The impression I have from the blog post is MS focused on security, things like only supporting hardware with TPM2 and UEFI with secure boot mean MS want to step up from the image of the platform most affected by malware. Take alone Ransomware, I think that's a threat which makes people think of moving to Apple or Linux.

On the other side, when a PC is ready for Win11, which demand on hardware features would affect VFP software? VFP requirements about the Windows system are 32bit platform and NTFS, mainly. GDI+ should still be a supported interface to graphics.

Chriss

Thanks Chriss

The only reason I ask is because other questions have come up on this forum when Windows has been upgraded to new versions in the past and VFP apps have not worked.

I appreciate your post.

Thank you

Steve Williams
VFP9, SP2, Windows 10

I think every Windows version introduced some quirks. Since Vista the UAC first was a problem, but once you know its effect you can deal with it, SMB3 was a problem, so this limits use of DBFs somewhat, but surely not in the local case. And there are some things you can do now.

Then also PACK became a little problematic. I don't remember anything breaking in Win 10.
Gen fields perhaps, but they're not recommended since very long.

DPI problems of FoxyPreviewer are solved, Standard Printer problems are solved, I don't know what you have in mind that was never resolved with a workaround.

Chriss

Chriss/Steve

I believe Windows 11 drops IE so the first thing i'll be testing is the embedded web browser....

n

Appreciate the posts.

Thank you

Steve Williams
VFP9, SP2, Windows 10

Shell.Explorer.2 is located within shdocvw.dll, which is not only used in IE, AFAIK. I once knew what to put into a setup to have the webbrowser control working, but buthere is and it was not just a full IE install.

From what I found about Win11 there is a removal of IE, that's true, Edge also fully integrates the chromium render engine, which in turn could mean shdocvw.dll deprecates, too. That still won't mean it's not working anymore.

I bet Rick Strahl could tell you more about the exact dependencies.

Chriss

i just loaded win 11 and tried a fairly complex app; this has been running since 1992, updated, with customers throughout us. www.intelliform.net (forgive ancient website; you are welcome to download and checkout)
It appears to work fine; it even appears to fix a win 10 gdi+ problem.
al marino