What happened to the SRT Package?

**Jazkal** · December 2, 2006

I've been playing with WinPE v2.0 since early Beta. And I uninstalled all those once RTM came out. Now when I do a peimg /list command I don't see the "WinPE-SRT-Package" listed anywhere. But it is still listed in the docs as being there.

Here is my output for the list command:

Preinstallation Environment Image Setup Tool for Windows
Copyright (C) Microsoft Corporation. All rights reserved.

Culture:		  en-US
Time zone offset: (GMT-08:00) Pacific Time (US & Canada)
Time zone name:   "Pacific Standard Time" (use with /timezone)

Lang  | Version	   | Ins | Name
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-FontSupport-JA-JP-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-FontSupport-KO-KR-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-FontSupport-ZH-CN-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-FontSupport-ZH-HK-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-FontSupport-ZH-TW-Package
------+---------------+-----+-----------------------------------------------
en-US |6.0.6000.16386 |  -  | WinPE-HTA-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-HTA-Package
------+---------------+-----+-----------------------------------------------
en-US |6.0.6000.16386 |  -  | WinPE-MDAC-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-MDAC-Package
------+---------------+-----+-----------------------------------------------
en-US |6.0.6000.16386 |  -  | WinPE-Scripting-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-Scripting-Package
------+---------------+-----+-----------------------------------------------
en-US |6.0.6000.16386 |  -  | WinPE-WMI-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-WMI-Package
------+---------------+-----+-----------------------------------------------
en-US |6.0.6000.16386 |  -  | WinPE-XML-Package
------+---------------+-----+-----------------------------------------------
	  |6.0.6000.16386 |  -  | WinPE-XML-Package
------+---------------+-----+-----------------------------------------------

Listed 15 package(s).

PEIMG completed the operation successfully.

Can anyone verify it is missing from your list command also?

I'm hoping I'm just missing something really basic and stupid. I'll probably have to hit my head and say "DOH!".

**m_arth** · December 2, 2006

hello Jazkal,

I have the same problem since i use the new WAIK, i can not list the SRT package.

Did you find something ?

Mathieu

**Jazkal** · December 2, 2006

No, I'm trying to figure out how to get it back. I just want to make sure everyone is having this problem, and it's not just something stupid I'm missing.

Does anyone have the SRT package since RTM?

**sgauvin** · December 4, 2006

I have the same problem with AIK RTM.

I can`t create a BDD Deployment with BDD 2007 Beta and WAIK RTM because BDD doesn`t found Winpe SRT package.

Steve

**Jammrock** · December 4, 2006

I don't see the "WinPE-SRT-Package" listed anywhere.

Just got off the phone with MS support (being corporate has its perks from time to time). WinPE-SRT-Package was pulled at the last second because they couldn't get one of the batch files to work. Or something like that. Until they fix the WAIK, you need to extract BOOT.WIM from a bootable Vista DVD in order to get the SRT package.

I am attaching the alternate direction provided by MS. They state their documentation will update accordingly as soon as poissible. Whevever that may be:

