locked
WTPe Build 9879 RSAT Removed and will not install RRS feed

  • Question

  • After 9879 installed, RSAT was removed and receive this message while reinstalling:

    Windows Update Standalone Installer encountered an error 0x8024001d.

    I need to get this working again asap.

    Thank You

    Thursday, November 13, 2014 5:35 PM

Answers

  • Ok I have a solution to this problem now.

    Expand WindowsTH-KB2693643-x64.msu by using the following command:

    WUSA WindowsTH-KB2693643-x64.msu /extract:<destination>

    Then from an elevated command prompt run the following command where the extracted files are located:

    pkgmgr /ip /m:<locationoffiles>\WindowsTH-KB2693643-x64.cab for example

    pkgmgr /ip /m:c:\temp\rsat\WindowsTH-KB2693643-x64.cab

    Wait for a few minutes then this will pop up:

    Restart your PC and your right to go. Tools should be installed now and working.

    Cheers

    Damon




    Thanks Damon,

    Instead of using pkgmgr I used the following command:

    DISM.exe /Online /Add-Package /PackagePath:C:\WindowsTH-KB2693643-x64.cab

    Friday, November 14, 2014 2:13 AM
  • Ok I have a solution to this problem now.

    Expand WindowsTH-KB2693643-x64.msu by using the following command:

    WUSA WindowsTH-KB2693643-x64.msu /extract:<destination>

    Then from an elevated command prompt run the following command where the extracted files are located:

    pkgmgr /ip /m:<locationoffiles>\WindowsTH-KB2693643-x64.cab for example

    pkgmgr /ip /m:c:\temp\rsat\WindowsTH-KB2693643-x64.cab

    Wait for a few minutes then this will pop up:

    Restart your PC and your right to go. Tools should be installed now and working.

    Cheers

    Damon




    Friday, November 14, 2014 12:41 AM

