citizend13 Posted September 7, 2017 Share Posted September 7, 2017 We had a sudden power outage and the vm restarted in the windows repair menu - can't access keyboard to tell it to start windows normally so it goes into the repair menu and promptly gets stuck there. any ideas on how to get keyboard running while stuck on the repair menu? Quote Link to comment
Squid Posted September 7, 2017 Share Posted September 7, 2017 Is the keyboard on a passed thru Usb controller? Quote Link to comment
SSD Posted September 7, 2017 Share Posted September 7, 2017 Did you try VNC access? Quote Link to comment
citizend13 Posted September 8, 2017 Author Share Posted September 8, 2017 yeah. works fine with VNC access. do I need to remove drivers or something. Not really sure what caused windows repair to show up in the first place. Quote Link to comment
citizend13 Posted September 8, 2017 Author Share Posted September 8, 2017 14 hours ago, Squid said: Is the keyboard on a passed thru Usb controller? I think so. I'll try moving it to different slots to see if it starts working. Quote Link to comment
SSD Posted September 8, 2017 Share Posted September 8, 2017 I was thinking if you ran the Windows repair with VNC access, that it would not attempt a Windows repair the next time. Apparently that didn't work. I don't have any specific suggestion, but do recommend that users confine their VMs disk1.img files to Windows and Apps, with no data stored inside. Instead use mapped array disks or mapped unassigned devices for your data. Backup the VM's disk1.img file from time to time. Then, if something nasty happens with the VM, you can restore a functioning backup and have lost almost nothing. One of the nice things about a VM is the backup is very fast. You are copying a single large file. Good luck unraveling the mystery. Quote Link to comment
citizend13 Posted September 8, 2017 Author Share Posted September 8, 2017 2 minutes ago, bjp999 said: I was thinking if you ran the Windows repair with VNC access, that it would not attempt a Windows repair the next time. Apparently that didn't work. I don't have any specific suggestion, but do recommend that users confine their VMs disk1.img files to Windows and Apps, with no data stored inside. Instead use mapped array disks or mapped unassigned devices for your data. Backup the VM's disk1.img file from time to time. Then, if something nasty happens with the VM, you can restore a functioning backup and have lost almost nothing. One of the nice things about a VM is the backup is very fast. You are copying a single large file. Good luck unraveling the mystery. thanks for the suggestions. We don't have critical data stored on it yet. this is more of a trying it out stage. Quote Link to comment
Jcloud Posted September 29, 2017 Share Posted September 29, 2017 On 9/7/2017 at 7:47 PM, citizend13 said: yeah. works fine with VNC access. do I need to remove drivers or something. Not really sure what caused windows repair to show up in the first place. Your first post mentioned sudden power outage, assuming your computer went down, Windows would have called that an unclean shutdown and at the very least would have ran chkdsk /f /x %BOOTDRIVE% Now if Windows 10 is interrupted trying to boot normally (ie the twirlly circle) this can cause Windows to trip into that Automatic repair. Could also happen if it hiccups on chkdsk and has to redefine the disk volume for boot manager -- I some times run into this issue with HD clones where I've resized the partition, and on first boot of clone tell it to run check disk. I could see it being a similar issue as an image file with your host possibly running a repair on file system in background? Few bits shift around. Just a hypothesis though. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.