FirstLogonCommands in unattend.xml do not work in Unattended Windows 10 Installation Posted June 15 8 hours ago, Tripredacus said: The unattend if not perfect, there have been times that certain characters in the XML cause a problem with the parser. Take a look at the generated unattend.xml in c:\windows\panther to see if your commands survived parsing. First is to add into your ps command something like Write-EventLog. Because while you can see in the setupact.log in the UnattendGC folder whether or not the command is executed, you cannot see anything further. To see if the command is run at all, just have it write to event log. If that works then you know there is something wrong with your line item. Second is to have a .cmd file in your Commandline and then inside of the .cmd you put in your powershell commands. Or alternatively, you can call powershell and have your commands in a .ps1 file. A thing to remember as well is that the FirstLogonCommands in the xml has two conditions: - it runs under the context of the user account that is the first to log into Windows after OOBE. If this account does not have sufficient priveledges, it may fail because messages will be suppressed or will appear in Session 0. (You can see indications that this happens in Windows on the regular because you can sometimes find an event with text like "tried to show the user a message but failed" or something like that (I can't remember exactly) where a dialog box is generated in a session other than the one the User runs in. - it runs via the 32bit cmd.exe. This is usually only an issue when trying to write to specific parts of the registry, but could potentially cause issues beyond that I am not aware of. Thank your for your thorough answer. I will try your suggestions and see if I can come up with a solution.