Don't panic! This doesn't mean that it was removed from the Windows Vista DVD, but it does mean that our corporate customer's will now need to use the boot.wim from the Vista installation media to install WinRE on the harddisk or on WDS.
The OPK has not changed and WinRE is still part of that WinPE. If your customer has access to the OPK, they can use that in the meantime.
If a customer attemps to mount the WinPE.wim file from the Windows AIK and install the SRT optional component (which is WinRE) using PEIMG, SRT will not be listed as an option. Unfortunately, the “BuildWinRE.cmd” file is still included in the C:\Program Files\Windows AIK\Recovery folder. If a customer runs this batch file, it will fail because the component isn't there.
As a workaround, corporate customer's or those of us with access only to the Windows AIK can use the boot.wim from the Vista installation media to install WinRE to the harddisk or on WDS. Instructions are expected to come out soon, but until then, for those of you that want to get a head start or for those of you who receive calls on this, the instructions are posted below.
Note: I only posted Part 1 as the only thing that has changed is how you create the WinRE image. For the remaining steps, please refer to the topic titled “Walkthrough: Build a Windows Recovery Solution” in the Windows PE CHM file included in the Windows AIK. Just ignore Part 1 and replace it with the following:
Part 1: Creating a Windows RE Image
In this section, you will create a customized Windows RE Image on your technician computer.
Step 1: Copy Windows PE from the Installation Media
In this step, you will create a directory structure and set up a Windows PE image for editing.
1. On your technician computer, click Start, point to All Programs, then Windows AIK or Windows OPK, and then click Windows PE Tools Command Prompt.
The menu shortcut opens a command prompt window and automatically sets environment variables to point to all the necessary tools.
2. Create a directory for the Windows PE image and a mount point
mkdir c:\winre_image
mkdir c:\winre_mount
3. Copy the Windows PE image from the installation media using ImageX
imagex.exe /export /boot e:\sources\boot.wim 2 c:\winre_image\winre.wim “Windows Recovery Environment”
4. Mount the image using ImageX
imagex /mountrw c:\winre_image\winre.wim 1 c:\winre_mount
Step 2: Add custom Windows RE scripts
In this step, you will add a custom Window RE scripts to your image. You will create a script called winpeshl.ini that will launch the Windows RE shell at startup.
1. Using a text editor, create a file called winpeshl.ini that contains the following text:.
[LaunchApp]
AppPath=x:\sources\recovery\recenv.exe
2. Copy this file to \Windows\System32 directory in your working Windows PE directory. For example,
copy winpeshl.ini c:\winre_mount\Windows\System32
Step 3: Add mass-storage drivers (optional)
If necessary, you can include third-party drivers (.inf) in your Windows RE image by using the peimg.exe /inf command. For example,
peimg.exe /inf=<path> c:\winre_mount\Windows
Where <path> is the location of the. inf file.
Step 4: Add custom tools to Windows RE (optional)
You can customize Windows RE shell by creating an .xml file called WinREConfig.xml. WinREConfig.xml enables you to define custom support and diagnostic tools within Windows RE. This step is optional. For more information, refer to the Appendix.
Step 5: Save changes to the image
In this step, you will save all the customizations into the image file.
1. In a Windows PE Tools Command Prompt window, unmount the image by using ImageX. For example,
imagex.exe /unmount /commit c:\winre_mount
2. Copy the Windows RE image and related files onto a UFD device
copy c:\winre_image\winre.wim f:
copy “c:\Program Files\Windows AIK\Tools\PETools\x86\boot\boot.sdi” f:
copy “c:\ Program Files\Windows AIK\Recovery\setautofailover.cmd” f:
This completes Part 1 of installing Windows RE. To install the Windows RE image onto the hard disk, follow the instructions in Part 2a or Part 2b. To create recovery media, for example, a CD-ROM, you can create an .iso file of your custom image and burn it to a CD-ROM. Follow the instructions in Part 3.

Haven't tested this yet, but this should take care of the WinRE problems for the time being.

Jammrock

**Jazkal** · December 4, 2006

Thanks for the updated info.

**Jammrock** · December 5, 2006

Just started tinkering with the new instructions.

Good news: The ...mount/sources/recovery path is there with all the RE files.

Bad news: Even after mounting the WIM off the DVD, PEIMG sees the image as having been prepped with /PREP, which means you cannot add additional packages to the mount, nor can you see what is already installed. From PEIMG /?:

/prep
Optimizes the Windows PE image for size. This operation cannot be
reverted, and after /prep is issued, the /install, /uninstall,
/import, and /list commands will not function. The /lang, /inf and
/targetpath commands will continue to function. The tool will prompt
the user to confirm the command. To suppress this prompt for
scripting, specify the /f flag.

This means that you can only add scripts and drivers to the mount, and nothing else. This is not turning out as clean as I would have hoped. I guess this is better than nothing though.

Jammrock

**styxx_78** · December 5, 2006

Guys,

I noticed this too but was not too concerned given that I was not aware what the SRT was used for. Could someone explain to me what I am now missing to see if I may need it?

Thanks

**Jazkal** · December 5, 2006

It is the replacement for the recovery console.

**jamieo** · January 15, 2007

MS seems to have dropped a lot of things from Vista at the last minute - seems quite unprofessional for such a large operation.

I'm using the vista installation's boot.wim as my winre.wim which works fine but I obviously can't add any packages to it so how to support html for chm viewing etc?

Jamie

**Metzen** · September 21, 2007

Please check out this thread for an answer:

