• SONAR
  • Beware the Microsoft .NET Framework 4 Client Profile
2012/11/06 13:43:00
Resonant Order
I was updating Win7 last night while I slept. When I woke, I restarted my machine, and everything was not ok. Sonar X1 was behaving erratically. I couldn't get it to save properly. My song file became corrupted, and the computer would hang if I tried to shut down the program. Basically, I was seeing a lot of the behavior that others have posted on the forum.

I went to the update install list, and there was a catagory above the regular updates, and they were all installed last night. They all had to do with Microsoft .NET Framework 4 Client Profile, so I deleted everything in that upper category, and left all the regular updates alone. Sonar now runs perfectly, just like it did before. Wanted to post this in case anyone else ran into the problem and they could do a search for the info.
2012/11/06 13:59:30
vaultwit
But is it safe for windows to delete that? Is it a necessary update for window to run trouble-free?
2012/11/06 14:38:14
Resonant Order
It looks like just an add on for the regular .net framework for extra functionality. It wasn't installed on my comp until last night, so I assume that everything will run fine. Maybe so programs can run on Win7 that are designed for Win8? I'll admit that I don't know exactly what it does, but I know that my comp/daw was broken when it was installed, and now it works fine. That's good enough for me. If anyone knows of why it would be critical to install, please chime in.

http://www.microsoft.com/en-us/download/details.aspx?id=17113
2012/11/06 14:39:54
panup
.NET 4 Client Profile works here perfectly with SONAR. I haven't heard anyone else using my SONAR add-on (Duckbar requires and uses .NET 4 Client Profile) reporting any issues. Yout problem may be in the update process, not in the framework itself.
2012/11/06 14:45:58
Splat
Not recommended for uninstall, applications that are written in .NET framework 4 require it. If it is installed chances are it is needed for some app.

I suspect the .Net 4 installation got corrupted somehow... if Mr Order re installs it and runs Windows update afterwards I suspect everything will be fine.
2012/11/06 14:52:26
Sidroe
I had the exact same thing happen a few months ago. It turned out the automatic update process did not go well. I had to uninstall the new updates and go to the Microsoft Update site then download and install the patch updates one at a time. After that everything was fine.
2012/11/06 16:45:49
Splat
Hey Mr Order - if you do decide to re install please don't forget to run scandisk on your hard drive first.
Cheers..
2012/11/06 23:29:18
lanstrad
Just go on Microsoft forums and see how .NET can even corrupt your entire Windows installation and prevent even Office doftware from completing install... Thoushands of users have complained about this problem. The only ''so-called solution'' offered by MS is to remove .NET and reinstall it (or newer version)... But this worked for **nobody**. This is a problem reported since Office 2007 at least (thus many still under Win XP), not resolved after almost 6 years.  The only ones who have been able to solve the problem did it... through a complete clean Windows 7 reinstall.  I choosed instead to go back to Office 2003 !

All this to say : if this MS crap can harm even MS flagship suites, just go figure out what it can do to non-MS programs...
2012/11/06 23:54:43
Splat
Been a .NET programmer since it began. Never had an issue. Once in the early days I had an issue with .NET cache which is a simple matter of clearing out a folder within the Windows folder. The only thing a faulty .NET manifest can effect is a .NET application. I suspect these issues are away from .NET, but because some apps run on it everybody blames it. .NET framework can corrupt like any application, even office (which used to corrupt regularly in its infancy well before it required NET framework libraries even existed).

> But this worked for **nobody**

As thousands apparently had the problem that must have been some survey. Guess all of them were developers and IT experts who knew what they were talking about ;). Microsoft continues to transfer it's codebase towards .NET for good reason.
2012/11/06 23:57:54
Splat

NB a better method to repair is:

a) Run scandisk on the hardrive for errors.

b) Run SFC /scannow on a command prompt as administrator.

c) Goto control panel->programs->installed programs and select the .net 4.0 entry. Now click on repair to repair .net 4.

d) Run windows update.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account