Why PowerChute Personal Edition 3.0.2 won't install on Windows 7 Home Premium 64-bit?

[Anonymous user]

Why won't PowerChute Personal Edition 3.0.2 install on Windows 7 Home Premium 64-bit? 

When I download PowerChute Personal Edition 3.0.2 from APC and run the install file as administrator, nothing happens!  No dialog window opens or anything.  Previously, I think I had PowerChute PE version 2-something, but I uninstalled it awhile ago.

[BillP]

Hi,

Look in the system event log for errors. Also, please run the installer in debug mode.

1. Trigger the 3.0.2 installation process by executing (double clicking) PCPE_Setup.exe
2. Go to c:\Documents and Settings\ or Search for PCPE_3.0.1.msi to find were it was installed to.
(not a typeO. The MSI was not renamed from the 3.0.1 installer)
3. Copy the PCPE_3.0.1.msi file to the desktop
4. Open a command prompt as administrator
5. Change directory to desktop
6. Run the command
msiexec /i PCPE_3.0.1.msi /l*vx install.txt  (letter l then *vx)
7. The installer UI will be launched again
8. Run the normal installation steps

9. Send  the log file "install.txt" for analysis that is created.,

Thanks,

[Anonymous user]

I didn't notice any errors regarding PowerChute in the system event logs, and the install file I have is named PCPEInstaller.exe.

I ran PCPEInstaller.exe (which nothing happened) and searched my C drive for PCPE_3.0.1.msi but it was not found.  I then searched for just PCPE and found a folder named:
C:\Users\Brendan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_PCPEInstaller.ex_37ce7bc4480f17f6d0b1c1c0c9c9c48a1f452f_138936a9

which contained one file called Report.wer.  Here are the contents of Report.wer:

Version=1

EventType=BEX

EventTime=130474052644515222

ReportType=2

Consent=1

UploadTime=130474052644935246

ReportIdentifier=e5eab5da-f568-11e3-98bb-485b395df82f

IntegratorReportIdentifier=e5eab5d9-f568-11e3-98bb-485b395df82f

WOW64=1

Response.BucketId=2751966258

Response.BucketTable=5

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=PCPEInstaller.exe

Sig[1].Name=Application Version

Sig[1].Value=3.0.2.0

Sig[2].Name=Application Timestamp

Sig[2].Value=4f1e922a

Sig[3].Name=Fault Module Name

Sig[3].Value=PCPEInstaller.exe

Sig[4].Name=Fault Module Version

Sig[4].Value=3.0.2.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=4f1e922a

Sig[6].Name=Exception Offset

Sig[6].Value=00001679

Sig[7].Name=Exception Code

Sig[7].Value=c000000d

Sig[8].Name=Exception Data

Sig[8].Value=00000000

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.768.3

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=db31

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=db31771ad73b86c942f333f82f9e4b50

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=e1b7

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=e1b7fc3bf945bd553fa629bea674fe09

UI[2]=C:\Users\Brendan\Desktop\PCPEInstaller.exe

UI[3]=PCPE Application has stopped working

UI[4]=Windows can check online for a solution to the problem.

UI[5]=Check online for a solution and close the program

UI[6]=Check online for a solution later and close the program

UI[7]=Close the program

LoadedModule[0]=C:\Users\Brendan\Desktop\PCPEInstaller.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll

LoadedModule[4]=C:\Windows\SysWOW64\SYSFER.DLL

LoadedModule[5]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[8]=C:\Windows\syswow64\GDI32.dll

LoadedModule[9]=C:\Windows\syswow64\USER32.dll

LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[15]=C:\Windows\syswow64\LPK.dll

LoadedModule[16]=C:\Windows\syswow64\USP10.dll

LoadedModule[17]=C:\Windows\system32\apphelp.dll

LoadedModule[18]=C:\Windows\AppPatch\AcGenral.DLL

LoadedModule[19]=C:\Windows\system32\UxTheme.dll

LoadedModule[20]=C:\Windows\system32\WINMM.dll

LoadedModule[21]=C:\Windows\system32\samcli.dll

LoadedModule[22]=C:\Windows\syswow64\ole32.dll

LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[24]=C:\Windows\system32\MSACM32.dll

LoadedModule[25]=C:\Windows\system32\VERSION.dll

LoadedModule[26]=C:\Windows\system32\sfc.dll

LoadedModule[27]=C:\Windows\system32\sfc_os.DLL

LoadedModule[28]=C:\Windows\syswow64\USERENV.dll

LoadedModule[29]=C:\Windows\syswow64\profapi.dll

LoadedModule[30]=C:\Windows\system32\dwmapi.dll

LoadedModule[31]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[32]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[33]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[34]=C:\Windows\syswow64\urlmon.dll

LoadedModule[35]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[41]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[42]=C:\Windows\syswow64\iertutil.dll

LoadedModule[43]=C:\Windows\syswow64\WININET.dll

LoadedModule[44]=C:\Windows\system32\MPR.dll

