Many devices not applicable on XP SP3 fixlet

(imported topic written by jefister91)

I have many XP SP2 devices that are not showing as applicable for XP SP3. I have found nothing in the relevance that would stop these devices from being applicable. They do not have the KB925877 update or the other registy values in the relevance, they do have at least 20 gb of free space. I could easily copy the fixlet and eliminate the relevance but am a little nervous about doing that if there is something I am missing. Any help would be appreciated. Thanks.

(imported comment written by jeremylam)

We’ll need some more information to investigate this issue. What are the results when you evaluate each of the relevance statements on one of the non-applicable computers?

(imported comment written by jefister91)

I did this on one PC yesterday and I did it on another PC today. The PC does not show the update as applicable. I remoted in and ran qna on each different relevance statement and they all came back true. See below:

Q: name of operating system as lowercase starts with “win”

A: True

Q: (language of version block of file “kernel32.dll” of system folder contains “English”) OR (exists value of key “HKLM\System\CurrentControlSet\Control\Nls\MUILanguages” of registry)

A: True

Q: not exists key “HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion” whose (exists value “ProductId” of it OR exists value “CommonFilesDir” of it) of registry AND not exists values “PROCESSOR_ARCHITECTURE” whose (it as string as lowercase = “ia64”) of keys “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment” of registry

A: True

Q: name of operating system = “WinXP”

A: True

Q: build number of operating system >= 2600

A: True

Q: (it = “” OR it = “Service Pack 1” OR it = “Service Pack 2”) of csd version of operating system

A: True

Q: (free space of drive of parent folder of system folder /1048576) >= 1500

A: True

Q: NOT exists key “HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\KB925877” of registry

A: True

(imported comment written by jefister91)

Also, I restarted all the devices, just to make sure that that was not an issue.

(imported comment written by BenKus)

Try clearing your console cache.

Ben

(imported comment written by jefister91)

I have cleared my console cache and it had no effect on the applicability of these devices. Any other ideas? Thanks.

(imported comment written by BenKus)

Maybe check and see if the agent is in “Restricted mode”… but if that doesn’t work, it sounds like someone needs to take a look at it…

You should start a support case.

Ben

(imported comment written by GRALLEN91)

What was the solution to this issue? I’m having the same thing happen to every fixlet that was released on 4/12/2011.