262 replies to this topic

[wimb]

In other words:

Apparently the VHD was not given the name that it should have.

But given that filename, everything is as expected and booting is OK.

 

Can you give me the makebt\wim_info\wiminfo.txt file for that Win 8.1 case ?

 

There is something not as expected in that file, so that parsing goes wrong.

[alacran]

In other words:

Apparently the VHD was not given the name that it should have.

But given that filename, everything is as expected and booting is OK.

 

Well yes, I only wanted to report item by item to let you know all was checked carefully, not only just reporting the first thing saw.

 

alacran

[Wonko the Sane]

VHD file was created with wrong name W10x64_ES_1.vhd, it should be W8.1x64_ES_1.vhd or 8.1x64_ES_1.vhd.

 

I would anyway advise against using a multidot file name, W81x64_ES_1.vhd would have BTW the same length of W10x64_ES_1.vhd

 

 

 

Wonko

[wimb]

I would anyway advise against using a multidot file name, W81x64_ES_1.vhd would have BTW the same length of W10x64_ES_1.vhd

 

 

 

Yes you are right. It is Microsoft that introduced this extra dot in the Name. So may be we need to remove it again ...

 

I hope alacran can provide the makebt\wim_info\wiminfo.txt file so that I can see why parsing goes wrong in his case.

[alacran]

Sure:

 

Spoiler

WIM Information:
----------------
Path:           K:\Wimboot\8.1x64-WB.wim
GUID:           0x0dad0b8b5c4306f922b32ed59b1337c6
Version:        68864
Image Count:    1
Compression:    XPRESS
Chunk Size:     4096 bytes
Part Number:    1/1
Boot Index:     0
Size:           4554505150 bytes
Attributes:     Integrity info, Relative path junction

Available Images:
-----------------
Index:                  1
Name:                   8.1x64_190309_153621
Description:            L:/
Display Name:           Windows 8.1 Pro
Display Description:    Windows 8.1 Pro
Directory Count:        18208
File Count:             94293
Total Bytes:            13938063169
Hard Link Bytes:        5469458254
Creation Time:          Sat Mar 09 21:36:39 2019 UTC
Last Modification Time: Sat Mar 09 21:36:55 2019 UTC
Architecture:           x86_64
Product Name:           Windows 8.1 Pro
Edition ID:             Professional
Installation Type:      Client
HAL:                    acpiapic
Product Type:           WinNT
Product Suite:          Terminal Server
Languages:              es-ES 
Default Language:       es-ES
System Root:            WINDOWS
Major Version:          6
Minor Version:          3
Build:                  9600
Service Pack Build:     16384
Service Pack Level:     0
Flags:                  Professional
WIMBoot compatible:     yes

alacran

[wimb]

Download -  coming later

 

@alacran

 

In Windows 7 OS then bcdboot.exe 7/8/10 cannot make the VHD internal BCD entry and that is the cause of the problem that you encountered.

 

I have no solution for this problem and so the program VHD_WIMBOOT needs Windows 10 Or Windows 8 / 8.1 OS.

 

The failure in giving the VHD the right name is solved and for Windows 8.1 the extra dot in the VHD filename is removed.

[alacran]

Thanks for this new version, if the program is not compatible with 7, it may not be a big issue, but it is good we now are aware of that before running it.

About the dot on 8.1 I'm glad you fixed it. but also a warning like:  Do not use dot(s) or espaces on files names could be enough, sorry for the extra work my friend.

 

Just downloaded, I'll run some tests ASAP and let you know of my findings.

 

alacran

[Wonko the Sane]

In Windows 7 OS then bcdboot.exe 7/8/10 cannot make the VHD internal BCD entry and that is the cause of the problem that you encountered.

I have no solution for this problem and so the program VHD_WIMBOOT needs Windows 10 Or Windows 8 / 8.1 OS.

 

If I get this right, you could boot (Wimboot) Windows 7 but you stop because the BCDBOOT cannot make a "correct" BCD entry for it?

 

A possible solution is here (whether you will like it or not is another thing):

http://reboot.pro/to...ch-using-linux/

 

Wonko

[alacran]

@ wimb

 

Download -  VHD_WIMBOOT  New Version 1.1 available for testing

 

@alacran

 

In Windows 7 OS then bcdboot.exe 7/8/10 cannot make the VHD internal BCD entry and that is the cause of the problem that you encountered.

 

I have no solution for this problem and so the program VHD_WIMBOOT needs Windows 10 Or Windows 8 / 8.1 OS.

 

The failure in giving the VHD the right name is solved and for Windows 8.1 the extra dot in the VHD filename is removed.

 

