RC1 Stop Message Must uninstall 'HP ProtectTools Security Manager'

[Guest]

After first running the compatiblity check, with everything coming back fine
(other than a couple minor programs), I start the installation of RC1, using
upgrade option. Setup searches the internet for updates; and then does a
scan of the computer, and returns the stop message above: must uninstall the
following program: HP ProtectTools Security Manager. Setup says to go to
Programs and uninstall in order to continue.

But, there is no such program listed. I'm using a fairly new Laptop (which
carries the "Vista Capable" logo) by HP. Doing some checking (Goggle), I
discovered HP has an embedded security chip in business grade computers which
is designed to reduce the threat of hackers, and the technology is called "HP
ProtectTools Security Manager."

I checked their (HP) web site, but find no way to disable/change settings.

Anyone have any ideas, other than wait until HP provides an update later on
down the line?

Guess what floors me, is that the initial scan shows everything to be ready
to install, but during the setup, the installation scan says otherwise.

 

[Guest]

I am having the same issue. I am running the pre RC with no problems so i am
wondering why this is happening. I checked with HP and found that there are
no suck programs running as it is for their business computers and I have the
dv8000. I checked on the site and it is the security for smart cards etrc.

i spoke with HP and they were no help at all.

So, there must be somethng with this RC as it runs on the pre releasae

 

[Guest]

I am having the same issue. I am running the pre RC with no problems so i am
wondering why this is happening. I checked with HP and found that there are
no suck programs running as it is for their business computers and I have the
dv8000. I checked on the site and it is the security for smart cards etrc.

i spoke with HP and they were no help at all.

So, there must be somethng with this RC as it runs on the pre releasae

 

[Guest]

That's what I discovered also...the program device is only on the business
computers. I had checked the registry, program files, startup programs,
applications, etc., and there was no reference to either the ProtectTools or
Credentials manager (as it can be called). Also HP was not able to help
either, as you noted...so it seems like it is something that RC1 is 'looking
for' on HP machines..guess it's another item MS will have to deal with.
Hopefully they will do so in the near future.

 

[Guest]

I'm with all of you on the issue. I spent an hour on the phone with the free
HP support, and they can't help. They agree the program is in there, and
it's for my own protection & if I disable it I'll lose my warranty. Also
that if I can find it in the Programs/uninstall, it's loading from the
registery with a criptic file name. Of course I knew all of that before I
called. They suggest a full system wipe and load, to get it installed. I
resist this because of all of my other loaded programs, Office & many others,
would need to be reloaded. I can save my profile & reload it, but reloading
all of the programs is too big of a hassle

I tried to escalate the call, but they weren't taking the bait. They told
me to call the apy for service guru's who can help. That number is the same,
but you ask for "HP solutions" or "Smart Friends" which may get you to
someone who can kill this Feature. ($59.99/45mins)
1-800-474-6836

PS I have a dv5163 from Costco. It gets exchanged for an AMD 64 bit system
next week, so I may wipe the drive and load it anyways just to see what it
looks like. I don't know if I'll load it at all on my new laptop.

 

[Guest]

Thanks for the info...they didn't happen to tell you what the 'cryptic' file
name was did they? I'd be willing to remove it from the registry (I have a
full disk image of my original setup, along with the recovery, so if I want
to go back, it's not a problem).

Like you, I'm not willing to pay that kind of money to find out what the
name of the file is.

 

[Guest]

No dice on the file name. I suspect they really didn't know, that's why I
escalated the call to the floor manager. He didn't know and blah blah blah.

You and I know that it's getting loaded from the regisitry, so we'll just
have to campout in there to find the culprit. I have a old program called
DLL show, which may reveal it. I'll post again when I find the little bugger.

Walt

 

[Guest]

I have the same problem. (dv8000)

Someone at Microsoft should have the name of this file, as the reported that
it should be uninstalled. My laptop is presently working with Jyly CTP with
no problem. My guest is that Protecttools conflict with Bitlocker.


