Hi, Welcome back to the HP Support Forums! I read your post and see that you installed the HP Support Assistant Software and you keep getting a message that the HP Support Assistant Software can't be found.
I would like to help you resolve this issue. If this helps you to reach a solution, please click the 'Accept as Solution' button down below in this message.
If you wish to say thanks for my effort to help, click the ' Thumbs Up ' to give me a Kudos. Run any critical Windows Updates to see if that will help resolve this issue. I suggest you try uninstalling the HP Support Assistant.
Download and reinstall the. Hopefully an updated version will resolve the issue. Restart the computer.
See if the error goes away and if you can open the HP Support Assistant Software now. If the issue persists, please try booting into safe mode with network and then uninstalling the HP Support Assistant. If you are able to complete the uninstall then download and reinstall. You can take a look at this post by @ to see if it will help, Please let me know the outcome and if there is anything else I can help you with. Hi, Welcome back to the HP Support Forums!
I read your post and see that you installed the HP Support Assistant Software and you keep getting a message that the HP Support Assistant Software can't be found. I would like to help you resolve this issue. If this helps you to reach a solution, please click the 'Accept as Solution' button down below in this message. If you wish to say thanks for my effort to help, click the ' Thumbs Up ' to give me a Kudos.
Run any critical Windows Updates to see if that will help resolve this issue. I suggest you try uninstalling the HP Support Assistant. Download and reinstall the. Hopefully an updated version will resolve the issue. Restart the computer. See if the error goes away and if you can open the HP Support Assistant Software now.
If the issue persists, please try booting into safe mode with network and then uninstalling the HP Support Assistant. If you are able to complete the uninstall then download and reinstall. You can take a look at this post by @ to see if it will help, Please let me know the outcome and if there is anything else I can help you with.
Admaai: Any chance you can post that vbscript or regkey. I have been able to semi-automate the installation by using a similar command line like jmaclaurin posted. HPHKS.EXE /q /l.v '%windir% system32 logfiles HPHKS.log' REBOOT=REALLYSUPPRESS That command worked for a silent install, but it doesn't fix the new hardware prompt upon reboot. I am using Altirs not SCCM, but none the less we are running into the same problem. I was going to run a job that would temporarily login with local admin credentials so that the software would install properly after reboot, wait 30 seconds, then logoff. However that seems kind of sloppy. Thanks in advance for any help!
Sorry for late response, the reason it is needed is because it controls a lot of features, like changing the screen mode from laptop to external on the fly (with Fn keys). Although SCCM restart the computer many times after installation and installs other programs, if I do not add the reg entry it still comes out with missing driver in the end. I got so swamped at work today that I totally forgot to check the reg entry, sorry for that too:).
But here is the method to find it, i used it for xp, since we have not yet migrated, download Regshot linkput it somewhere you can find it, install the hotkey software on a new laptop, and reboot when it prompts, login as a restricted user, you get the admin popup to install a new hardware, fire up regshot as local admin, take 1st snapshot, insert localadmin credentials in the popup for installing new hardware and let it get installed, then take your second snapshot. I actually found this when quicklaunch started playing its song and dance, amazingly the exact same registry script works for Hp hotkey. BTW I opened the msi in wise, at a fast glance, it had nothing except properties. Everything else was done in mst. Just to add my two bits, I was able to deploy the HP HotKey Support SoftPaq via SCCM using the following steps.
Download the SoftPaq here. From the sp53547.exe I used WinRAR to extract the source files. Run the following command in the SCCM program HPHKS.exe /qn /norestart I've been able to test this via Run Advertised Programs on both x86 & x64 Windows 7 8460p & 8460w machines. Because to package does require a reboot and rebooting is unexceptable when in the TS I added the /norestart and add a reboot task immediatly aftward.
I did notice that during testing it would install but I couldn't use the Fn keys for brightness right away. The following services should be started automatically but don't start right away. HpHotKeyMonitor HP Software Framework Service HP Service Hope this helps someone else, and thank you to everyone who has already left comments on this topic, I wouldn't have been able to get this otherwise.
Hp Support Assistant Silent Installer Msi
I was recently updating the HP Support Assistant on my HP Probook laptop. While attempting to run the install, I kept receiving the follow errors: The install log showed the following: Windows Installer installed the product. Product Name: HP Support Assistant. Product Version: 7.7.34.34. Product Language: 1033.
Manufacturer: Hewlett-Packard Company. Installation success or error status: 1639. Thankfully I came across the following article which helped clear things up: To resolve this problem, remove all special characters or extended characters in the company name.
To do so, modify the registry entry for the RegisteredOrganization string value. Sure enough, I browsed to HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion & noted that the RegisteredOrganization/RegisteredOwner value was added in quotes as part of the corporate SCCM build. After changing the registry settings, I was able to run the installer with no further issues. Latest Twitter Updates.
Scary stuff! Important to ensure out-of-band management is included as part of your patch management planning.
Purely focusing on process automation without considering potential outcomes allows this to happen. This is also. Startling, but not surprising insights at #hpediscover from the FBI Cyber Crimes division: 75% of cyber crime is o. Wow, almost a year since I've blogged! It was long overdue. Set Hyper-V VM Resynchroniza. Service Manager PowerShell Workflow: 'The operation has timed out': #SCSM #ServiceManager #Powershell.
The older version of. Cannot be removed. Contact your technical support group.' It's not a very helpful message - especially if you're your own 'technical support group'. The usual advice on this forum and elsewhere seems to be to re-run the install/remove program for the last version of the program.
If you have it, try it - it might work. But if you don't have it, or that effort fails, or you just want to go straight to the problem, try the following. It won't remove left-over files from a previous install, but it will hopefully reveal and fix what caused the Error 1714 failure.
Hp Support Assistant Msi
The usual warnings about making changes to the registry apply. Open a command window and enter the following but do not enter return until told: 'msiexec /i ' without the quotes. This will execute the MicroSoft Installer program in the install mode. Enter the name of the.msi file (including the path) or drag it from wherever it is in Windows Explorer to the command window. If the file or path includes spaces, enclose the entire path in '. (If you drag the file name, Windows will do that for you if it's needed.) Enter ' /l.v ' without the quotes. 'l' is the letter 'L'.
This requests the generation of a verbose log about the process, and you will need a file to capture it, so: Enter the name of a log file to receive a detailed log of the msi execution. The entire path is needed. Examine what you've just entered and make sure there is at least one space between each part of the command. The command should look something like this, with appropriate changes based on your msi file, what you chose to call the log file, and the paths to each: Code: msiexec /i C: DownloadedFiles LibreOffice4.4.5Winx86.msi /l.v C: temp msi.log Now, enter return and follow the directions for the install as you did before when it failed. It will fail again. When it does, close out the installer process, and open the log file. Search in that file for 'Error 1714'.
It should be towards the end of what may be a long file. A few lines above that you will hopefully find what the msi installer didn't like, and it is usually a registry key that is missing something msiexec is looking for. An example might be: 'Unexpected or missing value (name: 'PackageName', value: ') in key HKLM Software Classes Installer Products E9FFD8907BD5F964E8A51312EEBD6B0E SourceList'. What's missing for you may be something else, and the long hex key can be anything. Open the registry and find that key ('HKLM' is short for 'HKEYLOCALMACHINE'). If you're feeling brave and confident, just delete that key (E9FFD8907BD5F964E8A51312EEBD6B0E in this example) and all of its sub keys.
If you'd rather be cautious and conservative, add something like '-00' to the end of that key to hide it from the installer. Now repeat the install procedure.
(If you just go back to the command window, recall the same command line, and re-execute it you will have a new log file to review in case it fails again.) If the install is successful and you hid the offending key, then go back to the registry and remove it. However, it's possible that there may be more than one problem, and if so, it/they will be revealed one at a time with each install try. Alex6361 wrote:'Error 1714. The older version of. Cannot be removed. Contact your technical support group.' It's not a very helpful message - especially if you're your own 'technical support group'.
Hi, I just wanted to say thanks for posting this. I have been trying to uninstall the last remnants of an old MySql version for hours so that the new version would install, and getting nowhere, and this is the only thing that actually allowed me to see exactly why and where the install of a newer version was failing.
Gucci Leather Belt with Double G Buckle Out of all the Gucci belts, this one is probably the most minimalist. Real gucci belt serial number. This is an iconic piece, well worth every dollar you’ll spend on it! Get yours from or from! Available in 4 different color options, it is made out of Gucci’s unfinished faded leather and can be easily worn either as a hip or waist belt.
I'm constantly switching between my Surface Pro 3 and my HP Spectre x360. The Spectre has a few quirks, primarily with the audio driver, but it's manageable until HP releases an update or two. However, one of my most immediate concerns was that I would be notified when a new driver was released. I rely on the HP Support Assistant app that comes pre-installed on HP systems. This app runs in the background to alert when updates are available, but can also be executed to force a manual check.
It's a great way to keep your HP system up-to-date, knowing when new drivers and BIOS updates are available. After I started experiencing the audio driver quirks, I pulled up the trusty HP Support Assistant app, hoping the company had made an update available already.
To my surprise, the part of the app that allows for manual checks was broken. Other areas worked just fine, I just couldn’t initiate a manual checkup and it looked as if the automatic checkup wasn't working, either. And, unless you've gone into the app, you are probably unaware that it's broken. The fix is simple.
You need to download and reinstall the HP Support Assistant app. It installs right over top the broken one – no need to uninstall the old one first. Here's where you can get it: P.S. The HP Support Assistant isn't the only app reported to be fixed by a reinstall. If you experience other apps that just don't work quite right, try a reinstall.
It fixes the problem in most cases. If you chose to do a clean installation of Windows 10 on an HP system, instead of performing the upgrade, the HP Support Assistant won't be there anyway. I highly recommend installing it so you know when updates are available. HP does a great job quickly delivering fixes and patches through this mechanism.