My Tablet XP is definitely XP Pro SP3. OK. Prior to my rebuilding my tablet
from scratch, I was running SP2 and definitely there is a template entry to
set up the dispatching update notification to non-Admin account, please see
On my VM running XP Pro SP3 that was upgraded from SP2, I have found that
entry in the template. But I was surprised not to have found it in my Tablet
PC version. I am just wondering if it could be because I updated it to SP3
immediately after I have recovered the tablet from the Recovery CD (SP2).
Anyway I definitely used this in all my current still XP Pro SP2 machines to
make all my LUA machine to receive such notification and I did not need to
touch the Registry.
On my recently rebuilt Tablet that I subsequently updated from XP Pro SP2 to
SP3, the template was not there.
So far, I have managed to add the ElevatedNonAdmin to
and setting its value to 1 and I have received update notification. I am not
sure if this registry key is the answer when I am not using WSUS. This
registry setting is what is prescribed in the technet article Harry
suggested. Also in that article it mentioned that you could use GpEdit.msc
but I could not find the familiar entry.
Long before the infamous 'Black Screen Attack' (http://tinyurl.com/nbondk
I have always turn off 'automatic updates' preferring to select updates I am
sure are safe.
"Harry Johnston [MVP]" <email@example.com> wrote in message
> Leon wrote:
>> In XP SP2, one can configure the machine to allow non-admin user to
>> receive updates notifications. This can be configured via the GpEdit.msc.
>> This is particularly useful for those running in LUA that does not use
>> automatic updates but has chosen to be notified and then select the
>> But in XP SP3, the GpEdit.msc templates for
>> "Computer Configuration\Administrative Templates\Windows
>> Components\Windows Update" does not contain the "Allow non-administrators
>> to receive update notifications" option.
> I don't think this is true, i.e., I don't think SP3 is your problem.
> However, the information you need to use registry settings rather than
> group policy is here: