USB Win10 installation does not create "System Reserved" - not booting

I have HP ZBook. I want to install fresh Windows 10 using installation
media with USB.

When it comes to the section "select your drive to install" where I can
format partitions and delete partitions, I delete the old System Reserve
partition and the old System partition (on C). After that it looks
something like that:

250giga unallocated space

1000 Giga System partition

1000 giga is the data disk (so I do not delete/format it).Â* I have 2
disks, And the win10 is installed on 250giga drive. After I select it
and press Next, when it boots first time i get this error


Boot Device Not Found 3F0 Error

and black screen and it does not boot. But if I go to bios and select
the 250giga the Windows boots ok. But if I then again reboot I get that
error again and I need to manually select boot disk.


If I do not delete the old System Reserve and install on 240giga old
C-drive then all goes well. But I would rather delete all if possible to
start 100% fresh.

Any idea why the System Reserve is not created by the installation
media? Do I need to format it first of press "New"?

Thank you.

JiiPee wrote:
I have HP ZBook. I want to install fresh Windows 10 using installation
media with USB.

When it comes to the section "select your drive to install" where I can
format partitions and delete partitions, I delete the old System Reserve
partition and the old System partition (on C). After that it looks
something like that:

250giga unallocated space

1000 Giga System partition

1000 giga is the data disk (so I do not delete/format it). I have 2
disks, And the win10 is installed on 250giga drive. After I select it
and press Next, when it boots first time i get this error


Boot Device Not Found 3F0 Error

and black screen and it does not boot. But if I go to bios and select
the 250giga the Windows boots ok. But if I then again reboot I get that
error again and I need to manually select boot disk.


If I do not delete the old System Reserve and install on 240giga old
C-drive then all goes well. But I would rather delete all if possible to
start 100% fresh.

Any idea why the System Reserve is not created by the installation
media? Do I need to format it first of press "New"?

Thank you.


With all the too and fro, I don't know if I follow all that.

Taking a picture of it would be nice, because the Disk Management
puts labels on stuff.

https://www.tenforums.com/attachment...r-pw-vs-dm.png

In that example, there is a Recovery partition (with a 350MB
boot.wim inside it), there is a 100MB ESP (system partition)
which contains a Microsoft folder with boot materials.

While the Windows 10 C: partition is labeled "Boot", that's
the operating system partition, while the "System" word in
the ESP, means the "boot materials" are in it. Which they
are.

Notice that D: in that picture, is an ordinary partition
and doesn't have any Windows 10 dependencies in it.

On a legacy disk, at a guess you *could* place all materials
in a single partition. But the boot.wim would not be very
useful there, as if C: was corrupted and needed a CHKDSK, the
boot.wim would not be accessible. Consequently, on legacy
disks, you have to be careful to not shoot yourself in the
foot when consolidating partitions. You *can* substitute
a bootable Windows 10 install DVD, to provide some of the
emergency boot services (you could do a CHKDSK from there),
but doing so is for people who love to work hard to keep
a computer running.

In the case of GPT partitioned disks (HP, Dell, might do
this, even to disks too small to really need it), the ESP
can't really be removed, because as far as I know, the
BIOS has a fixation with the ESP, and would not be too
happy if the ESP went missing.

Take a picture of your Disk Management *while* the system
is running, so we can review what is present, what is on
the wrong disk drive, and so on.

You can try imgur (if you can figure out how to use it),
or postimg. The domain you post from, and the domain
serving the images, can be different on this thing. Use
the direct link when you get your picture uploaded.
These aren't "good" sites, but they don't need an account.

https://postimages.org/

Paul

Thanks for the detailed answer. Ok, I made pictures now and I posted
them in:
https://postimg.cc/gallery/z3xhYkG
(I put 30 days expiry, if you want pics after that please let me know)

I explain the pics:
1) When first time coming to "where do you want to install"
2) First deleting the C-drive (the Drive 1 in the pic is a separate hard
disk. so I have 2 disks total, one SSD and one hard disk)
3) After deleting the "System Reserved"

Then I install the Win10.

6) After installation Win10 reboots and I get this.
7) then I get this
4) After 7) I start laptop and go to bios (Esc)
5) If I choose manually this "Notebook Upgrade Bay" the windows starts
normally. But next time I start windows (reboot) I get again screen 6).
So I always have to do 5) to get windows started.

Is the problem the second hard disk seen in 3)? I should remove the
second hard disk first before installing?

So, after installing when I go and check my partitions the "System
Reserved" is missing. So installation did not make it.

On 27/06/2020 02:07, Paul wrote:

You can try imgur (if you can figure out how to use it),
or postimg. The domain you post from, and the domain
serving the images, can be different on this thing. Use
the direct link when you get your picture uploaded.
These aren't "good" sites, but they don't need an account.

https://postimages.org/

Â*Â* Paul

JiiPee wrote:
Thanks for the detailed answer. Ok, I made pictures now and I posted
them in:
https://postimg.cc/gallery/z3xhYkG
(I put 30 days expiry, if you want pics after that please let me know)

I explain the pics:
1) When first time coming to "where do you want to install"
2) First deleting the C-drive (the Drive 1 in the pic is a separate hard
disk. so I have 2 disks total, one SSD and one hard disk)
3) After deleting the "System Reserved"

Then I install the Win10.

6) After installation Win10 reboots and I get this.
7) then I get this
4) After 7) I start laptop and go to bios (Esc)
5) If I choose manually this "Notebook Upgrade Bay" the windows starts
normally. But next time I start windows (reboot) I get again screen 6).
So I always have to do 5) to get windows started.

Is the problem the second hard disk seen in 3)? I should remove the
second hard disk first before installing?