http://www.msfn.org/board/WinPE_SRT_Package_t104854.html

**Juxp0** · December 15, 2009

WinPE 3.0 (I'm using OPK, haven't tested using WAIK)

Look in the following folder: C:\Program Files\Windows OPK\Tools\PETools\x86\WinPE_FPs (x86 is architect, looks like theres one per arch type)

10/14/2009 01:49 PM <DIR> .

10/14/2009 01:49 PM <DIR> ..

10/14/2009 01:49 PM <DIR> en-us

07/14/2009 06:10 AM 9,851,612 winpe-fontsupport-ja-jp.cab

07/14/2009 06:10 AM 6,099,607 winpe-fontsupport-ko-kr.cab

07/14/2009 06:10 AM 34,077,627 winpe-fontsupport-zh-cn.cab

07/14/2009 06:10 AM 34,373,417 winpe-fontsupport-zh-hk.cab

07/14/2009 06:10 AM 34,365,117 winpe-fontsupport-zh-tw.cab

07/14/2009 06:10 AM 7,242,167 winpe-hta.cab

07/14/2009 06:10 AM 8,754,403 winpe-legacysetup.cab

07/14/2009 06:10 AM 7,517,922 winpe-mdac.cab

07/14/2009 06:10 AM 343,740 winpe-pppoe.cab

07/14/2009 06:10 AM 771,038 winpe-scripting.cab

07/14/2009 06:10 AM 2,896,718 winpe-setup-client.cab

07/14/2009 06:11 AM 2,040,838 winpe-setup-server.cab

07/14/2009 06:11 AM 4,890,370 winpe-setup.cab

07/14/2009 06:11 AM 1,891,040 winpe-srt.cab

07/14/2009 06:11 AM 404,261 winpe-wds-tools.cab

07/14/2009 06:11 AM 4,205,296 winpe-wmi.cab

16 File(s) 159,725,173 bytes

Now use DISM to inject the above package:

-copype x86 c:\bin

- DISM.exe /Mount-Wim /WimFile:C:\test\images\myimage.wim /index:1 /MountDir:C:\test\offline

-C:\bin>dism /image:.\mount /add-package /packagePath:"C:\Program Files\Windows OPK\Tools\PETools\x86\WinPE_FPs\winpe-srt.cab"

=============================================

**(captured while injeting to show process)**

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - Adding package WinPE-SRT-Package~31bf3856ad364e35~amd64~~6.1

.7600.16385

[===========================75.0%=========== ]

at 100% I got "The operation completed successfully."

=============================================

[to verify]

C:\bin>dism /image:.\mount /get-packages

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Packages listing:

Package Identity : Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35

~amd64~en-US~6.1.7600.16385

State : Install Pending

Release Type : Language Pack

Install Time : 7/14/2009 3:03 AM

Package Identity : Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~6.1.7

600.16385

State : Install Pending

Release Type : Foundation

Install Time : 7/14/2009 3:01 AM

Package Identity : WinPE-SRT-Package~31bf3856ad364e35~amd64~~6.1.7600.16385

State : Install Pending

Release Type : Feature Pack

Install Time : 12/15/2009 8:58 PM

The operation completed successfully.

=============================================

now unmount and commit:

C:\bin>dism /unmount-wim /mountdir:.\mount /commit

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Image File : C:\bin\winpe.wim

Image Index : 1

** wait for it** took a while for the progress bar to show up ..

Saving image

[==========================100.0%==========================]

Unmounting image

[==========================100.0%==========================]

The operation completed successfully.

C:\bin>

**Jazkal** · December 20, 2009

Thanks for the info, but this was a two year old dead thread discussing the problems of the very first version of the WAIK, not the current one. They have since fixed the SRT package problem.

**DyJohnnY** · March 10, 2010

Thanks for the info, but this was a two year old dead thread discussing the problems of the very first version of the WAIK, not the current one. They have since fixed the SRT package problem.

Hi,

Is it possible to use the srt package if you don't have OPK and just the WAIK?

Edited March 10, 2010 by DyJohnnY

**Jazkal** · March 11, 2010

Hi,
Is it possible to use the srt package if you don't have OPK and just the WAIK?

Yes, the WAIK has the SRT package available

Sign In

What happened to the SRT Package?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members