looksmart5000
asked on
Net framework problems at windows 10 creators edition
I had this question after viewing Corrupt .NET Framework on Server 2012 Standard causing software issues, CBS Log attached, Help!.
Hi, my name is Jose Machado and wotk in IT department of an enterprise.
A few weeks ago, my windows 10 installed updates (I think that was) and when restarted the pc, I tried to open the powershell utility and it fails to start giving an error, but the Powershell ISE opened well.
I lived with the problem a few days more and I make a search and found a webpage that says that the problem is related with one of the windows updates that corrupts the powershell instalation and recommended to uninstall framework and install it again.
I tried to say that but don't find any .net framework under Program and features control panel. I started to uncheck the framework 3.5 and 4.7 under available windows features.
The problem remains and I made another search that guides me to the page https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/ .
I tried to uninistall framework versions but the utility was running about three hours and I cancelled it.
When I restarted the pc the error continues when opening powershell.
I tried one more time without success, but it may advanced a bit because now I open powershell but now when I start the pc, it gives a few errors of application stop working due to lack of framework.
I tried to install framework 4.6 and 4.7 but it says that an advanced 4.7 version is already installed.
I had my computer joining to enterprose domain and have affraid that repairing windows 10 breaks my connection and loss of connectivity.
How may I solve the problem and restoring framework to health condition and powershell working?
I have a home computer with windows 10 Pro and never had this powershell problems.
I attached the two logs file generated by the net framework verification tool from MSDN page.
I can't open eventviewer mmc console due to this problem.
With best regards,
Jose Machado
setupverifier_errors_10-17-17_22.58..txt
setupverifier_main_10-17-17_22.58.42.txt
Hi, my name is Jose Machado and wotk in IT department of an enterprise.
A few weeks ago, my windows 10 installed updates (I think that was) and when restarted the pc, I tried to open the powershell utility and it fails to start giving an error, but the Powershell ISE opened well.
I lived with the problem a few days more and I make a search and found a webpage that says that the problem is related with one of the windows updates that corrupts the powershell instalation and recommended to uninstall framework and install it again.
I tried to say that but don't find any .net framework under Program and features control panel. I started to uncheck the framework 3.5 and 4.7 under available windows features.
The problem remains and I made another search that guides me to the page https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/ .
I tried to uninistall framework versions but the utility was running about three hours and I cancelled it.
When I restarted the pc the error continues when opening powershell.
I tried one more time without success, but it may advanced a bit because now I open powershell but now when I start the pc, it gives a few errors of application stop working due to lack of framework.
I tried to install framework 4.6 and 4.7 but it says that an advanced 4.7 version is already installed.
I had my computer joining to enterprose domain and have affraid that repairing windows 10 breaks my connection and loss of connectivity.
How may I solve the problem and restoring framework to health condition and powershell working?
I have a home computer with windows 10 Pro and never had this powershell problems.
I attached the two logs file generated by the net framework verification tool from MSDN page.
I can't open eventviewer mmc console due to this problem.
With best regards,
Jose Machado
setupverifier_errors_10-17-17_22.58..txt
setupverifier_main_10-17-17_22.58.42.txt
ASKER
Hi, I have tried many .net framework setups and always get that version 4.7 is already installed. I have unchecked the 4.7 in windows features and restart pc again but problem remains.
Now I will uncheck again .net framework and restart pc to try again tomorrow.
I have the windows version 1703 (15063.674)
Where can I download an instaler that works with creators edition and repair it ?
I'm running Iberian Portuguese (Portugal) version and in past I had problems with windows insider and at moment I don't subscribe it.
Thanks for help.
after-unckeck-4.7-version-and-before.JPG
before-unckeck-4.7-version.JPG
sccm-error.JPG
Now I will uncheck again .net framework and restart pc to try again tomorrow.
I have the windows version 1703 (15063.674)
Where can I download an instaler that works with creators edition and repair it ?
I'm running Iberian Portuguese (Portugal) version and in past I had problems with windows insider and at moment I don't subscribe it.
Thanks for help.
after-unckeck-4.7-version-and-before.JPG
before-unckeck-4.7-version.JPG
sccm-error.JPG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problem is that when I try to install or running .net setup it aborts saying that 4.7 is installed (by windows 10 edition). I could not install other.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Small note @ John: Let's be very careful with recommending the media creation tool at this time since it will upgrade to the latest windows version, which is not considered business ready ("CBB") yet. For repairs, he should use an ISO of v1703.
I understand. Version 1709 is out in production and reliable at this point.
No doubt, it's reliable, but 3rd party vendors have not adjusted to it - that's the problem.
ASKER
Hi, the DISM command gives error when is near 100%.
"Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[========================= ==95.3%=== ========== ========== ]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism. log"
One time I tried to mount ISO file as F: but I couldn't repair files
"Deployment Image Servicing and Management tool
Version: 10.0.15063.0
Image Version: 10.0.15063.0
[=========================
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.
One time I tried to mount ISO file as F: but I couldn't repair files
ASKER
I forgot to attach the output of DISM....
DISM-error.JPG
DISM-error.JPG
I would try the Repair Install I outlined above. That will likely take you to V1709 which I have running well here.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok John Hurst,
my doubt related to 1709 is that if i have errors at present, it will continues at 1709.
my doubt related to 1709 is that if i have errors at present, it will continues at 1709.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok. thanks. I will try to upgrade to 1709 now. Where you download the .net framework verifier and what should command line to repair it?
I'm asking this because has happened in other windows 10 enterprise laptops.
I'm asking this because has happened in other windows 10 enterprise laptops.
I use .NET Framework Setup Verifier to verify the version and repair any deficiencies.
The current web links I have from the current version are:
http://support.microsoft.com/kb/2698555
http://go.microsoft.com/fwlink/?LinkID=246062
Try these, and also enter .NET Framework Setup Verifier into Google.
The current web links I have from the current version are:
http://support.microsoft.com/kb/2698555
http://go.microsoft.com/fwlink/?LinkID=246062
Try these, and also enter .NET Framework Setup Verifier into Google.
ASKER
Ok. Thanks.
I upgraded windows installation to 1709 and appears that the framework problem are solved.
For now I don't get more "application stop working" at startup.
I don't know if was any update from coming from System center server that corrups instalation.
If was that, what is the update?
I saw this because I prepared a base machine with software and configurated it to work in enterprise environment and made an WIM image without joining to domain and activate applications. Then give the image to vendor that replicate for mora 50 machines that we bought.
I have turned on one machine and activate the windows and office and made last minute changes not included in the WIM image.
I left pc connected to network from one day to another to update windows and when it restarted I had problems with powershell.
My lucky is that normal user don't make use of powershell. ;)
I upgraded windows installation to 1709 and appears that the framework problem are solved.
For now I don't get more "application stop working" at startup.
I don't know if was any update from coming from System center server that corrups instalation.
If was that, what is the update?
I saw this because I prepared a base machine with software and configurated it to work in enterprise environment and made an WIM image without joining to domain and activate applications. Then give the image to vendor that replicate for mora 50 machines that we bought.
I have turned on one machine and activate the windows and office and made last minute changes not included in the WIM image.
I left pc connected to network from one day to another to update windows and when it restarted I had problems with powershell.
My lucky is that normal user don't make use of powershell. ;)
ASKER
Thanks for all help.
Doing the major Windows upgrade replaces many files and that is the reason .NET started to work.
1. Did you allow / see evidence of .NET Setup trying to repair .NET installs?
2. Go to Windows Features (in Programs and Features) and uncheck .NET. Restart and back and enable .NET and restart again.
Does that repair .NET?