A salient lesson here for anyone interested. Had .NET Frameowork 4.5 installed and running quite happily. Went to install a Stardock Fences freeware program, which would not install as it repeatedly kept asking for a v2.0 .NET Framework when I already had v 4.5. DId not make sense. In the end, I had to purchase the application before it would install correctly. I do wonder sometimes do program developers deliberately sneak in bugs to freeware programs to force freeware users to buy a full version? H'mm.

 

However that was not the end of it. First, it screwed up my perfectly-working PMDG aircraft bar the 737NGX. Then when I had done a complete re-intall on that and got that back working, I discovered that now my AivlaSoft EFB would not now load because of some .NET Framework error. So I used a clean-up tool and totally got rid of .NET. Back to trying to re-install .NET v4.5, and most annoyingly, it fails to install. Some error about netfx_Core_x64.msi, whatever that 'Microsoft-speak' means.

 

Why does Microsoft repeatedly screw up programs?

 

Anyone any idea how this can be resolved?  Thanks.

Have you got a restore point before the error?

Best to try it in "Safe Mode with Networking" initially.  Press F8 after the BIOS screen just before Windows is starting .  . .

[A rare occurrence is that the WinSxS folder becomes corrupt or one of the manifests and if that has happened - well only a clean install will fix it.]

IMHO this is not an MS error if you or a piece of software have/has created a major corruption deep in the system how can MS be blamed?

This might be useful: http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/71b094fa-106e-4415-a9b5-ebee000dc387 see the posts by pvdg42 about posts 4 and 6.  This post gets around the issue by renaming the assembly folder: http://www.sevenforums.com/software/242584-framework-net-nothing-installing.html

 

Good Luck

PeterH

Thank you for your reply, Peter and pointers therein.

 

The reason I blame MS is because there was a technical article published recently in an esteemed tech mag, and it clearly did state that MS was to blame for the problem the reader of that tech mag was experiencing. Something on the lines of  how MS tries to force IE down our throats. For starters, how do you explain that a progarm asks for NET v 2.0, and then immediately afterwards my PMDG installation goes belly-up when the PMDG installation has not the remotest connection with that Stardock Fences program except that PMDG uses .NET , and now, to my utter horror I've just discovered an Outlook program that was working about 2 hours ago, has now ceased to function all because of this damned MS product called .NET Framework?

 

EDIT: Outlook issue resolved after successfuly, at the umpteenth attempt, re-installing .NET v 4.5

Dotnet is not backward compatible so, if a program is looking for dotnet 2.0, you need to install 2.0.  For FSX, you need versions 1.1 through 4.5 (or the latest).  FSX is an old program so you need all of these versions.  You can check to see what versions you have installed (they are installed when you install FSX/Acceleration or a FSX addon if not found on your system) by looking in C:\Windows\Microsoft.net\Framework (x86)\ the various versions.  You can also run a verification tool to make sure you have everything properly installed for each version - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx.  In line with this, you also need the latest versions of Microsoft Visuals C++ 2005, 2008 and 2010 installed.  They are not backward compatible.

 

Best regards,

Jim

Hi Jim

 

I was so much hoping when I posted this that it may catch your attention coz when it comes to all things, .NET Framework, you are the man. That was precisely the website I went to get the cleaner. Gave it a good clean-out, and re-ran v 4.5 and this time it installed fully, which enabled me to recover my Outlook. Seems to have also patched up the EFB.

 

Fingers crossed I do not hit rocky shores again. This can be so maddening when it happens.

 

Thanks all the same, Jim. LInks to the MS Visual C++, please?

 

EDIT: Just ran verification tool-----all okay