Jump to content











Photo
* * * * * 1 votes

Boot issues with Windows 10 PE


  • Please log in to reply
21 replies to this topic

#1 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 10 December 2017 - 04:29 PM

Hi

 

I have created a working PE using WAIK under Windows 10

 

If I boot the ISO file in VirtualBox it boots really quickly and works fine

 

If I burn the ISO to CD/DVD and boot it on a real machine I get the blue logo, but it then sits for absolute ages before the spinning circle appears and it starts to boot - it does eventually go in, but can take several minutes

 

If I create USB using (MakeWinPEMedia /UFD D:\PE_TEMP G:) then it creates fine, but when trying to boot I get blue screen error with "winload.efi error 0xc0000225"

 

Any thoughts please



#2 Wonko the Sane

Wonko the Sane

    The Finder

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

Posted 10 December 2017 - 08:59 PM

Hmmm. :dubbio:

 

http://www.msfn.org/...-windows-10-pe/

 

:duff:

Wonko


  • darren rose likes this

#3 getnikkoo

getnikkoo
  • Members
  • 8 posts
  •  
    India

Posted 11 December 2017 - 07:04 AM

hmm.

 

Which os are you using for making this ??

 

Just do one thing

 

Don't use MakeWinPEMedia, Instead follow this commands on your USB drive

 

1 win+R type Diskpart and enter
2 list disk

3 select disk X (Disk no. of your usb drive)

4 clean

5 create partition primary

6 format fs ntfs quick

7 active

now extract content of your iso in your usb drive(or mount iso and copy content into USB drive)

 

if it didn't work inform me, I have other methods as well


Edited by getnikkoo, 11 December 2017 - 07:05 AM.


#4 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 11 December 2017 - 02:18 PM

Hi getnikkoo

 

Thank you for your reply, sorry for delay in replying - been at work

 

I am building on Windows 10 1709 64-bit and using the relevant Windows ADK for that version

 

Just tried that method and yes it does seem to boot okay on a system set to legacy rather than UEFI, but still seems slow even from USB, but at least it does boot

 

I get the blue windows logo in middle of screen, and then it waits for an age before spinning circle appears and then from that point it boots in seconds

 

Must be some way of disabling something it does at startup to speed it up perhaps

 

Also would like to find way to get it working on UEFI booting systems if at all possible

 

So happy to hear any other ideas/methods you have

 

Thanks again



#5 steve6375

steve6375

    Platinum Member

  • Developer
  • 6647 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 11 December 2017 - 05:34 PM

What USB are you using?

What happens if you boot from the USB using a VM?


  • getnikkoo likes this

#6 getnikkoo

getnikkoo
  • Members
  • 8 posts
  •  
    India

Posted 11 December 2017 - 07:12 PM

There could be many things causing that.

 

I can think of 3-4 reasons.

I can give solutions to them, try these if these don't work then i may need to inspect the image my self.

 

1st usb drive speed

If the drive is very old 6-8 years then, it could cause that, normally read speed above 8 MBps should boot under 1 min, if it boots fast in VM

so try other drive only if your drive is old.
 

2nd UEFI/secure boot there are many names to what MS did in its new booting mechanism.
But basically its a fast booting mechanism in windows 8 and higher OS, In which some part of OS is loaded in BIOS/ROM available in system to boot installed OS around 3 sec, So its basically a half pre-loaded installed os which is causing the problem, In multi-OS boot setup, if you boot OS other than default setup it takes minute or 2, in re-configuring that, you may have experienced it your self
so try any win 7 installed PC, or restart PC and at post (keep power button pressed for 8-9 sec) and then try.

 

3rd your source OS for PE may not be comparable.

Microsoft may have again modified booting mechanism.

In that case you know what to do.
 

4th file system of your pendrive
If you didn't formatted to active NTFS as i said early
If you did then try power iso's option write image to pendrive in options menu
It normally should be slower then default method, but it will give us idea about where are you mistaking.

 

There are few other things but you should try these, I think they should work if it boots fast in VM.


Edited by getnikkoo, 11 December 2017 - 07:26 PM.


#7 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 11 December 2017 - 08:38 PM

@Steve6375

 

I have tried several different ones, but mainly Sandisk Cruzer Blade 8Gb

 

Not tried that - will give it a go

 

EDIT - can't seem to get virtualbox to boot from any USB devices



#8 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 11 December 2017 - 08:46 PM

@getnikkoo

 

1) Drive is not that old - it is a Sandisk Cruzer Blade 8Gb - also tried 32Gb of same drive, and a Kingston one

 

2) tried UEFi boot on several different machines, mainly Dell's and same issues as reported

 

3) Will have to try building on a Windows 10 machine with older build of 10 and see if any different

 

4) Yes I did follow steps and do it as NTFS as you said, as per previous reply, it booted legacy but NOT uefi, just very slow - it is like it is trying to do something between the blue logo appearing and spinning circles appearing

 

Perhaps I should buy a new drive as well - any recommendations for a good reliable one for this sort of usage?



#9 steve6375

steve6375

    Platinum Member

  • Developer
  • 6647 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 11 December 2017 - 09:00 PM

So all drives you tried were removable USB drives (not fixed disk)?

 

You can easily boot USB from VBOX using VMUB

http://www.easy2boot...or-virtual-box/


  • getnikkoo likes this

#10 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 11 December 2017 - 09:31 PM

@getnikkoo

 

Just tried it using PowerISO create bootable ISO option - and it boots fine for legacy AND UEFI modes

 

