Currently, if no unattended installation file is found on the drive, a default one is placed that removes the recovery environment. This might be OK (and works with vanilla Windows 10.wim image files,) but if you add this default unattended installation file to an image that was pulled from an existing Windows To Go drive where the drive image was captured after sysprep ran and the generalization step with OOBE was selected, but no unattended installation file was included in the image sysprep, the newly created drive will fail with an error that the installation cannot be completed. The message also says to reboot to complete installation, but that doesn't help.
Currently, if no unattended installation file is found on the drive, a default one is placed that removes the recovery environment. This might be OK (and works with vanilla Windows 10.wim image files,) but if you add this default unattended installation file to an image that was pulled from an existing Windows To Go drive where the drive image was captured after sysprep ran and the generalization step with OOBE was selected, but no unattended installation file was included in the image sysprep, the newly created drive will fail with an error that the installation cannot be completed. The message also says to reboot to complete installation, but that doesn't help.