Hi there. First of all thanks for taking the time to investigate this topic. I've always waited for someone to develop a method to implement BTS Driver Packs in a Sysprep Image. I'd like to give you some feedback and provide you with a description of all the errors that I came across. 1. When I use unpack_style2.cmd it unpacks all the Driver Packs to C:\D and creates an empty Folder C:\DP. The go_OemPnPDriversPath.cmd points to the empty C:\DP folder and won't do anything unless you edit it to "OemPnPDriversPath.cmd C:\D C:\SYSPREP\inf\sysprep.inf" without the quotes. 2. The go_hwid.cmd already points to C:\D\M, but in the HWID.txt it generates I found those lines with spaces in them: PCI\VEN_1283&DEV_8212&SUBSYS_00011283 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_00000000 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8211&SUBSYS_82111283 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_2A1D103C =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8211&SUBSYS_2A1D103C =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_813A1043 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_81381043 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8211&SUBSYS_81381043 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_2C0717F2 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_1458B000 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_1940B000 =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8212&SUBSYS_0A46174B =C:\D\M\IT\iteraid.inf PCI\VEN_1283&DEV_8211&SUBSYS_0A46174B =C:\D\M\IT\iteraid.inf I removed those spaces before I pasted the content of HWID.txt to c:\sysprep\sysprep.inf. 3. I downloaded the missing Driver Files to fix the missing QLSDM.dll in C:\d\m\q\3 and cerccin.dll in C:\d\m\d. Now the reseal Process runs fine, although it literally takes ages and then suddenly it exits with the very same Registry Error that you reported. BTW I only get this error when I use the GUI Sysprep and not the Sysprep.cmd you provided. I guess that's caused by the -quiet option int the .cmd. I don't know what causes this error, but I guess it is a faulty driver somewhere in the Driver Pack. Maybe Bashrat can comment on this, he would know best which errors occur with the Mass Storage Pack. I tried installing everything but the Mass Storage Driver Pack and that worked fine for me. I also tried using the new MassStorage Driver Pack 5.05, but that gives me the very same errors as the old one. Using the unpack style2.cmd didn't fix that error for me, so could you please describe what exactly you changed to fix it? I'm gonna keep on trying to get this thing to work for me and post all the stuff I come across.