When you add your UserAccountName this is changed to true. If you remove CloudHostExperience you need to set an UserAccountName. I understand what you mean. But also if the person doesn't know how to use it, this one won't even touch it. However if you want to learn, there is quite a bit of material there. I agree with you. About this. EULA would be for those who don't usually install Windows. But anyone looking to customize their own ISO should already have some experience and don't need this screen to appear. Tell me any situation where an ISO for personal use would need the EULA being displayed. These people won't even use the function. Those will likely put their own Autounattend.xml in the DVD folder once they extract an ISO to work with. It's a good idea to put an option to choose to use your own file. Yes, but only because of my mistakes in not predicting some very basic things. I went with the idea: it's working here and it will work for everyone, heheheheeh But deep down I already expected that there would be adjustments to be made. Yes, this is a great idea.
@inTerActionVRI Yeah, I tested it on LTSC with only 1 edition present (IoT). I don't have a serial number, I already have a key activated in motherboard. I will do a test today, hopefully it'll work. Thanks![/QUOTE]
Just put <Key></Key> before </ProductKey> line. you can change "Never" for "Always" or "OnError". It is your choice.
@tempdrive1 @inTerActionVRI I made everything just as you said and it is the same error again and again... I tried different variations multiple times and had to reapply every tweaks on ISO 4 times. Is there any way to just swap the autounattend.xml file and not re-do the ISO over and over again?
Use AnyBurn to edit the .iso, that's how I was doing the quick testing. I have not checked the re-ordering the tags, but the Key tags are within the ProductKey tag as hints for the current generated autounattend. Given that you got the error message again, I believe it must stay there, you cannot move it outside and make it work then. I thought I was not getting the ProductKey prompt because of the stored key in bios (I was running a Win11 base virtual machine setup, which uses UEFI bios emulation or access), but it is not the case.
I'll check AnyBurn, thanks! In my screenshot the <Key> tag is withing the <ProductKey> , right? My Windows key is stored in bios as well, but when installing a stock iso it still gives a product key prompt which I just skip. Then why it does not work? It's really weird.
I guess having the empty <Key> tags there means overriding the stored values from the bios, otherwise it looks fine. Strangely, the prompt just did not appear for me at all, regardless of which non-enforcing option I chose. I'm going to do some more testing, because things might be done a little better (as in in a more consistent way) perhaps. What I wanted to say is that you only need autounattend.xml if you removed CloudHostExperience. If you did not, I recommend not using autounattend.xml and just do a normal installation. You will have to click on things anyway, a couple of more clicks will not make a difference, and I assume you are not doing dozens of deployments (especially with your account name hard-wired) either.
My point is that I want to remove as much UWP crap (even though it's not using resources and appears only one time) as possible. Hence I remove literally everything in the "Remove" section and leave nothing. And also I'm sick of seeing that crappy setup stage with telemetry prompts. I just want to enter my password and go straight to the desktop. I'm doing a deployment for myself only so I need this cleanest ISO which I will use on my PCs.
I believe it does not replace. I think It will just bypass the prompt. If you install the original machine Edition, it should activate automatically. Note: The automatic activation depends on the user not having disabled some features. Or inserted tweaks that prevent this.
It looks like it is getting too complicated to a point where it becomes counterproductive. Based on what you said, if you store settings in the .xml for which the required components have been removed, it adds a lot of confusion and will take quite some time to debug why they don't work, which is hardly suited for beginners. You would need to make it more dynamic: do not include options that will not work (based on the removed components). This would be more effort for you. Alternatively the minimalistic option is still there and you could let "experts" add their required settings, since I imagine they would be adding additional custom entries that would never be there by default, in which case they will have to edit it anyway. I have been fooling around a bit with the data included, and it can be quite unstable depending on what is present, but the errors were showing the ProductKey references regardless. It is still an optional feature, so don't take it as a complaint, since I am not required to use it. All I am saying is that it should be less trouble to use it, doesn't matter who the target audience is.
There is nothing wrong with this. My only point was that a more generic approach brings less trouble along the way.
But I removed all settings for components that can be removed. I didn't understand. What else could be removed? As for the sessions you specified to remove, don't get in the way. For this version I'm just going to add the empty Key tag and remove all the firstlogon configuration sessions. These were tweaks for the w10 control panel. The initial proposal was not just to make a generic autounttend, but a generic autounttend (that works for everyone) and comprehensive (that contemplates the largest possible number of configurations). However, as problems surfaced, it really got bad for users who still don't know how to make the modifications themselves. In W10, in the past, when I removed a component that had some configuration in the autounattend, it went to the log, but it didn't prevent the installation. This was ignored and continued with the installation. Today, anything, stops the intallation progress.
What would the ideal functioning that you are looking for look like? Putting: Code: <ProductKey> <Key></Key> <WillShowUI>OnError</WillShowUI> </ProductKey> Did not work? Attached is your AutoUnattend: I put in the suggested changes and removed the FirstLogon settings as I said.