As a workaround until this is sorted by Adobe, you could always start explorer at the end of the installation script if it's not running. Definitely not a fix, but at least there's a usable PC after the install routine completes.
I have the same exact issue in Windows 7 64bit after creating a package via Creative Cloud Packager a couple days ago. This is my crappy duct tape fix for now. This does not occur in Windows 8.1.
Chris
