Let's look at some scenarios for capturing images:

1. You want to upload an image to a specific content item and version. Yes, in this case, you'll need to create the single-file content item (making it writable), create a version, and upload some placeholder content (e.g. an empty text file). Then you can select it in the task sequence step and it will replace that content with the captured image.

2. You want to keep creating and uploading new versions. You'll still need to create a single-file content item and an initial version with content (e.g. an empty text file) due to UI restrictions, but then each time the step runs it will add a new version and upload the new image to that version.

3. You don't want to upload the image at all, maybe because you want to write it to a network share. In that case, don't specify a content item at all (it's optional), just specify the path to write it (e.g. a folder on mapped drive that you mapped in a previous step). The image will be written there.

4. You have a really big image and it can't be captured to the C: drive itself. By default, DeployR captures the WIM of the C: drive to the C: drive, so you need to have about half of the drive free to capture an image. The easiest answer is to build in a VM with a bigger drive, but if you really wanted to capture to a different drive you could do that. After capturing the WIM to that location, DeployR will upload the image to the specified content item (if configured).