clareq Posted December 20, 2017 Posted December 20, 2017 I have, in the past, used Windows 10 hyper-v manager to create images. I reloaded my machine recently, reloaded hyper-v manager and tried to start a client. Nothing. It hangs at "starting" - I've left it 24hrs, but nothing. I've stripped out hyper-v manager and re-installed it, double checked it's enabled in the BIOS, which is fully updated and still, no clients. It isn't important, just annoying that I can't fix it. Any ideas?
sted Posted December 20, 2017 Posted December 20, 2017 at some point in the windows 10 version auto checkpointing got enabled turn it off that may help (sorry not got it infront of me and its per vm but its pretty obvious in the options for each vm)
clareq Posted December 20, 2017 Author Posted December 20, 2017 I have two clients - one had autocheckpointing on, one had it off. Changing it made no difference I'm afraid. One of the clients was imported from my previous install of Windows 10, where it worked perfectly, and one was created on this install.
computer_expert Posted December 20, 2017 Posted December 20, 2017 Are you using Windows 10 1709 and sophos intercept x? if so see this: https://community.sophos.com/kb/en-us/127797 I ran into the same problem but ended up going back to 1703 before the above kb was published.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now