Well, the sort of thing I caution others about all the time.
A power failure not only happened at almost the exact same time as a battery failure on the UPS, but a hard disk failure on the backup UBS drive had happened a week before without me knowing.
When the Hyper-v host came back up, the virtual domain controller started just fine but after a few minutes died with a kernel check blue screen. After two days of trying, it is still at that place:
1. It does not fail in safe mode. However, SFC and DISM do not fix the problem when I run them in safe mode. Says can't find source, although i point to install.wmi:1 with a /source parameter.
- I cannot do a Windows install to update the files from safe mode. It won't stay up long enough to do this in a normal mode boot.
3. I thought I would be clever and create a bit of work by provisioning another virtual machine, joining the domain, promoting it to a DC, then removing the failing server. But at dcpromo step, even with the other server up before an error occurs, I get
a message that it cannot find the forest and therefore the domain to join.
Any suggestions? It would be terrible to lose all the domain stuff and have to start from scratch, and I could just cry. Hoping someone might be able to help: maybe help me on the /source parameter or know of another way to do this? Any way to correct
the problem via the .vhdx when it is offline?
Many thanks in advance.