Windows Insider Windows 10 Iso

0 views
Skip to first unread message

Cecelia Seiner

unread,
Aug 5, 2024, 11:48:02 AM8/5/24
to emopenmat
Itried, to remove it from the "Turn Windows features on or off" windows, with no luck. I tried, to mark it as "off" in the above windows and delete its files manually located in %USERPROFILE%/AppData/Local/lxss, with no luck.

And someone brought up about pagefiles. I have four drives and three of them had pagefiles. I set the pagefile to one drive and set it to be automatically managed. Rebooted the computer. Then I was able to install the BASH prompt for Windows, but instead of using lxrun /install I used


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.


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.


This build, for those with Windows 11 version 24H2, gradually rolls out a wide variety of new features, including pinning apps to the taskbar by dragging and dropping items directly to taskbar from the pinned section in the Start menu, using your mouse to drag files between breadcrumbs in the File Explorer address bar, and directly sharing to specific Microsoft Teams channels and group chats in the Windows share window.


This build introduces the ability to duplicate a tab by right-clicking it in File Explorer. In addition, if you use the netsh wlan show networks command, you should be able to read SSIDs that are UTF-8 encoded. This means that Wi-Fi SSIDs with Unicode characters (like emojis) should be properly displayed in netsh output. This change is just beginning to roll out, so not all Insiders in the Canary Channel will see it right away.


In this build, those in the Dev Channel who have turned the toggle on to receive the latest updates can now pin apps from the Start menu to the taskbar by dragging and dropping items directly to taskbar from the pinned section in the Start menu.


Everyone in the Dev Channel gets a variety of bug fixes, including for one in which some Insiders saw a bug check with error KERNEL_SECURITY_CHECK_FAILURE, and another in which Settings > System > Power & Battery had duplicate text when showing a warning about a slow charger.


In this build for Windows 11 version 23H2, those in the Beta Channel who have turned the toggle on to receive the latest updates can get quick access to files that have been shared with you. If you are signed into Windows with your Microsoft account, you will be able to view files that have been shared with your account, such as email, Teams chat, etc. If you are a commercial customer who is signed in with your Microsoft Entra ID account, you will additionally be able to view files that they have shared with others. You can access this feature by launching File Explorer Home and clicking on the Shared tab item.


In addition, those in the Beta Channel who have turned the toggle on to receive the latest updates can access Studio Effects in Quick Settings from the system tray of the taskbar. Note that this is being gradually rolled out and so is not yet available to everyone.


In this update, you can drag apps from the Pinned section of the menu and pin them to the taskbar, and when you right-click a tab in File Explorer, you have the choice to duplicate it. Note that these features and several others might not be available to all users because they will roll out gradually.


Several bugs have been fixed, including one that caused colors in the Performance section of Task Manager to not display correctly in dark mode, and another in which Settings > System > Power & Battery had duplicate text when showing a warning about a slow charger.


In this build, those in the Beta Channel who have turned the toggle on to receive the latest updates get some minor changes to simplify the Windows share window, including removing the search box. In addition, the preview thumbnail title in the taskbar, Alt + Tab, and Task View for File Explorer windows will now indicate if that window includes multiple tabs.


Those in the Beta Channel who have turned the toggle on to receive the latest updates get a number of bug fixes, including some addressing accessibility issues where File Explorer, Common File Dialog (CFD), and Browse/Shortcuts Dialogs did not respond appropriately to your text size / scaling preferences.


This build includes a small set of general enhancements and fixes that improve the overall experience of running Windows, according to Microsoft. In addition, a new Game Pass recommendation card on the Settings homepage will be shown to you if you actively play games on your PC.


In this build for Windows 11, version 23H2, those in the Beta Channel who have turned the toggle on to receive the latest updates can use their mobile device directly from the Start menu. See this blog post for details.


Those who have turned the toggle on to receive the latest updates get one bug fix, which addresses contrast issues of certain elements in File Explorer (left navigation pane, view pane/folder view, status bar buttons on the bottom right) in light, dark, and high contrast themes.

3a8082e126
Reply all
Reply to author
Forward
0 new messages