Sorry for the delate but I was busy with other things.

 

I can confirm the dot problem is fixed, but this time on W81x64_ES_1.vhd and also on W10x64_MX_1.vhd even if lang is correct on VHD name, it was not applied to all the BCDs as it was before on first version, I assume when you edited the code you just forgot to add this feature, (it was working fine before, at least on W10x64_MX_1.vhd the right lang was selected on BCDs).

 

alacran

Attached Thumbnails

• 

[wimb]

Download -  coming later

 

@alacran

 

- Option Added - Capture WIM File with LZX Compression

- Added - Locale Language in BCD is taken into account

 

For making new BCD entries there was only code to use default Language en-US, but now the Locale value is taken into account.

[wimb]

If I get this right, you could boot (Wimboot) Windows 7 but you stop because the BCDBOOT cannot make a "correct" BCD entry for it?

 

A possible solution is here (whether you will like it or not is another thing):

http://reboot.pro/to...ch-using-linux/

 

 

It is not Wimboot Windows 7, but Boot with Windows 7 x64

Then Mount Win10x64 VHD as Drive N: and try to make new entry into the VHD internal BCD e.g. N:\Boot\BCD

 

When I use W10x64 version of bcdboot and command as given Or W7 bcdboot without /f ALL, it all fails, wheras I can use such command with succes in Win10x64  or Win8/8.1OS

bcdboot.exe N:\Windows /s N: /f ALL

I tried your suggestion to use bcdedit for that purpose to create new entry in BCD

 

Using Windows 7 x64 OS Or Win 10 x64 OS then I can create such entry in the N:\Boot\BCD but it is not correct

bcdedit /store N:\Boot\BCD /create /d W10x64_NL_7-VHD /application osloader
gives guid {513f748d-4e64-11e9-b210-3052cb53659e}
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} device partition=N:
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} path \Windows\system32\winload.exe
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} osdevice partition=N:
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} systemroot \Windows
bcdedit /store N:\Boot\BCD /displayorder {513f748d-4e64-11e9-b210-3052cb53659e} /addlast
bcdedit /store N:\Boot\BCD /default {513f748d-4e64-11e9-b210-3052cb53659e}

The problem is that the generated entry refers to the VHD instead of to the mounted partition.

 

Strange enough enum and enum /v show total different info for the last entry

C:\Windows\system32>bcdedit /store N:\Boot\BCD /enum

id                      {default}
device                  partition=N:
path                    \Windows\system32\winload.exe
description             W10x64_NL_7-VHD
osdevice                partition=N:
systemroot              \Windows


C:\Windows\system32>bcdedit /store N:\Boot\BCD /enum /v

id                      {513f748d-4e64-11e9-b210-3052cb53659e}
device                  vhd=[M:]\W10x64_NL_2.vhd,locate=custom:12000002
path                    \Windows\system32\winload.exe
description             W10x64_NL_7-VHD
osdevice                vhd=[M:]\W10x64_NL_2.vhd,locate=custom:22000002
systemroot              \Windows

Do you you know the commands to get the correct entry for BCD inside VHD booting Windows of that VHD ?

 

I need probably something else than device partition=N: but what code will give succes ?

[karyonix]

@wimb
bcdedit /store N:\Boot\BCD /set {bootmgr} device boot
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} device boot
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} osdevice boot

[alacran]

Download -  VHD_WIMBOOT  New Version 1.2 available for testing

 

@alacran

 

- Option Added - Capture WIM File with LZX Compression

- Added - Locale Language in BCD is taken into account

 

For making new BCD entries there was only code to use default Language en-US, but now the Locale value is taken into account.

 

This time I used 10x64-WB.wim LZX compressed as source, located on Wimboot file on the USB, the program created W10x86_MX_1.vhd in a few minutes on USB device.

 

All working as expected, not a single issue during building or during Rambooting the created VHD of 1.5 GB fixed size.

 

So the program is totally fine as far as Apply, haven't tested Capture yet.

 

As a personal test I manually changed grub4dos version from 0.4.6a-2018-12-23 to 0.4.6a-2017-12-20 and tested Rambooting the W10x86_MX_1.vhd without making any change to munu.lst, I mean the command map --top --mem was not changed to map --mem for use on the older version, and W10x86_MX_1.vhd Rambooted as fine as before.

 

This was done with the idea to suggest you 2 optional additions to your program:

 

1 - An option for the user to select/use grub4dos 0.4.6a-2017-12-20 (the last known version capable to Ramboot Dynamic Expandable VHDs)

 