All replies

  • Same here. Tried some of the fixes I found online, such as clearing C:\Windows\SoftwareDistribution, but it didn't resolve the issue. Had to install them on a Windows 7 VM for now.
    Thursday, November 13, 2014 6:06 PM
  • I forgot to mention that this also breaks the PowerShell AD Module. Too bad, because I use it all the time.


    • Edited by zienky Thursday, November 13, 2014 9:29 PM
    Thursday, November 13, 2014 9:26 PM
  • I also have this problem following the installation of Build 9879...looks like it partially installs then bombs out.

    If you try and run wusa /uninstall WindowsTH-KB2693643-x64.msu you get this:

    • Edited by Damon. Johns Thursday, November 13, 2014 10:37 PM
    Thursday, November 13, 2014 10:33 PM
  • Ok I have a solution to this problem now.

    Expand WindowsTH-KB2693643-x64.msu by using the following command:

    WUSA WindowsTH-KB2693643-x64.msu /extract:<destination>

    Then from an elevated command prompt run the following command where the extracted files are located:

    pkgmgr /ip /m:<locationoffiles>\WindowsTH-KB2693643-x64.cab for example

    pkgmgr /ip /m:c:\temp\rsat\WindowsTH-KB2693643-x64.cab

    Wait for a few minutes then this will pop up:

    Restart your PC and your right to go. Tools should be installed now and working.

    Cheers

    Damon




    Friday, November 14, 2014 12:41 AM
  • Ok I have a solution to this problem now.

    Expand WindowsTH-KB2693643-x64.msu by using the following command:

    WUSA WindowsTH-KB2693643-x64.msu /extract:<destination>

    Then from an elevated command prompt run the following command where the extracted files are located:

    pkgmgr /ip /m:<locationoffiles>\WindowsTH-KB2693643-x64.cab for example

    pkgmgr /ip /m:c:\temp\rsat\WindowsTH-KB2693643-x64.cab

    Wait for a few minutes then this will pop up:

    Restart your PC and your right to go. Tools should be installed now and working.

    Cheers

    Damon




    Thanks Damon,

    Instead of using pkgmgr I used the following command:

    DISM.exe /Online /Add-Package /PackagePath:C:\WindowsTH-KB2693643-x64.cab

    Friday, November 14, 2014 2:13 AM
  • I used the DISM solution in PowerShell and it worked perfectly. I didn't even have to restart.

    Thank You So Much to both of you!


    • Edited by zienky Friday, November 14, 2014 1:12 PM
    Friday, November 14, 2014 1:09 PM
  • Thanks jmerriweather....the DISM method worked for me.  
    Monday, November 17, 2014 12:38 PM
  • Thank You!   This worked for me!
    Monday, November 24, 2014 4:58 PM
  • I have tried with all my might and still cannot get the RSAT working on Windows 10 9879. 

    The Dism command runs then errors out. When I look into the Dism.log I find loads of funny characters at the end on the log file.

    I have downloaded the RSAT several times always using the official MS site and the same issue.

    Anyone resolved this as the above instructions did not work for me. :(


    • Edited by Emilios Theori Wednesday, November 26, 2014 3:36 PM add email on replies
    Wednesday, November 26, 2014 3:36 PM
  • What is the exact error your seeing when you run the command? Can you post the relevant bits of the DISM log?

    Cheers

    Damon


    • Edited by Damon. Johns Wednesday, November 26, 2014 9:26 PM
    Wednesday, November 26, 2014 9:25 PM
  • Thanks for the reply.

    I had to revert the VM back to Windows 8.1 as I had some work to do but I will try and get this done some time today.

    Thanks

    Thursday, November 27, 2014 9:26 AM
  • I have tried with all my might and still cannot get the RSAT working on Windows 10 9879. 

    The Dism command runs then errors out. When I look into the Dism.log I find loads of funny characters at the end on the log file.

    I have downloaded the RSAT several times always using the official MS site and the same issue.

    Anyone resolved this as the above instructions did not work for me. :(



    I have the exact same issue., I believe it's because I am running the EN-GB version.
    Monday, December 1, 2014 1:16 PM
  • Thank you! I've been unable to use ADUC for a couple weeks now, and I've looked everywhere for a fix.  Nothing worked but this!

    Monday, December 8, 2014 8:11 PM
  • When I run the command:

    WUSA WindowsTH-KB2693643-x64.msu /extract:C:\Temp

    The temp folder appears but there is nothing in it...

    Any ideas?

    Thanks,

    Anthony

    Saturday, December 20, 2014 12:42 AM
  • Maybe try re-downloading the file? try extracting from an elevated command prompt?  I assume your trying to extract it on your Windows 10 TP instance?

    Cheers

    Damon

    Sunday, December 21, 2014 9:58 PM
  • Thanks Damon and jmerriweather!  I've been leaving an RDC console open to my DC for a few weeks now until I finally got tired of it and started researching.  The DISM fix worked like a champ and, as mentioned, no reboot necessary (which is good, because my reboot with Win 10 hangs at my RAID controller and takes forever to boot up).

    Thanks again!

    Tuesday, December 23, 2014 6:19 PM
  • Actually mine also hangs and takes forever to boot up / restart - is this a known issue?
    Wednesday, December 24, 2014 3:15 AM
  • This is not working on Build 10041.

    PKGMGR - Does nothing following this command.

    DISM:Error: 0x800f081e


    William Lee

    Monday, March 23, 2015 7:50 PM
  • You don't need to follow this thread for installing RSAT onto Build 10041 - Just download the January release of the tools here: http://www.microsoft.com/en-us/download/details.aspx?id=45520

    Regards

    Damon

    Tuesday, March 24, 2015 2:24 AM
  • I have Build 10049 and cannot get WindowsTH-KB2693643-x64.cab. DISM gives the error:

    Error: 0x800f081e

    The specified package is not applicable to this image.

    I'll continue Googling. Any other suggestions?

    Tuesday, April 14, 2015 5:36 PM
  • Have you attempted to install the January release of the RSAT tools yet by just running the downloaded msu file? (from http://www.microsoft.com/en-us/download/details.aspx?id=45520)
    Wednesday, April 15, 2015 12:45 AM
  • Yes, that was the first thing I tried. It gives the error "The update is not applicable to your computer". I started doing web searches and ended up in this thread.

    Any help would be appreciated. I can get by without the remote management tools for a while, but I sure hope there's a solution.

    Wednesday, April 15, 2015 1:19 PM
  • I downloaded the file again. Same file name but this time it worked. The first one must have been corrupted.

    Thanks!

    Wednesday, April 15, 2015 4:12 PM
  • I have Build 10049 and cannot get WindowsTH-KB2693643-x64.cab. DISM gives the error:

    Error: 0x800f081e

    The specified package is not applicable to this image.

    I'll continue Googling. Any other suggestions?

    Same , any suggestions ? Do we have to wait for an updated rsat  ?


    Flucato, New Orleans

    Wednesday, April 22, 2015 3:48 PM
  • same issue here though I have heard on spiceworks that the issue only seemed to pertain to windows 10 pro and that it still worked on the enterprise version. Originally I was using the enterprise version but installed the pro version since that is what we will be using in my company.
    Wednesday, April 22, 2015 9:29 PM
  • Same here on enterprise build 10074

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\rsat\WindowsTH-KB2693643-x64.cab

    Deployment Image Servicing and Management tool
    Version: 10.0.10074.0
    Image Version: 10.0.10074.0
    Processing 1 of 1 - Adding package Microsoft-Windows-RemoteServerAdministrationTools-Client-Package-TopLevel~
    31bf3856ad364e35~amd64~~6.4.9840.0
    Error: 0x800f081e

    The specified package is not applicable to this image.


    Thursday, May 21, 2015 7:31 AM
  • I am also facing the same issue above mentioned solutions never worked i got files extracted but nothing appears after running the command

    pkgmgr /ip /m:c:\temp\rsat\WindowsTH-KB2693643-x64.cab

    please tell me what to do?


    Wednesday, May 27, 2015 6:54 AM
  • Personally I gave up on this until they release an update. Removing in to one of my servers for now. Are you using enterprise or professional 10?
    Wednesday, May 27, 2015 1:55 PM
  • Has anyone had any luck with this? Is Microsoft really going to leave RSAT broken until the final release???

    Friday, June 19, 2015 11:44 AM
  • I've been able to install the RSAT tools no problems on every build for ages now. Just makes sure you get the right version here http://www.microsoft.com/en-us/download/details.aspx?id=45520)

    If your still having problems, it might be due to doing in place upgrades so maybe consider a wipe and load.

    Cheers

    Damon

    Saturday, June 20, 2015 2:20 AM
  • I have the latest version of the RSAT tools. On my personal desktop which I've been using for testing Win10 (build 10130) but also as my main productivity system, trying to run the RSAT installer gives me error 0c800b0101 (A required certificate is not within its validity period when verifying against the current system clock). I have a feeling this error has nothing to do with the RSAT installer, but the process worked fine on previous builds.

    I've also tried installing RSAT on a clean install of build 10130. The installation process goes better, but when it completes nothing has been added to the start menu and if I check under Windows Features nothing shows up there. Is there some other step I need to do to turn the tools on?

    Thanks!

    Monday, June 22, 2015 12:25 PM
  • Not that I can think of - however following the installation on the clean build I assume you did a restart? I think one is required to complete the install.

    Cheers

    Damon

     
    Monday, June 22, 2015 9:04 PM
  • Still no luck. I guess I'll just have to find alternatives...

    Tuesday, June 23, 2015 11:26 AM
  • Has anyone found the trick to install the RSAT tools? I'm still having no luck. The installer runs and closes, but even after a reboot I can't find any sign of the tools. The process worked fine in earlier builds but now I'm stumped. I've tried it on a completely clean build with the same results.

    Any suggestions would be appreciated!

    Wednesday, July 15, 2015 2:47 PM
  • Last thing I heard was a statement from Microsoft that rsat will not work with the current builds and that the official rsat release will be sometime after the 29th. I DID read a blib somewhere about someone being able to copy over the powershell modules and getting THAT to work so you way want to search for that.
    Wednesday, July 15, 2015 4:06 PM
  • Thanks for the update. I guess I can be patient for a few more weeks.

    Wednesday, July 15, 2015 5:18 PM