Mystery Registry Key After SP2 Installation
Jon
other SP2 installers have discovered a similar key or it owes its origins to
something else. Thanks.
HKEY_CURRENT_USER\S\P\2846389128
Jon
Thorsten Matzner
I do not have this key here. Export it via File > Export and then
delete it to see if it is really necessary. If so, you can restore it
with the exported file later.
--
(tm)
Maurice N ~ MVP
Did not find "2846389128" doing a search in my XP registry. (Running SP2)
btw, I'm not familiar with your specific subkeys. Are \S\P your abbreviation?
--
Maurice N
MVP Windows - Shell / User
-----
Jon
related to the Service Pack. Clearly not.
Nothing via Google that I could find about it.
[The S and P were specific one-letter key names
ie
HKEY_CURRENT_USER > S > P > 2846389128
It had these value keys
"Prompt"=dword:00000000
"MsgPrivacy"=dword:00000001]
Have exported / deleted it and will see what happens, if anything.
Jon
"Maurice N ~ MVP" <mau...@mvps.org> wrote in message
news:Ov2JECHi...@TK2MSFTNGP11.phx.gbl...
Alex Nichol
I have the S but no subkey in it
--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. Al...@mvps.D8E8L.org (remove the D8 bit)
Peter
--
Peter.
Toronto, Canada.
Windows XP Home SP2.
Pentium4 Dual HT @ 3.0ghz, 160gb HD, 1gb DDR.
"Alex Nichol" <alexn....@ntlworld.delete.com> wrote in message
news:eetji0d4vqd3265t1...@4ax.com...
Haggis
"Peter" <0spam0 AT rogers DOT com> wrote in message
news:eQDRq6Ri...@TK2MSFTNGP10.phx.gbl...
i have one ...different number tho....msgprivacy ?
Jon
Jon
"Haggis" <bingsna...@THIShotmail.com> wrote in message
news:OVD4krS...@TK2MSFTNGP10.phx.gbl...
Peter
--
Peter.
Toronto, Canada.
Windows XP Home SP2.
Pentium4 Dual HT @ 3.0ghz, 160gb HD, 1gb DDR.
"Jon" <Email_...@SomewhereOrOther.com> wrote in message
news:eQ9UpOTi...@TK2MSFTNGP10.phx.gbl...
Jon
Jon
"Peter" <0spam0 AT rogers DOT com> wrote in message
news:O1mcIgTi...@TK2MSFTNGP11.phx.gbl...
Jon
"Prompt"=dword:00000000
"MsgPrivacy"=dword:00000001
it's probably more likely to be related to a program like Windows Messenger,
than to SP2 eg an add-in I've installed. Not a major problem anyhow, was
just curious.
Jon
"Peter" <0spam0 AT rogers DOT com> wrote in message
news:O1mcIgTi...@TK2MSFTNGP11.phx.gbl...
OShah
news:uZ18AcUi...@tk2msftngp13.phx.gbl:
>
> From the names of the 2 value keys
>
> "Prompt"=dword:00000000
> "MsgPrivacy"=dword:00000001
>
> it's probably more likely to be related to a program like Windows
> Messenger, than to SP2 eg an add-in I've installed. Not a major problem
> anyhow, was just curious.
>
>
I know it's way too late to post on this topic, and you're probably no
longer reading this newsgroup, but JIC, I've posted an analysis of this
problem at microsoft.public.windowsxp.messenger
Mystery Reg Key caused by Windows messenger:
news:Xns9565AE00...@207.46.248.16
Well it's not exactly the same problem, but it is similar, and possibly
related, particularly if Windows Messenger created your key.
--
------------------------------------------------------------------------
oshah
Control Panel -> System -> Advanced -> Error Reporting -> Choose Programs
-> Do not report errors for these programs:
Acrobat.exe
waol.exe
------------------------------------------------------------------------
Jon
Thanks for your reply.
I didn't repost to my original thread because I wasn't sure anyone was
interested, but what I did discover is that the key
HKEY_CURRENT_USER\S\P\2846389128
(where the final number may vary according to machine)
was recreated, (if I deleted it) each time I ran Windows Messenger version
4.7.3000
It is NOT created, when running the version of Windows Messenger prior to XP
Service Pack 2 (ie version 4.7.2009)
Thanks for your analysis. Pleased that it appears to be a coding error
rather than anything else.
Jon
"OShah" <nos...@aol.com> wrote in message
news:Xns9565EF99...@207.46.248.16...
Jon
Windows Messenger 5.0.0.468 case is that the key also seems to be created
with Windows Messenger 4.7.3000 when
i internet access is readily available
ii Windows Messenger is not blocked by a firewall
ii and when signing in is as normal
Strange
Jon
"Jon" <Email_...@SomewhereOrOther.com> wrote in message
news:uHLTJJAn...@tk2msftngp13.phx.gbl...
Jon
HKEY_CURRENT_USER\S\P\4876289128
doesn't vary according to machine, but rather by the particular .net
password that you log in with.
So if you log onto your account using a different machine then the SAME
number is created in the subkey ie 4876289128
Also, if you use a different .net password from the same account, on the
same machine, then a separate key is created for that one, again with a
uniquely identifying number
Jon
"Jon" <Email_...@SomewhereOrOther.com> wrote in message
news:%23RD14UA...@TK2MSFTNGP15.phx.gbl...
OShah
@tk2msftngp13.phx.gbl:
>
> Actually I was wrong. The number in the key
>
> HKEY_CURRENT_USER\S\P\4876289128
>
> doesn't vary according to machine, but rather by the particular .net
> password that you log in with.
>
> So if you log onto your account using a different machine then the SAME
> number is created in the subkey ie 4876289128
>
> Also, if you use a different .net password from the same account, on the
> same machine, then a separate key is created for that one, again with a
> uniquely identifying number
>
> Jon
>
>
>
I was wrong, you are still reading!
In your case, that key should have been "PerPassportSettings" instead of
P. The reg key setting is a hash of your passport ID, and that key stores
settings for that user id.
This either suggests that the problem code is being utilised multiple
times, or that my spot is not the only part which suffers from WCHAR
detection troubles.
It's a good thing that Messenger is calling the char version with a
wchar_t string, and not the other way round (calling RegCreateKeyExW with
char strings). In that case you would get keys with garbage letters in
them, or a potential buffer overflow.