Hi @MSMG @inTerActionVRI Today I'm here to ask a different question, maybe you guys could help me since this forum a lot users has a little bit more knowledge than me =) I'm trying to integrate Compact + LZX in Windows ISO, and aso make this question to ghost spectre on youtube and he or she (not sure if is she or he) reply saying that use command while windows setup compact /c /s /a /i how can I use this while windows setup? I notice that al the ISOs don't have the $OEM$ folder as well. And in the unattend is not using the Compact OS feature.
make a $OEM$\$$\setup\scripts folder inside your DVD\sources\$OEM$\$$\Setup\Scripts\SetupComplete.cmd folder to make setupcomplete.cmd, open notepad and do this; Code: @echo off COMPACT.EXE /CompactOS:Always cd /d "%WINDIR%\Setup\" if exist "Scripts" rd /s /q "Scripts" >nul exit save this as setupcomplete.cmd inside DVD\sources\$OEM$\$$\Setup\Scripts\ folder, i hope this is what you want, and i could have helped, abs
If I'm making Windows 10 22H2 ISO, should I integrate the newest CU [KB5025221] or there are gonna be problems with removing component with that version and I should use supported version v10.0.1904x.2728 and integrate [KB5023696] update?
For a short answer: No, you should wait to MSMG to complete support the Windows version. For a long answer: No, because when you're integrating updates, the version will not be the same as previous and you can have some issues while editing the ISO. And also, is recommended use only the supported versions since Microsoft are constantly changing a few things in windows, and MSMG Team needs to check if everything is the same or even update the code to support the version. Your options are wait to an update or try to use another program that already support the latest versions of windows, or you can risk and edit the ISO after integrating the update.
I know that when someone says they want functionality, I think of Store fully working. But keeping the Store without the Client Component to keep other Apps working I don't know if it will need the dependencies of the Xbox components. As this needs testing, if you test it and find the ideal combination of components to stick with, please bring us the results. I would like to have, in the way you mentioned, only WinGet working. But, for you to have an idea, Winget requires updating the Store Client even if the DesktopAppInstaller is installed, otherwise it doesn't work. If I'm wrong about that. I believe it could be because it needs the Store to update the DesktopAppInstaller for it to work. One thing is for sure... Winget doesn't work on a clean install of an untouched ISO, before you go into the MS Store and update the MS Store itself and DesktopAppInstaller W10 or AppInstaller to W11. Of course, there is the option to integrate InboxApps, but I always had problems with the store and gave up using it. I believe that perhaps the @MSMG already has more data on this. Let's wait for a positioning from him and other users who have already done this.
@MSMG always said that when the build is not supported, just get, for example, a 19041.1 (this means having a UUPdump iso made without integrating updates there). .1 builds are supported by the MSMG Toolkit. The 19041.1 after integrating the update will become a 19045.xxxx or 22621.1 to 22624.xxxx, if that is your doubt. They're called Fake Builds on the forums, and I don't think this term is official, but it's the nickname it got. This change will only be made if the specific EP update for the 19045 or the 22624 which is still Preview is present. Then... Spoiler: STEPS Step 1: Mount boot and winre, when it comes to integrating updates. Newbies are having boot issues because of this (I won't delve into this content). Step 2: Do the activities you want to perform in the MSMG Toolkit according to the order of the Menus; Step 3: Within the "Integrate Menu", with the updates in the correct folder, integrate the updates after "Integrate Features"; Note 1: the "Integrate Updates" option is out of order because that's how the integration order has to be. That said, "Integrate Custom Features" comes last. Note 2: If the image is not committed, outside the script (users with a little more knowledge can do this), the Toolkit does not lose support for component removal. It just won't remove newly released components. This would require an update from the MSMG. Step 4: Go remove unwanted components. This has always worked for my use. And, I already make something else clear: I don't remove Windows Update, I just disable it. I only do In-Place Update (installation from above). My system is updated once every 1 or 2 months. I make new ISO for this. I consider this a good practice. But many don't, it's up to you to choose. In this way, perhaps the errors that you may encounter are related to the cut in functionality generated by the simple removal of components that are prerequisites for others.
Is there a way to use this in unattend.xml. I've seen this on some NTDEV Win10Lite or Win11Lite. But I don't know if I saw it on video or inside the install.wim of the ISO. Just know one thing, if you have storage space to spare, don't do it. This will increase processing demand and memory consumption.
But that's not what I was talking about... It is during daily use of the system that processing and memory consumption increase. If you want to see the thing take too long, too much to bear waiting... echo To "/F"orce Compression of All Files, regardless of their size or type in the SystemDRIVE with the OS (it will take more time) Code: Start "" /Wait "%SystemROOT%\System32\Compact.exe" /EXE:LZX /F /C "%SystemDRIVE%\*.*" /S /I
I see, I gave you two options there, setupcomplete, which will take a long time, and consume a lot, and the response file, now another option, I don't know.
I don't use Xbox myself, so therefore it will never be integrated into 99% of my builds, however I sometimes get asked for the Xbox functionality. Therefore it isn't too important if it doesn't work, but it would be nice if it did. For me, the functionality of the store in 10 and 11 is far more important, so I can install WhatsApp - this is the only essential app I use, as the standard WhatsApp desktop is now labelled as "Outdated" when I run WhatsApp. I will never sign in to Microsoft's store or accounts to use Windows - personally, I would rather stay with an older and/or enterprise version of Windows without this enforcement. By the way, I hope you weren't offended by what I said in the post that you replied to. I didn't mean to question your ability or answers. Perhaps I am being overcautious and my questions might seem that I doubt what you say.
It's not like that at all, sometimes I use translator, sorry if it seemed somehow if my answer was rude. I really want to know the answer to your own question. I'm also interested in adding minimal functionality, because I really don't have time to test it. If you test and find a combination of components that must be retained, please let us know the results.
Don't worry, I didn't find your reply rude at all. I was just worried that you might have found my reply rude - which I now know you didn't, so everything is all good. If I get proper time, I shall try to test. As I say, the Xbox isn't too important for me.
hey, i cant seem to get the latest version working on my computer. it wont run here. heres the error message 'C:\custom' is not recognized as an internal or external command, operable program or batch file. The system cannot find the file specified.
I need to build an image with the search box on the taskbar that works. Is that the "[32] Search app"? It says it's dependent on WebView2SDK. Which one is that? So MIcroscum has linked the old search to Edge's Webview2? Or is this some "new modern" search app? If so, how do I get back the old search functionality? thanks