Sebastian Arcus wrote on 03/04/2018 09:57 AM:
On 03/03/18 01:36, Donald R Laster Jr wrote:
Sebastian,
Could you be dealing with a locked screen where the first reboot command is sending a
"ctl-alt-del" that unlocks the screen and the second reboot command send a second
"ctl-alt-del" th
Sebastian Arcus wrote on 03/04/2018 09:57 AM:
>
> On 03/03/18 01:36, Donald R Laster Jr wrote:
>> Sebastian,
>>
>> Could you be dealing with a locked screen where the first reboot command
>> is sending a "ctl-alt-del" that unlocks the screen and the second reboot
>> command send a second "c
On 03/03/18 01:36, Donald R Laster Jr wrote:
Sebastian,
Could you be dealing with a locked screen where the first reboot command is sending a
"ctl-alt-del" that unlocks the screen and the second reboot command send a second
"ctl-alt-del" that is actually telling Windows-10 to reboot?
O
Sebastian,
Could you be dealing with a locked screen where the first reboot command is
sending a "ctl-alt-del" that unlocks the screen and the second reboot command
send a second "ctl-alt-del" that is actually telling Windows-10 to reboot?
One way that might be useful to see if that is th
Sebastian,
Could you be dealing with a locked screen where the first reboot command is
sending a "ctl-alt-del" that unlocks the screen and the second reboot command
send a second "ctl-alt-del" that is actually telling Windows-10 to reboot?
One way that might be useful to see if that is th
All the 8 Windows 10 vm's I have will only reboot if I issue the reboot
command twice. They simply don't react on the first reboot command. I
use virsh to issue the command - but I am guessing it is nothing to do
with virsh itself (but I am ready to be corrected on this). Has anybody
else seen
