Sluggish builds and F5 in VS2005 since last round of XP Pro security updates

  • Thread starter Thread starter Earl
  • Start date Start date
E

Earl

This could be a coincidence, although my experience has been that it usually
is not, but it seems like since the last round of Microsoft security updates
(Dec 12, Dec. 18) were applied to my development system, VS2005 builds and
executes super-slow (even slower than the usual). I can hear the hard drive
working hard to do "something". Checked defrag and disk condition,
everything is clean there. Checked the Task Manager and could not really
discern any potential issues there. I'm running Norton AV up-to-date (no
problems with that previously) and the latest version of the Windows
Defender. Having had previous experience with security updates that run amok
(anyone remember the infamous update that blue-screened certain video
cards), I'm strongly suspecting that one of these new security update is
forcing the IDE to jump through a new set of hurdles before I do a build.
This is SERIOUSLY impacting my development iterations. Any knowledgable
folks have any idea what in the world is going on?
 
Earl said:
This could be a coincidence, although my experience has been that
it usually is not, but it seems like since the last round of
Microsoft security updates (Dec 12, Dec. 18) were applied to my
development system, VS2005 builds and executes super-slow (even
slower than the usual). I can hear the hard drive working hard to
do "something". Checked defrag and disk condition, everything is
clean there. Checked the Task Manager and could not really discern
any potential issues there. I'm running Norton AV up-to-date (no
problems with that previously) and the latest version of the
Windows Defender. Having had previous experience with security
updates that run amok (anyone remember the infamous update that
blue-screened certain video cards), I'm strongly suspecting that
one of these new security update is forcing the IDE to jump through
a new set of hurdles before I do a build. This is SERIOUSLY
impacting my development iterations. Any knowledgable folks have
any idea what in the world is going on?
Click to expand...

Uninstall all of the last updates you applied (Control Panel --> Add and
Remove Programs --> Check the "Show Updates" box and uninstall those you
installed last.) Also - if you made the mistake (IMHO) of updating to
Internet Explorer 7.0 - Revert back to 6.0 for now and see if that helps.

Come back and let us know the results.
 
I had failed to mention that I had already rolled back out of IE7 into IE6.
That was not the issue. I had also applied the latest service pack to
VS2005. Oddly, as I was sitting here opening the Control Panel, out of the
blue, I get the yellow triangle with a message "The file ...
Debugger\cscompee.dll is corrupt and unreadable." I'll tell you more as I
find out.
 
FWIW, the last round of updates DID have a hotfix for VS2005, to fix the
well-known security bug. I have had no issues w/ it, but it may be your
issue. Also, installing the latest SP for VS2005 might have actually
un-done that hotfix - typically SP installs do effectively rollback all
hotfixes and they'll need to be installed again. Or, perhaps you were
bitten by the vulnerability prior to being patched, and you've got a
baddie onboard; perform the usual scans.

Check in MSDN, they always have good advice for these sort of issues...
 
The problem was indeed a handful of corrupt files, centered around the IDE
and some .Net common files. All I can speculate is that the update blew out
these files since the corruption was only related to the Microsoft files.
Otherwise just a big coincidence that these particular files were corrupted
randomly on the disk.
 
Back
Top