Windows 10: Maintaining State using differencing VHDs in Windows 10

I found this download some years ago - and incorporated it extensively on kiosk pcs for work. It utilizes native-boot in Windows 7 Ultimate or Enterprise to enable rollback to a pristine installation state.
I would be grateful if someone with better skills than myself could adapt this for Windows 10 - as this worked quickly and flawlessly for my purposes in Win 7 - and is really easy to use. I incorporated this within SCCM to rollback kiosk workstations to a pristine state every night. I have included a link to the files and the simple documentation that came with them.

Thanks in advance,

Pete.
https://mega.nz/folder/qE9kwBbb#_NwdzKb71qQ3wlX4LhyFiw

:)

 

Windows 10 VHD Native Boot

Is it possible to native boot a vhd created from an image of an existing and working Windows 10 (April Update) installation (native PC, not VM, and no Sysprep), using UEFI or BIOS interchangeably on the same machine the installation was first setup (Since
it's the same device, I was hoping Sysprep wouldn't be required)? I'm testing with a 64-bit OS, and a fixed size VHD (and optionally differencing VHD). I'm interested in details for both Pro and Enterprise.

When I try to boot, Windows loads partway, through two loading indication screens up to a blank (black) screen, with a mouse pointer continuously switching between normal and busy pointers, and keeps reading the disk.

I have placed the boot files on a UFD, but the VHD is on a Hard Disk (not SSD) with plenty of space for expansion.

Is it an issue if a page file can't be created on the parent HDD volume?

I also tried to boot a differencing VHD, but through UEFI, only the entry for the parent VHD is shown, even though I know for a fact that the entry for the differencing disk also exists in the efi BCD, and when I try to add the differencing entry to non
UEFI BCD, I get errors (IIRC there is an invalid object in the boot configuration data store), with error codes such as 0xc00000bb when using the boot files from 1803 ADK, and 0xc3a000b when using those from the ADK for Windows 8.1 Update...

The VHDs were created using diskpart. I'm primarily interested in VHD, not VHDX, though any relevant info on the latter is also welcome.

I HAVE in the past managed to native boot from VHDs on the same system, including differencing disks, but with a parent VHD I had obtained from the Microsoft website (Windows 10 Development Environment VHD, but I don't have that anymore to test, and I'm
not sure if it was x86 or x64).

Correction:

I believe one of the error codes is 0xc03a000b, NOT 0xc3a000b. I mistyped.

Also, I have tried creating the boot files with bcdboot with /f ALL and also creating the BCDs manually with bcdedit...

 

Maintaining State using differencing VHDs in Windows 10

I found this download some years ago - and incorporated it extensively on kiosk pcs for work. It utilizes native-boot in Windows 7 Ultimate or Enterprise to enable rollback to a pristine installation state.
I would be grateful if someone with better skills than myself could adapt this for Windows 10 - as this worked quickly and flawlessly for my purposes in Win 7 - and is really easy to use. I incorporated this within SCCM to rollback kiosk workstations to a pristine state every night. I have included a link to the files and the simple documentation that came with them.

Thanks in advance,

Pete.
138.79 MB folder on MEGA

 

Changes to the contents of a VHD

Hello! I am an Independent Advisor, I would love to help you out!

What pages is this from?

Depending on the program you can make differencing disks from VHD's. Which will boot up and allow differences to be made by restoring the default VHD when rebooted.

A gold image of the VHd could be set up and redeployed anytime something needs a new image, etc.

A copy or clone of a VHD could also easily be made as well.