Check my input above with address bar problem. Jon Kennedy gave correct URL
link to go to this explanation. I went through the registry edit program,
entered the new word string, and figured out how to set this newly entered
word string value to 1. I printed out the pages that the URL gave, because
you have to be careful, and the new DWORD string was long. I took this route
without a problem after reading a post on this issue yesterday. The only
issue I had was setting the new DWORD Value to 1. But I figured it out. As
I described in a post above on 4/19, you have to double click down to caches,
then right click to new, then click DWORD Value, enter the data string
{A4DF5659-0801-4A60-9607-1C48695EFDA9}
{000214E6-0000-0000-C000-000000000046} 0x401 (There is one space between
each string). When this is entered into the new DWord Value box, then point
the mouse away to blank screen area and click. This enters the new string.
Then you have to set this value to 1. You right click on the new DWORD Value
entered, select edit binary, box drops with 0000 00 00 00 00 ........,
click for cursor between first and second 00 00, backspace out first 00, then
enter 01, then click ok, then close registry and restart the computer. This
corrected the problem as described in the URL referring to security update
MS06-015 (908531). Take it slow and be careful if you wish to edit the
registry to correct this problem. It is fairly easy to do. There is no
downlad involved. Make certain that you enter the string correctly. When
the data value is set to 1, the number string associated listed below data
number column will end with (1). When you enter the new DWORD Value string,
you will see that this is all zeros inlcuding (0) at the end. After setting
to 1, it will be (1) at the end.
As I stated previously, I wish there was someway to notify all about this
issue. I have HP share to web printer and scanner, many others do as well.
In my opinion, this is an example of a Microsoft security software screwup.
The reason I say this is that so many folks use HP products. It forces the
computer user to either go into the registry to fix the problem, or take some
other action. Whatever you decide, don't contact Microsoft. They'll niclke
and dime you to death when it is not neccessary. Especially, if the
Microsoft person is unaware of this issue.