I think there has been a consensus on here not to move to UEFI boot until you start deploying Windows 8 or newer - too many variables and roadblocks with Windows 7.
On Tue, Jul 26, 2016 at 12:58 PM, Wilbers, Scott < [email protected]> wrote: > The one I currently have at my desk for troubleshooting has the latest > BIOS version and does not have an SSD drive. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Miller, Todd > *Sent:* Tuesday, July 26, 2016 12:30 PM > *To:* [email protected] > *Subject:* [MDT-OSD] RE: Windows 7 x64 with UEFI enabled issues on Dell > Latitude Exx30 and Exx40 models > > > > Any chance those Latitudes with problems have NVMe SSD hard disks? You > need to embed extra hotfixes into Windows 7 in order to boot from those > devices. You don’t mention whether you have checked for BIOS updates, but > if you have not, you should. > > Here’s some info from Intel… > http://download.intel.com/support/ssdc/hpssd/sb/nvme_boot_guide_332098001us.pdf > > Here’s some info from Dell… > http://www.dell.com/support/Article/us/en/04/SLN301149 > > > > Dunno if this is your problem, but we ran into similar problems on similar > models. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Wilbers, Scott > *Sent:* Tuesday, July 26, 2016 11:26 AM > *To:* [email protected] > *Subject:* [MDT-OSD] Windows 7 x64 with UEFI enabled issues on Dell > Latitude Exx30 and Exx40 models > > > > I am having an issue with deploying Windows 7 x64 to certain Dell models > with UEFI enabled. So far the models I have seen it on are Latitude Exx30 > and Latitude Exx40. > > > > I have them set to boot in UEFI mode with Legacy ROM options disabled > during the initial UEFI network boot. After it applies the image and > reboots, I started getting the Windows Boot Manager error: > > File: \EFI\Microsoft\Boot\BCD > > Status: 0xc000000d > > Info: An error occurred while attempting to read the boot configuration > data. > > > > Found forum post indicating Legacy ROM options needed to be enabled for > Windows 7 even if booting into UEFI, so I added a command line to re-enable > that during the task sequence and that resolved the issue on some of the > models (including but not limited to the OptiPlex 5040). On the Latitude > models I mentioned though, it will not boot into Windows after that. I can > hit F12 to get into the Boot Selection screen and select Windows Boot > Manager option under the UEFI list, but it doesn’t recognize that as a > valid boot option and moves on to the next, which is always the legacy mode > network boot. > > > > I even tried reversing course on these models for Windows 7 x64 and going > back to Legacy Mode, but after switching everything back in the BIOS…after > it PXE boots the task sequence isn’t able to write to the hard drive for > some reason. I get this error message after each step: > > > > Failed to save the current environment block. This is usually caused by a > problem with the program. Please check the Microsoft Knowledge Base to > determine if this is a known issue or contact Microsoft Support Services > for further assistance. > > The parameter is incorrect. (Error: 80070057; Source: Windows) > > > > I also have a reboot back into WinPE step early in the task sequence, but > it fails to stage the boot image and the task sequence errors out. I > brought up a command prompt and I’m able to see the drive with Diskpart and > the format and partition step of the task sequence completes successfully. > > > > I am at a loss on these, at this point I don’t really care whether I go > with Legacy or UEFI, I just need one of them to work. Any > suggestions/theories are welcome. > > > > Thanks in advance > > > > *------------------------------------------* > > *Scott Wilbers* > > *Network Administrator* > > Central Technology Services > > 2100 Stewart Drive > > Jefferson City, MO 65109 > > Phone: (573) 634-5600 ext 6420 > > Fax: (573) 681-6301 > > <*mailto:[email protected] <[email protected]>>* > > > > ******************************************************************************************** > > Note: > The information contained in this message may be privileged and > confidential and protected from disclosure. If the reader of this message > is not the intended recipient, or an employee or agent responsible for > delivering this message to the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, > please notify us immediately by replying to the message and deleting it > from your computer. > ******************************************************************************************** > > > > ------------------------------ > > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is > intended only for the use of the individual or entity to which it is > addressed, and may contain information that is privileged, confidential, > and exempt from disclosure under applicable law. If you are not the > intended recipient, any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify the sender immediately and delete or > destroy all copies of the original message and attachments thereto. Email > sent to or from UI Health Care may be retained as required by law or > regulation. Thank you. > ------------------------------ > ******************************************************************************************** > > Note: > The information contained in this message may be privileged and > confidential and protected from disclosure. If the reader of this message > is not the intended recipient, or an employee or agent responsible for > delivering this message to the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, > please notify us immediately by replying to the message and deleting it > from your computer. > ******************************************************************************************** > >
