>>>>>>I think I will soon have to replace my Windows 10 desktop, and I'm wondering if it would be better to stay with Win 10 as opposed to getting a Windows 11 pc.
>>>>>>
>>>>>>Do we have any feedback yet on whether our VFP apps will have any difficulty on the Win 11 platform?
>>>>>>
>>>>>>Would like to hear your feedback and opinions on 10 vs 11.
>>>>>>
>>>>>>Thanks,
>>>>>>Rich Murillo
>>>>>>
>>>>>>Has anyone used Thor tools in Windows 11?
>>>>>>Regards Eugen
>>>>>
>>>>>I have used Win11 on three different machines for several months, and I haven't experienced any problems at all. The only problem I have heard of, is VFP9 and general fields, a combination we have warned about since the last millennium, for several reasons.
>>>>>
>>>>>So my conclusion is that there is absolutely no reason to wait with the upgrade.
>>>>
>>>>The primary reason I've not preformed the upgrade to Windows 11 is that my current rig doesn't meet the specs for it (CPU too old, no TPM, etc.). Will be switching over to Windows 11 once I get a new computer. I've no doubt that I'll probably have to put up with some inconveniences (I've heard user toolbars feature was removed in Windows 11).
>>>
>>>If you don't care if M$ will remove the feature on later upgrades. There are 3 (official) reg keys and it installs on anything. I can provide the reg files. (different stuff for vanilla or upgrade.)
>>>I wait some years, as on every M$ product, until it's out of the cradle. I'm not the early bird eaten by the cat. :)
>>
>>I am indeed well aware of the registry patches to bypass some of those requirements, but I'd prefer to avoid using such measures -- there's the chance that such "hacks" will stop working after an update (and chances are, when it does happen, it will happen at the most inopportune time).
>
>Wouldn't call it a hack - MS must have programmed something to use it, so it is a feature. Just tracing the upgrade with Process Monitor, and you see where it fails to find a key isn't hacking. :)
>Anyway, I fully agree with your point to avoid it. Maybe I switch to Win10 next year.

I'm calling those registry keys a "hack" on the grounds that the feature was probably not meant to be used in production -- most likely they exist for testing and diagnostic purposes, as well as kept as a "just in case something doesn't work" scenario when they start rolling out OS features that actually utilizes those CPU, hardare and firmware features that are stated in the Windows 11 requirements (i.e. they can use these to shut off those features if they run into trouble when rolling out those OS changes). Basically the code that checks for these keys will eventually be deactivated or removed once they've finalized the planned OS security features.
I suspect that Microsoft has released some of this information (the registry keys to deactivate the CPU, hardware and firmware check) mostly to appease some of the user base -- especially those that were vocal about the requirements seemingly being "too high".