Windows Resource Protection did not find any integrity violations. Use the "Source" option to specify the location of the files that are required to restore the feature. NET Framework 3. We suggest that you follow the troubleshooting steps found on this link to resolve your issue. Was this reply helpful? Yes No. Sorry this didn't help.
Thanks for your feedback. The solution is very simple and it is a bug. If you have another situation that is related to DISM.. For us to isolate the issue, we recommend that you create a new user profile. If it's not happening on the test user profile, it only means that the current user profile is corrupted.
In case you experience the same issue on the new user profile, we suggest that you perform a System File Checker scan. This will allow you to scan for corrupted system files and restore corrupted files. You can find steps on this link. Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect.
This behavior isn't by design and has been corrected in the Volume Licensing build that was released on December 11, Use the new media for any Windows Server R2 installations. See the Resolution section to resolve this problem on servers on which you can't install features.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Use the "source" option to specify the location of the files that are required to restore the feature. This issue actually got me scratching my head for quite a bit of time because the error appeared to suggest that there was something wrong with the source files. Executing this cmdlet or using the Add Roles and Features Wizard did not allow me to successfully install the components I needed for a Lync Server install I was doing and copying the source files from the Windows Server R2 media directly onto the server did not work either.
A bit of searching on the suggested to try getting the install. After a bit of searching, I finally realized that the reason why I was getting this error was because of the following installed security update: Security Update for Microsoft Windows KB The same cmdlet that continuously failed completed successfully once I removed this security update:.
To ensure that your newly-installed role or feature is automatically updated, turn on Windows Update.
0コメント