disable network so that no updates can be downloaded. If anyone has time it would be interesting to know if you can also repro. This should be very easily reproducible, I can reproduce it 100%. Also I have installed a new VM that isn’t sysprep’d and still have the problem, so I’m convinced it isn’t my installation method. I do now have InControl installed and used that instead of my manual reg editing, and I have the exact same problem. I’m having a problem getting an update to 22h2. Thanks Paul, but that link is for 21h2, not 22h2. So it’s just as if I’d run the reg add commands in a cmd prompt. There aren’t sysprep settings for this - the way I set it up is to add commands that add these values to the registry. I find it hard to believe that the difference here is that I set it up in sysprep. But I am going to try it on actual hardware next, to rule out some oddness of the VM environment. And this led to the Win 11 prompting.Įxperimenting in a VM is super valuable, I can iterate quickly. So I’m a little bit disturbed that I’m getting the Win 11 prompt, after removing TRV and TRVI. If I’m reading correctly, the instructions here say that if you set PV to “Windows 10” you stay on the Win 10 train with all updates, and don’t get asked for Win 11. Can anyone confirm they were able start from 21H2 reg settings, and then somehow able to update to 22H2? It seems my VM has permanently decided it would just be on 21H2. If I remove the entire WindowsUpdate reg key, it’s the same thing.Īlso, again in a VM, if I instead set the TRVI to “22H2”, I still don’t get offered 22H2. Now, in a VM, if I remove the TRV and TRVI values, leaving just ProductVersion (“Windows 10”), I get the Win 11 prompts back (“this hardware does not meet requirements” - my guess is due to lack of TPM), but I do not get offered 22H2. I didn’t do this to necessarily limit to 21H2, but this was how I found I was able to suppress the Windows 11 prompting. I’ve installed a bunch of Win 10 Pro machines and applied the 3 reg keys during installation using sysprep and an unattend.xml file. I cannot seem to get my Win 10 Pro machines to update to 22H2. Note: Steve Gibson has posted up a new GUI program that does similarly: Look for “Select the target Feature Update Version.” Click to enable it and enter Windows 11 in the box, “Which Windows product would you like to receive feature updates for? E.g. If you have group policy on Windows 10 Professional, drill down to Computer Configuration>Administrative Templates>Windows Components>Windows Update>Windows update for business. To use Group policy to move to Windows 11 while on Windows 10: Look for “Select the target Feature Update Version.” Click to enable it and enter Windows 10 in the box, “Which Windows product would you like to receive feature updates for? E.g. To use Group policy on Windows 10 to stay on Windows 10: To use group policy to do the same change (assuming you have Windows 10 professional): To move to a specific version of Windows 11Ĭlick here to install the Registry key to install to move to Windows 11 or stay on 21H2 To reset the values – and blank out the version do the following:Ĭlick here to download the registry key to reset these values (note this version is only supported until December of 2021)Ĭlick here to install the Registry key to install to stay on Windows 10 20H2Ĭlick here to install the Registry key to install to stay on Windows 10 21H1Ĭlick here to install the Registry key to install to stay on Windows 10 21H2Ĭlick here to install the Registry key to install Windows 10 22H2 when it comes out It will keep your system at that specific release until it is end of life on that platform.Ĭlick here to install the Registry key to install to stay on Windows 10 2004 To stay on specific versions of Windows 10 using registry keys:ĭownload any of these links to your computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |