QB Pro 2013 Install Problems on a Windows 7 computer and Error 1935

At his point, I have uninstalled all the .NET Framework V4 programs, reinstalled Version 4.5, and followed all the steps in the above link and still have same problem.  I've also deleted and reinstalled V1.1 of .NET framework I don't understand how I could have a problem with the .NET when I have done this.  I spoke to a computer professional, and he didn't have any idea.  Can't INTUIT help??

 Hi there, has your computer professional been able to look at the .NET framework log files?  There could be a clue in those as to whats going on.  Unfortunatley, errors relating to .NET Framework (such as 1935) are Microsoft errors and not Intuit related.  The steps in the KB article are there to try and help, but depending on the severity of the system damage, there may need to be more drastic repairs to be made (registry, Windows folder, reinstall Windows, etc). 

Unfortunately it is Intuit's problem that there poorly tested software doesn't work with Microsoft's components.  I have been using Quickbooks for over ten years, and it seems like more then not, there is problems right out of the box, on brand new computers with all updates installed.  It seems to me that Intuit has some internal problems with testing there software and making it work.  The reason I'm venting is because I just tried installing QB Pro 2013 on a out of the box, updates installed Dell, and I encountered errors and it did not install... going to try the download version instead.

I agree with your assessment.   I've been able to load other programs, subsequent to my attempt with Quickbooks, without any problem.  Intuit has implied it is a WIN7 problem, but why can I load other programs?

The've also suggested I show it to my computer professional, which I don't have (I am it) and it is a small business.  Shame on intuit.

 I totally agree. This is Intuit problem. My situation is just terrible at this moment. On Friday I tried to install QB 2013 (I would never go for this upgrade from my 2010 if not pushed by Intuit). I could not install necause of .NET error. Intuit tech reffered me to Microsoft without noting that Quick Books creates it's own .NET framework file. I spent 19 hours with OMNI miscrosoft, with 3 different levels technitians - no way to fix it. Thank another 8 hours with Microsoft guru - with no luck. Finally we had to reinstall Windows. It took another 6 hours for all updates (and I lost all my editting and graphic design software I used for my business). Finally, this morning I was able to install QB 2013, used it for 10 min, after that windows asked for new updates and crashed completely. I even cannot bring it back to factory settings anymore. Result - no QB, no way to send bills (due was this weekend), no graphic software - cannot finish my project - deadline is tomorrow. I am on my way to buy the new computer at least to keep business going for tonight and tomorrow. And I am just SCARED to install Quick Books 2013 again. It does crush Win 7 system. 

Hi there, if .NET framework is corrupted, it’s something on the Windows Operating System level and needs to be addressed by a qualified IT professional or Microsoft.

We have a few tools to help aid in the repair process, but it really comes down to the level of damage the operating system has.

QuickBooks uses .NET and other various Microsoft components to function, but so do other third party programs.  If .NET is not working properly, you may experience more serious problems than QuickBooks not working.  

Sometimes reinstalling Windows is the only way to fix that level of damage.  Viruses are notorious for targeting .NET and other Microsoft components, so it’s always a good idea to make sure you have a quality AntiVirus installed and up to date.

Hope this helps :)

I don't understand about a problem with the .NET framework.  I would think MS Office uses it, and it loaded/works fine.   Additionally, I have not had this problem with any of the many other programs I've installed.   A prior version on Quickbooks worked fine.

I would think that INTUIT should be able to assist/fix the problem and not ask me to go to a computer profession.   This is not what I would call good tech support - I frankly would rate this support as an F

Also, see post below on this problem and lack of a solution.

Glad it word for you.   Unfortuneatly, this did not work for me, even when I downloaded R6.