Beware the Microsoft .NET Framework 4 Client Profile

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.

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

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.

Hey Mr Order - if you do decide to re install please don't forget to run scandisk on your hard drive first.
Cheers..

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.

That .NET 4.0 stuff kills Sonar.

I accidentally installed it when I recently did a format/fresh install of my OS and my DAW does not run right with it. It never did, but it's been so long since I did a fresh install, I forgot about the .NET 4 crap and installed it.

Oh well, time to format ... again.

Honestly, these are DAW's. They shouldn't be on the net, period. Doing all these updates is a waste of time unless we actually see something from Cakewalk that says, hey, this is broken, do this update and it will fix it. To date, I've never seen that. So ... next time I format, I'm not doing a single update and the DAW is never going to see the internet.

Nope I'm saying in order to diagnose an issue and blame something you need to come up with something technical rather than point to something and blame it, it could easily be something else and there could easily be another solution.

To say that every-time they install .NET 4 it screws their machine up clearly points to another issue in my experience, far away from .NET

The last poster said he doesn't want to connect to the internet anymore... fair enough. Somebody else however might say I BLAME THE INTERNET! And then attempt to back it up by stating "thousand have used the internet and it crashed their machines". So you see what I mean, you need to be specific before you do the finger pointing. Look in logs, attempt repairs, check your hard drive. Most non-experts should be able to handle it to be honest if they take time to google, so I apologize for sounding a little snobbish.

For instance maybe it could be firewall type software was blocking the .NET application communication with another app. The fact that Sonar does NOT run on .NET here also seems a little strange. Why are you installing in the first place? Well because there's something else running on it that you are not tell us about. That could be something that's interfacing with your drivers... etc etc.


There's a bigger picture at work here.

Thank you for all the info. I did have a couple of updates fail, and when I was having problems, the first thing I did was go back and reinstall those updates. That just made things more unstable. So far, I haven't encountered any problems with my audio programs. Sound Forge uses the .NET framework, and it runs just fine, so I'm assuming it's using an older version. I surf the internet using my studio comp, and update my progs, but I don't play games or do anything else with it. So, for now, I'm going to leave it alone. If it works, then I'm not going to mess with it.

From what I've read, the client profile is a cut down version of the full framework, and it's main purpose is for tablet devices. I don't use tablets, or even connect my phone to the comp.

Sorry bro, don't agree.

Years of broadband connected to my DAW...never an issue...

V
 
btw - liked your Squirrel Nut Zippers cover...