This is, with high certainty, the release build number of 24H2. What do you think? Canary marched on, already on 26200.xxxx.
Created a 26100.2 ISO with UUP Dump yesterday, only clicked on "include updates" in the conversion options section. Windows Update did not give any errors and KB5037941 was not offered, everything is running silky smooth right now.
No, plus it's a couple of months old that Update Stack Package, the latest I have installed is 1301.2403.25021.1 currently enrolled in Dev.
was not able to install 26100.1 ISO on my lenovo laptop (failed while installing after like 10%) - trying 26100.2 now. I chose win pro -> "download, add additional editions and convert to ISO" -> chose "include updates (windows converter only)" -> checked "windows IoT Enterprise". Then created the download package and started the "uup_download_windows" file as admin. Then the ISO was being created and I put it on a usb stick using rufus. I checked all the options in rufus except the 4gb ram and TPM bypass. Maybe thats the reason the installation failed? because of the added rufus options?
in other words: don't get a "usb flash drive" (uas m.2 sata adapter + 2242 ssd can still be called a "thumb drive", and in my experience is still vastly superior on all fronts: performance, reliability, price per gb)
I have installed build 26100.2 directly and it does not ask for TPM 2.0 and Secure Boot, only the Micro PopCnt SSE4.2 requirement and my PC does not meet the former but does meet the latter
I get this error.Can someone help me? Code: ============================================================ Running W10UI v10.41 ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: Windows11.0-KB5037941-x64.msu [Combined UUP] ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/2: Windows11.0-KB5036616-x64-NDP481.cab [NetFx] 2/2: Windows10.0-KB5038000-x64_inout.cab [SSU] ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.26040.1000 Processing 1 of 1 - Adding package Package_for_ServicingStack_2~31bf3856ad364e35~amd64~~26100.2.1.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismSSU.log ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.26040.1000 Processing 1 of 1 - Adding package Package_for_DotNetRollup_481~31bf3856ad364e35~amd64~~10.0.9236.4 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismUpdt.log Windows11.0-KB5037941-x64.msu Deployment Image Servicing and Management tool Version: 10.0.26040.1000 Image Version: 10.0.26040.1000 Processing 1 of 1 - Error: 1726 The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\DismLCU.log .NET 3.5 feature: already enabled ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press 9 or q to exit.
looks like your build is 26040, and that update is for 26100 only just update your OS to the 26100 build first
That won't be fixed by trying to integrate an update for an entirely other build, what is the error you get when trying to upgrade to 26100 by ISO?
... as a last resort, you can always try the *Hybrid Method* --Place 26100 .WIMs in the Sources Folder of 26040 and run setup... worked for me a more extreme solution is provided here, but I would at least see what @Enthousiast has to say on the matter, before trying this
i have a strange issue with 26100.2... ever since i upgraded couple of days ago, when i start the computer from Off (a start after a shutdown) it gets stuck at the windows logo, no loading animation and nothing is actually active, i have to manually shut it down again and immediately start (or reset) then it starts and loads windows normally? any idea what that might be?