Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Search the Community

Showing results for tags 'UEFI'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server 2008/2012/2016
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)
  • X's Concepts
  • The Compaq Computer Corporation Club's Discussion

Forms

  • Contact MSFN
    • Your Name
    • Member Name
    • Email Address
    • Subject
    • Contact Message
  • Submit News
    • News Title
    • Your Mail or Member Name
    • News
    • News Link/Source

Calendars

There are no results to display.

There are no results to display.


Found 5 results

  1. Is it possible to set up a Windows virtual machine with 32-bit UEFI in VMware Workstation? I couldn't find an setting to configure UEFI. Please help!
  2. Virtualize Win8.1: BIOS + MBR Physical Partition > to > WIM Image > to > UEFI GPT VHD Virtualizing Win8.1 from BIOS + MBR Physical Partition > to > .WIM Image > to > UEFI GPT .VHD Sometime last year I found out about Native boot VHDs and tried to go that way for good. There were some issues with hardware and OS (Win7 at the time) not working out and lot of new things that I was learning about VHDs. Anyways, that confusion, learning and failure led to a better path So this 2015, I figured out how to get VHDs (with Fresh Win 8.1 Installs via Install.WIM DISM Apply Image) to Native Boot on Surface Pro 3 (Sp3). I am going to attempt doing the following steps using DISM/ ImageX: MBR [Customized Win 8.1] (Physical) > Create Image > [Customized Win 8.1 .WIM] (Virtual - File based so - No sectors or MBR/GPT?? ). [Customized Win 8.1 .WIM] (Virtual) > Apply Image > [Empty New GPT .VHD] (on SP3) My thought is that by going to .WIM I bypass the whole converstion drama between MBR/BIOS & GPT/UEFI as the .WIM is agnostic of both of them? Is this a valid thought or not? Thoughts? NOTE: I can.. try out the above with creating a small FRESH MBR Windows 8.1 partition on X61T/ T61 and then doing the above 2 steps. Convert it to a .WIM and then applying to a GPT .VHD I am guessing a SYSPREP is recommended somewhere in between. Someone somewhere also mentioned doing Sysprep in a VM/ Hyper V instead? Or is it not needed? Thoughts? Where and how would you recommend applying the SYSPREP?
  3. So as I've noted elsewhere before, WinPE for Windows 8 and 8.1 will use a display's native resolution if the hardware supports GOP in UEFI mode. Windows 10 seems to be the same way... and this WILL be a problem. Testing on a notebook with a native 4k display... installation is slightly... difficult: Picture is bad but it gets the point across. When I get hands-on with this specific system, I will get clearer pictures. *NOTE: This will be a problem for Windows 8/8.1 as well.
  4. On a BIOS PC, most folks use Grub4DOS to boot ISO images. But how to boot them on UEFI PC, especially without Legacy CSM Mode, since Grub4DOS doesn't support UEFI? Taking a popular Acronis True Image Home (ATIH2014) ISO as an example (either Linux or WinPE 5.0 based, or better BOTH), can someone explain, how to boot an ISO on UEFI Windows 8.1 PC? I found one example of booting seemingly WinPE-based UEFI ATIH2014 (release unknown) by Grub2. That didn't work for me - couldn't find dat8.dat and dat9.dat files in Boot.bif image extracted by UltraISO from the mounted ATIH2014 ISO boot sector. I couldn't also mount any *.img files from Floppy Image written on the ISO's CD track due to unknown *.img filesystem. Its unclear, why boot images extracted by ISOBuster were different from those extracted by UltraISO from the same ISO? As well, how an average user can derive similar grub.cfg menu section - based on what miracle vision? Any background explanation or more generalized logical approach would be handy... Also, how GOP-only HW support plays into this?
  5. If you have a computer with Windows 8 that was installed by an OEM on a GPT disk, the Windows 8.1 update from the Store will create a second recovery partition! Alternatively, if your OS is installed on an MBR disk, the 2nd partition is not created. This second partition is seen as a 350MB Recovery partition. For example a standard deployment of Windows 8 on GPT with recovery partition and diskpart: DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 300 MB 1024 KB Partition 2 System 100 MB 301 MB Partition 3 Reserved 128 MB 401 MB Partition 4 Primary 50 GB 529 MB Partition 5 Primary 5000 MB 50 GBThe above is outlined as: Part 1 = WindowsRE (winre.wim) Part 2 = BCD/boot file location Part 3 = MSR Part 4 = OS Part 5 = Recovery Image (install.wim) After the update to Windows 8.1, it will stick a new Recovery partition after the OS. Here is the new layout including details: DISKPART> sel disk 0 Disk 0 is now the selected disk. DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Recovery 300 MB 1024 KB Partition 2 System 100 MB 301 MB Partition 3 Reserved 128 MB 401 MB Partition 4 Primary 50 GB 529 MB Partition 5 Recovery 350 MB 50 GB Partition 6 Primary 5000 MB 51 GB DISKPART> sel part 1 Partition 1 is now the selected partition. DISKPART> detail part Partition 1Type : de94bba4-06d1-4d40-a16a-bfd50179d6acHidden : YesRequired: NoAttrib : 0X8000000000000000Offset in Bytes: 1048576 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- --------* Volume 3 Windows RE NTFS Partition 300 MB Healthy Hidden DISKPART> sel part 5 Partition 5 is now the selected partition. DISKPART> detail part Partition 5Type : de94bba4-06d1-4d40-a16a-bfd50179d6acHidden : YesRequired: YesAttrib : 0X8000000000000001Offset in Bytes: 54401171456 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- --------* Volume 5 NTFS Partition 350 MB Healthy HiddenThe update goes through a checklist when updating: 2013-10-25 09:41:16, Info SP F Suspend bitlocker if needed2013-10-25 09:41:16, Info SP S Boot WinPE2013-10-25 09:41:16, Info SP S Prepare SafeOS for rollback2013-10-25 09:41:16, Info SP S Set SafeOS boot entry as the default boot entry2013-10-25 09:41:16, Info SP S Cleanup safe OS mount directory2013-10-25 09:41:16, Info SP S Apply WIM file PathForNewOS, index 4 to C:\$WINDOWS.~BT\NewOS2013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postoobe for phase 32013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /presysprep for phase 02013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /postsysprep for phase 12013-10-25 09:41:16, Info SP S Set boot command %SYSTEMDRIVE%\$WINDOWS.~BT\Sources\SetupPlatform.exe /preoobe for phase 22013-10-25 09:41:16, Info SP S Set entropy for C:\$WINDOWS.~BT\NewOS2013-10-25 09:41:16, Info SP S Add boot entry for C:\$WINDOWS.~BT\NewOS\WINDOWS. Locale = en-US2013-10-25 09:41:16, Info SP S Set OS Switch rollback checkpoint2013-10-25 09:41:16, Info SP S Backup the recovery partition to C:\$WINDOWS.~BT\Sources\RecoveryPartitionBackup2013-10-25 09:41:16, Info SP S Apply EAs for C:\$WINDOWS.~BT\NewOS2013-10-25 09:41:16, Info SP S Install Dynamic Updates2013-10-25 09:41:16, Info SP S Install Driver DU Updates2013-10-25 09:41:16, Info SP S Install OS updates (DU) to keep installation up-to-date2013-10-25 09:41:16, Info SP S Relocate OS from C:\$WINDOWS.~BT\NewOS to C:\2013-10-25 09:41:16, Info SP S Add boot entry for C:\WINDOWS. Locale = en-US2013-10-25 09:41:16, Info SP S Prepare the new OS for first boot2013-10-25 09:41:16, Info SP S Setup the recovery partition2013-10-25 09:41:16, Info SP S Orchestrate OS switch for NewOS with safe OS SafeOS and rollback OS ExternalRollback. DelayedSwitch: 02013-10-25 09:41:16, Info SP S Copy log files from C:\$WINDOWS.~BT\Sources\Panther to C:\WINDOWSAttached is selected entries from the setupact.log after the update, which shows some of the things that the update does. Things left out is when the update downloads and install.wim, mounts it with DISM, scans the existing OS for applicable drivers and packages and injects them, unmounts the image and them uses DISM to apply it to the hard drive. Regarding the extra recovery partition, there does not seem to be a way to prevent it from happening. neatstuff.txt
×