Fixed this issue by using Management Studio.

I removed the AdventureWorks database off my machine and re-installed it using the AdventureWorksDBCI.msi

I then did not bother attaching the database using sqlcmd, but...