Gawd I hate patching .NET… newly released tonight is a bundle of “known issues” for .NET updates including this gem:

Files in use or File Locks can Result in Framework Assembly Files being Deleted:

If the installation of framework patches fail and roll back due to assemblies in the GAC (Global Access Cache) being held “*/in use”/* or */locked/* you might find some assemblies being deleted

Updating assemblies that are *locked* or *in use”* might cause them to be inappropriately deleted.  This is a bug.  Microsoft is presently working on a fix.

Microsoft is aware of this problem and is expected to create a hotfix soon. This article will be updated when release information is known. This fix will address only the deletion of assemblies from the GAC.  The failure of the patch must be addressed separately and will not be affected by this fix. 

There are no known workarounds.  If the problem and deleting of the files has not yet occurred the best approach is to reduce the risk of any patch installations from failing by shutting down any applications that might be locking files.  See KB 2263996 “Patching of Microsoft Framework can fail with Access is denied or File in Use error” for steps to detect and prevent applications locking framework assembly files.  See More Information section for instructions on how to counter the problem if it has already occurred.See More Information section for instructions on how to counter the problem if it has already occurred.  

Geeze dudes… then don’t release the patch.  This is where that lovely “we need patched out in 60 days” blows up for me.. I want solid good patches not ones that I read through the known issues and go “oh crap!”

4 Thoughts on “Gawd I hate patching .NET…

  1. Agreed. Microsoft’s QA on patches has gone down hill over the last 9 months. SharePoint patches not completing, service packs breaking features, hotfixes being reissued…

    Might be fine for the enterprise IT departments, but certainly no good for the SMBs.

  2. Where is the rest of the bundle so that we can read them ?

  3. bradley on August 12, 2010 at 12:56 am said:

    Hint it’s in the known issues link in MS10-60

  4. Jeeze, Microsoft spreads the information out for these security bullitens so far that it’s like they don’t want you to read it. Can’t they just put all of the information in one document ?

    I followed your hint ( yes I know you posted the links already ) just for kicks and it led me to this document

    I then did a search for the word ‘known’ which led me to this document

    Which is supposed to have the known issues in it. I couldn’t find them. I even did a search on the word ‘known’ again just in case I missed it. Word not found. So I click on one of the links listed and there they are in this document

    Which is one of seven. Now do I have to look at the other six or do they just repeat the same thing ?

    Come on Microsoft.

Post Navigation