For the watermark, only these two are required up to build 22572.201 Code: reg add "HKCU\Control Panel\UnsupportedHardwareNotificationCache" /v "SV2" /d 0 /t reg_dword /f For build 22000.588 & higher Code: reg add "HKCU\Control Panel\UnsupportedHardwareNotificationCache" /v "SV1" /d 0 /t reg_dword /f The last two lines are for IP rings tweaks, not related to that not supported h/w watermark
Wrong. It's for the settings app - windows update nag. Even if you stay on 10, it still adds a banner saying your hw does not support 11..
Yep, M$ are getting a little more annoying now. They also plan to splash the NAG MESSAGE in other areas at the top when you open apps, in this case settings. It wont surprise me if it appears in other apps as well.
@Mellipes This gets rid of it! Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "TargetReleaseVersion"=dword:00000001 "TargetReleaseVersionInfo"="21H2"
. Basically the same, just another way of doing it, HOWEVER one difference. Your version number is 21H2 (the current). The other is 25H2. Must be for a reason, pure speculation may suggest this will then work with future versions having a higher number, BUT who knows.
You're referring to this nag? If yes, then I didn't know that one can see it even in W11. Thanks for enlightening me. & About the targeted released difference between @OSMAN (25H1) & @Super Spartan (21H2) [21?? build from the past year? or that should be 22H2?], I'm too curious to know whether OSMAN used 25h1 for the same reason as you said ( "non-existent future build to preemptively make it work on 10, 11 Release") or any other reason. P.S: can anyone tell me, unlike other updates, whether the MSRT.exe is the same for both, W10 & W11 or different?
@SM03, OSMAN obviously quoted my post, and for totally different reasons (he can't upgrade old dev build via WU due to requirements). There's not a matter of right or wrong value here, can set it to an older release if needed. My reasoning was already stated in the post above. If on 10 with unsupported PC, requirements bypassed, offline enrolled, to still have 11 as optional update shown, but without the banner nag (just like on a supported PC). If using 21H2 (current latest 10) instead, then 11 would not show up as optional update. This is the more popular choice atm. As for having a banner in 11, did I not literally said "microsoft has not yet settled on a banner format for the 11 settings"? So, not yet.
Explorer Tabs aparently are back in last Cumulative Dev Update (10.0.22579.100) (KB5013192) with Vivetool
Getting this message while trying to do an in-place upgrade from one of my desktops equipped with 2nd Gen i5 2500K+Intel DH67BL mobo from W10 21H2.1620 to W11 22000.469 (modded W11 ISO to bypass the TPM & CPU system requirement). After accepting installation is in progress as usual What does this mean? If I install W11 in this system then I won't get any LCU or other updates via the windows update channel? Or is that just Micropsft's way to falsely warn & enforce the users to buy new hardware? P.S: I did the same in-place upgrade from W10 to W11 via this same iso in different systems a couple of days ago, one shaving 6th gen CPU & another one is having 7th gen CPU so far, never got this message earlier Update: 1st installation done from 1% to 100% with no issue, then rebooted automatically & in post screen started installing after that, it showed this & finally, after automatically reverting to W10, & logging into W10 again, this message appeared on the desktop Error Message: We couldn't install windows 11 0x8007042B 0x2000D the installation failed in the safe OS phase with an error during migrate_data operation Any suggestion/advice related would be appreciated, thanks.
No, simple hotfixes are installed without checking the system requirements on 22000.xxx (at least for now). The safeos phase errors are are caused by multiple things, incompatible driver, AV, other software, etcetc...
You are using preview build .1620, who knows what is wrong with it or in combination with your system drivers / antivirus / other stuff. Run 21H2 setup first, to repair your install (iso / mct, build .1288 preferable since it's the ESD base, guaranteed stable and upgrade-compatible). Then try the upgrade again. It's the best practice to ensure migration goes smoothly.
@Enthousiast & @BAU I resolved that issue by clean installing W10 first at the host machine Then after the clean installation of W10 21H2.latest, did in-place upgrade via the same (Modded) W11 ISO that was failing earlier So this means LCU will be offered & installed in my 2nd gen system I refereed earlier For testing, I intentionally modded the W11 22000.469 ISO & then clean installed that in that 2nd gen system (after performing W10 to W11 in-place upgrade as described above) The system was offered the latest LCU 22000.556 & able to successfully installed them without any issue. So I guess we're good in 'officially unsupported systems' for getting updates, at least as of now
It was known that Win 11 Boot And Upgrade FiX KiT, or MediaCreationTool.bat, or Rufus or etc. bypassed-media will work for Release builds, and that all updates will be fine via WU. Does not hurt to have a personal confirmation. Dev is more peculiar, and Beta might start to become too, unless Microsoft freezes the build to 22581 and just does minor updates. Any increase in build number, compatibility is rechecked. Minor updates (the .xxx part), compatibility is not rechecked.
Yeh, its an interesting problem M$ has. They tried to limit Windows 11 to compatable machines, but that failed. Now it can be loaded on any machine. Problem is they COULD stop updates on non compatable machines, but that will leave far too many machines likely to be infected or hacked as time goes on. That looks just plain BAD for a product. They could limit features, but again, that just looks bad for the product. Its little wonder they allow Updates, they have to. NAG MESSAGES/WATERMARKS are their only option to date. However would not surprise me if they try and insert a timebomb on unsupported machines.