Unsolved
This post is more than 5 years old
1 Message
0
495
E6230/E6430/E6530 issue with WinPE 10 (1507) and CCTK
I've been using various CCTK.exe, compiled BIOS config exe's and Command Monitor (OMCI/DCIM/WMI) scripts for years in my images. I recently tried switching my SCCM boot image over to WinPE 10 form my Windows 7 image to be consistent with my other new task sequences. So, really all things equal with my E6x30 series, just a new version of WinPE, and I've seen some new really bad behavior.
When the cctk.exe command runs to make a configuration change, the systems would all lock up hard, not even the light on the caps lock key would go on or off. It doesn't matter what command you ask cctk.exe to run, even just running a -h will make it lock up. This is in WinPE.
What's worse, is that after having one of these lockups, the machines are now fubar'd somehow in system memory. I tried reverting back to WinPE 5, which will allow the systems to pass through the WinPE phase, but then as soon as Windows 7 tries to boot, it hangs hard on the Windows 7 logo draw. Just a glimpse of the colorful dots start to draw and that's it. This is on the first reboot, so mini setup hasn't run yet, and the drivers haven't even scanned to initialize against the hardware.
Two things will revert the machine back to normal:
1.) Pull the CMOS battery. After doing this, machine will boot past the logo and continue on with the SCCM task sequence.
2.) Disable PXE. After doing this, all good as well, but turn PXE back on in the BIOS, won't boot again.
This is all Legacy BIOS, no UEFI enabled.
I'm not sure if I should try and report this as a CCTK issue or a hardware issue. An thoughts from the product group? I can 100% reproduce this on three machines.