4 replies to this topic

[noel]

Hi,

A long time ago I had found on a Chinese site the description of a WINPE installation named "RamOs".
It consisted of modifying the system and software hives taken from install. Wim.
I do not remember whether to carry out the installation of WINDOWS10 and make that levy afterwards.
Or just make a "DISM/apply" and use the hives of ISO without installing win10.

 

In my current tests:
I finalize the installation of WINDOWS10 and only then I change these hives.
So in a 20 GB VHD, I install WINDOWS10. I then capture the two hives. I edit them to make it a WinPE.
I kept the modus operandi but not the link.
When I reboot this VHD, I find myself well in a WINPE environment but more "rich" (more files, more keys, more post-installation changes).
This is what I call a WinPE "full-flat" to make it shorter in the following text.
It works well !

To make comparisons, I can replace the hives of win10 modified by those of WinPE.
And the next reboot works. So if hives come from winpe, that's works well also.

 

I use this "full-flat" in order to overcome certain limitations of WinPE.
And I'm led to useyour the hive of "full-flat" in WinPE: But the next boot fails.

 

Maybe you have some informations to answer my questions:
- Is it possible to copy the System hive of a WIN10 installed on a machine into another (same) machine?
- Is there any informations in the system hive that identifies the machine and prohibits it from running on another PC?

Merci

[vvurat]

-yes (maybe different machine too if there is not any special scsi drivers services installed)

-no (not prohibit but license key WPA values in system key)

[noel]

Hi vvurat,

Thanks for the information. They put me on the track.
In resuming the search, I found that the original hive loaded various critical drivers whose files were absent in the second environment.
Once these keys are neutralized, the VM starts.
I was also forced to remove the FirmwareBootDevice and SystemBootDevice values in "control". But I don't understand why they interfered.

Once again, thank you

[erwan.l]

Hi Guys,

 

Just my 2 cents:

-I have done many P2V without too much troubles

-I have done many V2V without too much troubles

-I have from time to time moved a disk from one computer to another without too much troubles (provided that the hardware is not too different)

 

Thus, many times, I had to boot in safe mode (at next reboot) to redetect hardware and also delete the mounteddevices key to avoid the (in)famous 0x7b BSOD.

 

What I never tried is to move one system hive from one system to another.

 

I purposedly do not touch on licence possible issues/legalities.

 

Regards,

Erwan

[vvurat]

Hi vvurat,

Thanks for the information. They put me on the track.
In resuming the search, I found that the original hive loaded various critical drivers whose files were absent in the second environment.
Once these keys are neutralized, the VM starts.
I was also forced to remove the FirmwareBootDevice and SystemBootDevice values in "control". But I don't understand why they interfered.

Once again, thank you

 

I also delete that values. They say the system to which drive and partition to boot on and ram disk is different i think so conflicts.