HP Solutions Center for my Windows 7 64-bit Home Premium PC?

[jmmseq]

That file was exactly the same I named before: AIO_CDB_NonNet_Full_Win_WW_130_141.exe

Of course I have a Windows 7 64-bit.

And the Flash Player up-to-date is one of the steps of message 115 I went through.

Let's see what happens with another admin user trying to install it.

I'm not at this time at my desk.

Thanks for replying 

[jmmseq]

So, the bug actually is:
running the file "AIO_CDB_NonNet_Full_Win_WW_130_141.exe" results in the creation of a folder named differently than expected by the same application further ahead.
I did what was said in message 1 of "Bug finally found - HP Photosmart C7280 Full Feature Software and Drivers Win 7 64 bit" - create a folder with the name shown in the error message and move all files from the 7s... folder to this correctly named - and could almost complete the installation (at first, the error was shown right in the beginning, now it was shown at the end of the process)

I got an error situation code:15647869
Thus, I have an installation unsucceeded that refers to a process that brings me all the way to the beginning, I think.
Tomorrow, I'll pay some more attention to this mishap.
Thanks for replying.

[VisionAiry]

Take your time. Thanks for working with me. I will keep searching.

[jmmseq]

Job done!
I ran again the file "AIO_CDB_NonNet_Full_Win_WW_130_141.exe" and chose "Uninstall".
While uninstalling, an error occurred. I followed the alternative steps and reached the end of the uninstallation process.
Then, went to Control Panel > Uninstall a Program and uninstalled what was left of the HP stuff.
Further, went to C:\Users\..\AppData\Local\Temp and wiped out the 7z... folder.
I ran once again the file "AIO_CDB_NonNet_Full_Win_WW_130_141.exe" and IT WORKED!!!
I have the strange feeling I have done all this before with no result!
Many thanks from Portugal!

κῦδος

[VisionAiry]

Very happy that worked! Thank you for sharing what you did to fix it too! Greetings from south USA!

Happy Printing/scanning!

[20131216]

Hi,

Thanks VisionAiry and others for the replies. I have run each of the fixes listed since my original post but still no success.

The latest problem is that the Setup application seems to get killed as soon as it is launched. This happens with and without firewall turned off.

Any further suggestions welcome.

Thanks

[VisionAiry]

Are you still getting a runtime error? Have you ran all the new Microsoft updates? Have you tried restoring to a point prior to a time when Solution Center didn't work?

What is the exact error message you are getting?

Always happy to help.

[20131216]

Thanks for your reply.

There is no longer a runtime error. I have uninstalled again and rebooted. Following this, the installer launched but stopped responding. Now when I run setup the program is killed immediately with no error mesage.

I have run windows updates. There is no restore point available prior to this problem.

Any further suggestions welcome.

[VisionAiry]

I have found this document linked below to be quite helpful in the past.  

--Fatal Error 1603--

I completely understand this is not the exact problem you are having, however it is that this link simply includes the same troubleshooting steps I would recommend you try, just written better than I could write out.  Sometimes Windows Installer likes to "crash" I guess you could say, so this will go through those steps to resolve it.  

The symptoms you describe are similar to when someone is trying to load a 64-bit driver onto a 32-bit operating system.  Not saying that is what is happening but just providing that information for future forum users to double-check first that they have the correct installation package before proceeding into tougher troulbeshooting steps.

I really hope this helps. Thanks for answering my questions.

[20131216]

OK, I have followed these steps and then uninstalled again.

Now the installer does run, but I get the error "The system cannot find the file specified".

There is a thread about this but it assumes that an error code is provided, which is not the case here. After clicking "OK" the dialogue box just disappears.

Definitely going round in circles!