WU Installed XP SP2 Despite the Regisry Hack

Anyone experienced Windows Update installing the SP2 for XP despite the
registry hack to block it? The install of the SP with the registry hack was
not suppose to expire until mid April of 2004?

Never heard of it. There is no requirement to install Service Pack 2. You
can disable automatic updates and simply go to the Windows Update website
and download and install the updates you want, when you want.

"Zach Burkett - City of Austin" <Zach Burkett - City of
> wrote in message
news3C9DCB7-3483-4EF7-A859-...
> Anyone experienced Windows Update installing the SP2 for XP despite the
> registry hack to block it? The install of the SP with the registry hack
was
> not suppose to expire until mid April of 2004?
>
>

I know there is no requirement to install it, we were attempting the block of
the install by using the registry hack. (See:
http://www.tech-recipes.com/windows_tips565.html and
http://www.microsoft.com/technet/pro.../sp2aumng.mspx),
but Windows Update allowed the install. It seems like Windows Update ignored
the 240 day grace period.

"Kevin" wrote:

> Never heard of it. There is no requirement to install Service Pack 2. You
> can disable automatic updates and simply go to the Windows Update website
> and download and install the updates you want, when you want.
>
> "Zach Burkett - City of Austin" <Zach Burkett - City of
> > wrote in message
> news3C9DCB7-3483-4EF7-A859-...
> > Anyone experienced Windows Update installing the SP2 for XP despite the
> > registry hack to block it? The install of the SP with the registry hack
> was
> > not suppose to expire until mid April of 2004?
> >
> >
>
>
>

Zach Burkett - City of Austin wrote:

> Anyone experienced Windows Update installing the SP2 for XP despite
> the registry hack to block it? The install of the SP with the
> registry hack was not suppose to expire until mid April of 2004?
Hi

Never heard about this issue.

To verify that you have applied the registry value correctly,
please run this VBScript (put it in a .vbs file):


'--------------------8<----------------------
Const HKLM = &H80000002

strComputer = "." ' use "." for local computer
Set objReg = GetObject("WinMgmts:{impersonationLevel=impersonat e}!//" _
& strComputer & "/root/default:StdRegProv")

strKeyPath = "SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate "
strValueName = "DoNotAllowXPSP2"

objReg.GetDWORDValue HKLM, strKeyPath, strValueName, intValue

If intValue = 1 Then
WScript.Echo "SP2 blocker is in place"
Else
WScript.Echo "SP2 blocker is NOT in place"
End If
'--------------------8<----------------------



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

I verified the entry stated at the url's below. The blocker is in place. It
happened to many machines; all updated from WU and most had the registry
entry. What is odd. Last month I attempted to install the SP from WU, but
denied and told to contact my administrator, which is me, I did not proceed
to remove the reg entry at that time. Then yesterday afternoon I get the
notification in the systray that there are updates avaiable. I hit the WU
site download, installed, and rebooted. SP is not installed despite the
block in the registry. Any further ideas? Why would WU allow the install of
the patch with the registry entry in place?

HMMM

"Torgeir Bakken (MVP)" wrote:

> Zach Burkett - City of Austin wrote:
>
> > Anyone experienced Windows Update installing the SP2 for XP despite
> > the registry hack to block it? The install of the SP with the
> > registry hack was not suppose to expire until mid April of 2004?
> Hi
>
> Never heard about this issue.
>
> To verify that you have applied the registry value correctly,
> please run this VBScript (put it in a .vbs file):
>
>
> '--------------------8<----------------------
> Const HKLM = &H80000002
>
> strComputer = "." ' use "." for local computer
> Set objReg = GetObject("WinMgmts:{impersonationLevel=impersonat e}!//" _
> & strComputer & "/root/default:StdRegProv")
>
> strKeyPath = "SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate "
> strValueName = "DoNotAllowXPSP2"
>
> objReg.GetDWORDValue HKLM, strKeyPath, strValueName, intValue
>
> If intValue = 1 Then
> WScript.Echo "SP2 blocker is in place"
> Else
> WScript.Echo "SP2 blocker is NOT in place"
> End If
> '--------------------8<----------------------
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Correction: SP did install despite the block in the registry.

"Zach Burkett - City of Austin" wrote:

> I verified the entry stated at the url's below. The blocker is in place. It
> happened to many machines; all updated from WU and most had the registry
> entry. What is odd. Last month I attempted to install the SP from WU, but
> denied and told to contact my administrator, which is me, I did not proceed
> to remove the reg entry at that time. Then yesterday afternoon I get the
> notification in the systray that there are updates avaiable. I hit the WU
> site download, installed, and rebooted. SP is not installed despite the
> block in the registry. Any further ideas? Why would WU allow the install of
> the patch with the registry entry in place?
>
> HMMM
>
> "Torgeir Bakken (MVP)" wrote:
>
> > Zach Burkett - City of Austin wrote:
> >
> > > Anyone experienced Windows Update installing the SP2 for XP despite
> > > the registry hack to block it? The install of the SP with the
> > > registry hack was not suppose to expire until mid April of 2004?
> > Hi
> >
> > Never heard about this issue.
> >
> > To verify that you have applied the registry value correctly,
> > please run this VBScript (put it in a .vbs file):
> >
> >
> > '--------------------8<----------------------
> > Const HKLM = &H80000002
> >
> > strComputer = "." ' use "." for local computer
> > Set objReg = GetObject("WinMgmts:{impersonationLevel=impersonat e}!//" _
> > & strComputer & "/root/default:StdRegProv")
> >
> > strKeyPath = "SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate "
> > strValueName = "DoNotAllowXPSP2"
> >
> > objReg.GetDWORDValue HKLM, strKeyPath, strValueName, intValue
> >
> > If intValue = 1 Then
> > WScript.Echo "SP2 blocker is in place"
> > Else
> > WScript.Echo "SP2 blocker is NOT in place"
> > End If
> > '--------------------8<----------------------
> >
> >
> >
> > --
> > torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> > Administration scripting examples and an ONLINE version of
> > the 1328 page Scripting Guide:
> > http://www.microsoft.com/technet/scr...r/default.mspx
> >

Zach;
How did you "hit the WU site"
Did you go to the Windows Update site and install SP-2 from there?
If so, it worked as advertised.
The fix stops Automatic Update from installing the Service Pack but
does not stop a deliberate attempt to install SP-2 such as installing
from the CD or navigating to the Windows Update site.
If that is what happened, that is by design.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/


"Zach Burkett - City of Austin"
< > wrote in message
news:962B0F05-A77F-4560-99FC-...
>I verified the entry stated at the url's below. The blocker is in
>place. It
> happened to many machines; all updated from WU and most had the
> registry
> entry. What is odd. Last month I attempted to install the SP from
> WU, but
> denied and told to contact my administrator, which is me, I did not
> proceed
> to remove the reg entry at that time. Then yesterday afternoon I
> get the
> notification in the systray that there are updates avaiable. I hit
> the WU
> site download, installed, and rebooted. SP is not installed despite
> the
> block in the registry. Any further ideas? Why would WU allow the
> install of
> the patch with the registry entry in place?
>
> HMMM

I deliberately visted the WU site, but there is another machine that does not
have the patch installed but had the registry entry to deny the install, and
we were unable to install from the WU site. It stated something about
contacting the network administrator about removing the policy.

Very odd...it seems like the WU site slipped from its 240 day period and
allowed some to install the patch. We have verified the the SUS and SMS were
not advertising or had approved the service pack.

"Jupiter Jones [MVP]" wrote:

> Zach;
> How did you "hit the WU site"
> Did you go to the Windows Update site and install SP-2 from there?
> If so, it worked as advertised.
> The fix stops Automatic Update from installing the Service Pack but
> does not stop a deliberate attempt to install SP-2 such as installing
> from the CD or navigating to the Windows Update site.
> If that is what happened, that is by design.
>
> --
> Jupiter Jones [MVP]
> http://www3.telus.net/dandemar/
>
>
> "Zach Burkett - City of Austin"
> < > wrote in message
> news:962B0F05-A77F-4560-99FC-...
> >I verified the entry stated at the url's below. The blocker is in
> >place. It
> > happened to many machines; all updated from WU and most had the
> > registry
> > entry. What is odd. Last month I attempted to install the SP from
> > WU, but
> > denied and told to contact my administrator, which is me, I did not
> > proceed
> > to remove the reg entry at that time. Then yesterday afternoon I
> > get the
> > notification in the systray that there are updates avaiable. I hit
> > the WU
> > site download, installed, and rebooted. SP is not installed despite
> > the
> > block in the registry. Any further ideas? Why would WU allow the
> > install of
> > the patch with the registry entry in place?
> >
> > HMMM
>
>
>

Jupiter Jones [MVP] wrote:

> Zach;
> How did you "hit the WU site"
> Did you go to the Windows Update site and install SP-2 from there?
> If so, it worked as advertised.
> The fix stops Automatic Update from installing the Service Pack but
> does not stop a deliberate attempt to install SP-2 such as installing
> from the CD or navigating to the Windows Update site.
> If that is what happened, that is by design.
Hi

Actually, according to the documentation, the SP2 blocker registry
value is also supposed to block delivery of Windows XP SP2 from
Windows Updates as well as Automatic Updates (but it will not block
installation from the full SP2 installation file that is e.g.
available on the SP2 CD).


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx