After deploy the image, windows not boot

[danilopinotti]

I decided to create a new topic after noticing that it was another problem. Follow the link below the first topic:
https://forums.fogproject.org/topic/6714/no-source-file-passed-writeimage/10

The problem is this: After spending a dual boot image to a new computer, Linux starts normally and the Windows does not start … He gets a pointer flashing in the left corner of the screen and does not start.

[Wayne Workman]

@danilopinotti What is the image type? what is the exit to hdd type? is the disk GPT or MBR?

[danilopinotti]

Image specifications:
Operation system: Windows 7 (5);
Image type: Single disk Resizable
Partition: Everything
Compression: 6
Protected: No
Image Enabled: Yes
Replicate?: Yes

MBR

[Sebastian Roth]

@danilopinotti Does it work if you use image type ‘Multiple Partitions - Single Disk’ (non-resizable!)??

[danilopinotti]

@Sebastian-Roth
in this way works

[Sebastian Roth]

@Tom-Elliott Do you know about “windows-blinking-cursor-on-boot” issues when using resizable image type?

By the way, @danilopinotti which version of FOG do you currently have installed (see in the blue cloud on the web interface)?

[danilopinotti]

@Sebastian-Roth
I use 6323

[Tom Elliott]

@danilopinotti how was this image uploaded? It seems, to me, that it was uploaded as non resize originally. The reason boot isn’t working is because it has no idea how to expand the partition . Just a guess though.

[Tom Elliott]

@danilopinotti to further clarify, and I’m just guessing here. It’s specific to the partition layout not having been written to the disk, or is in a weird state. That, itself, is fine but my guess is partclone isn’t even writing the image to disk. Before it writes the partition table, it wipes the disk. This makes it basically unusable to the host.

[Tom Elliott]

@Tom-Elliott forget all that. I have a suspicion I know what’s causing the problem, and it can be fixed relatively easily. In resize imaging, for Windows 7, I replace the BCD file with one that is in a generalized state. Bootmgr is looking for the proper point based on whatever layout the disk that created the bcd i use to replace. This is why multipartition works, but resize doesn’t.

I may have a relatively simple fix by putting back the original bcd file. One question comes to mind though (not for you to answer rather just getting theories out there) does this now mean I no longer have to replace BCD for resizable images?

[Tom Elliott]

@danilopinotti I know I’m asking a lot, but what if you change the OSID to Linux, and set it back to resizable? Does it work then?

[danilopinotti]

@Tom-Elliott I’ll test and reply

[danilopinotti]

@Tom-Elliott said:

change the OSID to Linux, and set it back to resizable? Does it work then?

Not work

[Wayne Workman]

@danilopinotti said:

@Tom-Elliott said:

change the OSID to Linux, and set it back to resizable? Does it work then?

Not work

Did you re-upload, and then try?

[danilopinotti]

@Wayne-Workman said:

Did you re-upload, and then try?

With Resizable option was not work, but not resizable i have no problem.

[Sebastian Roth]

@danilopinotti Is this still an issue or can we make this solved? Have you tried upgrading to the very latest version, re-upload and deploy again?