[MicroWin] 2026 Update #3837
[MicroWin] 2026 Update #3837
Conversation
This is required to run the diagnostics script, and any script that either we create here, or the user creates later. At least we don't go too wild and use unrestricted... we use something more "safe"
This will increase reliability and performance. Screw the Windows 8 installer, we're back with what was used on Windows 7! Anyway, there are problems with the new installer: 1. It is slow at everything. Some people did benchmarks of both installers. MoSetup lost to Panther (ofc). Source: https://www.reddit.com/r/Windows11/comments/1kmjavl/i_made_a_small_test_comparing_which_one_installs/ 2. It is unreliable. The "Install driver to show hardware" screen that appears in some systems AND in PXE/WDS for Server 2025 is possibly, and simply, due to Setup not being able to find the install image. From BlueBox.log in MoSetup: ... 2025-12-21 10:05:43: Creating path (with ACL): [X:\$WINDOWS.~BT]... 2025-12-21 10:05:43: Creating path: [X:\$WINDOWS.~BT\Sources]... 2025-12-21 10:05:43: CBootScenarioCtrl::PopulateWorkingDir: Install.wim/swm/esd was not found! ... Other contributors in the CTT community stated similar unreliability with borked installs. I'm pretty sure this change will benefit everyone. We'll see how long it lasts before Microsoft f's it up.
Thanks, but revisions don't really matter for now. |
Display appx package dependency full names
Those incompetent developers changed WindowsAppRuntime.CBS to WindowsAppRuntime.CBS.1.6 circa 10.0.26200.7462. No wonder why direct downloads were not causing this issue; they are still based on 10.0.26200.6584. The MCT, on the other hand...
Apparently they fixed that in November. Expanding the amd64_winappsdk-cbs-stable component manifest to a XML file reveals the dark secret:
<registryKeys>
<registryKey keyName="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications\Microsoft.WindowsAppRuntime.CBS.1.6_6000.653.2246.100_x64__8wekyb3d8bbwe">
<registryValue name="Path" valueType="REG_SZ" value="$(runtime.windows)\SystemApps\Microsoft.WindowsAppRuntime.CBS_8wekyb3d8bbwe\AppxManifest.xml" />
<securityDescriptor name="REGKEY_APPXALLUSERSTORE_SDDL" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Config\Microsoft.WindowsAppRuntime.CBS.1.6_8wekyb3d8bbwe">
<registryValue name="SetupPhase" valueType="REG_DWORD" value="0x00000427" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\UpdatedApplications\Microsoft.WindowsAppRuntime.CBS.1.6_8wekyb3d8bbwe" />
</registryKeys>
This is not a problem in .6899 because we don't have amd64_winappsdk-cbs-stable, but a vnext counterpart. But, at this point, why bother checking with that? MCT will not bundle this update with the image!
|
I had to do some additional tests on that file explorer fix. Now it's finally ready for review. |
|
Can you tell me when I can try it out? It's a very inconvenient file explorer. |
I did these steps, but on my Windows 25H2 26200.7462, the File Explorer remained broken. What could I have done wrong?I've tried it a couple of times |
|
Yes. |
Apart from a security improvement (let's remember ILOVEYOU from 2000), it's also a QoL.
Color mode settings are saved per-user, not system-wide. So HKLM\SOFTWARE is not our solution. HKCU is, and is mapped to \Users\Default\NTUSER.DAT
|
@CodingWonders why is microwin using reg.exe? |
|
@GabiNun, the reason why we use reg.exe instead of something more native to PWSH is because they lock the registry hives for longer so, when we unload them, those locks aren't released on time. Thus, unloading fails and we cannot proceed. For these technical questions, I don't recommend you ask here. Otherwise, stuff gets bloated up. |
|
@ChrisTitusTech, DO NOT MERGE WITHOUT TESTING THIS PR FIRST!!! |
ChrisTitusTech
left a comment
ChrisTitusTech
left a comment
There was a problem hiding this comment.
Still too many lines I say we remove all the Reporting tool and Formating the drive. I also think we need to streamline the Microwin to remove the ventoy option and clean up the code.
|
OK. I could put the reporting tool on a separate repo and point people to that script when they run into issues. As per the Rufus-like feature, I'll talk about it with @Real-MullaC. |
This reverts commit 64babfe.
The reporting tool is now hosted on a separate repo. The script itself can be run anywhere, not just in microwin, so...
ChrisTitusTech
left a comment
ChrisTitusTech
left a comment
There was a problem hiding this comment.
- Remove Custom Scratch Dir and oscdimg download option (auto download or install adk)
- Add Description that ISO automatically removes Win11 Requirements
- Remove Copy To Ventoy and code referencing this
- Tweaks section should be removed
- WPBT done by defaults
- Skip Logon Animation
- Remove convert to ESD and Upgrade to Win11 as Win10 is no longer supported
- WPBT done by defaults - Skip Logon Animation - Remove convert to ESD and Upgrade to Win11 as Win10 is no longer supported
Time to get rid of that mess and just use %TEMP%. All of these minor changes were made on a Server 2K8R2 VM.
|
@ChrisTitusTech, I'll test the automatic download of the ADK some more. Don't merge it yet. |
|
@CodingWonders i think you should remove the "get newest iso automaticly" option that uses fido, because must people dont use it and it makes it more streamed line |
5 participants
Type of Change
Description
A batch of changes for the upcoming year.
Testing
Testing was done with Windows 11 25H2 (26200.6584 and .7462)
Issue related to PR
Additional Information
Chris, TEST THESE CHANGES AS WELL!!!
Checklist