9.0b Installation Wizard ends prematurely !

Christian de Godzinsky wrote on 8/29/2009, 4:03 AM

Hi,

Trying to istall both 32 and 64 bit versions of the 9.0b upgrade on my two 32 and 64 bit versions of 9.0 (not a)....

Both installation wizards stops at the following popup:

"The Installation Wizard has ended prematurely! Your system has not been modified. To install this progam at a later time, please run the installation program again."

The installations were (probably) successful since I can launch both, and they show 9.0b in the spalsh screen.

Something spooky here, at least I leaves me a little uncertain what actually is missing in the installation???

Should I try to totally uninstall first?
Shouldn't it be possible to install 9.0b on top of 9.0 (not a)???
Anyone else experienced the same?

I'm runningon the WIN 7 x64 ultimate and a quad core QX9650 with 8Gig of DDR3 ram.

Christian

Comments

VideJoe wrote on 8/29/2009, 4:12 AM

I had the same, doesn't seem to affect a correct installation though. I encountered it with previous versions of 9 as well.

ritsmer wrote on 8/29/2009, 4:32 AM

Also have Win7 x64.
Could install V9.0b x32 over 9.0a x32 without problems, but got a "Ended prematurely" trying to install V9.0b x64 over V9.0a x64.

Have removed everything concerning V9.0a and b x64 and run V9.0b x32 - which works very well now.
Dunno - but think that there is no reason to possibly confuse the machine having 2 very similiar versions (x64 and x32) of the same software.

megabit wrote on 8/29/2009, 4:42 AM

Same here (only with 64-bit version, and under Vista x64). It started with VP 9.0.

Christian de Godzinsky wrote on 8/29/2009, 6:26 AM

Hi,

THX 4 your comments, reassuring.

I tried even to remove both VP9.0 installations first, but the 9.0b installer just again reports the premature ending, both in 32 and 64 install versions, on my 64 bit WIN7...

The installations themselves seem to work... Still a little spooky to feel unsecure about what did NOT get processed at the very end of the installations... If this problem is something that is quite common, probably SCS should do something about it. Hopefully some of you have reported this to SCS, I probably should do it also..

Christian

megabit wrote on 8/29/2009, 6:29 AM

Yes I did report it, but my report has been sorta' refused based on the fact people with unsupported (as of now) Windows version have this problem, too :(

Christian de Godzinsky wrote on 8/29/2009, 7:06 AM

Yeah, I know. I was running Vegas on XP x64. Whatever the problem you reported, the reply started "...not supported OS...". The same with (us) early Vista adopters. Somehow I understand also SCS since they probably newer had the time to test their SW thoroughly on new OS'es before someone was running them already...

Frankly W7 is just a revamped Vista. Look at W7 system file versions, majority starts something like 6.xxxx. Come on Windows 3 was still called windows, NT was actually W4, XP was W5, Vista W6 and now W7 is actually W6.....plus.

Programs that run on Vista runs on W7. Most of the drivers too. So SCS should take seriously W7 complains....

Christian

othersteve wrote on 8/29/2009, 9:00 AM

I had precisely the same problem on my Win 7 x64 box prior to clean installing/moving to Win 7 RTM. I had previously "forced" the upgrade from Win 7 beta, which I think may have caused the problem somehow indirectly due to directory permissions or something funky like that.

Let me ask you this: on this machine, have you upgraded from either Vista or 7 beta to your current build? If so, this might be the reason. It's still a bug of sorts I'd say, however, as Vista > 7 RTM is an officially supported upgrade path.

I hate to tell you this, but it seems until the problem is uncovered somehow, the best solution may be to perform a clean install of your OS. Whether or not the premature termination of the installer results in any other issues I cannot say.

Steve

Christian de Godzinsky wrote on 8/29/2009, 12:09 PM

Hi Steve,

I did a Vista Ultimate x64 to WIN7 x64 Ultimate upgrade, supported as you state. The Vista installation was originally a fresh installation, with all SP's installed later.

So, just for the SAKE of myself feeling uncertain - I am NOT going to perform a fresh install, als long as VP90b seems to work (albeit with the known bugs)... A fresh install would cause too much trouble with all settings, data and applications. a weeks work at least... aaaarghhh...

So, how did you fix your problem???

Here I envy the MAC users. A friend of mine recently bought a new Mac and transferred ALL his software and files from his former Mac, just by connecting a wire (was it firewire or ethernet) between the two computers, just hitting a BUTTON. After the transfer he thought that he had forgot to switch the monitor cable from the old mac to the new mac. He did not forget - because everything (everything!) just looked and felt and worked exactly the same on his new computer.... Pure magic - or - excellent OS!

Maybe Windoz 17 will some day have that kind of functionality...

Christian

John_Cline wrote on 8/29/2009, 12:59 PM

I had the same problem installing 9.0a-64 and 9.0b-64 on Vista64. Like you, after the install fails, the program seems to have installed correctly and runs.

Christian de Godzinsky wrote on 8/29/2009, 1:26 PM

Thanx John, reassuring to know that the installation is intact! Tomorrow I will give 9.0b (both versions) a tough ride and see how they perform....

Christian

othersteve wrote on 8/30/2009, 4:12 PM

Christian,

Don't sweat it; the Vista > 7 upgrade simply works slightly differently than a clean install. Honestly clean installs are a pain, but they're also awesome in the end.

Either way, if you ask me, Macs are ridiculously overrated. As a tech, I'm a lot more heavily-versed in PC than Mac tech, but nevertheless, I have several friends and co-workers who rely on Macs, and my productivity is off the charts compared to theirs. At our annual trip to E3 this year back in June, I edited/rendered circles around everyone with Mac hardware using my PC and Vegas... and that was with Win7 RC, no less. :)

In many ways I like to think of the Mac world as a bit of a fraternity phenomenon; you pay your exorbitant initiation fee and you're one of the gang--and then you're certain you simply must have something which is the cream of the crop, due largely in part to your self-validating beliefs that your money has gone to good use. :-D

Steve

Gidi wrote on 9/5/2009, 5:34 AM

Christian,

same effect/popup here with Vista64 and SVP9.0a and b 64bit upgrades.

Upgrade ended prematurely but SVP 9.0b seems to work in the new version (9.0b now, 9.0a before).

I'm not really trusting the installation but will use it as it is.

HW/SW Intel 9300/Quad 8GB Ram, 1TB Raid1 and 4TB NAS, Vista x64

megabit wrote on 9/5/2009, 5:46 AM

My SCS support ticket on this problem has never been resolved, and yet is now closed and marked as such...

I begged them to at least tell me what exactly is being done by the installer at its very last stage (where it fails) - no answer.

Everyone having this problem - please report to SCS, but do not necessarily mention your platform being W7 (not officially released, it's a very convenient reason for ignoring our reports).