You're using two different structures for running a command. You're using "RunSynchronousCommand" and "SynchronousCommand".

First, you should be using Windows System Image Manager to create unattend files. This will insure they are formatted correctly.

The problem here is that you are using the "RunSynchronousCommand" block which works during the specialize pass, or auditUser pass. It is supposed to be contained within a "RunSynchronous" block.

You've put in a "SynchronousCommand" block which runs during the oobeSystem pass after the first user logs on to the system. But, you've put it in the specialize pass.

The RunSynchronousCommand block has to be contained in a "RunSynchronous" block and located in the Specialize or auditUser pass. The SynchronousCommand block can only be located in the oobeSystem pass. For an explanation of Windows Setup Configuration Passes and when they run see here: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-configuration-passes

You need to make a decision when you want these commands to run and then properly format the unattend file by placing the commands in the proper locations. Again, Windows System Image Manager would not have validated this file.

Most likely, you want to use only "SynchronousCommand" during the oobeSystem pass. However, be aware, that Windows 10 does not run these commands synchronously. Windows will NOT wait for these commands to finish before logging the user on, contrary to what Microsoft has specified in documentation. This is new for Windows 10.

2018-07-23 10:38:29, Error                        [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-Deployment, Language: neutral, ProcessorArchitecture: amd64, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/FirstLogonCommands

2018-07-23 10:38:29, Error                        [setup.exe] SMI data results dump: Description = Setting is not defined in this component.

Windows setup indicates you have put the "FirstLogonCommands" block in the wrong pass in the unnattend file.

You're using two different structures for running a command. You're using "RunSynchronousCommand" and "SynchronousCommand".

First, you should be using Windows System Image Manager to create unattend files. This will insure they are formatted correctly.

The problem here is that you are using the "RunSynchronousCommand" block which works during the specialize pass, or auditUser pass. It is supposed to be contained within a "RunSynchronous" block.

You've put in a "SynchronousCommand" block which runs during the oobeSystem pass after the first user logs on to the system. But, you've put it in the specialize pass.

The RunSynchronousCommand block has to be contained in a "RunSynchronous" block and located in the Specialize or auditUser pass. The SynchronousCommand block can only be located in the oobeSystem pass. For an explanation of Windows Setup Configuration Passes and when they run see here: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-configuration-passes

You need to make a decision when you want these commands to run and then properly format the unattend file by placing the commands in the proper locations. Again, Windows System Image Manager would not have validated this file.

Most likely, you want to use only "SynchronousCommand" during the oobeSystem pass. However, be aware, that Windows 10 does not run these commands synchronously. Windows will NOT wait for these commands to finish before logging the user on, contrary to what Microsoft has specified in documentation. This is new for Windows 10.