UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with

Page 20 of 42 FirstFirst ... 10181920212230 ... LastLast
  1.    #190

    Are you booting the installation media as a UEFI device so you know you're doing a UEFI install?

    Try cleaning the drive first from installer's System Recovery Options Command Line using Diskpart Clean Command

    What are the UEFI, CSM, Legacy BIOS and Boot settings choices in BIOS setup. Pictures would be helpful. Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Forums
      My Computer


  2. Posts : 71,977
    64-bit Windows 11 Pro for Workstations
       #191

    Hello Happy Hopping, :)

    You'll need to have 64-bit Windows 7 and UEFI installation media to be able to install Windows 7 with UEFI. Did you have both?
      My Computer


  3. mjf
    Posts : 5,969
    Windows 7x64 Home Premium SP1
       #192

    Just for clarification Shawn,
    I gather some install DVDs allow direct UEFI installs. If so how do you determine if you have one?
      My Computer


  4. Posts : 71,977
    64-bit Windows 11 Pro for Workstations
       #193

    I guess you really don't know for sure until trying to boot from the DVD using UEIF.
      My Computer

  5.    #194

    A correctly created 64 bit Win7 DVD should install to a UEFI System if the UEFI settings are correct in BIOS.

    There is no modification as required for flash stick install to UEFI, if that's what you're asking.
      My Computer


  6. Posts : 15
    win 7 pro 32 bit
       #195

    gregrocker said:
    Are you booting the installation media as a UEFI device so you know you're doing a UEFI install?

    Try cleaning the drive first from installer's System Recovery Options Command Line using Diskpart Clean Command

    What are the UEFI, CSM, Legacy BIOS and Boot settings choices in BIOS setup. Pictures would be helpful. Screenshots and Files - Upload and Post in Seven Forums - Windows 7 Forums
    From the below link, I seem to encounter a ghost in the machine. As you can see at the green arrow on case 1 to 4, I clearly typed out: format fs=ntfs, following the steps at the link I paste in the prev. mesg.

    And as you can see from the mesg. from win 7, it keep saying "There is no volume selected"

    So in the end, I re-enter those cmd. from "clean" to "format fs=ntfs", and somehow it works.

    There is no difference of what I type at case 1, to case 4, vs. case 5.

    Now, as to the problem I post, I FINALLY got it to work. Again, I didn't make any changes, I go thru the steps here:

    UEFI (Unified Extensible Firmware Interface) - Install Windows 7 with

    and these steps are things that I have done before, a no. of times in the past many mth.

    The drive is set as NON-Secure boot, CSM boot, under the BIOS.

    The only difference is, after I try many times, including that time consuming format, I un-plug the power cord for about 10 to 15 min. And when I re-try those steps (Step 7), it works.

    However, it does NOT creates those 3 partitions, it only creates that 1 main partition, and before you know it, win 7 says "Installing windows....copying files"

    Could some genius explain if why the first 4 try (Case 1 to 4) does not work, and case 5 works. Likewise, please explain why the first few times I go thru those steps, it doesn't work, and after I disconnect the power for 10 to 15 min., going thru those steps works?


      My Computer

  7.    #196

    The Genius is busy so I'll reply: You have installed in Legacy mode. CSM on your mobo allows this.

    If you want UEFI disable CSM and don't try to format the drive. Just delete all partitions or Clean the drive from installer CMD.
      My Computer


  8. Posts : 15
    win 7 pro 32 bit
       #197

    I don't want UEFI.

    I am only interested in knowing how to avoid this kind of problems and why is it that it works in the last time (after I disconnect the power cord)? Is it because of a "low quality" PC?
      My Computer

  9.    #198

    It doesn't appear to have completed the "create partition primary" command because the word "primary" was misspelled the first time. Therefore it had no partition to perform the format upon.

    You wouldn't want to use the "Compress" command which it was only giving as a syntax example. To compress the C drive can make it unbootable. But it didn't accept that command anyway.

    Sometimes doing a power cycle can reset things that were causing problems before. But in this case it probably was resolved by typing the command correctly. If not you could probably get by deleting the old partitions to create and format using the drive options pictured in Steps 7/8 of Clean Install Windows 7 which may be enough without the Clean command.
      My Computer


  10. NoN
    Posts : 4,166
    Windows 7 Professional SP1 - x64 [Non-UEFI Boot]
       #199

    This can be useful for troubleshooting UEFI post-installs (no hotfix):

    -Article ID: 3004880 - Last Review: October 30, 2014 - Revision: 1.0
    A UEFI mode system cannot boot after maintenance or servicing activity.

    Symptoms:
    A Unified Extensible Firmware Interface (UEFI) mode system that has a boot partition that is larger than 2 terabytes (TB) cannot boot after maintenance or servicing activity. (For example, the system cannot boot after the installation of a hotfix, defragmentation, or restoration from a backup.)

    Cause:
    The UEFI specification does not provide guidance on whether to use the traditional option ROM drivers or UEFI drivers in Class 2 UEFI mode. This has caused some UEFI implementations to prioritize traditional option ROM drivers over UEFI drivers in this mode. In some cases, these traditional-option ROM drivers support only 32-bit Logical Block Addressing (LBA) for accessing storage. This behavior limits how much storage they can access to 2 TB.

    With the wider availability of storage devices that are larger than 2 TB, you can create a Windows boot partition that is larger than 2 TB. This poses a risk in the scenario described here, because a maintenance or servicing activity (for example, the installation of a hotfix, defragmentation, or restoration from a backup) can cause a boot-critical file to be moved beyond the 2 TB limit that is imposed by 32-bit LBA. Because the pre-boot environment cannot access this file, Windows will not boot.

    Resolution:


    To reduce the effect of this issue, use one of the following options:
    • OEMs can provide a fix for this issue through a firmware update, together with either 64-bit LBA support in traditional Option ROM drivers or prioritizing UEFI drivers when traditional Option ROM is loaded. Please contact your OEM to check whether such an updated firmware exists.
    • Some UEFI implementations provide a setting to select the drivers to use in this mode. An administrator can select UEFI drivers instead of traditional Option ROM drivers to access storage larger than 2 TB.
    • The administrator can also reduce the size of the boot and OS partitions so that the last logical block address for both the boot and OS partitions is located below 2 TB. This configuration prevents boot-critical files from being accidentally relocated to an address above 2 TB, where the boot environment cannot read them.
    See also More Information chapter.

    A UEFI mode system cannot boot after maintenance or servicing activity
      My Computer


 
Page 20 of 42 FirstFirst ... 10181920212230 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:36.
Find Us