sccm sql errors since .NET WU last week

I am having a ton of problems errors since last week's .NET updates with my SCCM 2012 install.  It manifests itself into inability to create applications, deployment failures, can't copy applications and more.  My State and Update point components fail and get marked as warning or failed.  Sometimes they will come back, but then fail again later.  When copying an existing app, it says I don't have permission in the current folder and that the app has been created in the root folder.  (I am copying into the root folder - and the app never appears in the list in the console, even after restarting it.)

This one section from statesys.log appears over and over with different .SMX files:

Found new state messages to process, starting processing thread  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.266+360><thread=4604 (0x11FC)>
Thread "State Message Processing Thread #0" id:5356 started  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.267+360><thread=5356 (0x14EC)>
Started task 'Update NAP Restriction Summary'  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.272+360><thread=4604 (0x11FC)>
total chucks loaded (1)  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.273+360><thread=5356 (0x14EC)>*** *** Unknown SQL Error!  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.275+360><thread=5356 (0x14EC)>
CMessageProcessor - Encountered a non-fatal SQL error while processing  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.276+360><thread=5356 (0x14EC)>
CMessageProcessor - Non-fatal error while processing fwqctc2t.SMX  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.276+360><thread=5356 (0x14EC)>
STATMSG: ID=6104 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_SYSTEM" SYS=********* SITE=***** PID=1504 TID=5356 GMTDATE=Mon Jul 15 23:56:23.276 2013 ISTR0="fwqctc2t.SMX" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.276+360><thread=5356 (0x14EC)>
Thread "State Message Processing Thread #0" id:5356 was unable to process file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\process\fwqctc2t.SMX", moving to corrupt directory.  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.277+360><thread=5356 (0x14EC)>
total chucks loaded (0)  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.278+360><thread=5356 (0x14EC)>
Thread "State Message Processing Thread #0" id:5356 terminated normally  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.278+360><thread=5356 (0x14EC)>
CThreadMgr::ThreadTerminating - All threads have stopped running  $$<SMS_STATE_SYSTEM><07-15-2013 17:56:23.278+360><thread=5356 (0x14EC)>

I can restart the SQL services, and it appears to work for a bit - but it soon effects everything again.  I can't seem to create applications, and some of my existing applications that have been deployed since the updates are having problems finding content.

I've followed the following articles and have removed the three updates (KB2835393, KB2804576 and KB2840628), and everything seems to work again:

http://henkhoogendoorn.blogspot.ca/2013/07/unknown-sql-error-in-configmgr-after.html?spref=tw and that links to:

http://www.edugeek.net/forums/enterprise-software/118888-dotnet-update-killed-my-sccm.html

This was a fresh install of SCCM2012 on Windows Server 2008 R2 about four months ago.  Until last week, everything was running perfectly.  No config changes have taken place before/after the problem started other than the windows updates.

I guess the question I am asking is if there is a workaround other than keeping these updates off my system.  Eventually SCCM is going to just push them back out.  Or, has anyone been able to correct this with some other workaround?

curious...

Darin R.