I'm running Vista 64 Home Premium. No system problems excepting that I cannot install any 64 bit programs. I get Error 1719. "The Windows Installer Service could not be accessed." .. I've tried about every solution out there. msiexec /unreg /regserver .. checked the registry entries .. permissions .. I loaded the latest MSIServer 4.5 (didn't help) .. I've run logging on the installation and can provide the logging detail .. I even replaced my main drive with a blank drive, installed a fresh copy of Vista 64, ran a successful installation of a 64 bit program with logging on .. I compared the logs to my system drive that fails to install 64 bit programs and while I see some differences I am not expert enough to figure out what is missing or misconfigured in my system. Driving me up the wall !!!



HELP anyone really sharp?

"Stan" <stan.kay@xxxxxx> wrote in message
news:A77831F8-FAB8-4AE5-8D98-C592E2CBAC5C@xxxxxx

>I had the same problem and found that the following helped to resolve the
>problem:-
>
> 1. Go to START then ADMINISTRATIVE TOOLS then select SERVICES
> 2. Scan for and then double click WINDOWS INSTALLER
> 3. It should be started. If it is not then first ensure that the STARTUP
> TYPE is set to AUTOMATIC.
> 4. Finally press the START button.
>
> Hopefully, everything should now be OK
>
> Good luck,
>
> Stan
>
> "pberk" <guest@xxxxxx-email.com> wrote in message
> news:0aa0ee071bb258b5495d2eac2ed8df2c@xxxxxx-gateway.com...

>>
>> I'm running Vista 64 Home Premium. No system problems excepting that I
>> cannot install any 64 bit programs. I get Error 1719. "The Windows
>> Installer Service could not be accessed." .. I've tried about every
>> solution out there. msiexec /unreg /regserver .. checked the registry
>> entries .. permissions .. I loaded the latest MSIServer 4.5 (didn't
>> help) .. I've run logging on the installation and can provide the
>> logging detail .. I even replaced my main drive with a blank drive,
>> installed a fresh copy of Vista 64, ran a successful installation of a
>> 64 bit program with logging on .. I compared the logs to my system drive
>> that fails to install 64 bit programs and while I see some differences I
>> am not expert enough to figure out what is missing or misconfigured in
>> my system. Driving me up the wall !!!
>>
>> HELP anyone really sharp?
>> *
>> *
>>
>>
>> --
>> pberk

>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 3451 (20080918) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>

Stan,
Thanks for your reply. I set the Windows Installer to "automatic" .. rebooted. Made sure it was "started" .. but no luck on the install. Same exact problem. Error 1719.
I've tried this solution before.

Do you know anything about .NET Framework64 .. I noticed that
InstallUtilLib.dll in the Microsoft.NET\Framework64 folder is different in size
than the one in my fresh install of Vista64 that works! .. It's a very sticky file
to change but I"m going to try to replace the file on my main system with
the one from the fresh install and see if it's the magic cure! Not too optimistic
it will.

Paul

http://www.planetamd64.com/index.php?showtopic=16021

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"pberk" <guest@xxxxxx-email.com> wrote in message news:b38349284a8f3457b15373579460c9c6@xxxxxx-gateway.com...

>
> Stan,
> Thanks for your reply. I set the Windows Installer to "automatic" ..
> rebooted. Made sure it was "started" .. but no luck on the install. Same
> exact problem. Error 1719.
> I've tried this solution before.
>
> Do you know anything about .NET Framework64 .. I noticed that
> InstallUtilLib.dll in the Microsoft.NET\Framework64 folder is
> different in size
> than the one in my fresh install of Vista64 that works! .. It's a
> very sticky file
> to change but I"m going to try to replace the file on my main
> system with
> the one from the fresh install and see if it's the magic cure!
> Not too optimistic
> it will.
>
> Paul
>
>
> --
> pberk

Peter,
I saw this fix for Windows Installer earlier. I'm no expert, but the fix seems dead wrong. If you set the registry value to C:\WINDOWS\SysWOW64\msiexec.exe /V
for 64 bit install you'd be making a mistake on Vista 64. Not sure about XP64 ..
Vista 64 keeps the 64 bit installer in \system32 .. I know it sounds backwards but all exe files startup on a Vista64 system in the WOW64 (Windows on Windows) translator so that it can find the right path. 32 bit stuff is kept in \SysWOW64 and the 64 bit stuff is kept in \System32. This includes msiexec.exe and associated dll's. .. I've done a fresh install of Vista 64 on a spare harddrive and this is the case. Check this out at Wikipedia ... http://en.wikipedia.org/wiki/WOW64

<i>The operating system uses the %SystemRoot%\system32 directory for its 64-bit library and executable files. This is done for backwards compatibility reasons as many legacy applications are hardcoded to use that path. When executing 32-bit applications, WOW64 redirects requests for DLLs from that directory to %SystemRoot%\SysWOW64, which contains legacy libraries and executables.</i>

Still looking for a solution.

Paul

You are correct and the "guru" on that website is wrong. Did you ever find a
fix for this? I'm experiencing the same situation.

Greg

"pberk" wrote:

>
> Peter,
> I saw this fix for Windows Installer earlier. I'm no expert, but
> the fix seems dead wrong. If you set the registry value to
> C:\WINDOWS\SysWOW64\msiexec.exe /V
> for 64 bit install you'd be making a mistake on Vista 64. Not sure
> about XP64 ..
> Vista 64 keeps the 64 bit installer in \system32 .. I know it sounds
> backwards but all exe files startup on a Vista64 system in the WOW64
> (Windows on Windows) translator so that it can find the right path. 32
> bit stuff is kept in \SysWOW64 and the 64 bit stuff is kept in
> \System32. This includes msiexec.exe and associated dll's. .. I've done
> a fresh install of Vista 64 on a spare harddrive and this is the case.
> Check this out at Wikipedia ... http://en.wikipedia.org/wiki/WOW64
>
> <i>The operating system uses the '%SystemRoot%'
> (http://en.wikipedia.org/wiki/%25SystemRoot%25)\system32 directory for
> its 64-bit library and executable files. This is done for backwards
> compatibility reasons as many legacy applications are 'hardcoded'
> (http://en.wikipedia.org/wiki/Hardcoded) to use that path. When
> executing 32-bit applications, WOW64 redirects requests for DLLs from
> that directory to %SystemRoot%\SysWOW64, which contains legacy libraries
> and executables.</i>
>
> Still looking for a solution.
>
> Paul
>
>
> --
> pberk
>

No. Did not find a solution. Tried everything! .. Vista 64 whipped me. Too threaded. It's like a chain of things .. Finally, I gave up, gave in, gave out and reinstalled Vista 64. I backed up my main drive data two different ways, using the Vista Backup routine and also backup up the old fashioned way by coping ALL the FILES on my main drive (C to another disc. Lucky for me I have a 150 gig Raptor for my main drive, so with the low cost of 500 SATA drives I could back up the entire C drive by just copying all the files. This was important in restoring certain .exe files and even Windows Mail.

In my case I had to nuke my main drive as my copy of Vista 64 is OEM and will not do a reinstall or repair -- only a fresh install on a clean harddrive. My system now happily loads 64 bit software and runs faster as I expected of a clean install. I am gradually adding back the software I use. One thing I forgot was to export my Windows Mail message rules. That info is stored in the registry. I did export the entire registry file before nuking the drive, hence I have what I need to restore the message rules but will have to go through some hoops to get to it.

I learned much about Vista along the way and consider the whole experience a positive one. I'm doing a much better job this time of make sure I have restore points etc. and being careful about what software I add.