Installing 1.3.7 fails (MSI*.tmp using all cpu)

[InverseChaos]

I have downloaded the gbpvr install package again, still no install.

Also have tried checking the various threads on different web sites that deal with error 1722 which is a windows installer error. There are posts about many different types of software that fail to install at the same point as my gbpvr. I have tried various fixes suggested including the following:

Un-install and remove all references to gbpvr.
Un-install SP3 and try install.
Un-install the java jre completely, clean out all reg and other entries and re-install jre.
Plus various suggestions involving modifying reg entries.

All this and trying the re-install of gbpvr in between the various un and re install of the various 'fixes'.

All to no avail :mad:

This does really seem to be a problem with the installer not running or stopping something during the process, but it has now got to the point when I am quickly getting fed up with all the time I am wasting trying 'fix' after 'fix'. I might as well just take the tv card out and give up.

cheers

[InverseChaos]

Bump! to see if anyone else had any ideas, Sub?

[sub]

Bump! to see if anyone else had any ideas, Sub?

Sorry, I've got no idea. There is a lot of more knowledge people with suggestions on this front. To me, the MSI installer stuff works in strange and mysterious ways...

[bgowland]

Also have tried checking the various threads on different web sites that deal with error 1722 which is a windows installer error. There are posts about many different types of software that fail to install at the same point as my gbpvr.

I'm not going to pretend I understand more than the basics of MS Installer but that's pretty much impossible - i.e., two different msi packages for two different applications can never have a 'same point'. They all do completely different things depending on what's required for installation.

The 1722 error, as its text suggests, relates to 'A program run as part of the setup...'. Looking at the msi logfile you posted, the relevant bit appears to be as follows

Code:

MSI (c) (74:3C) [22:06:28:765]: Doing action: Action1
Action 22:06:28: Action1.
Action start 22:06:28: Action1.
Action 22:12:09: Cancel. Dialog created
MSI (c) (74:3C) [22:13:21:453]: Note: 1: 1722 2: Action1 3: C:\DOCUME~1\Chaos\LOCALS~1\Temp\MSI30.tmp 4:  

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action Action1, location: C:\DOCUME~1\Chaos\LOCALS~1\Temp\MSI30.tmp, command:  
MSI (c) (74:3C) [22:14:54:609]: Product: GB-PVR -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action Action1, location: C:\DOCUME~1\Chaos\LOCALS~1\Temp\MSI30.tmp, command:  

Action ended 22:14:54: Action1. Return value 3.

Digging into the msi package with Orca, it seems that 'Action1' is something called 'Callkilltray' which suggests it was trying to terminate the GB-PVR systray application although that's just a guess.

The problem here is, having removed all registry entries and files related to GB-PVR, if the installation still fails with that error it surely can't be caused by it not being able to stop the GB-PVR systray app. (or whatever it's trying to do). The 'Return value 3' is apparently a generic failure according to what I've found on various websites.

I really wish I (or someone else here) could come up with an answer but it does seem like there's some problem with your machine - perhaps coupled with a quirk in the installer, but nobody else has reported the same problem and the msi has been available for a couple of weeks now.

Cheers,
Brian

[K.S.]

maybe your MSI installer freaked out... dunno if the 3.1 version is included in XP SP3 or not, but an update to the 4.5 version http://www.microsoft.com/downloads/detai...laylang=en could help...

[mmatheny]

Try this - merge this regedit by double clicking it and giving it permission to run - this allows the Windows installer service to run in Safe Mode. Then reboot, right after the bios page comes up, start pressing F8 and select Safe Mode. Then try to run the installer.

[Agent24]

I have the exact same problem (re: http://forums.nextpvr.com/showthread.php?t=36985)

I'm not sure what's causing it either.

Do you have any security products by Comodo or Avira installed? I've got a suspicion that something there may be causing the issue.

I'm about to try the registry mod as posted on my thread and attempt to install in safe mode, will let everyone know how I get on...

[Agent24]

Well I tried the new registry setting, but I still get the same error that

"The system administrator has set policies to prevent this installation"

[InverseChaos]

Just tried the reg fix to install in safe mode, fails because installer cannot be run in safe mode.

Using msconfig.exe removed anything from Comodo and Avira that was set to run at startup, rebooted and tried ordinary install. This failed.

Reinstated Comodo and Avira, but stopped the entry for .NET runtime optimization service v2.0.50727_X86. Rebooted and failed again, but this time with no TMP file using all cpu, but with a requester as show in the screen grab below showing that the installer was trying to work out how much disk space was needed.

This process and requester did not complete but just sat on the desktop with little cpu usage, but the pointer animation showing that it was doing something.

Does this show up on other users problems?

I'll try and see what else I can try.

Cheers
InverseChaos

[bgowland]

Try this - merge this regedit by double clicking it and giving it permission to run - this allows the Windows installer service to run in Safe Mode. Then reboot, right after the bios page comes up, start pressing F8 and select Safe Mode. Then try to run the installer.

The registry import you included is for Safe Mode with Networking.

The line...

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\MSIServer]

should be...

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer]

for starting in 'pure' Safe Mode.

Cheers,
Brian