The regedit fix for the KB908531 problem

[Barry Watzman]

Can anyone expound on or clarify the "fix" for the KB908531 problem?
I'm talking about the fix that involves Regedit. I am a certified
computer professional and I'm very, very familiar with Regedit, and I
understand the instructions, but the value to which the newly created
DWORD key is to be renamed seems invalid.

Specifically, in this procedure:

| Option 1 - Modify the registry
| ------------------------------
|
| - (If you have multiple user accounts set up) Log onto the computer using
an
| account with Administrator privileges
|
| - Click the Start button, then click Run and type "regedit" at the prompt,
| without the quotes; this will start Registry Editor
|
| - Locate the
| HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell
| Extensions\Cached key in Registry Editor
|
| - Right click on the key and select New / DWORD Value
|
| - Rename the resulting value "{A4DF5659-0801-4A60-9607-1C48695EFDA9}
| {000214E6-0000-0000-C000-000000000046} 0x401", without the quotes
|
| - Right click the value, select Modify, and type "1" into the Value Data
| field
|
| - Close Registry Editor
|

The value "{A4DF5659-0801-4A60-9607-1C48695EFDA9}
{000214E6-0000-0000-C000-000000000046} 0x401" seems invalid.

Thanks

 

[Alan Edwards]

What is there that you don't like about it?
If you take out the quotes, put it on one line, then it looks like
many other values in the key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell
Extensions\Cached

....Alan

 

[anon]

Can anyone expound on or clarify the "fix" for the KB908531 problem?
I'm talking about the fix that involves Regedit. I am a certified
computer professional and I'm very, very familiar with Regedit, and I
understand the instructions, but the value to which the newly created
DWORD key is to be renamed seems invalid.

Just curious, invalid in what way? I assume you created the value string
as a DWORD type in the specified registry key, first, and then set the
valud data to 1.
Or are you talking about the actual value string itself, not actually
adding it to the registry?

 

[Barry Watzman]

It was not

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell
Extensions\Cached

That I was questioning, it was:

"{A4DF5659-0801-4A60-9607-1C48695EFDA9}
(000214E6-0000-0000-C000-000000000046} 0x401"

that seems invalid

 

[Barry Watzman]

I'm talking about:

"{A4DF5659-0801-4A60-9607-1C48695EFDA9}

 

[Alan Edwards]

I know what it was you were questioning and I answered accordingly.

Please explain why you consider the value invalid when it is clearly
in the same format as many other values in the specified key.

....Alan

 

[anon]

It was not


That I was questioning, it was:

"{A4DF5659-0801-4A60-9607-1C48695EFDA9}
(000214E6-0000-0000-C000-000000000046} 0x401"

that seems invalid

Well, the one thing I was a little bit confused about, myself, is because the newsgroup post (and all subsequent copying/pasting into dozens of other newsgroups over the past three days) has that value string hard-wrapped, is whether there is suppose to be a space in between each CLSID, as in
"A9} {00". I've just assumed there is, since that is how an existing value under that same registry key shows up (although that value doesn't have the " 0x401" part.)

So, unless I'm missing something, the following reg.exe command should set the registry value as intended by the original MSFT poster, but I assume someone out there will correct me if I'm wrong.

reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Cached" /v "{A4DF5659-0801-4A60-9607-1C48695EFDA9} {000214E6-0000-0000-C000-000000000046} 0x401" /t REG_DWORD /d 1 /f

 

[Alan Edwards]

Well, the one thing I was a little bit confused about, myself, is because the newsgroup post (and all subsequent copying/pasting into dozens of other newsgroups over the past three days) has that value string hard-wrapped, is whether there is suppose to be a space in between each CLSID, as in
"A9} {00". I've just assumed there is, since that is how an existing value under that same registry key shows up (although that value doesn't have the " 0x401" part.)

Yes, you are correct. The space should be there. I have 28 values
under the Cached key in similar format.
27 of them have the " 0x401" part.

....Alan