Your Windows Insider Build Ran Into

[Janne Evers]

Thentried to disable the auto windows updates, because I have been shot in the foot more than once by MS pushing an update and breaking something. So I want to pick which updates I installed, like Windows 7 allowed. (Also their penchant for rearranging and hiding options and settings is super annoying - sorry one more rant)

The insider program pushes new stuff down on the user, and will eventually end up mutating your machine into a Windows 11 OS. And as those things are slowly installed, there is no way to get rid of them.

Then, the ISO you downloaded was a Windows Insider ISO in the first place. Windows Insider isn't an "option" while installing from a regular Windows ISO (and it also doesn't matter if your Microsoft Account has joined Insider, since this is a per-computer settings.)

The only polices you currently have configured, is that Windows will notify you of Windows Update downloads and you have configured Automatic Windows Update. If you want to remain on Windows 10 22H2 until it's no longer supported and replaced with a version that is supported, you will want to enable the following group polices:

Worth pointing out, cumulative updates released for Windows 10 22H2 will still be automatically installed, as the group polices you have enabled will not block them from being installed. The polices I have suggested will only allow you to remain on Windows 22H2 until it's no longer supported.

The insider program pushes new stuff down on the user and will eventually end up mutating your machine into a Windows 11 OS. And as those things are slowly installed, there is no way to get rid of them.

This is partially inaccurate. A Windows 10 machine opted into the Insider Preview program absolutely would not result in your machine being upgraded to any Windows 11. At this time, upgrading to Windows 11 is optional, and configuring ProductVersion to "Windows 10" would allow you to remain on Windows 10 until it was no longer supported.

Does anyone know what changes need to be made to make this work? I've solved a few other SSL decryption issues where decrypt-exceptions needed to be added or the CA imported as a trusted CA in the PA, but so far I have been unable to identify what needs to be done for this. I've seen decrypt-error and decrypt-cert-validation coming from this PC around the time of an update check so I know a cert probably needs to be added to the PA but have not yet been able to identify which one.

I temporarily used a decrypt profile that does not verify the CA but that alone did not fix it so we'll likely also need to add some exceptions as well. This was for testing - I am not going to keep a decrypt profile that does not verify CA.

I don't know in great detail about how it works, but I suspect it probably works differently. Normal windows downloads the updates - Insider updates download the build updates to upgrade to the next build. I believe this is more like an image then an update package.

Regardless of what the situation is, @OtakarKlier is right that you can't decrypt this traffic due to how the computer and Microsoft authenticate when pulling the updates from Microsoft's servers. I have multiple users utilizing the Insider program, myself included, and I didn't need to modify anything to get this to function correctly.

I am a little confused. You said you didn't need to modify anything to get it working but you also said you can't decrypt this traffic. Do you mean that you did needed to add to the no-decrypt URLs as per the article for the regular windows updates but after that you did not need to do anything else for windows insider updates?

You are right, we are early in the outgoing on 443 decryption so it is not yet widespread, and also most windows workstations and servers do get central updates. We are on all Windows 10 if it makes a difference, I have read some things saying it might get updates differently or from a different place. I was hoping I would not need to add decrypt exceptions for windows since some exist by default, but if needed I will add exceptions.

What I was trying to say is that I didn't need to modify anything for my users running Insider builds outside of the decryption exceptions that I've already put in place for other users to pull normal Windows Updates. As @OtakarKlier mentioned Updates require a few decryption exceptions for them to work properly.

Make sure to put the files that you will be accessing frequently with Linux applications inside of your Linux root file system to enjoy the file performance benefits. We understand that we have spent the past three years telling you to put your files into your C drive when using WSL 1, but this is not the case in WSL 2. To enjoy the faster file system access in WSL 2 these files must be inside of the Linux root file system. We have also made it possible for Windows apps to access the Linux root file system (like File Explorer! Try running: explorer.exe . in the home directory of your Linux distro and see what happens) which will make this transition significantly easier.

