i confirm that remplacing appraiserres.dll from windows 10 in this windows 11 22000.5 you can install over 21996.1 without TPM detection
The script for 22000.51 actually downloads 22000.1 then integrates the .51 update, So if running it on Linux doesn't do the update part, you end up with 22000.1.
That's normal. You gotta run the script until there are no downloading errors. MS servers seem to disconnect or refuse connection. When it gets all the files, it will finish.
thank you asus just update there bios for windows 11 support a few boards which is mine Strix X299-E Gaming II
Maybe there is some problem about "it". OS is Win 8.1 Ent N. Code: ============================================================ Running UUP -> ISO v64 ============================================================ ============================================================ Checking UUP Info . . . ============================================================ ============================================================ Configured Options . . . ============================================================ AutoStart 1 AddUpdates 2 NetFx3 ============================================================ Preparing Reference ESDs . . . ============================================================ CAB->ESD: microsoft-onecore-applicationmodel-sync-desktop-fod-package-amd64 CAB->ESD: microsoft-onecore-directx-database-fod-package-amd64 CAB->ESD: microsoft-windows-ethernet-client-intel-e1i68x64-fod-package-amd64 CAB->ESD: microsoft-windows-ethernet-client-intel-e2f68-fod-package-amd64 CAB->ESD: microsoft-windows-ethernet-client-realtek-rtcx21x64-fod-package-amd64 CAB->ESD: microsoft-windows-hello-face-package-amd64 CAB->ESD: microsoft-windows-internetexplorer-optional-package-amd64 CAB->ESD: microsoft-windows-kernel-la57-fod-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-basic-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-handwriting-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-ocr-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-speech-en-us-package-amd64 CAB->ESD: microsoft-windows-languagefeatures-texttospeech-en-us-package-amd64 CAB->ESD: microsoft-windows-mediaplayer-package-amd64 CAB->ESD: microsoft-windows-notepad-system-fod-package-amd64 CAB->ESD: microsoft-windows-powershell-ise-fod-package-amd64 CAB->ESD: microsoft-windows-printing-pmcppc-fod-package-amd64 CAB->ESD: microsoft-windows-printing-wfs-fod-package-amd64 CAB->ESD: microsoft-windows-quickassist-package-amd64 CAB->ESD: microsoft-windows-stepsrecorder-package-amd64 CAB->ESD: microsoft-windows-tabletpcmath-package-amd64 CAB->ESD: microsoft-windows-userexperience-desktop-package-amd64 CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmpciedhd63-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmwl63a-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-broadcom-bcmwl63al-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwbw02-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwew00-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwew01-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwlv64-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwns64-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwsw00-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwtw02-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwtw04-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwtw06-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-intel-netwtw08-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-marvel-mrvlpcie8897-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-qualcomm-athw8x-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-qualcomm-athwnx-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-qualcomm-qcamain10x64-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-ralink-netr28x-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtl8187se-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtl8192se-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtl819xp-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtl85n64-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane01-fod-package-amd64 CAB->ESD: microsoft-windows-wifi-client-realtek-rtwlane13-fod-package-amd64 CAB->ESD: microsoft-windows-wordpad-fod-package-amd64 CAB->ESD: openssh-client-package-amd64 ============================================================ Creating Setup Media Layout . . . ============================================================ ============================================================ Creating install.wim . . . ============================================================ Using LZX compression with 4 threads Archiving file data: 7377 MiB of 7377 MiB (100%) done ============================================================ Adding updates files to ISO distribution . . . ============================================================ SSU: ssu-22000.51-x64.cab UPD: windows10.0-kb5004567-x64.cab LCU: windows10.0-kb5004564-x64.cab 'it' is not recognized as an internal or external command, operable program or batch file. DNF: microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab ============================================================ Updating install.wim registry . . . ============================================================ ============================================================ Creating winre.wim . . . ============================================================ Using LZX compression with 4 threads Archiving file data: 1056 MiB of 1056 MiB (100%) done ============================================================ Adding winre.wim to install.wim . . . ============================================================ ============================================================ Creating boot.wim . . . ============================================================ ============================================================ Adding setup dynamic update(s) . . . ============================================================ windows10.0-kb5004569-x64.cab ============================================================ Creating ISO . . . ============================================================ OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility Copyright (C) Microsoft, 1993-2012. All rights reserved. Licensed only for producing Microsoft authorized content. Scanning source tree (500 files in 45 directories) Scanning source tree complete (938 files in 88 directories) Computing directory information complete Image file is 4523130880 bytes (before optimization) Writing 938 files in 88 directories to 22000.1.210604-1628.CO_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO 100% complete Storage optimization saved 25 files, 87058432 bytes (2% of image) After optimization, image file is 4438198272 bytes Space saved because of embedding, sparseness or optimization = 87058432 Done. Press 0 to exit.
Can I do a clean install if I replaced the appraiserres.dll and made a bootable USB without getting tmp error?
Can someone please help me with simple steps on how to apply the fixes for the iso please ? Does the UUP-> ISO process applies the fixes ?
I've got the same bug on 2 systems that had the same update path. Windows 10 -> Windows 10 insider -> Window 11 leaked -> Windows 11 official. The bug is that Windows update is missing. It does not show up on the system menu and there is no way to launch it. Clicking the button in the upper right of the system menu for Windows Updates does literally nothing.
Uploaded: Win 11 Boot And Upgrade FiX KiT v1.5 https://forums.mydigitallife.net/threads/win-11-boot-and-upgrade-fix-kit-v1-5.83724/
Nope, everything was normal until I upgraded from 11 leaked to 11 official. Both of these systems did have the identical update path though and these are the only 2 I am seeing the issue on so I am sure its related to a very corner case update path. I would be surprised if even .001% of the PCs on 11 went through these 4 build steps without a format. These are just test systems though so its no big deal. If I can't fix them by tonight I'll just format.