Cannot remove Microsoft .NET Framework 4 Client Profile Beta 1 & .NET Framework 4 Extended Beta 1 after uninstalling Visual Studio 2010 BETA

Question

My 8 year old son downloaded Microsoft Visual Studio 2010 BETA last month on our HP computer.  After realizing that it wasn't what he thought it would be, he uninstalled it.  Since he's uninstalled it, when we turn our computer on, we get 2 error messages:  1)  HPHC.Scheduler.exe-Unable to Locate Component   This application has failed to start because MSVCR100.dll was not found.  Re-installing the application my fix this problem.   2)  HPHC.Scheduler.exe-.NET Framework Initialization Error   C:\Windows\Microsoft.NET\Framework\v.4.0.20506\mscoreei.dll could not be loaded.   We then click Cancel on those messages and proceed to use our computer as usual.  However, we also began having an issue with our software Roxio Creator 2009.  For some reason, the installation screen would pop up sporadically if we right-clicked on something.  So, I decided to uninstall this software and reinstall it to see if it would solve that issue.  Now, I cannot reinstall it!  I had a friend take a look at the computer and he thinks it's all due to the .NET Framework entries that were not removed when my son uninstalled the Visual Studio 2010 BETA.  We cannot get rid of the following .NET Framework from our computer:   Microsoft .NET Framework 4 Client Profile Beta 1 and Microsoft .NET Framework 4 Extended Beta 1.  I was going to attempt a System Restore in Vista, but my restore points only go back one week.  My son installed the BETA in June.  Is there anyone who can tell me what to do?  Possibly what registry entries we need to delete?  I am not an extremely experienced computer user, so I'm hoping that someone can help in a computer language that I can follow.  Thank You!       

Answer 1

I am not expert on 4.0 installation/uninstallation, but I think that this information could help to figure out what was left behind after the uninstallation:
- Is there directory C:\Windows\Microsoft.NET\v4.0.20506?
- Are there any of these registry keys?
  HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\v4.0.20506
  HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Policy\Upgrades\v4.0.20506
  HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Policy\v4.0
  HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Policy\AppPatch\v4.0.205606.00000

-Karel

Answer 2

Karel,
Yes, all of the entries you mentioned are in my registry.  What should I do next? 
Thank you!

Answer 3

HPHC.Scheduler.exe-Unable to Locate Component   This application has failed to start because MSVCR100.dll was not found.  Re-installing the application my fix this problem.      

My issue is very similar - I haven't been able to uninstall the framework. To fix this, I simply reinstalled VS 2010.
What happened in my case was that the uninstall crashed in the middle, after struggling with the buttons, the only thing that worked was rollback. After the rollback is finished, I end up in a similar state as yours, where all .NET applications fail with similar error messages.
Repair hasn't been working - only the full VS2010 reinstall works.

Answer 4

I ended up reinstalling Visual Studio 2010.  Everything is now working fine again.  Unfortunately, I now have software on my computer that I really don't want or need.  Seems like I may just have to live with it.   

Answer 5

Hi,

You may have gotten into this state if VC Redist 10.0 was removed before attempting to uninstall .Net Framework 4.0 Beta 1.  Rather than reinstalling all of VS 2010 Beta 1, you can try to reinstall the .Net Framework, which will replace VC Redist.  Then I recommend removing .Net Framework first, before uninstalling VC Redist 10.0 Beta 1.

Thanks,
~Merrie

Answer 6

Uninstall and than install all .Net Frameworks. After every installation restart the computer. It works(I had the same problem)

Answer 7

I would try reinstalling the Microsoft .NET Framework 4 Client Profile Beta 1 let the system reboot then uninstall it.
Next time make sure that your son doesn't install anything without your premission on your computer or better
yet let him have his own PC or laptop to mess around with to prevent this sort of problem from occuring again.