Tweet
I get this error message when attempting to create an ISO file using WinPE Builder on Windows 10. I am able to create bootable USB drives with no problems. The OS is Windows 10 Pro, 64-bit. WinPE Builder v 1.02 (105). I am running WinPE builder as administrator and the Windows kits were installed as administrator. Here are the screen shots of the error messages. Perhaps somebody out there has encountered a similar error and knows where to start looking for solutions. Thank You.
-
-
Formatting of the log is misprinting on your screenshot and preventing us from reading the full text. Can you copy the contents of the log output? You should be able to select all and do a Copy/Paste. If not, you can start WinPE Builder with -d parameter from the command line and send in the debug log for us to take a look. -
I downloaded and installed the latest Windows kits and tried it again but get the error still. Here's the text of the log:
Fri 08/16/2019 5:22:42.51: Running WinPEBuilder Batch Script...
Fri 08/16/2019 5:22:42.55: Working from base directory: C:\rmsc
Fri 08/16/2019 5:22:42.59: Temp work directory: C:\rmsc\WPB0000
Fri 08/16/2019 5:22:42.63: Running DandISetEnv.bat to Setting Environment Variables... Complete
Fri 08/16/2019 5:22:42.91: Running CopyPE... Complete
Fri 08/16/2019 5:22:50.83: Mounting WinPE Source Wim... Complete
Fri 08/16/2019 5:23:16.52: Configuring SAN Policy... Complete
Fri 08/16/2019 5:23:17.24: Adding selected packages into WinPE Image...
Fri 08/16/2019 5:23:17.28: ---Adding WinPE-HTA.cab... Complete
Fri 08/16/2019 5:23:43.80: ---Adding WinPE-Scripting.cab... Complete
Fri 08/16/2019 5:23:58.70: ---Adding WinPE-WMI.cab... Complete
Fri 08/16/2019 5:24:30.69: ---Adding WinPE-NetFx.cab... Complete
Fri 08/16/2019 5:27:33.41: ---Adding WinPE-PowerShell.cab... Complete
Fri 08/16/2019 5:27:56.58: ---Adding WinPE-StorageWMI.cab... Complete
Fri 08/16/2019 5:28:14.55: Inject Drivers into WinPE Image...
Fri 08/16/2019 5:28:14.59: Adding Program File Directory into WinPE Image...
Fri 08/16/2019 5:28:14.63: Xcopying C:\burnintest to C:\rmsc\WPB0000\mount\Program Files\BurnInTest...
Fri 08/16/2019 5:28:15.92: ---Xcopying file to WinPE Image... Complete
Fri 08/16/2019 5:28:19.66: Complete
Fri 08/16/2019 5:28:19.70: Adding additional files into WinPE Image...
Fri 08/16/2019 5:28:19.74: Copying C:\WINDOWS\Sysnative\msvfw32.dll to C:\rmsc\WPB0000\mount\Windows\System32\msvfw32.dll ...
Fri 08/16/2019 5:28:20.83: ---Copying file to WinPE Image... Complete
Fri 08/16/2019 5:28:20.92: Adding Startup Script into WinPE Image...
Fri 08/16/2019 5:28:20.96: Copying C:\rmsc\2087.tmp to C:\rmsc\WPB0000\mount\windows\System32\startnet.cm d...
Fri 08/16/2019 5:28:21.00: ---Existing file found, taking ownership to overwrite... Complete
Fri 08/16/2019 5:28:22.41: ---Copying file to WinPE Image... Complete
Fri 08/16/2019 5:28:22.49: Saving Changes and Unmounting WinPE Source Wim... Complete
Fri 08/16/2019 5:30:41.23:
---------------------------------------------------------------
I am able create bootable USB drives (32 bit and 64 bit), the error arises when trying to make an ISO file. I don't think that log file sheds any light on what is causing this. I will try again using the debug option as you suggested. Also, I'm going to setup a standalone PC with a clean install of Windows 10 Pro and run it there just in case there is something (policy/program/configuration) on my workstation causing a conflict.
When running the WinPE builder, I did not add any drivers and used the default selections for adding packages. I did notice the program has 4 packages selected by default (checked) but is actually adding 6 packages. Powershell and netfx were not selected but are added anyway. Are those required by one or more of the other packages?
Also, where will WinPe Builder put the debug log? I ran it with -d option but can't locate any log from it.
Thank You.Last edited by SIP_SUPPORT; Aug-16-2019, 04:00 PM.Comment
-
Some packages require others to be installed as well. You can find a list of dependency on Microsoft's WinPE pages. The debug log (wpeblddebug.log) is written to the user's document folder, the default path is C:\Users\PassMarkUS\Documents\PassMark\WinPEBuilde r. Don't think we tested using the ISO option recently, we'll test it here and get back to you.When running the WinPE builder, I did not add any drivers and used the default selections for adding packages. I did notice the program has 4 packages selected by default (checked) but is actually adding 6 packages. Powershell and netfx were not selected but are added anyway. Are those required by one or more of the other packages?
Also, where will WinPe Builder put the debug log? I ran it with -d option but can't locate any log from it.Comment
-
I was able to reproduce and locate the issue when trying to create an ISO. The issue was with the current build template and has been fixed in V1.2 Build 106.Don't think we tested using the ISO option recently, we'll test it here and get back to you.Comment
-
Hello Richard,
The template you provided above fixed the issue. I am able to create both 32-bit and 64-bit ISO files without a problem. I've burned both to a CD and they boot to WinPe and load BurnIn just fine. No issues running the selected tests either.
Thank You!
Comment
-
The new build template script has been packaged into the new release.
Release 1.2.106
WIN32 release 30 Aug 2019
-Fixed Bug in template script where the build process would fail when creating ISO.Comment
-
Richard, help! Trying to use WinPE to make a bootable USB and the damn thing fails before it even gets started. Below is my log file. Also getting error 255. FRUSTRATING!
Please help:
=================LOG SESSION STARTED=================
Log Started: 05-Jun-2022 1:26:10 PM
PassMark WinPE Builder V1.2.106 (C:\Users\PNW\Downloads\winpebuilder\WinPEBuilder. exe)
1:26:10 PM - Program Started with Command Line: "C:\Users\PNW\Downloads\winpebuilder\WinPEBuil der. exe" -d
1:26:10 PM - WinPE Builder Started.
1:26:10 PM - Entered LoadDefaults()
1:26:10 PM - Entered LoadStartScripts()
1:26:10 PM - Entered LoadConfigFile()
1:26:10 PM - Loading Config File C:\Users\PNW\Documents\PassMark\WinPEBuilder\wpebl dlast.cfg
1:26:10 PM - Config successfully Loaded.
1:26:10 PM - Tab Changed. Selected: 0
1:26:11 PM - Tab Changed. Selected: 1
1:26:12 PM - WinPE Tab - Enter Settings:
1:26:12 PM - WinPE Version: 10
1:26:12 PM - Arch 64-Bit
1:26:12 PM - Packages: WinPE-HTA WinPE-Scripting WinPE-WMI WinPE-StorageWMI
1:26:14 PM - WinPE Tab - Exit Settings:
1:26:14 PM - WinPE Version: WinPE for Win10
1:26:14 PM - Arch 64-Bit
1:26:14 PM - Packages: WinPE-HTA WinPE-Scripting WinPE-WMI WinPE-StorageWMI
1:26:14 PM - Tab Changed. Selected: 2
1:26:14 PM - Program / Files Tab - Enter Settings:
1:26:14 PM - Program Selected: PassMark BurnInTest Professional (1)
1:26:14 PM - Program Path: "D:\BurnInTest_10.1"
1:26:14 PM - San Policy: 1
1:26:14 PM - Number of Objects to add to WinPE image: 1
1:26:14 PM - Object: "C:\Windows\Sysnative\msvfw32.dll", "\Windows\System32", IsFolder (0), DoRecurse (0), IsRequired (1), UserActReq (0)
1:26:18 PM - Program / Files Tab - Exit Settings:
1:26:18 PM - Program Selected: PassMark BurnInTest Professional (1)
1:26:18 PM - Program Path: "D:\BurnInTest_10.1"
1:26:18 PM - San Policy: 1
1:26:18 PM - Number of Objects to add to WinPE image: 1
1:26:18 PM - Object: "C:\Windows\Sysnative\msvfw32.dll", "\Windows\System32", IsFolder (0), DoRecurse (0), IsRequired (1), UserActReq (0)
1:26:18 PM - Tab Changed. Selected: 3
1:26:18 PM - Add Drivers Tab - Enter Settings:
1:26:18 PM - Number of Drivers to inject into WinPE image: 0
1:26:19 PM - Add Drivers Tab - Exit Settings:
1:26:19 PM - Number of Drivers to inject into WinPE image: 0
1:26:19 PM - Tab Changed. Selected: 4
1:26:19 PM - Strart Script Tab - Enter Settings:
1:26:19 PM - Start Script Type: startnet (1)
1:26:19 PM - Start Script Edited: False (0)
1:26:20 PM - Strart Script Tab - Enter Settings:
1:26:20 PM - Start Script Type: startnet (1)
1:26:20 PM - Start Script Edited: False (0)
1:26:20 PM - Tab Changed. Selected: 5
1:26:20 PM - Create Tab - Enter Settings:
1:26:20 PM - WinPE Image Target: UFD (0)
1:26:20 PM - Drive: E:\
1:26:20 PM - Workpath: D:\Temp
1:26:23 PM - Entered OnCreate()
1:26:23 PM - Thread Started OnCreateThread()
1:26:23 PM - Entered GenerateBatchScriptAlt
1:26:23 PM - Work Path: D:\Temp
1:26:23 PM - INFO: Temp work directory: D:\Temp\WPB0000.
1:26:23 PM - Exited GenerateBatchScriptAlt
1:26:23 PM - Building Custom WinPE Image...
1:26:23 PM - Creating Process: Start Dir[D:\Temp] Batch File[D:\Temp\_winpebuild.cmd]
1:26:23 PM - Script Executing...
--------START BATCH SCRIPT OUTPUT------
Base Work Directory: D:\Temp
Temp work directory: D:\Temp\WPB0000
\Windows was unexpected at this time.
--------END BATCH SCRIPT OUTPUT------1:26:24 PM - Error Building WinPE Image (255): Unknown Failure
1:26:25 PM - Finished. Cleaning up...
1:26:25 PM - Deleting Batch File: D:\Temp\_winpebuild.cmd
1:26:25 PM - Deleting Temp Work Directory: D:\Temp\WPB0000
1:26:26 PM - Exited OnCreate()
Comment
-
UPDATE: Duhhh me. Make sure you have as a minimum, Deployment Tools component added when you install the main ADK for W10. With W10, the PE environment is a separate setup. Quite misleading since all we need is PE but we also need the main ADK setup run first. It failed because I installed only the PE environment, thinking this is all I needed!Originally posted by speak@ae.auone-net.jp View Post
Tip: You may want to update the WINPEBUILDER docs to reflect these minimum requirements, as I didn't see anything to that effect.
Comment
Comment