Well.. this does not look good.. Ran .NET cleanup tool
Ran Eusing.. it found 1274 items.. told it to repair.. all the issues disappeared
and the program locked up?
Let it sit there for half an hour just in case it was doing something I could
not see... used task manager to end the program.. ran it again .. this time it
only found a few items... 12 .. files all made sense.. ran repair.. this time it finished ok.. ran it again... REBOOTED
cli.exe application error
The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
---------------------------------------
Running .NET reinstall now.. got past first hurdle.. seems to be going along
ok...
Spoke too soon.. did not get very far.. about 1/3 of the way and got an error
message..
.NET Framework has encountered a problem and needs to close. We
are sorry... blah blah blah
data within the error that they want me to waste my time sending to MicroS
EventType : clr20r3 P1 : servicemodelreg.exe P2 : 3.0.4506.648
P3 : 470e4746 P4 : servicemodelreg P5 : 3.0.0.0 P6 : 470e4746
P7 : 2b P8 : 1e P9 : system.typeloadexception
Then when you look at the actual report they want to send to microsoft
it is EXTREMELY long and they dont let you make a copy for yourself..
If that means anything to you let me know.
Clicked on the ok it ran some more then got another error message
setup.exe
EventType L visualstudio8setup P1 : 14001 P2 : 3.5.21022.08_orcas_x85_net
P3 : mc P4 : inst P5 : f P6 : dd_ca_installxwsregexe_x86.3643236f_fc70_11d3
P7 : 0 P8 : 1603 P9 : - P10 : gencomp780_{12cd
-------------------------------------
I also got an error log .. attached
---------------------------------
Right now I am going to reboot and try Windows update
then try .NET again
---------------------------------
I could try a repair again...