Microsoft has allowed most everybody to do what everybody wants. That has resulted in exposures, but great flexibility, and a huge tech boom.
Once an exposure is open, and a lot of code is written based on that lax situation, getting all the bazillion cows back in the barn, results in strays that are in the bushes and swamps being left out.
Did you read from the front of this thread all the way through? Try just going back and reading my posts instead of shortcutting and sending to everybody monitoring this thread.
What I did was just go through the keyboard registry keys, and delete every key that did not contain system32 in it. BACK IT ALL UP FIRST. ME to XP left junk that is now checked for security purposes after this fix goes on, so MS does not let it go on
to save your a**. This might not work for you, but you need to try the posts that reportedly help, especially what Susan wrote.
I don't think importing the entries back in is a good idea. I came up from ME, and I'm running fine. now (read my posts). In fact, Microsoft has provided a security fix for a hole to XP at a huge expense to therir support, and risked this happening- strays
(I was one) that are outside the system32 folder. They even prevented the fix from going on, and affecting your system operation by not allowing it to install if there was a possibility it would hurt your system. It might be that their checking was flawed,
but look at all the strange possibilities they had to allow for. They only allowed it to go on if there was NO possibility it would affect your system. Do you see complaints about the fix being installed, and it causing problems?
If you go back and read my posts, and the others, it should give you good things to check, and if not, email Susan, but do your research first. I am not all that fond of Microsoft usually, but would you rather they just not put out security fixes for XP
because the systems are old and cludged? I came up from ME, and got my XP to install the fix, so I am glad they did what they did, though it is possible their checking to utterly protect us was not totally correct. Better that MS err on the safe side, and
not install, than install, and kill your PC, right??
Lets hope this is the way they handle things in the future, as far as ERR on the safe side, anyway, and keep delivering security fixes for XP. Good Luck!
By they way, I backed up the keyboard major key that has all the keyboard keys under it, looked at each one, and if a keyboard key did not contain system32 inside, I deleted the whole key - about 10 or more of them, and then rebooted, just in case. Err
on the safe side.
The fix went on, and I have seen no problems, though I do not have any special keyboards, etc., but I think it was just old ME suff (from Dell?).