It formatted it as FAT32

 

So need to work out what it does differently and as to why it worked, as would like to be able to manually create working USB without having to rely on something such as PowerISO



#11 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 11 December 2017 - 09:43 PM

@steve6375

 

Yes all drives were USB removable flash drives rather than USB external hard drive

 

Thanks, hadn't come across that useful program before - it worked fine to boot the USB on VirtualBox and it boots fine - BUT that same delay between blue screen windows logo appearing and then the spinning circles appearing, once spinning circles appear it boots in seconds


  • getnikkoo likes this

#12 cdob

cdob

    Gold Member

  • Expert
  • 1366 posts

Posted 11 December 2017 - 11:21 PM

I am building on Windows 10 1709 64-bit and using the relevant Windows ADK for that version
  
I get the blue windows logo in middle of screen, and then it waits for an age before spinning circle appears and then from that point it boots in seconds

It's a unknown hardware / driver error.
Try: write the whole USB flash once, e.g. zero at windlg. Watch the write speed.
Any write errors or slow speed downs?

UEFI specifaction supports FAT32, but not NTFS.
Prefer FAT32 at UEFI booting.
  • getnikkoo likes this

#13 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 12:45 AM

@cdob

 

I did wonder if it could be a bad drive, but can't find a sandisk equivalent of windlg to do the test you suggest

 

Yes I thought it was FAT32 only for UEFI

 

Think I will order some new drives for testing - any suggestions on good ones



#14 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 01:11 PM

UPDATE:

 

Just bought a brand new corsair USB memory stick and it now boots perfectly fine for both UEFI and Legacy - so looks like all this was just caused by the drive

 

Thank you for all your suggestions

 

Still seems very slow though - as get that long delay between blue logo appearing and then the spinning circles appearing - once spinning circles appear it is very quick to boot.  If I create a Win10PE_SE using Winbuilder I don't get this delay, so must be something I can perhaps change to speed it up?



#15 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 01:57 PM

Okay I have worked out why my ADK PE seems slower to boot than say Win10PE_SE created with winbuilder

 

It is because when mine boots i just get blue windows logo at start and then eventually the spinning circles

 

But with Win10PE_SE you get a screen showing Loading files and a white progress bar at bottom of screen rather than the blue logo

 

So anyone know how to change this, as at least seeing a progress bar lets you know it is doing something rather than just hung



#16 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 02:19 PM

solved

 

Change bootmenupolicy for bcd to legacy and then you get loading progress bar rather than just blue logo - at least you then know it is actually doing something

 

Apologies for answering own question!

bcdedit /store D:\PE_TEMP\media\Boot\bcd /set {default} bootmenupolicy legacy


#17 getnikkoo

getnikkoo
  • Members
  • 8 posts
  •  
    India

Posted 12 December 2017 - 03:09 PM

So all drives you tried were removable USB drives (not fixed disk)?

 

You can easily boot USB from VBOX using VMUB

http://www.easy2boot...or-virtual-box/

Thanks a million @steve6375, wanted to learn it, from such a long time, i was going to create a new topic or was going try to PM you, you made my day thanks a lot.



#18 getnikkoo

getnikkoo
  • Members
  • 8 posts
  •  
    India

Posted 12 December 2017 - 03:31 PM

@darren rose

comands for fat32(just replaced ntfs with fat32)

1 win+R type Diskpart and enter
2 list disk
3 select disk X (Disk no. of your usb drive)
4 clean
5 create partition primary
6 format fs = fat32 quick
7 active
now extract content of your ISO in your USB drive(or mount ISO and copy content into USB drive)

I would suggest sandisk extreme for any future requirement, from booting a live OS to installing entire server in usb flash drive
If you have more money to spare try Hyperx from Kingston.
corsair is fine but these are better.

There are few software like HD tune and USBDeview for checking your pendrive for write cycles left (wear level) etc. although using them will also wear you pendrive a bit not much.

Edited by getnikkoo, 12 December 2017 - 03:35 PM.

  • darren rose likes this

#19 cdob

cdob

    Gold Member

  • Expert
  • 1366 posts

Posted 12 December 2017 - 09:20 PM

I did wonder if it could be a bad drive, but can't find a sandisk equivalent of windlg to do the test you suggest

Use windlg anyway.
If you have serious doubts about a mass storage reliability (HDD, SSD, USB stick, sd card, ... ) do a full erase at windlg.

Congratulations to thenew USB stick, it's booting now.

#20 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 10:22 PM

Just tried it, and assume must be issues with those drives as constantly getting as per screenshot below when doing full erase on the drive

 

 

 

Attached Files



#21 cdob

cdob

    Gold Member

  • Expert
  • 1366 posts

Posted 12 December 2017 - 11:11 PM

Just tried it, and assume must be issues with those drives as constantly getting as per screenshot below when doing full erase on the drive

There are write errors: this is the confirmation: broken hardware

At good hardware:
one full write is possible at full speed without any delays.

In addition: in case of a classic hard disk: use your fingers, touch the case. And use your ears.
Irregular feelings or listenings? Then there is a broken hard disk.

#22 darren rose

darren rose

    Frequent Member

  • Advanced user
  • 394 posts
  • Location:Norwich, Norfolk
  •  
    United Kingdom

Posted 12 December 2017 - 11:19 PM

Thanks, yes with classic hard disks, always easy to know just from sounds etc, memory sticks never so easy but this certainly helps

 

Thanks cdob






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users