2 - An option for the user to create Dynamic Expandable VHDs (They load on RAM like a lightning), not capable to Filedisk boot using grub4dos, but Windows manager boots them without any issue, and also we save more than 2/3 of VHD size = more than 66.6 % less espace used for the VHD.

 

alacran

[Wonko the Sane]

@wimb

Besides the suggestion by karyonix, I was suggesting more to use bcdboot and/or bcdedit to create a "base" BCD and then use reg.exe as cdob detailed in the given thread to "tweak it" as needed, and/or erwan.l's offlinereg:

http://reboot.pro/to...linux/?p=192410

 

and/or (if needed) direct binary editing to further refine it.

 

Wonko

[wimb]

@wimb
bcdedit /store N:\Boot\BCD /set {bootmgr} device boot
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} device boot
bcdedit /store N:\Boot\BCD /set {513f748d-4e64-11e9-b210-3052cb53659e} osdevice boot

 

It is useful in Windows 7 x64 OS to make existing <Unknown> entry of BCD in Win10x64 VHD bootable.

 

I can create also new working BCD entry using your code.

Important is to use the addlast for adding the entry to the menu

 

Thanks for your solution 

[wimb]

Download -  coming later

 

- bcdboot not used anymore in code to update internal BCD of VHD

- Program now compatible with Windows 7/8/10 OS

- added new grub4dos-0.4.6a-2019-03-25 version

 

Thanks to karyonix for giving solution to make the program compatible with Windows 7 

[alacran]

Better use new grub4dos-0.4.6a-2019-03-25, see: http://reboot.pro/to...e-3#entry210171

 

It is restoring again the lost (by mistake) capability to load to Ram and Ramboot expandable VHDs. Download: http://grub4dos.chenall.net/

 

So my two previous suggestions are reduced to only one now:

 

An option for the user to create Dynamic Expandable VHDs (They load on RAM like a lightning), not capable to Filedisk boot using grub4dos, but Windows manager boots them without any issue, and also we save more than 2/3 of VHD size = more than 66.6 % less espace used for the VHD.

 

alacran

[wimb]

Better use new grub4dos-0.4.6a-2019-03-25, see: http://reboot.pro/to...e-3#entry210171

 

It is restoring again the lost (by mistake) capability to load to Ram and Ramboot expandable VHDs. Download: http://grub4dos.chenall.net/

 

Thanks, I have just added the new grub4dos-0.4.6a-2019-03-25 version.

[alacran]

W81x64_ES_1.vhd was created running VHD_WIMBOOT from Win 7x64, external BCD is fine, including lang selection, internal BCD includes lang selection fine too, but the HD and partition to boot from are not selected, see attached picture.

 

alacran

Attached Thumbnails

• 

[wimb]

W81x64_ES_1.vhd was created running VHD_WIMBOOT from Win 7x64, external BCD is fine, including lang selection, internal BCD includes lang selection fine too, but the HD and partition to boot from are not selected, see attached picture.

 

alacran

 

Probably there is only one entry which is not set as default.

I will check it and find a solution.

 

What does the entry look like in Professional mode ?

[alacran]

This is it on Professional mode.

Attached Thumbnails

• 

[wimb]

Somehow the default entry has been removed.

So I have to check if a default entry is present and otherwise create one.

 

Normally Install creates a default entry.

[alacran]

I haven't noticed it before because I have about 10 entries on my BCD, but during running VHD_WIMBOOT to create W81x64_ES_1.vhd from Win 7, my win10x64 Pro that was selected as default on BCD,  was overwrited by W81x64_ES_1.vhd entry, so better delete the link to download that version 1.4, since it may create big troubles to non advanced users.

[wimb]

I haven't noticed it before because I have about 10 entries on my BCD, but during running VHD_WIMBOOT to create W81x64_ES_1.vhd from Win 7, my win10x64 Pro that was selected as default on BCD,  was overwrited by W81x64_ES_1.vhd entry, so better delete the link to download that version 1.4, since it may create big troubles to non advanced users.

 

OK, File has been removed.

 

Thanks for the Info.

[wimb]

Download:  VHD_WIMBOOT Version 1.7

 

- internal BCD create entry improved - solution also working without default entry present

- external BCD create entry improved so that default entry cannot be overwritten anymore

- VHD Expandable option added

- SVBus Filedisk entry removed, since it does not work with expandable VHD and Microsoft VHD entry in Boot Manager menu is better option

 

Thanks to karyonix, alacran, Wonko the Sane, tinybit, yaya, chenall, cdob, JFX, steve6375, ReTokener, synchronicity, schtrom and Microsoft    

 

== 

 

 

More Info in Support Topic on VHD_WIMBOOT  - Apply and Capture of WIM Files for OS in VHD