short answer: Windows 11 was always broken and MSFT quality control is cursed 525 build is almost a released one version, they didn't bother to update it for whatever reason because they are in rush for Windows 12 thing if you download latest refreshed ISO from MVS you shouldn't have any problems with any future retail updates in Windows Update I can download 525 build in MCT and install it in VMware WS without UEFI / TPM with labconfig reg and check WU update if you wish, but I'm sure it will be fine there's just some weird glitch in your case with old WIndows 11 build, that's it
Ok thanks. I'll let it go for now. I'm just antsy because I want to upgrade my main laptop to 11 and I hope to not have to jump through crazy hoops every time I want to update. Moving on - and again this might not be the best thread for it, but it is related to new build releases and I know there are a bunch of knowledgeable people with eyes already here: The last time I spent any significant time on MDL was end of 2019 when I was trying to build some new Windows 10 images. In my research at the time I was trying to build/obtain a clean copy of "Windows 10 Enterprise 1909" and my research let me to 3 methods: 1) Just use the MediaCreationTool with the /MediaEdition Enterprise switch. 2) Used an business edition SVF with the SVFtoSFX_370_x86 tool to apply the converted SVF directly to a consumer ISO. (I can't recall here why this was necessary instead of just obtaining the business ISO itself, but at the time this made sense...I couldn't find a link to a business edition ISO) 3) I downloaded an .ESD from the repo and converted it with the ESD>ISO tool I'm thinking that uupdump.net must have been an option too at that time and I just failed to uncover it? But perhaps it wasn't around yet. In my search on how to get the latest version of Windows 11 Enterprise I came upon the following options: 1) Used the W10UI_10.26 to apply the windows11.0-kb5025305.msu file to the .525 image I got from the MediaCreationTool 2) Just used uupdump.net to download .1635 directly Both of these appear to have created a .1635 build (though I haven't tried to install either yet), although they took an exceptionally long period of time (to be fair I had them running simultaneously. Option 2 took about 1.5 hours and after it ended option 1 took at least another 1-2 hours to complete). I then did another uupdump option because I forgot to include Enterprise and I think it took almost as long as the first. Because I was familiar with the SVF process from 2019 I first tried to look for SVF files for .1635 but as your link above shows the latest SVF is apparently the .1555 release. So how would I have created an SVF for .1635? From what I am seeing so far, it looks like uupdump can always just create an ISO of the latest build and nothing more is needed? Is that correct or am I missing something? What are the other, current methods of building an ISO of the latest build?
Normally there are no hoops for simple updates installation, as said before normal updates do not check for the minimum system requirements, only upgrades and clean installs do..
there's only Patch Tuesday updates on MVS, the latest one is 1555, 1635 is a D Patch (4th tuesday of the month) and it will never be available on MVS you can download that ISO and update it with W10UI, but it's best to just use Windows Update, 1635 update is optional after all UUP dump ISO is a little different: outbox apps will be integrated differently with Stub versions if possible, also app's versions will be the ones in the Bundle also useless SafeOS DU will be integrated in boot.wim and some updates will be missing (latest .Net Framework, DBX and so on) at the end it's fine, it's safe to use UUP dump ISO the other method is to build base .1 build on UUP dump without any updates and integrate all updates with W10UI (or W10MUI if you need to add some other languages) I prefer this one personally I suggest you to do not waste your time and just download latest 1555 ISO from MVS, 1635 update will be optional in WU if you need Enterprise edition then download Business MVS ISO
I agree with them. most problems only arise when people use some third-party tools and optimize their windows. That should be ruled out first.
got en-US 22621.525 ISO in MCT, installed it in VMware WS in BIOS mode without TPM with regs bypass in cmd updated Windows Defender two times, then updated all apps in the Store then run Windows Update - updates list is fine, can't see anything unusual after one reboot it was updated to 22621.1555 build as expected
at least appraiserres.dll is useful for in-place upgrades with incompatible with Server hardware and winsetup.dll is just for clean install, even Diskpart & Apply Image script from your tool can bypass that for obvious reasons ideally we need some appraiserres.dll patch, but who knows if it checks the signature
Thanks for all that info. Is there a good tutorial on the above method I can familiarize myself with. I don't understand UUP dump beyond the very basic download options and would like to get up to speed a bit more on what you can do with it. I should have taken your advice about the VM Ware build earlier. I had a version of Windows 11 (.318 21H2 build) running on a 16.x version of VM. I rarely used it and now that I think about it I recall I did need to modify something either in the .VMX file or perhaps the overall VMWare settings to get it to install (pretty sure it was from some official KB at the time). Anyway, I scrapped trying to install the .525 build and went with the .1555 but I couldn't even get past the first reboot after install without it giving me a blue screen. After trying to ensure that the .VMX file was the same for my other Win 11 install, I decided that I should probably upgrade VMware. I upgraded to 17.x and now it seem all my issues are gone. For full test I installed the .525 and upgraded it to .1555 and then .1635 no issues. Because the TPM module was installed I didn't even need the LabConfig bypasses. I didn't test without the TPM and using bypasses, and not sure I plan to. So, in short this was really a VMWare incompatibility issue likely with anything 22H2+. Really appreciate the help and guidance so far. I've been a member here at MDL for over 10 years, but mostly a lurker. I tend to only visit every few years when I'm trying to upgrade some systems or learn a bit more about the current way that MS is using for upgrades and image distribution. I'm always a bit flustered at how much information is spread out around the forums. It is often hard to find what I need because of the breadth of information, the inability to see what is current, and the competing methodologies that exist even within the same forum areas (and sometimes even threads) about what is the best way to do something. While these issues aren't unique to MDL, they do seem to be a bit more pronounced to someone that isn't on here every week keeping up with it. That being said, whatever issues the forum has on these fronts are combatted by the user base who mostly (like those of you helping me out here on this thread) are knowledgeable, helpful, professional, and friendly. I always have a good educational experience when I visit MDL. So again thanks and congrats to you die-hard MDL folk who keep this place going.
So as a workaround for the crashing bug with the Security Center App if you use Group Policy and choose to hide the Device Security section the service no longer crashes and you can keep TPM enabled you just won't be able to view the Device Security section anymore which is pointless anyways.
I guess the site has been down enough that it was necessary to create a local version? All the data still downloaded via MS, right - so not much quicker? Is this step here the main difference then just simply downloading the .1635 ISO from UUPDUMP? If not, what is/are the differences using this more manual method? So is the idea here kind of like applying an SVF exe file to an ISO? In how it uses one base version and can easily modify it to another? In general how long should this process take (from just the download/processing perspective)? As I mentioned it seemed that this would take upwards of 2 hours on my system. I plan to try this at least once just to be more familiar with the process since it is hard to follow just reading through the steps without actually following along. thanks for the tutorial though!
Yeah, website was offline for quite some time and our previous maintainer decided to create electron app instead, in the end I added Apache web server instead of slow and unstable PHP built-in one Some updates are not available on UUP system and integration routine is different in uup-converter, W10UI has more control and do not integrate useless update in boot.wim SVF is like delta patch, but more flexible, it's for sharing original files if they are mostly identical but little different Virtual editions are creating from any base editions, it applies to Windows editions only Creating base edition is pretty fast, you can keep that base edition and integrate any updates whenever you want Integrating updates with W10UI is slow because DISM is a major bottleneck here Its best to create base edition with only Pro edition if you don't have time, Home editions are useless anyway