Winpe 4.0 Iso Download
Rivka Licklider
As mentioned here and here, bootrec.exe and bcdedit.exe have trouble functioning from a usb-booted WinPE environment. They tend to see the wrong sets of files and they also tend to break things (which I found out the hard way). As of yet, I have found no way to get them to see any file set other than that from which they were booted, IE not the WinPE environment. Booted from an actual disk, they work fine. It seems to be an issue with usb drivers in windows PE & RE from what little I was able to find. I have also tried gandalf50's (awesome) PE4 disk (found at -win8-1update_pe-x64-or-x86-2/) with the same results.
I am a technician, though I still view myself as a novice. But I have built my own PE disks in the past and its not difficult at all. Why then does it seem impossible to get the functionality of these very necessary repair tools when the PE is booted via usb? I have found nowhere that describes a fix or any success stories or even anyone who has even attempted to get this to work. Personally, I run all my bootable tools from a single 250gb usb drive (setup with winsetupfromusb) and I greatly enjoy not being tethered to a CD/DVD binder anymore. Any help or knowledge on this matter would be greatly appreciated!
Edit: The bcdedit export operation fails. windows vista not booting The last post here contains a plausible fix. However, it requires that EasyBCD's iso caching method be used. I could re-do my huge drive with approx 30 bootable tools and this would work but its really a workaround in my mind. A creative solution regardless.
With both images mounted, copy these files/folders from the installer mount path (c:\mount) to the mount path for WinPE (c:\mount-winpe). The paths in WinSxs may look slightly differently, depending on what build of Windows you're running:
The ISO boots fine but it brings me to a command line where I have to manually type in "cctk.exe -i XE2.cctk" for it to change the BIOS settings. Reading on WinPE it appears as though the C:\Windows\System32\Startnet.cmd file is how you automate things. I would essentially like to add the "cctk.exe -i XE2.cctk" into this file but I don't know how to modify it once the ISO is built.
Looking at the cctk_x86_64_winpe_10.bat script I see that section 6 says "Add the Services" and appears to be what is written into the startnet.cmd file so I tried adding "echo X:\Command_Configure\X86_64\cctk.exe -i XE2.cctk %STARTNET% " into the bottom of this section but it didn't work.
That being said, has anyone tried to add an on screen keyboard to the WinPE startup? I have a lot of tablets to image and there are a couple places that we need to be able to type in some information.
I am working with SCCM 2012 R2 and the latest ADK. I mount the boot image using imagex, add the keyboard exe that I would like, add the line to run it in winpeshl.ini. Then i unmount, commit, and yadda yadda. When booting to this new winpe boot image the keyboard was not coming up on startup. So at this point i plug in a usb keyboard and hit F8 for the command prompt then try to run the keyboard exe from there.
Its a Panasonic FZ-G1 and touch screen works in WinPE, so I think the BIOS is ok. I do have a dock, for me, but there will be places where a dock(s) will not be available. We are pxe booting via usb to ethernet adapter (which has worked) as our tablets are configured with 1 usb port. If i had the on screen keyboard we'd be able to get multiple $20-40 usb to ethernet adapers instead of the really expensive docks. Ultimately it is going to be used by the person loading the image to put in the task sequence password and system name.
After some more digging I think my issue is that the on screen keyboards I have found are 32 bit. I need to find a 64 bit version and give that a shot. If it works I will post up what i did to get it to work.
Got you. Touch works but you need the keyboard to pop up to enter the computer name and password. We don't use a password on PXE and pre-populate SCCM with the computer name vs MAC address so don't enter anything. We use cheap Belkin USB 4 port unpowered adapters as well as the dock and they have worked with everything.
I'm trying to set up ESET SysRescue on a USB inside a WinPE environment. According to the KB about ESET NOD32 Antivirus (Link: -US/index.html?idh_rescuecd_create_winpe.htm, which includes information about SysRescue), SysRescue runs inside a WinPE environment. However, that is through the installer that comes from NOD32 as far as I can see. I am using the SysRescue Live installer (Link: ) and it seems to install just in a Linux environment on the USB. How do I set up SysRescue to install and run in a WinPE environment without having access to NOD32? NOD32 requires a purchase to download, and where I work, we do not use NOD32, but still use the ESET security solution. Would love help!
So far, I've been able to either use the SysRescue live USB creation tool to create the SysRescue Live linux environment, or create a WinPE environment using the ADK tools, but haven't been able to combine the two....
7fc3f7cf58