Ding! Ding! Ding!

Now, if you'd looked in diskmgmt.msc (Disk Management) like
I told you, your "second" disk would say "System" or ESP or
similar, and then we'd know you had "split" your installation.

The prime rule of installation:

Remove any disk drive where you *don't* want installation
materials going by mistake.

What I can't tell you, is why it did that. I don't know
why the installer chose to split the installation. It really
should have used the OS drive for that. But once you remove
some of the "hints" it uses for controlling the installation,
that's when these things happen.


So, after installing when I go and check my partitions the "System
Reserved" is missing. So installation did not make it.


Use your booting method that works, and right-click Start and
select Disk Management. It will show the current disposition
of materials. There could be "Boot", "System", or "ESP" style
materials on one or both of the disks.

I mean, you know right away, that the "System" partition is
now on the Data Drive.

It's possible to move some of these materials, but, not
particularly easy. But I also don't want to put you
through the hell of reinstalling either. That's no fun.

The storage devices, use a GUID-style identifier. You can
use Macrium Reflect emergency boot CD to repair the boot,
once the materials are moved. It can, in a few cases,
glue some of these things back together, and that's
better than struggling with BCDEDIT in a Command Prompt
window.

And the GUID itself, is mysterious. None of the identifiers
on the hard drive, seem to be long enough for that purpose.
The GUID is stored in the OS registry, but then, how does
the boot process know where to look ? Linux has some things
like BLKID, where it's obvious where the number is hiding.
The identifiers that Windows uses, tend to be 32-bit ones
(eight hex digits), and somehow, the identifiers point to
a GUID that is unique for the partition, and calls out
where to look for the boot stuff.

Paul

On 28/06/2020 01:01, JiiPee wrote:
Thanks for the detailed answer. Ok, I made pictures now and I posted
them in:
https://postimg.cc/gallery/z3xhYkG


*HTML is required to view the main post!!*

--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 28/06/2020 01:35, Paul wrote:
Now, if you'd looked in diskmgmt.msc (Disk Management) like
I told you, your "second" disk would say "System" or ESP or
similar, and then we'd know you had "split" your installation.


After installation:

disk 0 (SSD, c drive): Boot, Page File, Crash Dump, Primary partition

disk 1 (hard disk): System, Active, Primary partition


So you mean that because the disk 1 says "System", that is the problem?
So intallation added something there?

Thats what I did many times: I deleted the 2 partitions, but then the
computer does not boot like I describe in the first post

On 28/06/2020 01:36, 😉 Good Guy 😉 wrote:
On 28/06/2020 01:01, JiiPee wrote:
Thanks for the detailed answer. Ok, I made pictures now and I posted
them in:
https://postimg.cc/gallery/z3xhYkG


Your pics are very clear.Â* In the first picture, delete partitions 1
and 0 from DISK 0.Â* See this pictu

[ img attached ] https://i.imgur.com/re0ctIy.png


Don't do anything in Drive 1 on which you have DATA.Â* You want to
protect that DATA.

After deleting the partitions, just click NEXT button and voila
everything will go smoothly.Â* Windows will configure your system.

JUST MAKE SURE you are OFFLINE when doing all these things as you
don't want any updates when installing first time.Â* Updates will come
automatically but you don't need to force anything to get updates.Â* In
fact it is foolish to do so.Â* Let windows gives you automatically.


--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 28/06/2020 01:54, JiiPee wrote:
Thats what I did many times: I deleted the 2 partitions, but then the
computer does not boot like I describe in the first post



*HTML is required to view the main post!!*

--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Oh thanks you. This worked! When I remove the second disk and only have
SSD it install correctly.
All working now

On 28/06/2020 01:35, Paul wrote:
The prime rule of installation:

Â*Â* Remove any disk drive where you *don't* want installation
Â*Â* materials going by mistake.

JiiPee wrote:
On 28/06/2020 01:35, Paul wrote:
Now, if you'd looked in diskmgmt.msc (Disk Management) like
I told you, your "second" disk would say "System" or ESP or
similar, and then we'd know you had "split" your installation.


After installation:

disk 0 (SSD, c drive): Boot, Page File, Crash Dump, Primary partition

disk 1 (hard disk): System, Active, Primary partition


So you mean that because the disk 1 says "System", that is the problem?
So intallation added something there?


Yes, that's a split install. Half the OS is on the first disk,
half is on the second disk.

What you do next, is up to you.

a) Enter the BIOS and set the permanent boot order to boot
from the Data Drive (the second hard drive).

OR

b) Move the "System" stuff to a partition on the first drive.
Preserving the GUID would be ideal for this.

I don't think there is an install technique which will
migrate materials. Once it gets split like that, the
installer will keep it split.

To do (b), might require sufficient slack space on
the Data Disk. You could shrink down the 931GB data partition
(which says "System" right now). Create a Data partition next to it.
Move the materials from one to the other (the data files).
Leave the boot materials on the left most partition.
Then move the left-most partition to the first disk
(drag and drop in Macrium would do).

At this point, you could try to boot from the regular C:
disk (as the BIOS is still set to do that). If it doesn't
work, a Macrium Reflect emergency boot CD, has a Boot Repair
in the menu, and if you carefully select the partition on
the C: drive, then it should be able to edit the BCD and
make the pair on the C: containing drive, the new best buddies.

Now, if the Data Drive were to be disconnected, the original
C: drive should still be booting OK.

Are there steps missing there ? Probably. Some of these
things are too lengthy to reduce to 16 step recipes. I'd
give a web site link, if I had one. This happens often enough,
there really should be a web page for it.

Paul