I have never recovered from a recovery disk but in the last 5 years or so must have lost about as many machines due to 'unrecoverable boot errors' as a result of applying an update. These are complex Windows 10 workstations and next time this happens, I want to try the recovery disk option they tout in their otherwise useless recovery blue-screen dialogs.
I am thinking that these must be of recent updates at least, so I have inserted 16Gb USBs into each machine and manually set off the recovery creation. Now, I want to automate and schedule that process.
- What are my options for CLI commands to recreate the disk?
- Is my thinking even correct? Does this make sense?
- Is imaging the system disk the only reliable option?
The goal is to recover a machine, not to reload the OS - and I am not sure if this is possible. Complicating the above is the fact that the boot drives are high speed NVME 256SSD's fuzed (enmotus or StoreMI tech) with regular SATA SSD's of 512Gb in size, yielding a drive that is about 675Gb and for intents as fast as NVMe. The issue that twice, after a Windows update and on reboot, I get a blue screen after reboot and the system refuses to come up. Enmotus tech fuzes the drives at the EFI level by injecting a loader which is also injected into the windows recovery partition. This is the reasoning behind creating recovery disks and updating them on a regular basis. To be clear, I imagine that winRE will be uploading any enMotus related configuration to the recovery flash drive - this in unproven - but is a mute point unless I can be creating the recovery on a regular basis.
Hence the question, can I create recovery media using the CLI (so I can automate it and forget it). It is the first question to be answered before digging deeper into my line of thinking.