Problem patching with KB912919

On this page
"http://www.microsoft.com/technet/security/bulletin/ms06-001.mspx",
there was workaround to the problem until a patch was released. All you had
to do is type the following in the command: regsvr32 -u
%windir%\system32\shimgvw.dll to unregister the dll file
And when a patch became availalbe you would type the following:
regsvr32 %windir%\system32\shimgvw.dll to re-register the dll.
Okay, I followed the workaround procedure and now I cannot install the patch.
I keep getting the message "You do not have permission to update Windows XP,
please contact your system administrator".
I've checked the local security setting and all seems fine. I remember
downloading and installing security patches successfully before typing the
command in. In particular the last update "KB905915" was patched
successfully. All security settings are the same since then. The only
change I made was using the workaround.
Can any suggest a solution to this?

It may not have anything to do with the temp patch.
This sounds like one of several issues with updates in general that are
plentiful the past two weeks.

"Jerry" <> wrote in message
news:1D85F15D-50F2-4429-B1A7-...
> On this page
> "http://www.microsoft.com/technet/security/bulletin/ms06-001.mspx",
> there was workaround to the problem until a patch was released. All you
> had
> to do is type the following in the command: regsvr32 -u
> %windir%\system32\shimgvw.dll to unregister the dll file
> And when a patch became availalbe you would type the following:
> regsvr32 %windir%\system32\shimgvw.dll to re-register the dll.
> Okay, I followed the workaround procedure and now I cannot install the
> patch.
> I keep getting the message "You do not have permission to update Windows
> XP,
> please contact your system administrator".
> I've checked the local security setting and all seems fine. I remember
> downloading and installing security patches successfully before typing the
> command in. In particular the last update "KB905915" was patched
> successfully. All security settings are the same since then. The only
> change I made was using the workaround.
> Can any suggest a solution to this?
>