You can expect to get more features, bugfixes, and general updates to WSL 2 inside of the Windows Insiders program. Stay tuned to their experience blog and this blog right here to learn more WSL 2 news.

If you run into any issues, or have feedback for our team please file an issue on our Github at: , and if you have general questions about WSL you can find all of our team members that are on Twitter on this twitter list.

As appealing as this early access is, things can go wrong for members of the Microsoft Windows Insider Program for Business, so it's important to know how to resolve any issues. This is especially true for desktop administrators who may rely on the Windows Insider Program to test Windows OS updates in a lab setting before deploying them across an organization.

The Windows Insider Program is a free program that gives users access to Windows 10 Insider Preview Builds, and it can be an essential program for desktop administrators. The main advantage to enrolling in this program is that it gives IT pros a chance to see what's in store with the next Windows OS build and to learn how to use new features in advance.

Microsoft also benefits from this program because it enables the company to collect feedback on new builds before they are released to the public. This lets Microsoft fix reported bugs or revamp features that prove to be unpopular. While both parties benefit from the Windows Insider Program, some experts believe it has far too great of a role as an unofficial QA program, as customers are reporting issues that Microsoft should be finding on its own.

By far the most common issue that will leave a Windows Insider Program build not working is undiscovered bugs. Microsoft calls the process of discovering these bugs flighting. Although bugs do sometimes make their way into insider preview builds, they don't happen very frequently and are typically minor in scope. Even so, significant bugs may occur. One bug from a few years ago, for example, caused certain application windows to gradually shrink over time. Another well-known bug caused JPEGs to display in a way that made it seem as though the files were corrupt.

First, IT professionals should never install insider preview builds onto any device that is essential for daily business. This rule doesn't just apply to IT's own testing devices. Administrators will also need to avoid the temptation to roll preview builds out to users on physical or virtual desktops.

The second rule is to choose the insider build channel based on how comfortable the admin team is working around potential issues. Microsoft has replaced the fast ring and slow ring it used to offer with the following three channels for Windows Insiders:

If Windows administrators experience issues with Windows Insider builds, the first thing they should do is go to the Feedback Hub built into the Windows 10 system to report problems and suggest features.

If desktop administrators are having a difficult time dealing with bugs, one potential option is to switch to a different channel. For instance, if admins find the Dev Channel to be too buggy, they might opt for the Beta Channel or Release Preview Channel instead.

The Windows Insider Program screen lets desktop admins choose the desired channel or disable the previews altogether. Making such a change may require the administrator to reinstall the Windows platform from scratch, however.

The Windows Insider Program lets you get a peek at what Microsoft is working on and the new features that will be introduced to Windows---both Windows 11 and Windows 10. It isn't for everyone, however, and you definitely should not install an Insider Preview on your work computer.

The Windows Insider Program lets the general public access the changes and new features Microsoft is in the process of developing. The program benefits a lot of people: Microsoft gets a large number of testers to help identify and iron out bugs, and to see if people like changes, developers get to check out changes before they appear in the live version of Windows so they can plan updates for their programs, and enthusiastic early-adopters get to enjoy fighting with pre-release hiccups all day long.

The Windows Insider Program really isn't for everyone. Preview versions of Windows are usually much buggier than officially released versions. That alone makes them ill-suited for day-to-day use, but the fact that features and changes will often come and go makes things even worse.

The Windows Insider Program is divided into three channels, the Developer Channel, the Beta Channel, and the Release Preview Channel. Microsoft uses the term "flight" to describe joining and using Insider builds of Windows. Here is a brief idea of what flighting in each channel might be like:

The Developer channel is the "Bleeding Edge." It is the most frequently updated Insider channel and tends to be the most unstable as a result. New features crop up fairly regularly and disappear just as frequently, while Microsoft tests brand new code and features on a wider scale. You'll need to be comfortable working around bugs, and you should only pick the Dev channel if you're technically inclined, otherwise you're probably in for a miserable time.

3a8082e126