New
#41
The very easy move of deleting just the appraiserres.dll file from the boot files installed on C: early in the installation is very well known.
The very easy move of deleting just the appraiserres.dll file from the boot files installed on C: early in the installation is very well known.
I got it - as I am sure others did, but although I do not agree with all Microsoft polices I fail to see the intrusiveness of this "upgrade notice" in settings.People just don't get it. We do not want to upgrade.
It is not as though it is a continual pop-up, and IMHO one cannot in the least blame Microsoft for their policy in including this on systems, that Microsoft are offering a FREE upgrade - from 10 to 11.
I believe it will in due time disappear and I cannot see the large problem that is purported to be.
There was one laptop that had a compatibility hold on it because of those Conexant audio drivers. Well, they never got an update (surprise) but that laptop's compatibility hold was eventually lifted despite this, and the upgrade was forcefully started. I monitored the progress myself, and the upgrade stalled at the same percentage every time until I removed the offending driver before re-attempting upgrade. Had I not done this, it would still be in a performance consuming constant update->stall->restart->update->stall limbo.
So the lesson is this: If you don't want the upgrade, you have to take extra precautions. Trusting that Microsoft will know best or respect your wishes is never a good idea.
After much searching I have found a way to remove this red Windows 11 incompatibility warning message.
Open Regedit and go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators
Delete the key CO21H2
What I haven't found (yet) is a way to stop it returning when Windows Update decides to check for W11 compatibility again. One possible way may be to set the target release version, either using group policy or regedit.
How to Specify Target Feature Update Version in Windows 10
In addition to the two values TargetReleaseVersion and TargetReleaseVersionInfo that are given in Option Three of @Brink's tutorial, there appears to be another String value named ProductVersion that can usefully be set to the text "Windows 10".
Anyway, for now my incompatible machine's Windows Update has returned to looking like this. Let's see how long it stays that way......
EDIT: The policy to set the Target Feature Update Version is ignored by the Home edition of Windows, so you can only permanently prevent the compatibility warning returning for machines running Pro.
Last edited by Bree; 20 Nov 2021 at 09:49. Reason: Home vs Pro
Hi,
I never manually check for updates and the update system is disabled using updates minitool
This is how I avoid silly ms massages besides I already have 11 on four unqualified systems leapfrogging over all the silly restrictions during an inplace upgrade.
But as always @Bree and maybe even @Brink is on the case working on a reg magic file