Windows 10 The same image of Windows 10 with Sysprep cloned on different partitions of the same disk makes one of them not boot

  • Thread starter Thread starter Dani Medina
  • Start date Start date
D

Dani Medina

Guest
Hello
In my school we need to have two Windows 10 and two Ubuntu Linux installed on the students' computers. We also have a Debian for administrative reasons.

The partition structure is as follows:
- First primary partition: Debian.
- Second primary partition: Windows 10 for the morning shift.
- Third primary partition: Windows 10 for the afternoon shift.
- First logical unit: Ubuntu for the morning shift.
- Second logical unit: Ubuntu for the afternoon shift.
- Third logical unit: Swap.

In the Windows 10 morning partition we installed the operating system. We install and apply the procedure SYSPREP /generalize with a file of unattended responses that puts the computer in the domain.

Then we clone the second primary partition into the third one to have another Windows.
We update the Debian GRUB boot manager to have access to the startup of both Windows.

When we start the morning shift Windows again it goes seamlessly into the OOBE phase and puts the computer into the domain. If we reboot several times everything is fine.

When we start the afternoon shift Windows, it goes through the OOBE phase and everything works fine. The problem is that the morning shift Windows stops starting. It keeps showing the Windows logo and the dotted circle and it doesn't go through.

The afternoon shift Windows works without any problem.

Thank you.

More...
 
Back
Top