Easily manage Windows 10 and 11
out-of-control updating and upgrading.

What it does . . .
The first thing InControl does upon starting is verify that it's running on a non-Enterprise and non-Server edition of at least Windows 10. Earlier versions of windows lack the support for most of the Registry keys that InControl uses and Enterprise and Server editions are never upgraded automatically by the Windows Update facility.

What six Registry keys? . . .
InControl creates and manages the following six Registry keys. As noted above, they must all exist and have the proper values for InControl to indicate that the user is in control:

When the user clicks “Release Control” all six of these optional key names & values are deleted from the Registry and Windows Update will return to its normal operation.

InControl Version History
Q:Does InControl automatically update itself?
A:No. GRC's code typically settles down very quickly and then goes for years without problems or bugs. We expect InControl to only need updating when Microsoft introduces Windows 12 (and perhaps not even then). Since major Windows versions tend to occur only every six years or so, we decided to keep the app as clean and simple as possible.

The other consideration is that anti-malware scanners tend to generate many more false-positive hits when they see networking code in an app. Our DNS Benchmark and SQRL both already had networking, so adding version checking made sense there. But since InControl doesn't need any networking, it made more sense not to add it just for “probably never needed” version checking.
Q:Can InControl regress Windows to a previous version? Like move back to Windoss 10 from 11?
A:Unfortunately, No. InControl only controls Windows Update, and Windows Update is not able to move backward (even when going forward seems like going backwards!)
Q:Can InControl be used to hold only the current major release version – like Windows 10 – but still allow the annual feature releases to happen?
A:We don't think so. This is all frustratingly undocumented by Microsoft. But it appears that the reason Microsoft added support for a “Version” in the Registry is because both Win10 and Win11 call their most recent feature releases “21H2.” So it was necessary to be able to specify which 21H2 the user was refering to. It seems unlikely that leaving the “TargetReleaseVersion” unspecified would cause Windows Update to honor the “ProductVersion” by itself.

Jump to top of page
Gibson Research Corporation is owned and operated by Steve Gibson.  The contents
of this page are Copyright (c) 2022 Gibson Research Corporation. SpinRite, ShieldsUP,
NanoProbe, and any other indicated trademarks are registered trademarks of Gibson
Research Corporation, Laguna Hills, CA, USA. GRC's web and customer privacy policy.
Jump to top of page

Last Edit: Feb 17, 2022 at 09:42 (97.03 days ago)Viewed 13 times per day