I was able to get around this problem in my test environment in the following way:

1. Restored master database in single-user mode as described above... when complete, SQL server...

Thanks Apurva,

I've tried it both ways... windows authentication only, AND mixed mode. Logging in as SA once the master db has been restored gives me the same error...