We looked into this in a screen sharing session. The issue was that the username in windows had an '&' and that was preventing the secondary installer from running properly. We manually unzipped the files and that seems to have corrected the problem.