HP has a new version of Protecttools that is supposed to be Vista
compatible. I wonder if installing this new version could solve the problem ?
We will have to find the right version first ! It's worth the try !

 

[Guest]

I've looked for some of the programs that other sites have posted about, but
could not find any of them in the registry. So, apparently, they're using
some non-identifiable name for it, or it doesn't exist at all and Vista RC1
is confusing some other program with it and returning a false stop. Too bad
we haven't heard from one of the MS people, perhaps they could shed some
light.

 

[Guest]

i google searched on the internet today and found a suggestion to disable
hpqwmiex.exe and then delete it from C:\Program Files\Hewlett-Packard\Shared
did anybody try this yet?

 

[Guest]

Ran across it also...
YES...it does work to disable 'ProtectTools'.
After the install went almost 'without incident' (note, almost)...the last
reboot to "starting for the first time" stalled. (using upgrade option).
Tried all the 'Windows suggestions' (including 'repair'), to no avail.
Eventually, just did a clean install. And am reloading software/documents.

Other than a 'jumpy touchpad' after Vista downloaded a NEW Touchpad driver
update, things going well. The ATI Vista beta driver seems to work well also.

Hope others have good luck also.
Jerry

 

[Guest]

I have been experiencing the same problem on a HP Pavilion dv5220. Thanks so
much for the pointer to hpqwmiex.exe. I re-named it and the upgrade from
Beta 2 to RC1 went through smoothly, start to finish, although certain steps
took a very long time, particularly the last one. Bottom line, the upgrade
did work.

Now if someone could help me get past the 1920 error I'm getting while
trying to install Symantec AntiVirus Corporate Edition for Vista RC1...

 

[Guest]

I gave up. I decided if I was going to shoot the horse, I would just go get
another horse instead! Costco has this insane 6 month return policy, So
now I own another HP but with the AMD 64 2x 2GB/120GB... I loaded RC1 64 bit
and now I can't update the BIOS to fix the power management problems!

See my other post in Hardware.

Walt the BunnyMan

 

[Guest]

I'm running into the same problem on a Pavilion dv5120us Notebook PC. At
first HP support (all contacts via email for written documentation) was
helpful, suggesting to remove "hpqwmi.exe." Since the file does not exist on
my system (presumably Vista corrupted it on install per HP) they then
suggested reformatting the hard drive. When I pressed them further for
information regarding the file and its processes, they backed off and blamed
it on Vista & they are not supporting beta versions of the OS at this time.
I'm going to do a repair reinstall of XP Pro then see if I can then find the
offending file & delete it.

 

[Guest]

I'm running into the same problem on a Pavilion dv5120us Notebook PC. At
first HP support (all contacts via email for written documentation) was
helpful, suggesting to remove "hpqwmi.exe." Since the file does not exist on
my system (presumably Vista corrupted it on install per HP) they then
suggested reformatting the hard drive. When I pressed them further for
information regarding the file and its processes, they backed off and blamed
it on Vista & they are not supporting beta versions of the OS at this time.
I'm going to do a repair reinstall of XP Pro then see if I can then find the
offending file & delete it.

 

[Guest]

Just for grins I loaded the new RC2-64 bit OS on top of the current RC1-64
system. It loaded fine, but it still wouldn't let me load the new BIOS.
Also, it didn't resolve any of my missing drivers either. Not wanting to
waste any more time, I shot the horse and used the HP OS recovery disk I made
(like a good boy).

The recovery of the original OS (XP home) went just fine. Now all the
gizmos that the laptop came with, work again. (Webcam & Photo memory flash
slots, etc.)

I loaded all of the updated system drivers & the precious new BIOS update
too. Then I loaded Partition Magic & its companion Boot manager. With any
luck I'll get a multiboot system running tomorrow. Maybe I'll just load the
RC2-32 bit version so I can (re)load the available drivers. Maybe I'll make
another partition for the 64 Bit OS if I get carried away.

I hate that I've got to reload the Orifice suite again though.

Walt the BunnyMan