Showing results for 
Search instead for 
Did you mean: 
Level 7

WinTech in WinPE NOT BartPE

Ok... We do not use BartPE here, it’s a forbidden util (yeah - I know o.O )

We have WinPE - and I am using the WinPE guide (see below) found in the provided by Simon Hunt HERE :
and discussed HERE :

So I use all the files from the Plugin support sent me / from the KB article (and previously with the files from the Recovery folder of the 5.2.2 EEPC download) and the registry changes.reg file from the EEPC 5.2.2 / Recovery / Making a Rescue CD / Component Files folder.
Windows Registry Editor Version 5.00




"Group"="Primary Disk"

I follow the steps outlined in the attached guide, and it will run - but still shows under HELP / ABOUT :

I have verified all the files being used :

Has anyone created a WinPE (Not BARTPE) with SafeTech?
Tips? Tricks? Documentation? :confused:

Any help would be appreciated

Houston, Texas

Creating a Windows Vista PE Recovery CD with SbWintech Plug-in

This walkthrough describes how to create a customized Windows PE image with SbWinTech Plug-in. The primary tool for customizing Windows PE is PEImg, a Windows PE command-line tool. After creating a customized image, you can deploy the image to a hard disk or create a bootable Windows PE RAM disk on a CD-ROM, a USB flash drive (UFD) or a hard disk.

Windows PE is bundled in the Windows Automated Installation Kit (WAIK). You can download the Windows Automated Installation Kit (WAIK) from the Microsoft Website. This download will contain all the tools necessary to create the customized image.
Click the link below:

Step 1: Set up a Windows PE Build Environment

In this step, you create a required directory structure that supports building a Windows PE image.

On your technician computer, click Start, point to All Programs, point to Windows OPK or Windows AIK, 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. By default, all tools are installed at C:\Program Files\version\.
At the command prompt, run the Copype.cmd script. The script requires two arguments: hardware architecture and destination location. For example,

copype.cmd <architecture> <destination>
where <architecture> can be x86, amd64, or ia64 and <destination> is a path to the local directory. For example,

copype.cmd X86 C:\winpe_x86

The script creates the following directory structure and copies all the necessary files for that architecture. For example,


Step 2: Mount the Base Windows PE Image

In this step, you mount the base image to a local directory so that you can add or remove packages. At the command prompt, mount the base Windows PE image (Winpe.wim) to the \Mount directory by using ImageX. For example,

imagex /mountrw c:\winpe_x86\winpe.wim 1 c:\winpe_x86\mount

Step 3: Add Additional WINPE Packages

By using the Peimg tool, you install Windows features by using the /install option. Windows features are included with the base image (Winpe.wim) but are not installed. You can also import packages and add drivers and language packs.
Add a Windows feature to the base image by using the peimg /install command. For example,

peimg /install=<pkg> c:\winpe_x86\mount\Windows
where <pkg> denotes the package name. For example,

peimg /install=WinPE-HTA-Package c:\winpe_x86\mount\Windows
the following packages included with Windows PE and are required to be installed. Repeat this step for each package.

Package Name Description
WinPE-HTA-Package HTML application support
WinPE-MDAC-Package Microsoft Data Access Component support
WinPE-Scripting-Package Windows Script Host support
WinPE-WMI-Package Windows Management Instrumentation (WMI) support
WinPE-XML-Package Microsoft XML (MSXML) parser support

The next steps need to be carried out manually via Windows Explorer. If you are unsure of any of the information given please do not continue as attempting to do so may result in both the machine you are creating this image on and the recovery machine to become redundant!

Step 4: Adding SbWinTech Plug-in

In this step, you will need the following files to complete the SbWinTech plug-in. These files can be located under the “Recovery” folder from your SafeBoot installation CD. If you installed Endpoint Encryption (formerly called Safeboot) from the downloaded zip file from McAfee, then the “Recovery” folder is also extracted from that zip file.

• SbAlg.sys
• Safeboot.sys (also known as safeboot.w2k, this can simply be renamed to Safeboot.sys)
• SbAlg.dll
• SbComms.dll
• SbDbMgr.dll
• SbErrors.xml
• SbUILib.dll
• SbWinTech.exe
• SbXferDb.dll
• SbTokenPwd.dll
• Sbtag
• TxtSetup.OEM