LoadedModule[45]=C:\Windows\system32\IMM32.DLL

LoadedModule[46]=C:\Windows\syswow64\MSCTF.dll

State[0].Key=Transport.DoneStage1

State[0].Value=1

FriendlyEventName=Stopped working

ConsentKey=BEX

AppName=PCPE Application

AppPath=C:\Users\Brendan\Desktop\PCPEInstaller.exe

[BillP]

Hi,

The first step in the installation process is extract the msi file from the bundle and since that did not happen I believe the installation files are corrupt.

When I double click on PCPEInstaller.exe the shot below is what I see in C:\users\wpasquil

Go to http://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SFPCPE302

and download the installer again and try installing using that download.

[Anonymous user]

I downloaded the installer fromhttp://www.apc.com/products/resource/include/techspec_index.cfm?base_sku=SFPCPE302

and tried installing again, but still nothing happened.

[BillP · Accepted solution]

Hi,

I have uncompressed the files from the .exe and zipped them for you to download.

Here is the link  PCPE-Install-Files.zip - Box

After downloading and UN-zipping double click on PCPE Setup.exe If that errors then follow the step I sent on June 16th starting at step 4 and run the msi.

[Anonymous user]

The PCPE Setup.exe that you gave me worked perfectly.  So there must be something wrong with the install file on the APC website.  Thank you very much!

[Anonymous user]

I am having the same problem trying to install this for the first time on Windows Vista - I downloaded the zip file, and it still hangs when I click next on the select folder screen. I am on Windows Vista Premium - 64-bit.

The above post is over 6 months old - why has this not been fixed yet?

Thanks, Neil

Oops - just found this post which fixed the problem:

https://community.se.com/t5/APC-UPS-for-Home-and-Office-Forum/bd-p/home-office-forum

If you are on 64-bit go to the second page - which describes how to do this for 64-bit systems. 

[BillP]

Thank you for this link. It worked perfectly. My wife and I have identical PC's, running 64 bit WIN7 Pro. On hers, the disk installation worked fine. On mine, no go. Used the same disk and a different disk - no difference. Tried the d/l from the site as suggested - still no joy. But the zip file in the above link worked fine. Go figure. 

[Anonymous user]

It's just over THREE YEARS since this problem cropped up and apparently it's not solved yet.  I'm trying to install PCPE 3.0.2 on a Windows 10 Pro, 64 bit, Version 1703 system and it won't install - nothing happens when I try to execute the installer.  The ZIP file is 3.0.1 and that didn't work either (I didn't try the .MSI route yet).  In a long and varied life I've been, among other things, a dive instructor in Rhode Island.  Used to drive past the APC plant most weekends.  I was also once a software developer (also in Rhode Island).  IMO users shouldn't have to do registry tweaks to install basic utility software.  Please, guys, can you fix this? and in the meantime, tell me how to install PCPE on my system?

Thanks!

[BillP]

Hi,

Sorry for the inconvenience. Is the system a home computer or business and if business is the system part of a domain? 

On 8/1/2017 7:22 PM, John E said:

 The ZIP file is 3.0.1 and that didn't work either

Are you referring to the zip file attached to Schneider Electric FAQ FA235203? If so when the installer that is in the zip file runs PCPE 3.0.2 will be installed. Also, to avoid any future confusion PCPE_3.0.1.msi in the zip file attached to FAQ FA235203 has been corrected. 

[Anonymous user]

The system is a home computer.  I am a semi-retired scientist (biologist, oceanographer) who also doubles part time as a water district manager - so the occasional government-business-related E-mails appear.  The water district has its own computer system in an entirely different location, miles away.  I try to avoid transacting business from this home computer system.  I do occasionally provide technical advice by E-mail.

Yes, I am referring to that ZIP file.  I extracted its contents and tried to run that instance of PCPEInstaller.exe - without success.

I suppose we are doing a delicate dance around the power-management features of Windows 10?

[Anonymous user]

I have moved my Back-UPS RS1500 over to another computer running Win7 Pro. I am getting the error The installer is unable to locate the battery backup ....

Device Manager shows:

1. Batteries >> American Power Conversion USB UPS (Apcupsd)
2. Printers & Devices >> Back-UPS RS1500 FW: etc
3. HID >> No APC device listed

I have generated a DeView.txt file and an install.txt file as suggested in this thread. (Attached)

The UPS works correctly using Apcupsd. So the cable is connected correctly. The Apcupsd service is turned OFF when I try to install the PowerChute software.

Any insight into a solution would be appreciated. Thanks,

Rick

[BillP]

Hi,

You need to change the driver from APCUPSD to HID UPS Battery or APC UPS. See Schneider Electric FAQ FA164514

[Anonymous user]

Many thanks Bill! A change of the drivers and I'm in business!

Thanks again,

Rick

On 3/7/2019 2:29 PM, Bill said:

You need to change the driver from APCUPSD to HID UPS Battery or APC UPS. See Schneider Electric FAQ FA164514