1.3.7 Fatal error during install (3 different PCs)

[reyngreg]

I've been unable to install 1.3.7 on any of my PCs. The install appers to get all the way to validation, and then a rollback occurs. In the end I get the fatal error popup. At least everything still works after the failed install, so cheers to sub on that one.

It fails on Vista Business, Vista Home Premium, and XP Pro. All three PCs used separate downloads of the installer, and all three had 1.2.9 installed and working fine before the upgrade. Doesn't help to delete/move the devnz folder.

Can anyone point out where I'm being obviously stupid? :confused:

[FarNorthSAT]

Me to...I'm having the exact same problem

[FarNorthSAT]

Can you uninstall the previous versions of GBPVR??
I can't but I think I install it with another user name that doesn't exist anymore

[siliconaudio]

Is your PC logging into a domain? My PC was and I got the same error, even if I logged on as the domain admin. I had to log on to the local PC, (not the domain) as a local administrator and install, then all was fine. I'm not sure if this was due to a group policy that redirects some folders, but the local logon was the key to getting the install to work.

Then, once the install is done, you can log back on with your domain account and run GBPVR with no problems.

[reyngreg]

One of the PCs uses a domain, but the other two don't. I'll try to explicitly log in as the local admin on the one PC and see how it works.

Thanks.

[mcervi]

I went through this (and have with at least the last 1 or 2 versions). After a lot of work (i.e. I changed a lot of things and I'm not sure what finally worked), I was able to get the new version to install cleanly. My system is running Vista.

One thing I noticed was that Add/Remove programs showed two copies of GB-PVR being installed. One (0.99.x) wouldn't uninstall because the original msi file was gone. I found a Windows Installer Cleanup Utility from Microsoft and ran that to remove the extra version.

I ran the install in logged mode -- something like msiexec /i <msifilename> /log <logfilename> -- to see what was going wrong. If you're running Vista make sure you do that in elevated mode.

There's a lot of garbage in the log file, but basically it appeared that the installer thought some files were in use even though Task Manager did not show any sign of GB-PVR or any of its components running. I finally set the service to disabled and removed the tray app from my startup folder and rebooted. The upgrade installed cleanly after that.

I did a lot of other things in between all those steps that I don't think made any difference, plus I don't really remember what they were. Hopefully, this will help.

Ironically, I was dealing with this headache at the same time I was setting up my new MacBook this weekend, purchased because I was getting tired of Windows hassles. We'll see how that works out.

[InVermont]

When upgrading from 1.2.9 to 1.2.13, I had a similar issue. this cleared it.
open up a command prompt (start->run type CMD hit OK)

sc delete "gb-pvr recording service"

http://forums.nextpvr.com/showthread.php?t=33744&page=2

then run the installer.

[reyngreg]

Thanks for the pointers. The PC with the domain did install successfully when I logged in as the local admin.

I'll try that and the other pointers tonight on the remaining two PCs without a domain.

Thanks again!

[HarryH3]

I used the directions posted here: http://lifehacker.com/341521/enable-vist...or-account to enable the "real" Admin account in Vista. When I log into that account, the "rollback at the very end of the install" was gone and GBPVR installed perfectly.

[siliconaudio]

I used the directions posted here: http://lifehacker.com/341521/enable-vist...or-account to enable the "real" Admin account in Vista. When I log into that account, the "rollback at the very end of the install" was gone and GBPVR installed perfectly.

That makes me wonder if right-clicking on the installer and choosing "Run as Administrator" would have helped? Haven't tried this myself as I run GBPVR on XP, but have done this to solve other problems like this in Vista.