J
Josh
The behavior described in KB 940791 is happening on my system, but the "fix"
only works for a few minutes. I am running Windows 7, upgraded from Vista.
I am using Office Ultimate 2007. When I close all office applications and
delete the regkey per the KB, Word (and Outlook using Word as the editor)
function fine. But within a few minutes, the regkey has been re-written and
my mouse stops working.
This is unacceptable. "Fixes" should not require users to open and edit the
registry. They should be packages that self-install, downloadable via WU,
and they should actually fix the problem for more than 5 minutes. Loss of
funtionality as grave as using a MOUSE in a windows program should be a Sev1
bug for the Office team.
1) Is there something that I can do that will give me more than 5 minutes of
proper functionality?
2) Is MSFT going to put out a fix for their problem that was created by
another fix? It seems the issue is well-documented and over 4 years old, and
affects several platforms.
Thank you,
Josh Rice
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...e&dg=microsoft.public.word.application.errors
only works for a few minutes. I am running Windows 7, upgraded from Vista.
I am using Office Ultimate 2007. When I close all office applications and
delete the regkey per the KB, Word (and Outlook using Word as the editor)
function fine. But within a few minutes, the regkey has been re-written and
my mouse stops working.
This is unacceptable. "Fixes" should not require users to open and edit the
registry. They should be packages that self-install, downloadable via WU,
and they should actually fix the problem for more than 5 minutes. Loss of
funtionality as grave as using a MOUSE in a windows program should be a Sev1
bug for the Office team.
1) Is there something that I can do that will give me more than 5 minutes of
proper functionality?
2) Is MSFT going to put out a fix for their problem that was created by
another fix? It seems the issue is well-documented and over 4 years old, and
affects several platforms.
Thank you,
Josh Rice
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...e&dg=microsoft.public.word.application.errors