Windows 10 22H2 + InControl

  • SpinRite v6.1 is Released!
    Guest:
    That's right. SpinRite v6.1 is finished and released. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

    /Steve.
  • Announcing “BootAble” – GRC's New Boot-Testing Freeware
    Please see the BootAble page at GRC for the whole story.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


CredulousDane

Well-known member
Sep 26, 2020
58
6
Just read that a new version of Windows 10 is out:

So a quick question, is it just to release control (InControl), change the version number og take control again. Is that how it can work? I've only used it to NOT upgrade to Windows 11.

Right now I have version 21H2 - I actually thought that anything version 22 was Windows 11. But I guess not.
 
InControl has two fields, one to control if you use Windows 10 or 11, and one to control which version of the OS to use. Assuming Microsoft keeps using the same controls in the configurations that InControl is editing, it can be used for Windows 12 and beyond!

Since I never deleted my copy, here's an image of the values you can change:
1666276439641.png
 
  • Done!
Reactions: CredulousDane
If you release control and leave it that way, and then check for updates, you'll likely get offered the 22H2 update. It's very small and quick, because it's just flipping an "entitlement" or "activation" bit. You should have the option to install it on your chosen schedule (for the near term) and then once you choose to upgrade, you could take control again and stay where you are at that time.

If you release control, edit the target version number to 22H2 in InControl, and then re-take control immediately, then what will happen is the update will install on its own without ANY interaction or choice from you. In essence InControl tells Windows you MUST get to this version ASAP, and that is what will happen.
 
  • Done!
Reactions: CredulousDane
A bit of a side step on the thread, but what opinions are there on installing Windows 10 optional updates? I usually ignore the optional updates mostly because of Microsoft's track record of breaking things, and currently have "2022-10 Cumulative Update Preview for Windows 10 Version 21H1 for x64-based Systems (KB5018482)" pending install. As a rule I update things soon after release- except those optional Windows ones.
 
Update Preview
A preview update is usually released in one of the last weeks of the month before it will be in the required update the following month. You're just waiting approximately 2 weeks before you will get it anyway. If you don't want to be on the bleeding edge, simply wait and let others find any problems and if there are problems, hopefully MS fixes them over the two weeks before the rollout.
 
  • Like
Reactions: CredulousDane
A preview update is usually released in one of the last weeks of the month before it will be in the required update the following month. You're just waiting approximately 2 weeks before you will get it anyway. If you don't want to be on the bleeding edge, simply wait and let others find any problems and if there are problems, hopefully MS fixes them over the two weeks before the rollout.

Good to know.

About the Windows 10 22H2 update - it doesn't seem to be available in my region/on my systems. I can only get to 21H2.

But security updates should be available on 21H2 until at least October 2023.
 
About the Windows 10 22H2 update - it doesn't seem to be available in my region/on my systems. I can only get to 21H2.
Occasionally, I come across a system acting the same. I'll typically run the Windows Update Assistant and that'll kick it to current.

 
  • Like
Reactions: CredulousDane
Windows 10 22H2 update - it doesn't seem to be available
Well, as the OP, you asked about InControl. If you don't release control, it'll never show up. I assume you've released control and checked for updates? On my test system, this led to the update showing right away. As mentioned before, if you release control, edit the field to 22H2 and then take control, that will definitely speed things along, as it should auto-apply. If that didn't cause it to happen, then there is definitely something weird going on.
 
Occasionally, I come across a system acting the same. I'll typically run the Windows Update Assistant and that'll kick it to current.


I'll try that, thanks!

Well, as the OP, you asked about InControl. If you don't release control, it'll never show up. I assume you've released control and checked for updates? On my test system, this led to the update showing right away. As mentioned before, if you release control, edit the field to 22H2 and then take control, that will definitely speed things along, as it should auto-apply. If that didn't cause it to happen, then there is definitely something weird going on.

This is my InControl settings - so the update should come along...

InControl.png
 
This is my InControl settings - so the update should come along...
Hmm. That is odd... it should have already self applied. Are you sure it didn't when you weren't watching? Maybe run WinVer and see what it reports. Are you running Windows 10 Home or Pro? Maybe that's a difference.
 
Hmm. That is odd... it should have already self applied. Are you sure it didn't when you weren't watching? Maybe run WinVer and see what it reports. Are you running Windows 10 Home or Pro? Maybe that's a difference.

I use WIN+X and then chose System - and just tried starting the Update Assistent, JimWilliamson mentioned, and it suggest starting download etc. :)

System.png
 
Alright, it took quite some time for Update Assistent to help me... was beginning to get worried as I thought 22H2 was just a small update. But...

... it worked out :)

System22H2.png
 
Last edited:
  • Like
Reactions: JimWilliamson
It's really hard to know what Windows Update is doing sometimes. There have been recent updates to Windows Update Servicing, so maybe you needed that first so it could get itself figured out.
 
It's really hard to know what Windows Update is doing sometimes. There have been recent updates to Windows Update Servicing, so maybe you needed that first so it could get itself figured out.

Yeah, it had to forced to update as it didn't happen automatically. And you're right, there are no answers to why with WU. No errors, just no update.
 
Thanks for the info. As a habit when I fire up Windows I go into settings and manually check for updates. Pretty much every day Defender is updated and I like to keep that up to date.
 
  • Like
Reactions: CredulousDane
I have two identical machines bought at the same time. (They may not actually be inwardly identical because you know how manufacturers are with substitutions.) Both are treated identically at all times where Windows Updates are concerned. Both of them were on 21H2. One of them went right to 22H2 and the other had to be forced... There just appears to be no rhyme or reason for any particular delay.
 
  • Like
Reactions: CredulousDane