With the image still mounted browse using Windows Explorer to the <mount> directory, for example


The following folders will need to be created in the following locations under the mounted image. For example,

Location Folder to be created
C:\Winpe_x86\mount\Windows\System32\ SafeBoot
C:\Winpe_x86\mount\Program Files\ SafeBoot
C:\Winpe_x86\mount\Program Files\SafeBoot\ SbAlgs
C:\Winpe_x86\mount\Program Files\SafeBoot\ SbReaders
C:\Winpe_x86\mount\Program Files\SafeBoot\ SbTokens

Once the folders have been created copy the following files to those locations.

Location Files to be copied
C:\Winpe_x86\mount\Windows\System32\SafeBoot\ Sbtag

C:\Winpe_x86\mount\Windows\System32\drivers\ SbAlg.sys
Safeboot.sys (also known as safeboot.w2k, this can simply be renamed to Safeboot.sys)

C:\Winpe_x86\mount\Program Files\SafeBoot\ SbComms.dll
C:\Winpe_x86\mount\Program Files\SafeBoot\SbAlgs\ SbAlg.dll

C:\Winpe_x86\mount\Program Files\SafeBoot\SbTokens\ SbTokenPwd.dll

Step 5: Adding Registry Keys

You will need the following file to add the necessary registry keys. This file can be located under the “Recovery\Components” folder from your SafeBoot installation CD.

• Registry Changes.reg

With the image still mounted go to START > RUN and type in the following, regedit.exe.

In the Registry Editor locate HKEY_LOCAL_MACHINE

Next go to File > Load Hive and browse to your mounted image’s System32\config directory. For example


Locate the file named SYSTEM and open (note that this file will NOT have an extension).

A Load Hive dialog box will open asking for a Key Name, you must give it the name “SafeBoot”. (disregard the “Winpe” entry in the picture).

Select OK.

If you now expand HKEY_LOCAL_MACHINE you will see we have a key entry called Safeboot, this key contains all the registry keys etc for your image under HKEY_LOCAL_MACHINE.

To add the registry keys for the SBWintech plug-in go to FILE > IMPORT and import the registry file. The registry files will automatically create the entries needed.
Select the SafeBoot key you loaded previously and go to File > Unload.

Step 6: Commit Changes to the Image

In this step, you commit the changes to the original image file (Winpe.wim) by using the ImageX /unmount option with the /commit option. For example,

imagex /unmount c:\winpe_x86\mount /commit

Step 7: Replace the Default Boot.wim File

In this step, you replace the default Boot.wim in the \ISO directory with your new customized image. The image must be called Boot.wim. For example,

copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim

Step 8: Create ISO image

You now have a customized Windows PE RAM disk image that you can place on bootable media.

At the Windows PE Tools Command Prompt, create an .iso file by using oscdimg. For example, (NOTE: this is one command line)

oscdimg -n -bc:\winpe_x86\ c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso
Burn the image (Winpe_x86.iso) to a CD-ROM
0 Kudos
4 Replies
Level 15

RE: WinTech in WinPE NOT BartPE

I have asked that (similar) question already:

It must be a secret. WinTech code seems to be unchanged since 5.1.7.
0 Kudos
Level 7

RE: WinTech in WinPE NOT BartPE

Hope that's not the answer... b/c no matter which of the files versions I use, they show 517 and none of them will decrypt / remove EEPC from machines (yes - even known GOOD just freshly out of the box, imaged, and SafeBoot 5.2.2 client installed).

And unlike AutoDomain - WinTech is SUPPOSED to be supported... but you wouldnt think so from how the Tech's and others dont respond to open case returned emails. :mad:
0 Kudos
Level 15

RE: WinTech in WinPE NOT BartPE

Yes, WinTech is not performing "Remove EEPC" properly. It destroys EEPC disk information (error e002000a happens later) but does not proceed to partition decryption.
It just hangs. To recover from that situation, one need to run Forced Crypt partiton decryption operation and Restore MBR.
0 Kudos
Level 7

Re: RE: WinTech in WinPE NOT BartPE

Good to know. We have a mixed environment and have been running into problems. I just noticed a cd I was using is 5.1.3......

0 Kudos