Thanks for reporting, I can reproduce that. This target has backslashes in its repo entry image path, while the framework always uses slashes. I have a fix ready and will publish that the next time I do an update.
If somebody want the fix this before I get around to uploading, just add a repo folder to a content pack, containing the target's repo entry as a json file and replace the backslashes within.