The Windows Servicing Guy

Tips and tricks from a Windows support engineer on issues related to servicing

Installing the RSAT tools on Windows 7 SP1 installations

Installing the RSAT tools on Windows 7 SP1 installations

  • Comments 70
  • Likes

We currently have a known issue with the RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en) for Windows 7 SP1 installations.  You will get an error when you attempt to install the tools on integrated SP1 clean installs.  The error is: "The update does not apply to your system".  We know about the issue and will be re-releasing the tools in April for SP1 installations.

In the meantime, a workaround for this issue is to do the following:

  1. Install Windows 7 RTM
  2. Install the RSAT tools
  3. Install Service Pack 1 via the standalone package

NOTE: If you want to attempt to install the RSAT tools on an already existing installation of SP1, see the comments below for some suggestions.  From what I can tell people are having mixed results.  However, I will say this.  If you are going to attempt to workaround the RSAT tools issue by attempting the methods below, please make note of the machines that you do it to.  There is a chance that the methods used might break the actual installation of the post SP1 released RSAT tools once they become available in April. 

--Joseph

Comments
  • Why are MSU packages that deliver additional features that are not OS components tied to service packs? Should not be the case. For example, Ultimate Extras did not fail to install on any cardinal point level, RTM or SP1 or SP2.

  • Good question, honestly, I have no idea.

    But I will ask :)

  • @someone. this is only the case for RSAT. Virtual PC installs on Sp1 without any issues.

    ok, I'll take a look at it with procmon maybe I can see something. I was able to display it in the control panel. Now I look deeper into it. Installing from an integrated ISO makes the workaround impossible.

  • Well I know why it happens, I guess I shouldnt have said it that way.  It's because of the versioning information on the files.  Why it was decided to do that way, I'm not sure.  Frankly, even if I knew I dont know that I would be stating it <G>

  • April? That's a pretty long wait ...

  • I'm just reporting what I was given, maybe it will get done earlier :)

  • I will be waiting patiently. If someone hacks this in, please post :) In future service packs, would it be possible to build these tools into Professional ----> Ultimate versions?

  • MBC;

    Someone sent me some mail about a posting on another site for getting this to work on integrated installations.  NOTE: I havent tried this but here are the steps:

    • Expand the contents of the *.msu file from the command line using the expand command.

    expand -f:* "amd64fre_GRMRSATX_MSU.msu" %temp%\RSAT

    • After extracting the contents of the .msu file, you can install it by using Package Manager (pkgmgr.exe) from the command line using the following type syntax:

    pkgmgr.exe /n:%temp%\RSAT\Windows6.1-KB958830-x64.xml

    Feel free to test it and let me know your thoughts, I'll try and make some time later today to test it

    --Joseph

  • Haven't been able to get the expand/pkgmgr to work.  Fresh install of W7 with SP1.

  • blogs.technet.com/.../rtm-rsat-and-sp1-win7-shot-over.aspx

    Says expand/pkgmgr won't work and everyone is stuck till April for an SP1 working release, no workaround at all available.

    Pretty unacceptable if you ask me.

  • I havent had time to work on the expand test, sorry that's not working for you.  But yes, Ned's blog is basically saying the same as mine, which is April for the release of RSAT.

  • Seems like administrators have been left out a lot recently.

  • How hard can it be for a company like Microsoft to quickly develop a SP1 version of the RSAT package?

  • @Joseph

    the pkgmgr doesn't work, but I have an idea which I check later.

    Btw, do you know why an user has has this WU Client version?

    WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.7.414.0 The user had this version which expired in March 2010, which leads to an Sp1 install failure:

    social.technet.microsoft.com/.../5c95bd6f-041e-4d68-b19b-304c5162aa27

  • Andre;

    That's an odd version number.  The only thing I even seen internally (scanning very quickly) is a reference to a SCCM pushed version of WU.