creating a VM win7, on win 10 pro i3 gen 9 machine

I deleted all vhd's in users\public\hyper-v and copied the vhd from d: again, we now have c and x

which commands
bootrec /FixMbr
bootrec /FixBoot
bootrec /RebuildBcd

and where do I run THE COMMANDS FROM, DO i need to go windows\system32?

yes i inspected it earlier, it gave me a little report box

- - - Updated - - -

I did a windows repair it said fixed, then it went to press any key to boot from cd, I hit a key, it's now stuck on that screen...

- - - Updated - - -

I DID IT WITHOUT TOUCHING A KEY TOO, it STICKS ON PRESS ANY KEY screen either way..
\
I can't get it to boot I ran the bootrec files ( bootrec /FixMbr
bootrec /FixBoot) from windows\system32, go confirmation they both worked, running bootrec /rebuildmbr just brings up the parameters.

I've done it several times even invsafe mode.
I've stopped the vhd running, closed hyper-v console and I'm done for tonight...

thx again,
ts<----- a dog with a bone

No it's fine. You did good. If it's hanging try a power off or reset.
Try to start it without DVD now. VM window -> Media -> DVD -> Eject. Reboot VM
Is it hanging again?

In case it's not working and you want to run those commands, you cd to c: and run them there, in case they don't work in x:

hello,
yes it's still hanging...

The first thing i did yesterday after signing off 10 forums was to attach the vhd file I've been using to browse the boot files, to see what had changed after ''successfully'' running the fixboot, and fixmbr commands, rebuildmbr wouldn't run. There were no boot files/folders. They should be in the root folder usually c.. (-'
The same thing when I attached the xp vhd, it showed no boot files, and we never touched that file with hyper-v...

Do me a favor, (or maybe you know without looking) if you can, attach a windows image(vhd) created using the win7 backup and restore program to a win 10 machine via file explorer, and let me know if win 10 sees the boot folder and the other boot files, then try it on a win7 computer.

Fwiw I have a whole other set of vhd files on a 2nd external hdd created at the same time, same thing, no boot files.
Yes I have show hidden files ticked...

My win7 computer is in the other room, I have neither the space, the man power, or inclination to bring it back in my room.
I can still access all the files and drives over my network, but there is no need since I have all the files in vhd format c: d: and e: drives.

I've never had this much trouble restoring a physical computer or hdd...

ty,
ts

I just looked at c: dir in vm and saw no boot files, are they hidden in DOS?

sneauxwolf said:

The first thing i did yesterday after signing off 10 forums was to attach the vhd file I've been using to browse the boot files, to see what had changed after ''successfully'' running the fixboot, and fixmbr commands, rebuildmbr wouldn't run. There were no boot files/folders. They should be in the root folder usually c.. (-'

So it's not bootable... that's what we know so far. I don't know if repair detected is as Win7. But rebuildmbr should have created the missing files if disk was visible.

sneauxwolf said:

Do me a favor, (or maybe you know without looking) if you can, attach a windows image(vhd) created using the win7 backup and restore program to a win 10 machine via file explorer, and let me know if win 10 sees the boot folder and the other boot files, then try it on a win7 computer.

I'll have to try that one out when I get home.
Honestly I haven't used Win7 Backup in years, all works fine in Macrium Reflect in my case, even restoring directly IN VM.

How do I go with this Win7 Backup?
I just backup a working Win7 and then try to use the restore?
In any case, I'll let you know what I find.

sneauxwolf said:

I just looked at c: dir in vm and saw no boot files, are they hidden in DOS?

They might be hidden in a separate partition, usually a small one preceding c: and without drive letter.

I see.
That XP dependency to boot makes it complicated for a VM. Although you can boot and install XP in Hyper-V as well.
Something in your mix makes it fail at boot.

What do you plan to do next?
Dig here further in the backup or try a fresh install? It's up to you.

Keep in mind that the VM will have 8MB graphics so simple office stuff will run but no 3D gaming stuff.

I tried to create a new VM of 7, and again got stuck here... Do I need an iso of 7?


ty again...

- - - Updated - - -

It seems I was supposed ton hit custom after all...

ty

I'm back.

Hmmm...
The DVD you have is an upgrade-only one?
EDIT: select "custom", not "upgrade"; you got it.

Yes you need an ISO of an installable disk.

For example I have one made from Win7 SP1 with install options like this:

1.


2.


3.


- - - Updated - - -

sneauxwolf said:

It seems I was supposed ton hit custom after all...

Yes!
Try that one indeed.

jimbo45 said:

Running an XP VM on HYPER-V is a bit of a problem - especially if you have an early VM that doesn't have any SATA drivers, also XP won't boot from UEFI devices to the XP needs to be created on a Virtual Disk that''s MBR. The WIFI / network might also be an issue and remember XP doesn't support USB3 devices --- you can attach things like USB 3 drives but you need to attach them via a USB 2 port or set the VM to support USB2 in the configuration file.
...
As for XP -- I'm on Linux but you probably will need an update with XP that has SATA AHCI drivers - you'll need to get the SP3 version of XP then add the SATA / AHCI drivers via things like Driverpacks. You won't get USB3 to work natively on XP though.

@jimbo45
That's the problem indeed and you'll just have to switch to or use what's included.
Hyper-V does not use SATA. You don't need XP with SATA.
Simply create a Gen 1 VM, the old type... and it allows you to install anything from Win2k/XP/Vista/7 on IDE drive. Keep it simple.

That works without problems when you create new VM and install from scratch.
The problem is when you convert P2V, as the OP case, but in particular for Hyper-V you'll need to move back from SATA to IDE. That way you can convert your physical machine or VM from other hypervisors to boot properly without BSODs.