Yup. right click the icon choose Command Prompt(Admin) then type( or better yet cut and paste each line) without the number let each one run through(the Dism command can take a long time):
1.2.Code:Dism.exe /online /Cleanup-Image /StartComponentCleanup3Code:sfc /scannow4.Code:Dism /Online /Cleanup-Image /RestoreHealthAlso I found this at Microsoft support A .NET repair tool:Code:sfc /scannow
maybe it can help too.The Microsoft .NET Framework Repair Tool detects frequently occurring issues that affect the Microsoft .NET Framework setup or updates. The tool tries to resolve those issues by applying known fixes or by repairing the corrupted installations of the supported .NET Framework versions. The tool has an easy-to-use wizard-based user interface (UI). It also supports command line usage together with more advance options.
You can download it here if you can't repair it---
Download Microsoft .NET Framework 4.5.2 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2 from Official Microsoft Down
Yeah !! I have scanned using CMD 'sfc /scannow' which displayed some errors with logs.I dont know what to do next.And also I have already tried that .Net repair tool.It didn't resolve my issue.
CMD scannow Report:
What will happen if I run this commands?
Dism.exe /online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
This is what Dism is according to Microsoft:
It should repair the corrupt files. you might have to go through these commands with rebooting a few times(3-4) to repair every thing. the reboots are because windows is using or trying to use the files being repaired. You might also want to try it in safe mode. to remember the commands just save this page by clicking the gear icon go to file and save as, then reboot into safe mode and open an Admin Command Prompt.Deployment Image Servicing and Management (DISM) is a command-line tool used to service Windows® images offline before deployment. You can use it to install, uninstall, configure, and update Windows features, packages, drivers, and international settings. Subsets of the DISM servicing commands are also available for servicing a running operating system.
1. No, It's actually good procedure to do it once a month, especially before making a system image back-up, and after patch Tuesday updates.
Run every thing one after the other. To learn more go to this tutorial from Brink. to answer your question though componentcleanup cleans your WinSxS folder:The WinSxS folder is located in the Windows folder, for exampleC:\Windows\WinSxS. It’s the location for Windows Component Store files. The Windows Component Store is used to support the functions needed for the customization and updating of Windows. Here are some examples of how the Windows Component Store files are used:
- Using Windows Update to install new component versions. This keeps systems secure and up-to-date.
- Enabling or disabling Windows features.
- Adding roles or features using Server Manager.
- Moving systems between different Windows Editions.
- System recovery from corruption or boot failures.
- Uninstalling problematic updates.
- Running programs using side-by-side assemblies.
RestoreHealth - (recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption