Jump to content











Photo
- - - - -

Gandalf's Windows 10PE is not loading Y: (Showing error in Desktop)

winpe grub4dos y: gandalf winpe

  • Please log in to reply
1 reply to this topic

#1 Abdul Gafoor

Abdul Gafoor

    Newbie

  • Members
  • 13 posts
  •  
    United Arab Emirates

Posted 27 June 2016 - 06:49 PM

I made a USB with 3 partitions, each partition containing as follows;

  1. Partition 1 (FAT32): syslinux boot loader created with YUMI
  2. Partition 2 (NTFS): Windows 7 installer image
  3. Partition 3 (NTFS): Gandalf's Windows 10PE

Installed Grub4dos in MBR and updated menu entries. All working very well except WinPE. Though WinPE loads, I get an error in Desktop.

 

I tried writing WinPE in 3rd partition in 2 ways to find a resolution;

  1. Written WinPE.ISO image using Windows 7 USB DVD Download Tool. Then updated Grub4dos menu entry as following
    title 1. Gandalf Windows 10PE x64\n Win10PE_x64.ISO
    root (hd0,2)
    chainloader (hd0,2)+1
    boot
  2. Copied Win10PE_x64.ISO as it is in root folder of the partition and updated menu entry as following;
    title 1. Gandalf Windows 10PE x64\n Win10PE_x64.ISO
    root (hd0,2)
    map (hd0,2)/Win10PE_x64.ISO (hd32)
    map --hook
    chainloader (hd32)/BOOTMGR

Both time I got WinPE loaded and got following log when Desktop error shortcut is double clicked

CdUSB.Y or ISO NOT found !
Win10PESE can not mount and access files of your CD/DVD, USB, ISO on drive Y:

Possible Reason and Solutions :
1) You are not using .iso boot (You are using RealCD/DVD, BCD BOOTMGR, grub4dos BOOTMGR, etc.).
---> Check that the flag file CdUsb.Y is at the root of your media.
---> Your drive remained to the state "Not Ready" (More than 30 seconds) for a hardware reason.
---> Your drive is not recognised (driver missing or whatever, check if you can see your CD or Usb drive letter on explorer).

2) You are using .iso boot (grub4dos, isolinux, etc.) but you changed the build .iso name or path of your iso (ex: Win10PE_x86.iso, \Images\Win10PE_x64.ISO).

* If you use all from ram (all inside .wim) ignore this warning ;).
+ If you need files in your .iso to access, read following.

A) This feature requires imdisk, else will not work.
---> Be sure you have imdisk on your Win10PESE (Enable at Win10PESE\Tweaks).

B) Change your .iso name to the build .iso name (ex: Win10PE_x86.iso ) and put it to the correct path of your bootdrive.
---> Look for the default build configuration in the internal ini file (X:\Windows\System32\MountPEmedia.ini section IsoInfo/IsoName).
---> Rebuild by giving your personal Iso file name\Subfolder in the script Finals\Create ISO.

C) Use Win10PESE.ini to specify your personal .iso file name and location (solution for without rebuilding your project with your custom .isoname/subfolder settings).

2b) You are using .iso boot (grub4dos, isolinux, etc.) but .iso file to mount not accessible.
(= you can not see your Win10PESE iso file with explorer).
---> Driver missing -> add driver for your disk.
---> Some windows settings or software which disables mounting drives at boot -> disable such setting/software.
---------------------------------------------------------------------------------------------------------------

MountPEmedia.exe : Mount files of your CD/DVD, USB, ISO on drive Y:

Ini File (MountPEmedia.ini) :
  [Settings]
  ProjectName=Win10PESE
  MountDrive=Y:
  SearchFlagFile=Yes
  FlagFileName=CdUSB.Y
  SearchExternalIniFile=Yes
  ExternalIniFileName=Win10PESE.ini
  DesktopWarningLabel=Win10PESE Warning

  [IsoInfo]
  IsoName=Win10PE_x64.ISO

Program Imdisk found in : X:\windows\system32

What could be wrong? And, what can I do to fix this error? Please help.

 

Regards,



#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13480 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 27 June 2016 - 07:37 PM

Is it a Removable or a Fixed device?

ONLY first partition is accessible to a Windows System on Removable devices.

You will need to either change partition order or integrate CFADISK.SYS, dummydisk.sys or diskmod.sys or "flip the bit" (hardware of the stick, might be possible or imight not be).

If you are booting from a .iso it makes really little sense to have it on a dedicated partition anyway.

 

:duff:

Wonko







Also tagged with one or more of these keywords: winpe, grub4dos, y:, gandalf winpe

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users