mirror of
https://github.com/ChrisTitusTech/winutil
synced 2026-02-04 15:00:09 +00:00
aa719b49bf
* New reporting tool * Why did we EVER need to load the component store? * Up the execution policy for default PWSH sessions 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" * Force Panther Setup instead of MoSetup 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. * Improve reporting tool Display appx package dependency full names * Rework ADK detection * Add revamped detection for ISO creation * File Explorer ain't broken anymore on 26200.7462 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... * Patch maximum version boundary 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! * Default to showing file extensions Apart from a security improvement (let's remember ILOVEYOU from 2000), it's also a QoL. * Fix key for color modes 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 * Move color mode from offline servicing to firstrun * Drop build number by 100 * Update Invoke-Microwin.ps1 (#15) * Revert "Update Invoke-Microwin.ps1 (#15)" This reverts commit88f8a3031b. * Keep trying to commit and unmount images * Consistent REG ADD /F /V... Some issues happen with REG and strings if you put /f at the end... move it to the beginning, where it doesn't conflict with anything. * Rework stub path reg value set This works on both Windows 11 and Windows 10. It didn't work on Win10 before; it should work now * Remove copy link step We no longer do this * Move Copy-Files to microwin folder Only microwin calls this function; it's better if we place this script in that folder * Add Create Bootable USB (#18) * Add Create Bootable USB * Apply suggestion from @CodingWonders --------- Co-authored-by: CodingWonders <101426328+CodingWonders@users.noreply.github.com> * Download ADK to get oscdimg if not to download on GitHub If we don't download OSCDIMG from GitHub, because we now use ADK kits roots detection to get installed copies of the ADK and oscdimg, we just download the Deployment Tools. This is only 100 MB once fully installed, and removes the need to install Chocolatey. One caveat is that, on 64-bit systems, the script will output "Could not find ADK" once. This is normal as it does checks on both regular SOFTWARE and WOW6432Node, and it's able to pick it on the latter. If it isn't found anywhere, that message will appear twice. * Make indentation more consitent in bootable USB func. * Initialize petoolspath variable * Remove temporary adksetup on completion * Fix whitespace * Remove unnecessary comments and revamp admin check * Revert "Add Create Bootable USB (#18)" This reverts commit64babfe986. * Remove reporting tool creation The reporting tool is now hosted on a separate repo. The script itself can be run anywhere, not just in microwin, so... * Some formatting change here * Remove copy to ventoy option * Fix some more indents * Add Description that ISO automatically removes Win11 Requirements * Additional things - WPBT done by defaults - Skip Logon Animation - Remove convert to ESD and Upgrade to Win11 as Win10 is no longer supported * First attempt at OSCDIMG autodownload * No more custom ScratchPaths! Time to get rid of that mess and just use %TEMP%. All of these minor changes were made on a Server 2K8R2 VM. * Redetect ADK/OSCDIMG after autodownload * Leave ADK reg query error to debug only --------- Co-authored-by: Real-MullaC <callumjanes2007new+github@gmail.com>
18 KiB
18 KiB