[WinPartners] Microsoft Outlook 2003 Release Announcement

Jonathan McIndoe Hunt jmhunt at MIT.EDU
Wed May 12 10:48:09 EDT 2004


Hi Eduardo,

This is the first we are seeing or hearing of this problem with VScan 
having issues with installations.  We will take a look into and see if we 
can figure something out.  I wonder if some recent Microsoft update, change 
to the Windows Installer version (MSI), or something else is combining to 
cause this problem in some smaller set of cases.  Has anyone else 
experienced this problem?

Thanks,
Jon

__________________________________________
Jonathan McIndoe Hunt     617.253.0172
Manager of Client Software Services
Information Services & Technology, MIT
http://web.mit.edu/ist/topics/software/
At 06:10 PM 5/11/2004, Eduardo Gonzalez wrote:
>Hello,
>
>I just received the CD for Office/Outlook 2003 and tried to install but 
>I'm having problems. When the CD is inserted, it takes a few moments to 
>load files. Once the Office Setup wizard is running, the computer comes to 
>a near halt. I looked at the Task Manager and noticed that the 
>mcshield.exe's On-Access Scan will hog the CPU (close to 100%) for about 2 
>minutes. As a result of this, I can't do much of anything on the computer. 
>I realize all programs 'should' be exited before attempting such a huge 
>installation as M$ Office is likely to be. But all I was trying to do was 
>go into a Notepad where I had written the Product Key. Again, after about 
>a couple of minutes or upon leaving the setup wizard screen, the 
>mcshield's activity goes down to normal. But if I get back to the screen 
>where I am to put in the Product Key, the computer's CPU is again taken 
>over by mcshield. Has anybody seen this? I suppose I can get around by 
>waiting long enough for VirusScan to do its thing (or I !
>  could potentially just temporarily disable the On-Access Scan thingie). 
> However, I didn't think of this as normal behavior. One shouldn't have to 
> temporarily disable the antivirus program in order to install Micro$oft's 
> product. If others are seeing this though, I think it would be helpful to 
> include a note in the Installation section of the IS&T's Office 2003 page 
> so users don't get confused.
>
>Eduardo



More information about the winpartners mailing list