Security Update for Outlook 2007 (KB946983)

[Steven]

Does anyone know when Microsoft will have a fix for the problems created new
Outlook profiles (when setting up a new users, the name and initials box is
hidden, the reading pane doesn't work, and Outlook cannot be closed) created
by Security Update for Outlook 2007 (KB946983)?

 

[Diane Poremsky {MVP}]

I'm not aware it’s a problem that affects the average user and I don't know
when it will be fixed. Are you using add-ons or something that would affect
it?









** Please include your Outlook version, Account type, and Windows Version
when requesting assistance **

 

[Steven]

I am not using any add-ons. This only has an effect when someone sits down
at a PC they have not used before and goes in to Outlook on that computer for
the first time. It is mainly a problem when replacing computers or getting
new employees.

 

[Steven]

I find it more than a little annoying that you don't seem to care about this
issue because you don't believe it affects the average user. I don't think
that it does affect the average home or small business user, it does affect
users in medium and large business environments though. The problem only
occurs when a user goes to a computer that they did not previously have a
user profile on, log in, and then open Outlook.

Before this so-called fix, when a user would open Outlook for the first time
they would receive a box to enter their name and initials, now this box is
hidden and users are unable to do much with Outlook until they go into
another Office app such as Word, click OK on the name and initials box, and
then go into Outlook. This results in a lot of extra help desk calls and
much wasted productivity.

I think that most Microsoft customers would agree that the proper resolution
to this issue is for Microsoft to fix their patch instead of telling people
that the problem doesn't affect the average user.

-Steven

 

[Brian Tillman]

I find it more than a little annoying that you don't seem to care
about this issue because you don't believe it affects the average
user.

Diane doesn't work for Microsoft and whether or not she agrees with you has
no bearing on how likely it is that Microsoft will fix what you consider a
problem. If you want Microsoft to address it, contact them. This newsgroup
isn't an official support channel, just a bunch of Outlook users with
varying degrees of intimacy with the program trying to help each other. We
can all have opinions on how the program should work.

 

[Susan]

I work for a large school district running Windows XP on our computers.
Recently within the last month or so I noticed that when I logged on to a
computer for the first time and opened Outlook, I had issues with the
application hanging and had to use the Task Manager to stop the program. When
you first log on to Outlook, it attempts to configure your account; not
allowing you to click OK on the window with your name when it appears. It
disappears. Then you try to open an email and either you get a pulsing
Outlook button or an orange beam that runs across the page between the menu
buttons and the sent from field. Of course then you have to close it using
task manager. If you go to another office product, open it up, click OK on
your name, and close out you are then able to open Outlook, and use it
without problems.
Our Help Desk has looked for issues with this security update, but so far
has found none. We did test by removing the update and logging on to the
computer for the first time having no problems with Outlook. After installing
it, logging on to the computer for the first time, we again had the freezing
problem again.

Yes a user can use web mail when logging on to a computer, but what is the
update doing that it causes this problem. Just wanting to make not of this
issue and have Microsoft look into it.

 

[Brian Tillman]

I work for a large school district running Windows XP on our
computers.

Please don't hijack someone else's thread. Start your own.

 

[Robert Tuck]

I was having this same problem. Thankfully, Microsoft has addressed this
issue with hotfix 950282: <a
href="http://support.microsoft.com/kb/950282/">http://support.microsoft.com/kb/950282/</a>.